Five metrics that predict trouble
Milestone slip: days of movement across the project’s dated commitments this period, the earliest honest signal of drift. Decision latency: how long items wait for a named decision maker, the metric most correlated with quiet stalls. Risk trend: top risk scores rising or falling, direction mattering more than level. Burn versus gate commitment: spend against what the last gate approved, not against a fantasy annual budget. And ownership coverage: the share of milestones, risks and actions with a named owner and date, because unowned work is where projects rot.
None of these require timesheets, story points or capacity models, which is why they survive at SMB scale.
The one page steering pack
Per project: status in one sentence written as a delta, what changed since last review; the milestone picture; the top three risks with asks; the decisions needed, each with a named decider and a date needed by. Portfolio page: every project on one line, status, next milestone, and the single thing it needs. That is the whole pack. It reads in five minutes, and the review spends its time on the decisions column, which is the only column that changes anything.
Curing watermelon reporting
Watermelon status, green outside and red inside, is an incentives problem, not an honesty problem. Cure it structurally: define red, amber and green in writing against observable tests, a missed milestone is amber by definition, a missed gate commitment is red; make amber cost nothing, teams that get help when they flag early learn to flag early; and generate status from the live record, because a report assembled from actual milestones and risks cannot drift far from the truth. The trend in modern reporting practice is exactly this, from authored narratives toward system-generated status with a short human delta on top.
Steering packs that assemble themselves
On the PMO Desk, the steering pack is generated from the live project record: milestones, risks, decisions and gate commitments flow in automatically, and Velora writes the one sentence delta on top. My Day tracks decision latency and overdue items daily, so the five metrics run continuously instead of quarterly.
Print it, send it, or walk the room through it: the pack is always current because it is a view, not a document. Reporting discipline for the price of reading, included from the Plus membership.
Frequently asked questions
What KPIs should a small PMO track?
Milestone slip, decision latency, risk trend, burn against the last gate commitment, and ownership coverage. All five are computable from ordinary project records without timesheets.
How often should project status go to leadership?
Weekly at portfolio level, in one page. Monthly is too slow to steer at SMB speed, and daily reporting burns the trust that makes weekly honest.
How do you stop optimistic status reporting?
Define RAG against observable tests, make amber free to declare, and generate status from live milestones and risks. Optimism cannot survive contact with a system-generated milestone picture.