Every AI project has a moment — usually somewhere between the enthusiastic kick-off workshop and the first sprint — where the organisation has to make a real decision.

Not the budget approval. Not the vendor selection. Not the architecture review. Those are necessary, but none of them are the decision that determines whether the project actually succeeds.

The real decision is the Go/No-Go gate at the close of Phase 1.

Most AI projects don't fail because the technology didn't work. They fail because nobody asked the right questions before the project started.

When a technology program starts showing signs of trouble, the instinct is to act fast. But speed without structure often makes things worse—more meetings, more pressure, more resources thrown at a problem nobody has actually diagnosed yet.

Losing commercial control of a technology program is common. It happens gradually, often with good intentions, and frequently goes unacknowledged until leverage is significantly weakened. Restoring it does not require confrontation or crisis — it requires a structured sequence that reestablishes clarity, accountability, and commercial authority one phase at a time.

When a technology project is failing, speed matters—but clarity matters more.

When a technology project starts to fail, urgency takes over. Deadlines are missed. Costs rise. Pressure mounts. Leadership wants answers—and teams want direction.