It is the week between Christmas and New Year's. The inbox is quiet for a moment, so you open the portfolio list.

And you feel it immediately.

There is the official work, plus a second pile of shadow work that lives in Slack threads, hallway promises, and half-started initiatives. You funded some of it. You never approved it. Yet it is all drawing capacity.

In the last post, we closed the year the honest way: outputs vs. outcomes vs. adoption. This post is the bridge into 2026 that upgrades your PMO governance from reporting to decision-making, with a finance edge that forces realism.

Think of this as Assess in action, with just enough Align to prevent you from walking into January with a fantasy plan.

90 Minutes, One Goal: Make Tradeoffs Visible

A portfolio reset is not a strategy retreat. It is a short governance sprint that answers one question: What are we actually going to do with the capacity we truly have?

Your PMO is the natural home for this because PMO governance exists to:

• Create Visibility That Leaders Trust
• Force Prioritization with Evidence
• Protect Capacity from Quiet Overload
• Keep Funding and Commitments Coherent

Transformation Management is the next layer: once tradeoffs are visible, you can sequence change through a lifecycle, use readiness gates to prevent rework, and fund sustainment so wins stick.

Assumptions (So You Can Run This Immediately)

• You have 3–8 key leaders in the room (Ops, Finance, Tech, PMO)
• You can pull a list of active and in-flight initiatives from 2025
• You can estimate capacity in simple terms (hours per week or FTE slices), not perfect precision

The Sprint Agenda (This Is the Whole Post)

1. Inventory (20 Minutes)

Your first job is to end the we only have 12 projects story.

Do a fast sweep and list:

• Every Initiative On The Official List
• Every Shadow Initiative You Hear About Weekly
• Every Commitment That Keeps Coming Back As A Re-Worded Priority

Capture four fields only:

• Owner
• Estimated Spend (If Known)
• Capacity Draw (FTE, hours/week, or small/medium/large)
• Current State (Not Started, In Progress, Stuck, In Sustainment)

Note: if you cannot name an owner, it is not an initiative. It is a wish.

This step mirrors the year-end close discipline: you cannot govern what you cannot see.

2. Classify (20 Minutes)

Now force the most useful classification your finance partner will actually respect:

• Run — Keeps the business operating this quarter
• Change — Improves a capability, process, or customer outcome
• Technical Debt — Pays down fragility, risk, and rework

Then make the call everyone avoids: Must-Do versus Nice-To-Do.

Use simple rules:

• Must-Do means regulatory, safety, revenue protection, or material risk
• Nice-To-Do means valuable, but not worth breaking the system to do it

This is where governance becomes a decision ecosystem, not a reporting ritual.

3. Gate (20 Minutes)

Before you argue about priority order, run a lightweight readiness check across four lanes:

• People
• Process
• Data
• Tech

You are not doing a full assessment here. You are spotting initiatives that will create rework because they are approved in spirit but not ready in reality.

Ask one question per lane:

• People — Do we have the right roles with time and skill
• Process — Do we know the new way of working end-to-end
• Data — Is ownership, quality, and migration risk understood
• Tech — Is the solution path clear and supportable

If an initiative is red in two or more lanes, it is not high priority. It is high risk.

This is how readiness gates prevent rework before it becomes expensive.

4. Decide (20 Minutes)

Now you earn the reset.

For each initiative, pick one decision:

• Kill — Stop funding and stop pretending
• Pause — Park it with a revisit date and trigger
• Scale — Invest more because outcomes and adoption are proving out
• Sequence — Move it later because capacity is real and dependencies matter

Two governance rules keep this from sliding into debate:

• Assign Decision Owners And Dates
• Log The Decision And The Evidence

If you do not log the decision, you will re-decide it in February.

This is also where the year-end lens pays off: if an initiative cannot show outcomes and adoption, scale should be rare.

5. Lock The Cadence (10 Minutes)

This is the part most teams skip, and it is why priorities drift by week three.

Lock three forums:

• Weekly Execution Forum — Purpose: Remove blockers, manage dependencies, keep commitments
• Monthly Portfolio And Benefits Review — Purpose: Re-rank work, update funding assumptions, verify value
• Quarterly Reset — Purpose: Rebalance Run, Change, and Technical Debt intentionally

This is how your PMO governance becomes a Transformation Management operating system: Assess, Align, Execute, Sustain, on a repeatable rhythm.

One Tool To Include: The One-Page Worksheet

Use this as your single artifact for the sprint. Put it on one page, print it, and do not add extra fields. The constraint is the point.

For each initiative, capture six lines of signal:

• Initiative — The name people recognize in the hallway
• Run / Change / Debt — The category that shapes how you govern it
• Value Hypothesis — The one-sentence reason it exists
• Capacity Needed — The real draw on teams, stated in plain terms
• Readiness Risk — The most likely source of rework (People, Process, Data, Tech)
• Decision — Kill, Pause, Scale, or Sequence, plus an owner and date

How To Use It (Fast)

Use these rules to keep it crisp:

• Value Hypothesis — Write one sentence a CFO can challenge
• Capacity Needed — One developer for six weeks beats medium
• Readiness Risk — Name the lane most likely to create rework (People, Process, Data, Tech)
• Decision — Choose Kill, Pause, Scale, or Sequence, then assign an owner and decision date

Why This Works (And Why It Feels Different In January)

This reset works because it turns a familiar leadership pain into a governed choice:

• You stop treating capacity like an invisible tax
• You make tradeoffs explicit, not emotional
• You identify readiness gaps before execution churn begins
• You create a lifecycle path so change work does not die after go-live

Taken together, this is the bridge from PMO governance to Transformation Management: you are not just running projects, you are managing a portfolio of tradeoffs through a lifecycle that can actually sustain outcomes.

Closing Thoughts

You do not need a bigger portfolio for 2026. You need a smaller set of bets you can actually fund, staff, and sustain.

A 90-minute reset works because it forces the conversation most teams avoid: capacity is real, and tradeoffs are required. When you inventory the shadow work, classify Run versus Change versus Technical Debt, and apply a simple readiness gate, your PMO stops being the place where work is tracked and becomes the place where decisions get made.

Then comes the Transformation Management layer. Once you pick the winners, you can sequence them through a lifecycle, protect adoption, and avoid the January pattern of green status, red outcomes.

Start small:

• Run The 90-Minute Reset With Your Leadership Team
• Use The One-Page Worksheet As The Single Source Of Truth
• Make Four Decisions For Every Initiative: Kill, Pause, Scale, Sequence
• Lock The Cadence: Weekly Execution, Monthly Portfolio And Benefits, Quarterly Reset

If you want a facilitated portfolio reset with your leadership team, Flatirons Consulting can run it in two hours and leave you with a decision log, a capacity-backed plan, and a cadence that holds through Q1.