Whatever the delivery teams use — Jira, Azure DevOps, Microsoft Project, Planner, Smartsheet, Monday.com — the transformation view is assembled from live data rather than a monthly collection exercise that is stale before it is read.
Weighted strategic and risk factors with published value ranges, so a score means the same thing across workstreams that are nothing alike. When you stop a program, the reasoning is on record, and the same criteria were demonstrably applied to the ones you kept.
Build competing scenarios against one ceiling, see the Pareto-optimal set of trade-offs, check the survivors against people's free capacity, then publish the decision onto every project with the numbers baselined at the moment you made it.
“If we take 15% out, what stops?” is the question every transformation office is asked and few can answer live. Build competing scenarios against one budget ceiling, see the trade-offs on screen, and select one, with the numbers baselined at the moment of decision and the full history kept for the conversation six months from now.
Streamline Project Portfolio Management and Visibility at Scale
Integrations
Capture new project request, streamline evaluation and prioritization
Product
Structured Approach for prioritizing and aligning portfolios with strategic priorities and resource constraints
Product
Last updated 20 August 2026
Transformation Office portfolio management, answered.
A PMO assures delivery of a standing portfolio. A TMO exists to land one specific, time-bound change and then close down. Its distinguishing job is benefits: proving the value promised in the business case actually showed up, and recommending which workstreams continue, scale or stop. TMOs usually carry more authority and a much shorter life than the PMO they sit beside.
Defining the value a change is meant to deliver, giving it an owner, and tracking it through to the point where the business can evidence it. Three parts have to be in place: the benefit definition, a baseline to measure against, and someone accountable by name. Most transformation programs have the first one and neither of the other two.
It usually belongs in the portfolio platform rather than a separate tool, because a benefit only means anything next to the initiative delivering it and the money funding it. In PPM Express each workstream carries budget, forecast, benefits and impact, baselined at the moment of the funding decision. The promise and the outcome stay attached to each other instead of drifting into different decks.
Each workstream follows a process built from phases and stages, with gates in between. You decide which gates need approval. The workstream lead assigns approvers, who review in the Approval Center and approve or reject with comments. Unanimous approval advances the workstream. A single rejection holds it. If your organization already runs approvals through another system, gates can be routed there through the API instead.
Hold the benefit at the workstream that owns it rather than at the level where it gets reported. When three workstreams each claim a slice of the same headcount saving, all three claims sit against the same benefit and the overlap is obvious. Double-counting is almost always a side effect of benefits being added up in slides instead of tracked in one place.
Compare scenarios rather than defending workstreams one at a time. Pareto optimization shows the set of options where you can't improve strategic value, benefits, risk or cost without conceding something, so the board picks a point on that frontier. A workstream then stops because a better portfolio exists without it. Nobody has to lose an argument.
Usually the baseline was never fixed. If the "before" figure gets reconstructed afterward, any result can be made to look like progress, and your CFO knows it. PPM Express baselines numbers at the moment of the decision and keeps the decision history, so the comparison runs against what was actually approved rather than a figure assembled later to fit the story.
PPM Express works out capacity from each person's work week and calendar exceptions, then shows allocation against it in hours, percent or FTE, with overallocation color-coded. Transformations tend to fail in a specific way here: the same senior operators are written into six workstream plans, each of which looked reasonable on its own. Put those plans in one view and the double-booking is unmissable.
Portfolio position, movement since last time, decisions being requested, benefits against baseline. The week of prep exists because those four things live in four places. In PPM Express they're one live view, so the pack becomes a snapshot of the system rather than a rebuild of it. That also removes the awkward gap between what the pack says and what the delivery tools say.
Every selected scenario stamps its outcome onto each workstream, baselines the numbers at that moment, and keeps the decision history. Three months on, "this was never agreed" becomes a checkable claim. It's the difference between a governance forum that decides things and one that reopens the same argument each quarter with a slightly different set of attendees.
It does. Project Online and Project for the Web connect directly, and for the Microsoft Project Desktop client there's PPM Express Project Publisher, an add-in that publishes an open plan up into PPM Express. Desktop 2016, 2019 and 2021 are supported. Workstream leads keep their planning tool, and the TMO gets the portfolio view without asking anyone to rebuild a schedule.
Partly by asking less of people. Workstream leads stay in the tools they already use, whether that's Microsoft Project, Planner, Smartsheet, Monday.com, Jira or Azure DevOps, rather than keeping a parallel set of records for the TMO. Fatigue is often less about the change itself than about the reporting overhead that arrives with it.
Most are, in fact. TMOs typically get created once a program is already in difficulty. Because PPM Express connects to tools the workstreams are already using, you can assemble the current position without pausing delivery for a data-gathering exercise. The genuinely hard part is retrofitting baselines for workstreams that started without them, and that's a governance call rather than a software one.
.svg){kind=small}
