Delivery control

How old is your rollout status?

· 4 min read · MSDP team

Illustrative exampleThe project, numbers and chart below are fictional. They are not customer results, a forecast or a promised saving.

Every rollout has a plan. Fewer have a plan that is true this morning. The difference is rarely effort; it is how long an update takes to travel from the site to the people deciding what happens next.

The Monday question

A project manager opens the week with one question: where are we? The honest answer is usually "it depends who you ask". The field lead has yesterday's picture. The coordinator has Friday's spreadsheet. The customer has last week's report.

None of them is wrong. Each is looking at a copy, and every copy started ageing the moment it was made.

Example project

A regional team is upgrading 120 sites. Crews report progress by message, a coordinator updates a shared sheet twice a week, and the customer receives a summary every Friday.

What the plan looks like on an ordinary Wednesday

Ask a simple question of that sheet: for each site, how old is the latest update?

More than half the plan is over three days oldFictional example · 120 sites by age of latest status update
Example: sites by age of latest status updateToday: 22 sites. 1–2 days: 31 sites. 3–7 days: 41 sites. Over a week: 26 sites. 10203040 Today: 22 of 120 sites22Today 1–2 days: 31 of 120 sites311–2 days 3–7 days: 41 of 120 sites413–7 days Over a week: 26 of 120 sites26Over a week
Updated in the last two daysThree days or older

67 of 120 sites (56%) carry a status that is at least three days old.

Exact example values
Fictional example: sites by age of latest status update
Age of latest updateSitesShare
Today2218%
1–2 days3126%
3–7 days4134%
Over a week2622%

Nothing in this picture is a failure of the crews. The work may be far ahead of the sheet. That is the problem: decisions about next week's crews, materials and customer commitments are being made on a picture that is partly a week old.

What stale status costs

  • Meetings that exist to collect status. The weekly call becomes the place where the plan is rebuilt by asking each person in turn.
  • Crews sent to the wrong place. A site marked "waiting" was finished on Monday; a site marked "ready" is still blocked.
  • Reports nobody fully trusts. When the customer's view and the team's view differ, time goes into reconciling them.

What changes when status has one home

The fix is less about working harder and more about where an update lives. When the person doing the work records it once, in the same place the planner and the reviewer already look, the age of the plan stops being a question.

  • The Monday question is answered before the meeting starts.
  • The weekly call moves from "where are we?" to "what do we do about it?".
  • The customer summary is a view of the same record, so there is nothing to reconcile.

That is the idea behind MSDP: one shared record of each piece of work, its owner and its progress, kept current by the people closest to it.

Keep reading

Your own project

Ask the same question
of your own rollout.

Bring one project and the questions you need answered. We will agree the scope and measures together before anything is promised.

Get started ↗