Start from real user needs, design for flow, and evolve deliberately
When organisations start with structure (“these are our teams”) or solutions (“we need a platform / re-org / operating model”), they often end up reinforcing the very problems they’re trying to solve.
Instead, I start by helping teams answer more fundamental questions:
Who are we really creating value for — internally and externally?
What does “value” actually mean in this context?
What needs to be true for value to flow smoothly end-to-end?
Where are teams overloaded, tightly coupled, or unclear about ownership?
An outside-in perspective makes invisible constraints visible — without blame, and without prematurely jumping to fixes.
What typically happens in an engagement
While every engagement is shaped by context, most follow a consistent arc.
Establish shared intent and language
Before diagnosing anything, we align on purpose, outcomes, and constraints.
This creates a common frame of reference — so later conversations about teams, platforms, or flow aren’t driven by personal preference or hierarchy, but by a shared understanding of what matters.
The goal isn’t to “teach” models, but to ensure everyone can reason together using the same concepts.
Make value visible at a system level
We then step back and look at the organisation as a value network:
Who exchanges value with whom?
What currencies are involved (not just money)?
How do different parts of the organisation describe the same relationships?
This often reveals misalignment early — not because people disagree, but because they’ve been optimising different views of the system.
Connect value to real human needs
From there, we explore the value chain through the lens of user needs — both external users and internal ones.
This shifts the conversation from:
“Which team owns what?”
to
“What capabilities are required to meet these needs, reliably and sustainably?”
At this point, gaps in ownership, unclear boundaries, and overloaded teams tend to surface naturally — without needing to “call them out”.
Surface flow constraints and interaction friction
Only once value and needs are visible do we zoom in on team interactions:
Where work gets stuck, handed over, or constantly re-explained
Where teams are forced to collaborate by default rather than by design
Where cognitive load is silently accumulating
These aren’t treated as failures — but as signals about how the system has evolved.
Explore feasible future options
Rather than jumping straight to a re-org or platform decision, we explore credible future interaction patterns:
What would need to change for flow to improve?
Which constraints are structural vs situational?
What decisions would have the biggest impact with the least disruption?
This is where leaders often realise:
“We don’t need a big redesign — we need better decisions, in the right places.”
Turn insight into a flow-aware roadmap
Finally, insights are shaped into a clear set of flow-informed decisions, captured as:
A prioritised flow roadmap (what to address now, next, later)
Explicit Flow Decision Records that explain why a decision was made, not just what was decided
This creates continuity — so learning doesn’t evaporate after the workshops end.
What clients get out of this
Clients typically tell me they leave with:
A shared mental model of how their organisation actually works
Clearer decision boundaries around teams, platforms, and ownership
Reduced dependency debates and fewer “stuck” conversations
A safer path to change that avoids destabilising teams
Language leaders can reuse to explain why change is needed
Most importantly, they gain confidence — not because everything is solved, but because they now know what to act on.