Iteration vs Unresolved Clarity

Transformation is, by design, an iterative process. At the start of most change programmes, the organisation knows what it wants to achieve (if it doesn’t, that’s an entirely different article!). The broad outcomes are generally clear enough: perhaps the organisation wants to improve performance, change culture, reduce cost, modernise systems, introduce AI, or shift the operating model. At that stage, the whole thing is a kaleidoscope of unknown unknowns.

What’s rarely clear at the beginning of a transformation is how to achieve it, so a framework is put in place to make it happen. Project leaders create roadmaps, project teams, and governance protocols. The beginning of a transformation programme is hugely exciting, brimming with optimism and opportunity. At this stage, iteration is needed and helpful for exploring options, challenging assumptions and testing out ideas.

Then, somewhere down the line, something changes. The iteration that moved the work forward stops being helpful and starts sending ideas around in circles.

When iteration is valuable

Iteration is valuable when it reduces uncertainty. You can usually tell this is happening because each cycle produces something new:

• The problem becomes more specific

• Constraints become visible

• Options narrow rather than expand

• Decisions feel easier, not harder

  
  

And so the conversation evolves. People say things like “We didn’t know that before,” and “That changes how we think about it.”

Things are moving and the work is converging. Iteration, in this form, is how organisations think their way through complexity. It’s how to get from an outcome to a workable solution.

When iteration becomes a loop

The difficulty is that iteration doesn’t always look different when it stops working.

The meetings still happen, the governance continues and the language becomes more polished. But now, underneath all the achievements to date, progress has just… stopped.

It starts to feel like Groundhog Day:

• The same points are revisited in slightly different words

• Options reopen that were supposedly closed

• Feedback reflects preference rather than substance

• Increasing layers of governance are introduced to ‘move things along’

At this point, iteration is fostering ambiguity around the things that haven’t been resolved, but are dressed up as though they have. 

What iteration is often hiding

Iteration becomes a loop when something fundamental is missing. That tends to be one of three things:

1. There is no clear shared end state

People are working hard, but they are working towards different versions of ‘done’.

Without a clear picture of what success looks like in practice, iteration continues indefinitely, because there is no point at which anyone can confidently say, this is it, we’re done here, people.

2. The trade-offs haven’t been made

Most meaningful change involves tough choices. Speed vs. risk, cost vs. experience and centralisation vs. autonomy all circle each other. For example, let’s say a company is redesigning its customer support model. Their stated goal is to improve customer experience while reducing cost.

So the team iterates:

• New process maps

• Revised SLAs

• Updated scripts

• Different team structures

Each version gets refined through iterative feedback and adjustments. But the same tension keeps surfacing: should support be fast and human, or efficient and standardised? Faster, more personalised support means higher cost; lower cost means more automation and longer resolution times

Nobody explicitly makes that trade-off, so instead:

• The scripts get tweaked again

• Escalation paths are reworked

• Another pilot is launched

And the work keeps moving, but the core decision about whether cost or experience matters more never lands, so the iteration continues.

Implicit trade-offs generate iteration as a way of avoiding them. The work keeps moving, but the decision never lands.

3. The room isn’t aligned

Different stakeholders are optimising for different outcomes. It may be a genuine lack of alignment or it could be a subtle power play, but either way, iteration becomes negotiation by proxy. Feedback, revisions, and refinements stand in for conversations that haven’t been had directly.

So the work goes round again. And again. And again.

Why governance doesn’t stop iteration

When things seem to be slowing down or stuck, organisations often bring in more governance; more reviews, approvals and checkpoints. They do this because iteration isn’t producing clarity, so something needs to force progress.

The thing is, governance formalises, rather than resolves, ambiguity. If the underlying issue is lack of clarity or alignment, more structure won’t fix it. It will simply make the loop more elaborate.

A simple test

There’s a much faster way to tell whether iteration is doing useful work by asking one simple question:

What will be different on Monday if we land this?

Not in abstract terms, or in strategy decks or executive summaries, but in terms of what people will actually do differently.

• What will stop?

• What will start?

• What will change?

If each iteration makes that answer clearer, the work is progressing. If, after multiple rounds, the answer is still vague or inconsistent, then iteration isn’t the issue. The issue is clarity, alignment, or both.

Why does this matter?

Iteration feels useful and productive. It creates movement without forcing commitment, and it allows organisations to keep going without resolving tension. In complex environments, that can feel safer than making a call, but the cost is significant. Because when iteration stops reducing uncertainty:

• Decisions get delayed

• Governance expands to compensate

• Delivery slows…

…and the original intent of the change becomes harder to recognise. The work doesn’t necessarily fail, but it loses its edge.

How iteration can make decisions easier

Used well, iteration helps organisations navigate complexity and arrive at better solutions. Its role is to clarify the problem, surface the constraints and make decisions easier to take.

If iteration isn’t doing those things, it’s worth asking why, because more iteration won’t help at that point. What’s needed now is something different: making the end state explicit, naming the trade-offs and aligning the room. Only then can iteration move the work forward in the way it’s supposed to do.

If your work keeps iterating but the decision never lands, it’s a clarity problem.

Book a call