This blog is part one of a three-part series on turning process insight into real transformation outcomes.
Read the others at Seeing the Whole Journey: Why Value Stream Thinking Changes Everything and Turning Insight into Action: Why Transformation Fails Without Execution Discipline.
It starts with where you are
Imagine you open the Uber app and enter your destination; you know exactly where you want to go but Uber can’t find your current location.
No starting point means no route. No direction. No ETA. Just guesswork.
You might still get moving but you have no real idea if you’re heading in the right direction.
The Problem with Transformation Without Clarity
This is exactly what happens in organisations that define a future state without first understanding their current state.
Most organisations are not short on ambition. They have strategies, transformation roadmaps, and a clear sense of where they want to go.
Yet many initiatives struggle to deliver value. Projects overrun, benefits are delayed, and outcomes fall short.
In our experience, the issue is rarely the destination. It’s the starting point.
Too often, transformation begins with a future-state vision that isn’t grounded in operational reality.
Assumptions creep in. Complexity is underestimated. And the gap between intent and execution widens.
At Millpond, we see this as fundamental: clarity about the current state is the foundation for meaningful change.
Understanding the Current State: Seeing What’s Really Happening
The current state is not what’s documented – it’s how work actually happens.
Mapping it means taking a clear, structured view of processes, systems, roles, and decisions.
Done well, it creates a shared understanding of reality.
This consistently reveals:
- Bottlenecks slowing delivery
- Embedded workarounds
- Duplication of effort
- Misalignment in roles and responsibilities
These insights rarely surface through documentation alone. They come from engaging with teams and tracing how work really flows.
A common pattern we see is the gap between perception and reality – how people think work happens versus how it really happens. Closing that gap is critical. It replaces assumption with evidence and provides a reliable baseline for decision-making.
Defining the Future State: Turning Ambition into Design
If the current state grounds you, the future state gives direction.
It defines how the organisation needs to operate to achieve its strategic objectives – across processes, capabilities, and outcomes.
A strong future state is:
- Aligned to strategy and customer outcomes
- Realistic within organisational constraints
- Clear enough to guide decisions and delivery
This doesn’t have to mean large-scale transformation. It may be incremental – simplifying a process or improving cycle time – or more significant, involving new technologies or operating models.
But without a credible view of the current state, future design quickly becomes theoretical. It risks solving the wrong problems or introducing change the organisation isn’t ready to deliver.
The value lies in connecting the two.
The Gap: Where Strategy Becomes Action
The gap is the difference between how the organisation operates today and how it needs to operate to succeed.
This is where insight becomes actionable.
Gap analysis makes that difference explicit. It identifies what needs to change – processes, capabilities, technology, or structure – and why.
Without this clarity, organisations tend to default to isolated initiatives that improve parts of the system but don’t address underlying issues.
A well-defined gap, by contrast, enables:
- Focused prioritisation
- Logical sequencing of work
- Early identification of dependencies and risks
- Alignment around what matters most
Put simply, the gap is the bridge between strategy and execution.
Why This Matters: The Benefits
Taking a disciplined approach to current state, future state, and gap analysis delivers real organisational value.
Better Decision-Making
Decisions are grounded in evidence, not opinion. Leaders can clearly see where performance is falling short, where bottlenecks exist, and where intervention will have the greatest impact.
For example, what might initially appear to be a technology problem (e.g. “we need a new system”) is often revealed through mapping to be a process or role issue—such as duplicated approvals or unclear ownership. This avoids costly misdiagnosis and ensures decisions target root causes, not symptoms.
Alignment Across the Organisation
A shared understanding of reality and ambition reduces ambiguity and improves collaboration across teams.
In practice, this means finance, operations, and frontline teams are no longer working from different assumptions about how a process operates. Instead, they are aligned on a single view of “how things actually work” and “what good looks like,” which reduces rework, conflicting priorities, and friction between teams.
Focused Investment
Effort is directed toward the highest-impact areas, rather than spread thinly across competing initiatives.
Organisations often have long lists of improvement ideas, but limited capacity to deliver them. Gap analysis helps cut through this by identifying which changes will materially improve performance—whether that’s reducing cycle time, improving data quality, or eliminating manual effort.
For example, rather than funding multiple small system enhancements, an organisation may identify that simplifying a core process removes the need for several of them entirely.
Clear Roadmaps for Change
Organisations gain a structured, actionable path forward, with defined steps, sequencing, and dependencies.
This moves transformation from a set of aspirations to a practical delivery plan. Dependencies—such as upstream data quality, policy changes, or system constraints—are surfaced early, reducing delivery risk.
Just like with your Uber ride, once you know both your starting point and your destination, the route becomes clear: what comes first, what follows, and where delays or detours might occur.
Greater Likelihood of Successful Transformation
Change grounded in reality is easier to deliver and more likely to achieve intended outcomes.
When the current state is well understood, requirements elicitation becomes significantly more effective. Stakeholders can engage with concrete scenarios rather than abstractions, and proposed changes can be validated against real-world operations.
This reduces the risk of designing solutions that look good on paper but fail in practice—one of the most common causes of transformation underperformance.
Increased Transparency
Mapping makes the organisation visible to itself—surfacing systemic issues and enabling more informed, constructive conversations about improvement, even before any transformation begins.
This often reveals quick wins that can be implemented immediately, such as removing redundant steps, clarifying roles, or automating simple manual tasks within existing systems.
Just as importantly, it creates a shared language for discussing performance and change – shifting conversations from opinion and anecdote to evidence and insight.
Common Pitfalls
While the approach is straightforward, a few common pitfalls can undermine it:
- Jumping straight to solutions
- Over-engineering analysis without adding value
- Designing unrealistic future states
- Treating gap analysis as a one-off activity
The key is balance, enough detail to inform decisions, without losing momentum.
Where this leads next
Understanding the current state is not the end of the exercise. It is the foundation.
It tells you where you are, but not where you should go next or how value should flow when the process is working effectively.
That is the next step.
In the following article, we move from understanding the present to designing the future, exploring how organisations define value and rethink the flow of work across the entire journey.
Because knowing your starting point is essential. But on its own, it does not define the journey.
Not quite what you’re looking for?
Other blogs
of interest
