A programme is a chain of decisions.

The schedule shows tasks completed. It does not show decisions waiting. That is why a programme can report green for weeks and arrive at commissioning late.

Most of us were taught to see a programme as a stack of tasks. A Gantt chart, a work breakdown, start dates and end dates, float. Keep it. You will need it. But hold a second lens beside it, because it shows what the schedule cannot.

A programme is a chain of decisions. Tasks get done, and they are easy to track: finished or not, reported on a Friday. Decisions are different. They sit. They get passed between people, or left for someone to take responsibility. They sit in the gap between the person who knows the answer and the person who has the authority to make it official. And as they sit, they age.

Donald Reinertsen took the mathematics of queues, the same maths that describes traffic and call centres, and applied it to management decisions. A decision delayed by a week does not cost a week. It costs the week, plus everything downstream that waited, plus the rework when the decision finally lands and collides with the workarounds that filled the gap, plus the management time spent clearing up afterwards. The cost compounds.

None of that shows in the weekly report. The report shows tasks done. The decisions that were not made in time are invisible, right up until they appear six weeks later as a schedule revised and a programme director sitting in a review wondering what happened.

What happened was the gap. Compounding quietly until the bill arrived.

The lens changes what you do when a programme slides. If a programme is a stack of tasks, you add supervision, tighten targets and push harder on the people doing the work. That is the usual response, and it rarely helps, because the people at the workface are often already doing everything they can. What is in the way sits above them, in the decision chain. Pushing harder at the bottom when the block is at the top produces effort without recovery.

If a programme is a chain of decisions, you ask different questions. Where are decisions sitting? Who holds them? How old are they? Is the system built to move decisions quickly, or to move information correctly? Those are not the same thing, and most complex programmes were built for the second when they needed the first.

Which decisions on your programme are older than a week, and who is holding them?