In short
- If a task can be written as a rule, a person adds nothing to it except delay.
- Build the pack from the record, so the hours go on what the committee must decide.
- Challenge, judgement, coaching and the decision stay with a named person.
On Monday morning the PMO analyst opens the tracker and starts writing to project owners. By Wednesday about half have answered. Thursday goes on chasing the rest and copying their answers into slides. The pack goes out late that night, and on Friday someone notices that two of its numbers disagree with the finance sheet.
The following Monday it starts again.
Before I started Lodestar I mapped six roles in a PMO and every handoff between them that was done by hand. Four chores took most of the week: chasing status, assembling the board pack, spotting trouble early and tracking value. All four matter. Very little of the time they took was spent thinking.
What goes wrong
Each chore has the same shape. A fact lives in one place, it is needed in another, and a person carries it across.
Every carry is a copy. The owner knows the date has slipped. That becomes an email, then a row in the tracker, then a bullet on a slide. Each copy takes hours and can go wrong on its own. By the time the board reads the slide, the fact is a week old and has passed through three pairs of hands.
The carrying has a deadline, and the thinking does not. The pack must go out on Thursday. Nobody sets a date for asking whether a green is true, or for sitting with an owner whose plan is drifting. So the work with a deadline fills the week, and the work that needs judgement gets what is left.
Trouble is found when someone has time to look. Early warning done by hand means reading eighty rows to find the one that changed. That reading happens after the pack is out, which is after the meeting it was needed for.
Value is counted once, late. The benefit sits in a business case that nobody opens after approval. It is added up by hand at year end, when the project team has moved on.
The result is a team of experienced people working as couriers. The larger cost is the challenge a PMO exists to give, which never gets its hour.
What good looks like
The fix starts with a sort, and it can be done on paper. Take every recurring task in the PMO's week and put it in one of two piles.
Hand over anything you can write as a rule
Ask of each task: could a new joiner do it from a written instruction, knowing nothing about the programme? Sending the weekly request passes. So does reminding the owner who has not answered, escalating after five days, copying a number into a chart and flagging a milestone that is overdue. These are collection, reminders, escalation, assembly and first-pass checks. A person adds nothing to them except delay.
Let the owner answer once, where they already work
The owner should give the update one time, in plain words, in the mailbox or chat they already have open. The answer should arrive at the record itself, as a proposed change that a person confirms. Publish the reminder and escalation ladder in advance, so that a chase is the rule working and nobody takes it personally.
Build the pack from the record
If the pack and the dashboard read the same numbers, they cannot disagree, and nobody spends Thursday on copy and paste. The hours go on the page that needs a person: what changed, why, and what the committee is being asked to decide. Keep the benefit on the same record as the project, planned against realised, so that value is read every period.
Run the first check before a person looks
Write down the early signs you already know: a milestone overdue, spend running ahead of progress, a green with no report behind it, a risk score above the line. Let rules watch for them every day. The PMO then starts from a short list of exceptions and spends its time on the cause. I wrote about the first of those checks in Green, and wrong.
Keep four things with people
Challenge, judgement, coaching and the decision stay with people. A system can tell you that a claim has no evidence. It takes a person to ask the owner why, to weigh a delay against a budget, to help a new project manager write an honest plan, and to sign. Anything that changes the record should carry a person's name, which is the subject of Agents that act, and the person who signs.
The work with a deadline fills the week, and the work that needs judgement gets what is left.
Expect the handover to decay
A handover like this wears away over a quarter, in four familiar ways.
The shadow tracker comes back. An analyst keeps a private sheet "just to check" the record. Within weeks the pack is built from the sheet again, and the record is one more thing to update. Treat any second copy as a defect in the record, and fix the record.
Reminders turn into noise. A ladder that never reaches anyone senior teaches owners that the third reminder costs nothing. An escalation has to arrive at a named person who acts on it, or it should be removed.
The freed hours fill with more reporting. Someone notices the PMO has time and asks for another weekly report. Decide in advance what the hours are for: a fixed number of project reviews each week, with the owner in the room.
The exception list outgrows its readers. Rules are added and none are retired. When the list reaches eighty lines it is the tracker again. Review the rules each quarter, and drop the ones that never led to a decision.
Put the handover where the plan lives
A sort that lives in a procedure document is kept by the disciplined teams and dropped by the stretched ones. It holds when it is how the system of record works.
That is the split Lodestar is built on. Owners answer by email, or in Microsoft Teams, Slack or WhatsApp. Polaris turns the answer into a proposed change, shown before and after, and nothing changes until a person approves it. Reminders, escalation and the board pack run from the same live model, so the PMO's week starts at the exceptions.

Questions for your next review
- How many hours did the PMO spend last week collecting and copying status, and how many questioning it?
- Which numbers in this pack were typed by hand, and from which source?
- When an owner misses a reporting deadline, what happens next, and where is that written down?
- Which early signs do we check by rule, and which depend on someone noticing?
- Who tracks the benefit of a project after it closes?
A PMO earns its seat by what it questions. Hand the carrying to the system, and keep the people for the questions.
