IT Portfolio Management
Teaching a team to capture demand, rank it and defend the answer.
The discipline taught to the people who have to run it every month.
Delivery. Usually alongside or after a portfolio engagement.
PMO, IT finance, business engagement and architecture teams who own the process after we leave.
A portfolio process exists on paper, or an engagement set one up and it is already drifting back to the loudest sponsor.
What we teach
Demand capture
Getting every request into one place in a consistent shape, including the informal asks and the work already underway.
Sizing and costing
Enough estimate to rank against, including what it costs to run once it exists — without pretending to a precision nobody has yet.
Force ranking
Weighing value, risk, dependency and effort together, and recording the reasoning so the ranking survives being questioned.
Scenario planning
Building the portfolio at three funding levels, which is what turns a budget argument into a trade-off conversation.
Capacity
Testing the plan against real delivery capacity, including the people already committed to keeping the lights on.
Running the forum
Who attends, what they decide, what gets recorded — and how to hold a decision when the sponsor who lost comes back.
Reporting
Telling leadership what changed, what slipped and what was traded, in one page they will actually read.
Keeping it current
The monthly rhythm that stops a portfolio decaying into a spreadsheet nobody has opened since planning.
Month three, not month one.
Portfolio processes rarely fail at design. They fail when the forum is skipped and an urgent request goes straight to delivery.
- 01A list exists
Built once, in a spreadsheet, usually for a budget round.
- 02Ranked with reasoning
Value, risk, dependency and effort weighed together, with the thinking recorded.
- 03Tested against capacity
Including the people already committed to keeping the lights on.
- 04A monthly rhythm
Intake, review and one page of reporting that leadership actually reads.
We teach the people who have to run the portfolio every month: demand capture, sizing and costing, force ranking with the reasoning recorded, scenario planning, capacity testing, and the forum where a decision has to hold.
The skill is holding the line, not building the list
Anyone can build a ranked list once. What takes practice is running the conversation where two sponsors both believe theirs is first, and coming out with a decision that holds — which is mostly about having the reasoning written down before the meeting.
Scenario planning changes the argument
Show leadership the portfolio at three funding levels and the question stops being whose project matters. It becomes what the business is willing to give up, which is a question executives can actually answer.
It is a rhythm, not an event
Monthly intake, monthly review, monthly reporting. Teams that treat it as an annual exercise rebuild the list every year and defend it never.
What you keep
The code and the data·Your existing relationships·Approval and control·The ability to stop·The off switchWhat that means
Start with a 45-minute briefing.
No pitch. We’ll map your situation against what actually works and tell you honestly where to start.