-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathsample-output.html
More file actions
37 lines (37 loc) · 5.8 KB
/
Copy pathsample-output.html
File metadata and controls
37 lines (37 loc) · 5.8 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
<!doctype html><html><head><meta charset="utf-8"><title>PPMO Formation Kit — Sample Output</title><style>body{font-family:Arial,Helvetica,sans-serif;max-width:1050px;margin:36px auto;line-height:1.55;color:#17202a}h1{border-bottom:4px solid #1f4e79;padding-bottom:8px}h2{color:#1f4e79;margin-top:28px}table{border-collapse:collapse;width:100%;margin:14px 0}th,td{border:1px solid #d5d8dc;padding:8px;vertical-align:top}th{background:#eef3f8;text-align:left}code,pre{background:#f4f6f7;border:1px solid #d5d8dc;padding:10px;white-space:pre-wrap;display:block}.note{background:#fff8e1;border-left:4px solid #c49a00;padding:10px}.ok{background:#edf7ed;border-left:4px solid #2e7d32;padding:10px}</style></head><body>
<h1>PPMO Formation Kit — Sample Output</h1>
<p class="note">This is a shortened illustrative output using the fictional NimbusWorks scenario. It demonstrates the shape of the formation package, not a final client deliverable.</p>
<h2>Formation brief</h2>
<table><tr><th>Element</th><th>Draft</th></tr>
<tr><td>Formation trigger</td><td>NimbusWorks has roughly 500 initiatives with inconsistent ownership, no trusted baseline, side-channel intake, and competing CIO/CFO/COO priorities.</td></tr>
<tr><td>Operating problem</td><td>Leadership cannot make reliable tradeoffs because work is not consistently captured, classified, sponsored, or routed to the right decision forum.</td></tr>
<tr><td>PPMO purpose</td><td>Create enough structure to make portfolio work visible, comparable, sponsor-owned, decision-ready, and governed without creating a heavy process office.</td></tr>
<tr><td>Human confirmations</td><td>Executive sponsor, portfolio scope, decision authority, mandatory vs discretionary work rules, and reporting data owners.</td></tr></table>
<h2>Operating charter excerpt</h2>
<ul><li><strong>Owns:</strong> portfolio visibility, intake structure, taxonomy, governance cadence, decision preparation, reporting model, decision/action follow-through pattern.</li><li><strong>Does not own:</strong> funding approval, risk acceptance, executive priority decisions, delivery ownership, headcount assignment, tool administration, or project execution.</li><li><strong>Initial service model:</strong> intake facilitation, portfolio baseline cleanup, governance agenda preparation, decision-log maintenance pattern, and executive reporting support.</li></ul>
<h2>Decision-rights excerpt</h2>
<table><tr><th>Decision</th><th>Owner</th><th>Forum</th><th>PPMO role</th><th>Confirmation needed</th></tr>
<tr><td>Accept demand into discovery</td><td>Portfolio intake forum</td><td>Biweekly intake review</td><td>Check minimum fields and route</td><td>Confirm chair and quorum</td></tr>
<tr><td>Approve funding</td><td>CFO plus accountable sponsor</td><td>Executive council</td><td>Prepare options and evidence</td><td>Confirm finance threshold</td></tr>
<tr><td>Resolve cross-functional priority conflict</td><td>Executive council</td><td>Monthly portfolio review</td><td>Surface tradeoffs and impacts</td><td>Confirm escalation path</td></tr>
<tr><td>Accept high delivery or compliance risk</td><td>Named accountable executive</td><td>Executive council or risk forum</td><td>Document risk and decision request</td><td>Confirm risk owner</td></tr></table>
<h2>Portfolio taxonomy excerpt</h2>
<table><tr><th>Field</th><th>Required</th><th>Example values</th><th>Use</th></tr>
<tr><td>Portfolio lane</td><td>Yes</td><td>Technology, Finance Systems, Operations, Customer, Data, Compliance</td><td>Reporting and ownership</td></tr>
<tr><td>Lifecycle stage</td><td>Yes</td><td>New, Discovery, Business Case, Chartered, Active, Blocked, Closing</td><td>Governance routing</td></tr>
<tr><td>Funding class</td><td>Yes</td><td>Funded, Pending, Mandatory, Discretionary, Unfunded Mandate</td><td>Tradeoff review</td></tr>
<tr><td>Readiness state</td><td>Yes</td><td>Ready, Incomplete, Needs Sponsor, Duplicate Suspected, Blocked</td><td>Intake triage</td></tr></table>
<h2>Governance cadence</h2>
<table><tr><th>Forum</th><th>Cadence</th><th>Purpose</th><th>Primary output</th></tr>
<tr><td>Intake review</td><td>Biweekly</td><td>Classify and route new demand</td><td>Accepted, incomplete, deferred, rejected, or routed</td></tr>
<tr><td>Portfolio review</td><td>Monthly</td><td>Inspect active portfolio health and decision needs</td><td>Decision agenda and escalation list</td></tr>
<tr><td>Executive council</td><td>Monthly or exception-based</td><td>Resolve funding, priority, capacity, and risk tradeoffs</td><td>Decisions, actions, and owner commitments</td></tr></table>
<h2>30/60/90 plan excerpt</h2>
<table><tr><th>Period</th><th>Focus</th><th>Output</th></tr>
<tr><td>30 days</td><td>Confirm authority and build baseline v0</td><td>Charter draft, decision-rights draft, taxonomy, intake fields</td></tr>
<tr><td>60 days</td><td>Pilot intake and governance cadence</td><td>Intake pilot, first council agenda, reporting model v1</td></tr>
<tr><td>90 days</td><td>Stabilize and hand off to operating modules</td><td>Formation package v1 and downstream handoff brief</td></tr></table>
<h2>Handoff brief</h2>
<ul><li><strong>To Portfolio Intake and Readiness Triage System:</strong> intake fields, intake states, routing outcomes, and taxonomy.</li><li><strong>To Portfolio Prioritization Scoring Agent:</strong> confirmed taxonomy, funding class, strategic themes, and scoring boundary assumptions.</li><li><strong>To Executive Portfolio Review Pack Builder:</strong> governance cadence, reporting views, decision-owner fields, and escalation rules.</li><li><strong>To PMO Governance Operations Log:</strong> decision-log pattern, carry-forward fields, action owner fields, and unresolved assumptions.</li></ul>
<p class="ok"><strong>Readiness view:</strong> Ready with caveats. Human confirmation is still required for sponsor authority, finance thresholds, council membership, and source-system ownership.</p>
</body></html>