I was recently talking to a programme director about go-live readiness. The programme was a CRM and billing implementation with regulatory requirements, working to a fixed go-live date. The date couldn't move. Everything else would have to.
Inside the room, outside the room
At Performance Radar, we talk a lot about being outside the room. It's a different place to stand.
Inside the room, you have a stake. You've been living the programme for over a year. You want it to succeed, and you will it to succeed with every fibre. That commitment is what gets programmes over the line. It's also what makes it hard to see when the line is moving.
What the evidence said
SIT exit had been delayed several times. When we asked about the recovery plan, the answer was that the slippage would be absorbed through UAT.
We then went through the go-live readiness criteria:
- Training: none delivered. The training material hadn't been created yet.
- Change impact assessment: not complete.
- Day 1 users: the SMEs who had been involved in UAT, not the wider user base.
- BAU organisation: not in place, and not trained.
None of these is unusual on its own. Together, they describe a programme where the technology might be ready on the day but the organisation isn't. Absorbing a late SIT into UAT doesn't recover time. It takes it from the weeks the business needs to get itself ready. And when your Day 1 users are the SMEs who helped test the system, go-live will look smoother than it really is, right up until everyone else logs in.
The confidence question
The programme director was very experienced. He understood the solution and he understood the industry. So I asked him directly: what's your confidence level?
"Yes, we will go live."
Then came a nested IF statement, five levels deep. If this lands. If that holds. If the other gets resolved in time.
Readiness was being reported as amber. So I asked: how many ifs would it take for it to be red?
Why the ifs matter
He wasn't being dishonest, and none of his conditions was unreasonable. That's the trap. Inside the room, each condition is judged on its own merits, and each one looks achievable.
Outside the room, you see them compound. Give five independent conditions an 80% chance each, and the odds of all five holding fall to roughly one in three. That's not amber.
A fixed date also changes the question. When the date can't move, the question isn't "will we go live?" It's "what will we go live with, and can the business run on it from Day 1?"
Questions worth asking before your go-live
- Ask for confidence, then count the ifs. If the answer needs conditions, list them and ask who owns each one.
- Ask what would make it red. If nobody can say, the RAG status isn't measuring anything.
- Separate technical readiness from business readiness. Training, change impact, BAU ownership and real Day 1 users are go-live criteria, not follow-on tasks.
- Treat "absorbed in the next phase" as a risk, not a plan. Ask what it displaces.
- On a fixed date, know your levers early. If time can't move, scope and readiness have to. Decide which before the decision is made for you.
The difference
Being outside the room isn't about knowing more than the people inside it. It's about having nothing invested in the answer, and so being free to say what the evidence shows.
Performance Radar provides independent delivery assurance for technology leaders running complex programmes. To discuss your situation, schedule a 15-minute introduction.