The minimum viable governance stack
Four artifacts cover a startup’s needs. A portfolio list: every initiative, owner, stage and next milestone, visible to everyone. A one page charter: why this project exists, what done means, what it may spend. A weekly delta review: what changed, what is stuck, what needs a decision, thirty minutes, standing. And a decision log: what was decided, by whom, when, so relitigating stops.
Notice what is absent: methodology mandates, time tracking, resource capacity models, tooling committees. Those earn their place later, if ever. The stack above fits a company of eight and still works at eighty.
What to formalize at each stage
Around ten people, formalize only the portfolio list and the weekly review; charters can be verbal until a project involves outside money. Around thirty people, charters and stage gates become mandatory for anything crossing a team boundary or a meaningful budget line, because hallway alignment has stopped scaling. Around a hundred people, add portfolio prioritization on a quarterly rhythm and a real risk register, because the number of concurrent bets now exceeds what any one leader holds in their head.
The pattern to notice: each layer is added when its absence starts costing more than its overhead, never before. That timing discipline is what separates a lean PMO from a bureaucratic one.
Anti-bureaucracy rules
Three rules keep the function honest. Every artifact fits on one page, and anything longer is an appendix nobody is required to read. Every ritual produces decisions, and a review that ends without any is cancelled next week. And the PMO serves the projects, so if a template slows a team down, the template changes, not the team.
The market has moved this way too: the last decade’s trend in the project management literature is away from heavyweight stage documentation toward outcome gates and continuous reporting, which is exactly the shape a lean PMO takes naturally.
A lean PMO is the PMO Desk’s default shape
The VelorStrategy PMO Desk ships the four artifact stack out of the box: portfolio view, one page charters, stage gates you can pass in one review, and My Day as the standing delta view with decisions and risks called out. Velora drafts each artifact from a sentence, so a founder gets governance at the speed of typing.
Because it lives in the same workspace as the Consulting, Sales, Legal and Tools desks, the projects connect to the proposals, contracts and numbers they touch. One login, from the $19 Plus membership, built for startups and small and midsize companies in the US and globally.
Frequently asked questions
Is a PMO compatible with agile teams?
Yes. A lean PMO governs which bets run and whether they are healthy; agile governs how a team delivers inside a bet. Friction appears only when a PMO tries to dictate delivery mechanics, which the lean model explicitly avoids.
Who should run the PMO in a startup?
Whoever already carries cross-team operating cadence: a chief of staff, an operations lead, or a founder. It is a few hours a week with the right tooling, and rotating it works badly because the value is in the standing rhythm.
When is a startup too early for any PMO?
If the whole company fits in one conversation and runs three or fewer projects, a shared list is enough. The stack starts paying for itself at roughly five concurrent initiatives or the first project with external money attached.