Skip to main content

For CEOs, CIOs and CTOs

Project Delivery · Digital IT

The project ran over. Everyone can explain why. Nobody can say who decided.

Ask a delivery team what pushed the date and you will get a sensible answer: scope grew, testing took longer, sign-off was slow, the estimate was optimistic. Each answer is true. But every one of them is also a decision, and the decision is rarely written down.

Most overrun reviews list causes. This piece looks at what sits behind each cause: a decision, a person who made it (or didn't), and a record that either exists or doesn't. In an October poll on our LinkedIn page we asked what caused your last IT project to run over and offered four answers: scope grew, testing took longer, sign-off was slow, and the estimate was never realistic. Those four are the structure of this article.

1. The Status Meeting Where Nobody Could Say Why

Scenario — a composite of patterns common in delivery reviews

A programme to replace an internal system was planned for 12 weeks. At week 9, the sponsor asks why go-live has moved to week 16. The project manager gives a clear account: a late scope addition, a shortened test window, two weeks waiting for an approval.

The sponsor asks one more question: “Who agreed to each of those?” The room goes quiet. Each change was agreed in a call, a chat message or a conversation in a corridor. Nobody is blamed, and nobody can reconstruct the order, the reasons or who accepted the risk.

The delay wasn't the surprise. The missing record was.

This isn't a sign of a weak team. It's what happens by default when plans change faster than the record of why they changed.

“Projects don't run over. Decisions do.”

2. Four Common Causes, and the Decision Behind Each

Each familiar cause of an overrun is a decision that was taken, or one that was never taken. Naming the decision is the first step to owning it.

Scope grewSomeone accepted a change without re-planning the date or the budget.The sponsor or product owner, with the project manager recording what it costs in time.
Testing took longerSomeone set the test window before the build was stable, or shortened it to hold the date.The delivery lead, with the person accountable for quality agreeing to any cut.
Sign-off was slowNobody agreed how long an approval may take, or who steps in when it stalls.The business owner who signs, with an agreed time limit.
The estimate was unrealisticAn estimate was accepted as a commitment without its assumptions being written down.The person who signed the estimate, with the assumptions listed beside it.

None of these decisions is unreasonable on its own. The trouble is that they accumulate with no record of the trade-off each one accepted. It's the same pattern as savings that stay on paper after a migration: the plan was sound, and nobody recorded the point where it changed.

3. The Decision Log

Decision Log (n.)

A short, dated record of each decision that changed the plan: what was decided, who decided it, and where it is written down.

It isn't a project plan or a risk register. It answers one question: what changed, and who agreed? A decision log takes a minute to update and saves hours at the review, because the review starts from facts instead of memory.

“The decision is easy to see. The record is what goes missing.”

4. Why Your Current Project Reporting Doesn't Catch This

Status reports track progress: percent complete, budget used, risks open, milestones met. They tell you where the date is, not why it moved. A project can look healthy on every one of those measures and still turn red in a single meeting.

The questions that catch it are ownership questions. It's the same gap as a KPI that stays green while the business doesn't improve: the report is accurate, and what it means has drifted.

The three-question overrun audit
  1. Which decision moved the date?
  2. Who made it?
  3. Where is it written down?

Ask these about the last date change on your most important project. If answering takes more than a minute, that isn't a planning problem. It's a recording gap, and it's cheaper to close before the next project than during its review.

5. A 30-Minute Exercise: Rebuild the Story of Your Last Overrun

You don't need a new tool. Take the most recent project that moved its date, and do this:

  1. List every date change. From the original plan to today, one line for each time the delivery date moved.
  2. Find the decision behind each one. Scope accepted, test window cut, approval waited on, estimate revised. If the team can't agree on what the decision was, mark it as unclear.
  3. Write who decided and where it is recorded. A name, not a team. A ticket, document or email, not “we discussed it”.
  4. Mark anything without a name or a record as “unrecorded”. Look at which kind of decision goes missing most often. That is where the log should start.

The aim isn't to assign blame. It's to see which decisions the project makes without leaving a trace.

6. What a Project That Can Explain Itself Looks Like

1

Every date change has a decision behind it

The plan moves only when someone decides, and the change states what it costs in time and budget.

2

Every decision has a name

Not a team or a meeting. One person who accepted the trade-off on the project's behalf.

3

Every decision is written where the team looks

In the ticket, plan or log the team already uses, not in a side conversation.

4

The log is read at every review

Status meetings start from what changed since last time, not only from percent complete.

None of this adds process. It changes what a change is allowed to skip.

7. The 5-Question Self-Assessment

Run these against your last project that moved its date. Three or more answers that aren't a clear yes means part of your delivery story is still reconstructed after the fact.

#QuestionYes / No / Unsure
1Can you name the decision behind every change to the delivery date?
2Is there a named person, not a team, for each of those decisions?
3Is each decision written down where the team can find it?
4Do status reviews start from “what changed” rather than only “percent complete”?
5Are approval times and test windows agreed before the work begins?
5 × YesYour projects can explain themselves — keep the log current.
3–4 × YesFoundations exist — the gaps are specific and closeable.
1–2 × YesPart of your delivery story is reconstructed after the fact.
0 × YesTreat your next overrun review as the first draft of the log.

8. Three Questions We Hear Most Often

Isn't this just more paperwork?

It's one line per decision: the date, the decision, who decided and where it is written. A log that takes more than a minute to update won't be kept, so keep it that small. The test is whether the next review can start from the log instead of from memory.

What if the decision was made by a committee?

Record the committee, and also the one person who is accountable for the outcome. A committee can recommend, but a project needs a named person who accepted the trade-off, so that someone can be asked about it later.

Does this apply to AI and automation projects?

Yes, and more so. Faster delivery means decisions are made faster, and fewer of them are recorded. It's the ownership question we raised in who owns the risk when AI acts: everyone can explain their part, and nobody owns the outcome.

The Question for Your Next Project Review

Pick the project that most recently moved its date and ask one thing: which decision moved it, and where is it written down? If the answer takes more than a minute, the cause is still a story, not a record.

“A project can explain itself when every change has a name and a record.”

Related service: Digital IT Solutions

Facing similar ServiceNow challenges?

Get a free ServiceNow assessment and understand where your platform may be losing value.

No spam. No sales pressure. Only actionable insights.