A WIP limit for the company
Teams learned work in progress limits from kanban; companies need them more. Count the initiatives that demand leadership attention and shared people, and cap them, typically one to two per senior operator who actually clears blockers. The cap converts prioritization from an abstract exercise into a concrete trade: starting this means pausing that.
The queue is not waste, it is where good ideas wait without taxing anyone. A visible, ranked queue also ends the political pattern where projects launch because saying no felt rude.
Two questions beat weighted scorecards
Weighted scoring models with nine criteria produce arguments about weights. Two questions produce decisions: how much does this move a number we have committed to this year, and what does it cost in the scarcest resource, usually a named person’s time? Plot everything on those two axes and the portfolio sorts itself into obvious yes, obvious no, and a middle that leadership debates for an hour a quarter.
Strategic fit is enforced upstream: if an initiative cannot name the committed number it moves, it does not reach the plot.
The quarterly rebalance and killing well
Each quarter, re-rank the portfolio against the same two questions, promote from the queue into freed capacity, and review every running project against its kill criteria, the conditions written at the commitment gate under which continuing stops making sense. Killing well matters: celebrate the information the project bought, land the people on the next ranked bet within days, and log the decision so the lesson persists. Companies that kill cleanly get truthful midpoint gates, because teams stop defending projects to protect themselves.
The broader market has moved to shorter funding horizons for the same reason: quarterly recommitment keeps portfolios matched to reality at the speed reality now changes.
One portfolio view, ranked and live
The PMO Desk’s portfolio view puts every initiative on one screen with stage, owner, next milestone and status, so the WIP limit is enforceable by sight. Gate records carry the kill criteria written at commitment, and the quarterly rebalance runs off the same live data as the weekly review, no season of spreadsheet archaeology first.
Velora drafts the two question assessment for each queued idea and a closure summary when a project ends, either way. Portfolio discipline sized for a company of ten or two hundred, from the Plus membership.
Frequently asked questions
How many projects should a small company run at once?
Roughly one to two per senior operator who actively clears blockers, counting only initiatives that need shared people and leadership attention. Most SMBs discover their honest number is smaller than their current list.
How do we prioritize without a complex scoring model?
Two questions: impact on a committed number this year, and cost in the scarcest named person’s time. Rank on those and spend debate only on the genuine middle.
When should a project be killed rather than fixed?
When the kill criteria written at its commitment gate are met, when its midpoint gate shows remaining spend exceeds remaining value, or when the quarterly rebalance ranks it below the queue. A logged, blame-free kill is a portfolio win.