Service · Diagnostic
Make the current system visible—before deciding what to change.
A focused diagnostic engagement that shows leaders where value is waiting, why, and what to work on first.
The problem
You can't fix what you can't see.
Most delivery friction sits between teams—in queues, handoffs, dependencies and decision delays—not inside them. Standard status reports show what teams are doing, but not where the system is losing time. Without a clear picture of the whole flow, improvement effort defaults to whichever framework is loudest.
Who this is for
Ideal client
- →Chief Product, Technology or Information Officers
- →Transformation Directors and Programme leaders
- →Heads of Product, Engineering or Delivery
- →Enterprise Agile coaches inheriting complex environments
Warning signs
Signals this may help
- ◆Delivery feels slower than it should, but no one can point to why
- ◆Teams appear busy while roadmap commitments keep slipping
- ◆Improvements from previous transformations have quietly faded
- ◆Leaders lack a shared view of where value is getting stuck
What's included
The engagement
- ◇Value stream mapping across strategy → discovery → delivery → outcomes
- ◇Analysis of work-in-progress, work-item age and throughput
- ◇Dependency and handoff mapping across teams
- ◇Decision-making and governance latency review
- ◇Interviews with leaders, coaches, product and engineering
- ◇A written findings report with prioritised constraints
- ◇A leadership working session to align on what to change first
- ◇Recommended experiments and next steps
The approach
How the work unfolds
- 01
Frame
Agree the value stream in scope, key questions and success criteria for the diagnostic.
- 02
Observe
Follow the work. Interview roles across the stream. Gather evidence from tooling and delivery data.
- 03
Synthesise
Map the system. Identify the largest sources of delay and lost value with the evidence to support them.
- 04
Decide
A working session with leaders to agree the first constraint to address and how progress will be measured.
Expected outcomes
Not guarantees — direction of change
Every organisation is different. These are the outcomes typically observed when the work is done well.
- ✓A shared, evidence-based view of how value actually flows through the system
- ✓Prioritised list of the constraints most likely to be limiting delivery
- ✓Clarity on which experiments to run first and what to measure
- ✓A common language for leaders and teams to talk about the system
- ✓Confidence to say no to improvement effort that won't move the needle
Engagement options
Sensible ways to work together
Focused diagnostic
Typically 3–5 weeks. One value stream, one clear question, a written report and leadership working session.
Multi-stream diagnostic
A larger review across several value streams or tribes. Duration and shape agreed in scoping.
Diagnostic + follow-on coaching
The diagnostic feeds directly into a coaching engagement to run the first experiments.
Duration, scope and pricing are agreed in a scoping conversation. No fixed enterprise pricing published.
FAQ
Frequently asked
Is this a maturity assessment?+
No. There is no maturity score. The output is a description of the current system—where value flows well, where it doesn't, and why—supported by evidence.
How much of my leaders' time will this take?+
Interviews are typically 45–60 minutes per leader, plus one working session at the end. Most of the effort sits with me, not your team.
Do you use a specific framework?+
No prescriptive framework rollout. The work draws on systems thinking, flow measurement, product operating principles and enterprise coaching—applied to your context.
Will this recommend making people redundant?+
The work is about system conditions—structures, policies, WIP, dependencies, decisions. Recommendations focus on what leaders control, not headcount.
Ready to start the conversation?
A scoping call is the fastest way to know if this is the right fit.