Strategy that never touches a portfolio decision is a PDF. Alignment is the ongoing work of funding what the strategy claims to want — and starving what it does not.
Line of sight, not a slogan on the charter
Every initiative should be able to complete the sentence: we are doing this so that strategic objective X moves, as shown by measure Y, owned by Z. If the sentence requires a poet, the work is not aligned. It is adjacent and hopeful.
Alignment is not a keyword-stuffing exercise in the business case. 'Supports digital excellence' can be said of a printer refresh. Ask for the mechanism. Which customer journey, which cost line, which risk, which capability? Then ask what you would stop if this is truly the priority.
Strategies change. A portfolio that cannot re-align is loyal to last year's offsite. When the objective moves, run the selection verbs again. Keeping the old mix because the teams are mid-flight is sometimes right — switching costs are real — and sometimes cowardice. Make the switching cost explicit and decide.
Translate down without playing telephone
Strategy becomes portfolio themes, themes become programs and stand-alone projects, projects become outputs, outputs become operational change, change becomes benefits. Each translation loses information. Your job at each altitude is to keep the measure and the owner intact, not to invent a new purpose that is easier to status-report.
Project charters that copy the corporate mission statement and then list a local IT output are how alignment becomes fiction. Write the local contribution. 'This project retires system A so that program B can offer a single client view, which is how we reduce onboarding time — the measure on the strategy map.' Specific or silent. Pick one.
PMO reporting should show the map: objective → investment → status of benefits, not only a wall of project RAGs. A wall of green projects that do not move a strategic measure is a well-run distraction. Nobody should applaud the wall.
Misalignment is a decision, not a surprise
Pet projects, shadow IT, and 'just a small team in marketing' are portfolio leaks. If they consume the same scarce specialists, they are in the portfolio whether the register admits it or not. Bring them into the light or admit you do not have a portfolio.
Sometimes the organisation will fund misaligned work on purpose — a political promise, a founder hobby, a customer exception. Fine. Label it. Hidden misalignment is what wrecks capacity models. Visible exceptions can be managed. Invisible ones become the reason the 'strategic' program is always late.
Your next action when you spot a leak is not a rant in the Slack channel. It is a short paper: capacity taken, benefit claimed, strategic objective affected, recommendation to stop, absorb, or relabel. Then a decision. Alignment without a decision rights is just commentary.
Course complete — what's next
Keep a line of sight from objective to measure to owner to investment. Translate without inventing a new purpose. Treat leaks as portfolio decisions. Strategy is what you fund and what you stop.
You now have the three altitudes — project, program, portfolio — plus benefits after go-live and alignment as a living practice. Use it on one real investment conversation this month. The next courses take the same honesty into enterprise agile change and harder scenario work.