The Strategy That Falls Apart: Why Organisations Still Think Inside-Out
Most organisations genuinely believe they are taking an outside-in approach. Strategies are full of customer insights, market movements, competitive analyses, and ambitious visions. But when implementation begins, everything slows down. Not because people resist change or don’t care; in fact, most teams care deeply and work incredibly hard. The real issue is quieter: the organisation plans outside-in but executes inside-out.
Why this happens more often than leaders realise
In almost every company I work with, strategy is built with the external world in mind; customers, competitors, regulators, partners, markets. But when the work hits the organisation, it must run through existing hierarchies, functional silos, and historical team boundaries that were designed for a different era. This results in:
Teams optimising for their piece of the puzzle, not the outcome.
Dependencies piling up because no team owns the end-to-end outcome.
Everyone doing their best… but pulling in slightly different directions.
Strategy “failing” not because it was wrong, but because the structure wasn’t designed to execute it.
Essentially: your structure still reflects yesterday’s constraints, even when your strategy reflects tomorrow’s opportunities.
Where inside-out thinking shows up
Inside-out thinking isn’t an attitude problem, it’s a systems problem. Common signs include:
Mapping systems instead of mapping users
Starting with the org chart instead of needs
Optimising internal handoffs
Designing around specialists rather than outcomes
Prioritising internal efficiency over external progress
Teams don’t intend to think this way, they’re shaped by the structure they operate in. In the past, organisations had long periods of “normal” where stable structures made sense. But today, change is constant. Digital products never stop evolving and AI is accelerating expectations further. Static structures can't keep up with dynamic needs.
The fix: align structure to user needs before you optimise anything else
This is where User Needs Mapping comes in. It creates the missing connection between strategic intent and team design by asking:
Who are the users?
What do they need?
What capabilities are required to meet those needs?
Where do those capabilities live today?
How might we design boundaries that support autonomy and flow?
When you design from the outside in, everything sharpens; team priorities become clearer, decision rights become obvious. Flow accelerates because teams finally own coherent slices of user-centred value.
The organisations that win are the ones whose structure can absorb change
This is the uncomfortable truth: strategy cannot succeed if the organisation delivering it was designed for a different world. In times of accelerating complexity, competitive pressure, and AI-driven disruption, the organisations that thrive will be those whose shape matches the world they operate in.
You don’t need to begin with a transformation, an operating model redesign, or a new set of processes. Start small and start where clarity matters most:
Ask “Who is this serving?” in your next planning meeting.
Define needs in outcome language rather than feature language.
Visualise the disconnect between needs, capabilities, and teams.
Look for places where multiple teams contribute to a single user outcome.
Notice where work cuts across boundaries the organisation never designed for.
These small shifts create the conditions for much bigger organisational change. When you start with users and design from the outside-in, your structure becomes a strategic asset, not a historical artefact.
If you're seeing the signs of inside-out thinking in your organisation and want to explore these ideas further, I’m always happy to have a conversation. Feel free to DM me.
