How much discovery is “just enough”?

One of the most persistent challenges in service design is not whether to explore a problem — but how far to go.

At a leadership level, this is more than a question of methodology. It is a question of risk, organisational maturity, and decision integrity.

In my work with organisations at different stages of service transformation there is a pattern:

The lower an organisation’s maturity, the less visible its real problems.

Symptoms present themselves loudly. Meanwhile, root causes remain obscured and fragmented across teams, buried in legacy processes, or misinterpreted through conflicting narratives.

This creates a tension:

• Explore too little, and you make poorly informed decisions.

• Explore too much, and you delay value, dilute focus, and exhaust teams.

So how do we determine what “just enough” looks like at an organisational level?

Reframing discovery as a risk management activity

At a strategic level, discovery should not be treated as an open-ended research phase. It should be governed as a risk-reduction mechanism.

The critical question becomes:

What is the risk of acting without deeper understanding?

• High risk contexts (e.g. regulatory exposure, high-cost transformation, reputational impact) demand deeper, more rigorous exploration

• Lower risk initiatives justify lighter, faster approaches

This framing enables leaders to calibrate effort proportionately, rather than defaulting to either over-analysis or premature execution.

Aligning depth of exploration to organisational maturity

Discovery is not one-size-fits-all. Its depth should be explicitly aligned to the organisation’s digital maturity:

• Low maturity organisations
  Require significant effort to even define the problem space.
  Expect ambiguity, conflicting perspectives, and hidden dependencies.

• Medium maturity organisations
  Benefit from targeted exploration, building on existing insight while addressing specific knowledge gaps.

• High maturity organisations
  Already possess strong service understanding. The focus shifts to alignment, prioritisation, and orchestration across the service ecosystem.

For leaders, this means designing discovery as a capability, not just a phase, and one that evolves alongside organisational maturity.

Establishing a minimum viable understanding

In practice, exploration should continue until three fundamental dimensions are understood:

1. Who is affected

2. What is actually happening (end-to-end reality, not assumptions)

3. What constraints shape the problem (organisational, technical, regulatory, cultural)

If any of these remain unclear, decision-making remains speculative.

This “minimum viable understanding” acts as a governance checkpoint, ensuring that exploration is purposeful, not performative.

Defining an evidence threshold for decision-making

Strategic decisions require more than isolated insights. They require confidence grounded in evidence.

Leaders should ask:

Do we have sufficient evidence that this problem is real, shared, and solvable?

This threshold is typically reached when:

• Patterns emerge consistently across qualitative and quantitative data

• Multiple stakeholders recognise the same underlying issues

• Signals converge rather than contradict

Without this, organisations risk investing in symptoms rather than systemic change.

Measuring progress through alignment, not artefacts

A common failure in discovery is over-indexing on outputs, journey maps, reports and frameworks, rather than outcomes.

At a leadership level, the true measure of “enough” is shared understanding.

You are ready to move forward when:

• Teams describe the current state consistently

• The problem definition is stable and uncontested

• Decisions feel grounded in evidence rather than opinion

In other words:

Clarity and alignment, not documentation, are the indicators of readiness.

Recognising when you haven’t done enough

There are clear signals that further exploration is required.

These are not minor inefficiencies, they are strategic risks:

• Stakeholders describe the same problem in fundamentally different ways

• Ownership across the service is unclear or fragmented

• The problem definition shifts repeatedly in decision forums

• Data contradicts anecdotal understanding

• Symptoms are repeatedly mistaken for root causes

These conditions indicate structural ambiguity, not just incomplete research and justify deeper investigation.

A leadership heuristic for “just enough”

At an executive level, the goal is not exhaustive understanding. It is decision-quality understanding.

A practical rule of thumb:

Do enough discovery to reduce meaningful risk and expose the real problem — then stop when additional insight no longer changes your decisions.

Beyond that point, further exploration becomes a diminishing return.

From exploration to action

Ultimately, the role of leadership is to balance inquiry with momentum.

Too little exploration leads to misaligned investments and systemic failure.
Too much leads to inertia and lost opportunity.

“Just enough” is not a fixed point. It is a strategic judgement, shaped by risk, maturity, and the consequences of being wrong.

The organisations that get this right are not those that explore the most but those that know when to stop exploring and start experimenting.