Incoming demand
A mixed list of requests arrives from finance operations, customer support, security, and a department AI sponsor. Some requests are mandates. Some are ideas. Some are fixes with unclear ownership.
Scenario
The starting point
This synthetic scenario represents a common portfolio problem: leaders can see activity, but the work is not yet clean enough for funding, sequencing, or executive review.
Current risk
The organization could push everything into a backlog, start business cases too early, or hold another status meeting that does not create a decision path.
Review goal
Give executives a clean view of what needs clarification, what can move toward tradeoff review, what is blocked, and what decisions need named owners.
Module route
How the work moves
The journey uses six public portfolio modules. Each module owns one decision-support layer and hands cleaner evidence to the next step.
1. Form the lane
PPMO Formation Kit defines intake ownership, decision rights, taxonomy, and governance cadence.
Open PPMO Formation Kit
2. Audit signal
Portfolio Signal Quality Auditor identifies weak status, duplicate demand, stale confidence, and missing evidence.
Open Portfolio Signal Quality Auditor
3. Triage readiness
Portfolio Intake Readiness Triage System classifies each request and recommends a next route.
Open Intake Readiness Triage
4. Score tradeoffs
Portfolio Prioritization Scoring Agent compares approved candidates against criteria, constraints, and risk.
Open Prioritization Scoring
5. Sequence capacity
Portfolio Capacity Sequencing Planner exposes sequencing conflicts, capacity pressure, and dependency choices.
Open Capacity Sequencing Planner
6. Build review pack
Executive Portfolio Review Pack Builder packages the decision agenda, portfolio view, risks, and follow-up register.
Open Executive Review Pack Builder
Synthetic input
Starting demand list
The point of the journey is not the specific items. The point is the operating pattern: rough demand becomes reviewable signal before leaders are asked to decide.
| Request | Initial signal | Problem with the signal | Likely route |
|---|---|---|---|
| Billing exception cleanup | Finance operations reports repeated manual corrections. | Impact is plausible, but no owner has confirmed baseline volume or control exposure. | Clarify, then business case |
| Customer notification workflow | Support leaders want fewer status calls and faster customer updates. | Benefit is clear, but dependency on platform release timing is unknown. | Readiness triage, then scoring |
| AI knowledge assistant | A sponsor wants a prototype for internal policy lookup. | The workflow, reliance boundary, and content ownership are not defined. | AI opportunity review |
| Security access review | Compliance deadline is approaching. | Mandate is real, but effort, decision owner, and delivery capacity are unclear. | Clarify mandate, then executive review |
Evidence produced
What each step creates
Each artifact is small on purpose. The journey is meant to show decision quality, not a heavyweight methodology.
Formation output
- Named intake owner and review forum.
- Minimum fields for demand entry.
- Decision-right boundary for intake, scoring, funding, and executive review.
- Taxonomy for mandate, improvement, AI opportunity, platform, compliance, and operational fix.
Triage output
- Request-by-request readiness classification.
- Missing evidence and owner follow-up.
- Recommended route: reject, hold, clarify, business case, charter, scoring, or AI review.
- Confidence level and assumptions for human review.
Tradeoff output
- Comparable priority view for approved candidates.
- Capacity and dependency notes that may change sequence.
- Risks that require sponsor or executive attention.
- Decision options, with the tradeoff visible for human review.
Executive review output
- Decision agenda with named asks.
- Portfolio signal summary.
- Risks, blockers, dependencies, and evidence gaps.
- Follow-up register for owners, dates, and unresolved decisions.
Review pack
Final executive view
A sponsor should not have to decode the whole module library. This is the kind of final view the journey should support.
Decision frame
Two requests appear ready for further review after evidence cleanup. One AI request should move through AI opportunity review before any prototype commitment. One compliance-driven request needs executive attention because the deadline is real but delivery capacity and ownership are not yet clear.
| Item | Recommended review route | Executive question | Human decision needed |
|---|---|---|---|
| Billing exception cleanup | Business case after baseline confirmation | Who owns the value baseline and control-risk evidence? | Name accountable sponsor and due date for evidence. |
| Customer notification workflow | Portfolio scoring and capacity sequencing | Should this move ahead of current support and platform commitments? | Choose sequence option after capacity review. |
| AI knowledge assistant | AI opportunity intelligence review | What workflow will this change, and what reliance boundary is acceptable? | Approve, delay, or stop the proof plan after opportunity review. |
| Security access review | Executive review with blocker escalation | Which owner can commit capacity before the compliance deadline? | Name decision owner and escalation path. |
Repository route
Where to inspect the modules
The journey summarizes the route. The repositories hold the operating details, examples, runtime files, and boundaries.