Introduction
A target operating model cannot be designed in the abstract. It is designed against specific workflows that will actually change. Without naming those workflows explicitly, transformations drift: scope creeps, stakeholders push their pet processes, and the team ends up touching everything shallowly instead of transforming anything deeply.
The Workflow Transformation Portfolio is the strategic selection artifact in Design. It answers the question that tends to go unanswered: of all the workflows in scope, which ones are we actually going to redesign in this cycle. Typical answer: 2 to 5. Everything else waits for the next cycle.
This exercise sits upstream of the detailed design work. Once the Portfolio is signed off, all subsequent exercises (target process design, task assignment, role evolution) operate inside the selected workflows. Everything else stays as-is.
Phase | Design |
Lens | Operations |
Purpose | Select the 2 to 5 workflows to redesign in this transformation cycle |
Output | Named portfolio of 2 to 5 workflows, with scoring rationale and explicit exclusions |
Who's Involved | Transformation sponsor, program lead, operations leads of candidate workflows |
Duration | Half-day workshop, preceded by one to two weeks of data gathering |
Steps
List candidate workflows in scope. Draw from Current Process Architecture, the AI Initiative Inventory (existing activity), and stakeholder input. Expect 10 to 30 candidates for a mid-sized transformation.
Score each candidate on four dimensions: frequency (how often does this run), friction (cost, time, errors, senior capacity consumed), impact potential (business or mission value if redesigned), and AI readiness (how ready are the systems and data for AI to participate).
Rank by combined score. The top cluster is the shortlist; everything below is parked for future cycles.
Test the shortlist against the Transformation Vision Canvas constraints (budget, timeline, regulatory). Cut any workflow the program cannot realistically transform in this cycle.
Select 2 to 5 workflows as the Portfolio. Document the rationale for each inclusion and the explicit exclusion of the rest.
Name an owner and a target redesign cadence for each selected workflow.
Socialize the Portfolio with stakeholders. Manage expectations for workflows that were excluded.
Templates
Coming Soon
Continue reading
Looking to contribute?
Orbit evolves through practice. Whether you're applying the method, testing ideas, or finding gaps, your experience helps refine it. Share what you're learning and help shape the next update.