If you have a preferred direction — a working investment thesis about what kind of capability investment is right for your organisation and roughly what it should address — but are building the evidence and alignment to commit to it confidently, this is the stage where most capability investments either gain or lose momentum.

The risk at this stage is rarely about choosing the wrong option. It is about moving forward with something that others do not fully believe in. A technically sound investment case that has not brought the right people with it will stall — not because it is wrong, but because trust in it is uneven.

This is also the stage where the investment case needs to be stress-tested against the scrutiny it will face from finance, the board, and the investment decision-makers who need to approve it. The question is not just whether the direction is right, but whether it is expressed in a way that the people who need to say yes can actually evaluate and defend.

Why the Build Confidence stage?

Decisions move into this stage when the direction of travel is becoming clearer but confidence around it is uneven. There is a preferred approach, short-listed options, or a working plan — but what is less certain is whether that direction will be understood, trusted, and supported by everyone who needs to stand behind it.

The conditions that characterise this stage are: a diagnosis that has been tested and broadly accepted, a solution direction that has been identified, and a growing recognition that the investment case needs to survive contact with finance, the board, and investment decision-makers who have not been through the diagnostic journey. The gap between internal conviction and external credibility is where most capability investments stall at this stage — not because the direction is wrong, but because the case for it has not yet been built in a way that others can evaluate and defend.

The practitioners who navigate this stage well are those who actively sought peer validation of their investment thesis before presenting it formally — and who used that challenge to sharpen the case rather than simply confirm it.

Decisions typically move into later stages when certain conditions begin to show up:

• a clearly defined problem,
• a shared sense of what success looks like,
• visible senior sponsorship,
• identifiable trade-offs,
• and some form of commitment pressure (time, budget, reputation, or dependency).

Based on your responses, those signals don’t yet appear to be consistently present. That doesn’t mean a decision isn’t forming — only that it hasn’t yet solidified into something that most stakeholders would recognise as a concrete project requiring sustained commitment of time, attention, or capital.

In practice, this usually means that while there is intent or concern, key elements of a well-framed decision are still emerging: the real alternatives may not yet be clear, consequences are still being explored, uncertainty remains high, and it’s not yet obvious what would be hard to reverse later.

This is a common — and often sensible — position in complex contexts, where acting too early can be riskier than waiting until the decision is framed clearly enough for others to engage with it confidently.

Teams at this stage often underestimate how much genuine alignment matters — and how different counterfeit agreement looks from the real thing until implementation begins.

Common patterns include:

• Mistaking nominal agreement for genuine commitment — stakeholders who nod in meetings but hedge in practice, comply without owning, or disengage when conditions change
• Securing investment decision-maker approval without building alignment across the functional leads, operational teams, and IT partners who will live with the decision daily
• Assuming that a sound analysis will automatically lead to buy-in — without recognising that finance, IT, and operational leadership are often asking fundamentally different questions
• Discovering late that key stakeholders have concerns that were never surfaced — because the conversations happened too late, in the wrong sequence, or without the right framing
• Building a business case that is technically accurate but not legible to investment decision-makers — particularly around ROI, sequencing, and what needs to be true before the investment is likely to deliver
• Overstating the case in ways that secure approval but create credibility problems later when reality diverges from the projection

When these gaps surface, progress slows or stalls — not because the investment direction is wrong, but because the confidence and alignment behind it were thinner than they appeared.