The morning I learned my portfolio existed only in the boardroom
Ninety days after 14 executives approved our portfolio for the year, I ran a small experiment. I asked 20 department managers, the people who assign the analysts, approve the timesheets, and decide what their teams work on each week, to name our top three projects.
Two of them could.
The other 18 were not disengaged. Several named projects that had been cut in the approval meeting. Four named work their own executive had personally voted against. Every one of them was making resourcing decisions every day based on a portfolio that no longer existed.
I had treated the approval meeting as the finish line. It was the starting line. This issue is about the discipline that turns an approved list into a shared commitment, which is the part of the portfolio definition that most PMOs skip because it does not feel like PMO work.
Why does executive approval not produce buy-in?
Three reasons, and none of them is a communication skills problem.
First, approval happens at one altitude and work happens at another. Executives approve outcomes. Managers allocate people. The translation between the two, what this priority means for your team on Monday, is nobody's job, so it does not happen.
Second, the PMO communicates once, at the moment of least relevance. The roadmap goes out the week it is approved, before anyone has a decision to make against it. By the time a manager faces a real trade-off in March, the email is four months old and the priorities have shifted twice.
Third, the priorities are invisible at the point of request. When a sponsor submits a new project, nothing in the intake form shows them where it would land against the current top ten. So every request arrives as if it were the only one, and every approval feels free.
Better slides do not fix any of this. It gets fixed by treating communication and buy-in as a portfolio discipline with its own cadence, owners, and measurements, the same way you treat prioritization or capacity.
Five disciplines that turn an approved portfolio into a followed one
Discipline 1. Write the portfolio on one page, in outcomes, including what you said no to. Not a deck. One page: the top ten by rank, the business outcome each serves, the three to five things you decided not to do this year, and the date it was last changed. The "not doing" list is the part people read most carefully, because it is the part that affects their week. If your portfolio cannot fit on one page, the problem is upstream of communication.
Discipline 2. Run the name-three test 30 days after approval, in every function. Ask ten to twenty managers, in person or by a two-question form, to name the top three projects and the reason behind number one. Record the score. Mine was 2 of 20. Any score under half means the portfolio has not left the room yet, and every capacity conflict you are about to have traces back to that number.
Discipline 3. Make sponsors the voice, and give each function its own translation. The PMO writes the message; the executive who voted for it delivers it, in their own words, to their own people. Each function gets three lines: what this means for your team, what you will be asked to stop or delay, and who to call when a conflict comes up. The month our CIO said "we are not doing the reporting rebuild this year" in his own staff meeting, requests for reporting resources dropped to near zero. The PMO had said the same thing in an email four times.
Discipline 4. Publish every priority change within a week, with the reason. Priorities move. That is healthy. Silent movement is what destroys trust, because managers find out from a vendor or a resourcing conflict instead of from you. A short monthly note, what changed, why, and what it means for capacity, does more for buy-in than any kickoff presentation, because it proves the portfolio is alive.
Discipline 5. Put the ranked list where requests are made. The intake form shows the current top ten. Every new request answers one question: which strategic outcome does this serve, and which ranked item should it displace? Sponsors who can see the line before they ask write better requests, and about a third stop asking.
Where Smartsheet fits
Four of these five disciplines fail the moment they depend on someone remembering to send an email. We run ours from a single portfolio register in Smartsheet: one row per initiative, with rank, outcome, sponsor, status, and a last-changed date.
A published dashboard shows the one-page portfolio to anyone in the company with a link, always current, no version control. An automated workflow watches the rank column and sends the sponsor and the affected managers a note the day a rank changes, with the reason pulled from the register.
The intake form reads from the same sheet, so the ranked list sits directly above the request fields. The monthly "what changed" note becomes a filtered report of everything with a change date in the last 30 days, which takes about ten minutes to write instead of an afternoon.
What changed after the first quarter
The name-three score went from 2 of 20 to 15 of 20 in two quarters. Capacity conflicts fell, not because we had more people, but because managers stopped assigning them to work that had been cut. Intake volume dropped by about a third and the requests that arrived were written against the outcomes, which made the prioritization meeting shorter and less political. And the executives noticed something they had not expected: their own decisions started holding, because the organization could finally see them.
Your one action for next week
Pick five managers outside your PMO. Ask each to name the top three projects in the portfolio and the reason behind the first one. Write down the score. If it is under three of five, the portfolio you approved is not the one your organization is running, and that is the first thing to fix before 2027 planning locks.
If you want a second set of eyes on how your portfolio moves from approval to execution, that is what the Assess step of the Vision2Value Framework does. The PMO Value Blueprint is a focused 4 to 8 week engagement that looks at exactly this gap, often with a Smartsheet pilot so the fix is live before we leave.
PS. If building this kind of portfolio capability is where your own career is heading, the PMI-PMOCP credential now tests for it. Details on the next cohort at pmoevolution.com/training/pmocp.
Click the image to book a call
