-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathproof.html
More file actions
275 lines (267 loc) · 13.1 KB
/
Copy pathproof.html
File metadata and controls
275 lines (267 loc) · 13.1 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
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Portfolio Evidence | Marco Policani</title>
<meta name="description" content="The proof behind Marco Policani's PMO and portfolio governance work: named engagements, the walkthroughs behind them, and the boundaries keeping claims honest.">
<meta name="author" content="Marco Policani">
<meta name="robots" content="index, follow">
<meta property="og:title" content="Portfolio Evidence | Marco Policani">
<meta property="og:description" content="A front door to the work: real outcomes from named engagements, the walkthroughs behind them, starting-template modules, and clear proof boundaries.">
<meta property="og:type" content="website">
<meta property="og:url" content="https://policani.net/proof.html">
<meta property="og:image" content="https://policani.net/assets/social-card-1200x630.jpg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta name="twitter:card" content="summary_large_image">
<link rel="canonical" href="https://policani.net/proof.html">
<link rel="icon" type="image/svg+xml" href="assets/favicon.svg">
<link rel="apple-touch-icon" href="assets/apple-touch-icon.png">
<link rel="preload" as="image" href="assets/portfolio-operations-hero-1920.webp" type="image/webp">
<link rel="stylesheet" href="assets/portfolio-site.css?v=20260706-productioncopy">
<link rel="stylesheet" href="assets/experience-dashboard.css?v=20260617-type">
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebPage",
"@id": "https://policani.net/proof.html#webpage",
"name": "Portfolio Evidence | Marco Policani",
"url": "https://policani.net/proof.html",
"description": "The proof behind Marco Policani's PMO and portfolio governance work: outcomes from named engagements, walkthroughs, starting-template modules, and proof boundaries.",
"inLanguage": "en-US",
"isPartOf": {
"@type": "WebSite",
"name": "Marco Policani Portfolio",
"url": "https://policani.net/"
},
"author": {
"@type": "Person",
"name": "Marco Policani","alternateName": "Marc Policani",
"url": "https://policani.net/"
}
}
</script>
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600&family=Geist+Mono:wght@400;500&display=swap" rel="stylesheet">
</head>
<body>
<a class="skip-link" href="#main">Skip to content</a>
<nav class="local-nav" aria-label="Top-level portfolio sections">
<div class="nav-inner">
<a class="nav-title" href="index.html">Marco Policani</a>
<div class="nav-links">
<a href="pmo-portfolio-governance-leader.html">Role Fit</a>
<a href="operating-history.html">Case Studies</a>
<a href="artifacts.html">Walkthroughs</a>
<a href="governance/">Governance</a>
<a href="modules.html">Workflow Systems</a>
<a href="proof.html" aria-current="page">Evidence</a>
<a href="resources.html">Resources</a>
<a href="contact.html">Contact</a>
</div>
</div>
</nav>
<header class="hero" data-parallax-travel="200">
<div class="portfolio-hero-filament-bg" aria-hidden="true">
<canvas class="portfolio-hero-filament-canvas"></canvas>
</div>
<div class="hero-inner">
<div class="hero-copy">
<p class="eyebrow">Evidence</p>
<h1>The proof, strongest first.</h1>
<p class="subhead">A front door to the work, in evaluation order: outcomes from named engagements first, then the walkthroughs behind them, then the starting-template modules.</p>
<div class="actions">
<a class="button primary" href="#outcomes">See the outcomes</a>
<a class="button" href="operating-history.html">Open all ten case studies</a>
<a class="button" href="index.html">Back to overview</a>
</div>
</div>
</div>
</header>
<main id="main">
<section aria-labelledby="outcomes">
<div class="section-inner">
<p class="section-kicker">Strongest proof · named engagements</p>
<h2 id="outcomes">Outcomes from real portfolios, under real constraints.</h2>
<p class="lead">Ten named case studies across enterprise software, telecom, SaaS, energy, and infrastructure. The headline results:</p>
<div class="metro-grid" aria-label="Top outcome signals from named engagements">
<div class="tile t-blue">
<span class="tile-kicker">T-Mobile</span>
<span class="tile-num">65%</span>
<span class="tile-title">Delivery cycle-time cut across a ~500-initiative T-Mobile revenue technology portfolio (340 to 120 days).</span>
</div>
<div class="tile t-teal">
<span class="tile-kicker">Microsoft</span>
<span class="tile-num">$1.8B</span>
<span class="tile-title">Influenced renewal revenue at Microsoft, with a finance-validated 8% lift.</span>
</div>
<div class="tile t-gold">
<span class="tile-kicker">Doosan GridTech</span>
<span class="tile-num">~$125M</span>
<span class="tile-title">Capital storage program sequenced across three utility-scale sites at Doosan GridTech.</span>
</div>
<div class="tile t-ink">
<span class="tile-kicker">Microsoft · GDPR</span>
<span class="tile-num">3,424</span>
<span class="tile-title">GDPR-relevant suppliers identified across 362 acquired entities, with structured remediation and acquisition safeguards completed in nine months.</span>
</div>
</div>
<div class="actions">
<a class="button primary" href="operating-history.html">See all ten case studies</a>
</div>
</div>
</section>
<section aria-labelledby="worked-example">
<div class="section-inner">
<p class="section-kicker">Worked example · T-Mobile Revenue Technology · 2021–2024</p>
<h2 id="worked-example">A ~500-initiative portfolio, reset from 340 to 120 days.</h2>
<p class="lead">Revenue-critical work tracked through 75+ inconsistent fields with no standard lifecycle. A material share of “active” work was unfunded, under-defined, or stalled — artificial congestion that hid real capacity and stretched delivery cycles to ~340 days. The constraint was distorted work-in-progress and weak readiness discipline, not execution capability.</p>
<div class="grid-3">
<article class="card">
<h3>Maintain the structure</h3>
<p>Avoids disruption, but sustains the distortion and the reactive reprioritization.</p>
</article>
<article class="card">
<h3>Re-platform the tooling</h3>
<p>Structural consistency, at the cost of delay and adoption resistance.</p>
</article>
<article class="card">
<h3>Reset signal in place — chosen</h3>
<p>Reclassify work, normalize lifecycle definitions, and separate qualification from execution — without replacing the platform.</p>
</article>
</div>
<div class="grid-2">
<div class="proof-box">
<h3>What I put in place</h3>
<p>Reviewed ~500 initiatives and reclassified stalled or under-defined work out of the active pipeline. Normalized 75+ tracking fields into one lifecycle with staged readiness gates from concept to launch. Ran a dual-rail model so work entered delivery only when build-ready, and shifted executive reporting to change-based discussions of risk and sequencing rather than status reconciliation.</p>
</div>
<div class="proof-box">
<h3>The outcome</h3>
<p>A 65% reduction in average delivery cycle time — from ~340 days to ~120 — across roughly 500 initiatives, with 75+ tracking fields normalized into a single lifecycle and no platform replacement.</p>
<div class="repo-links">
<a href="engagements/tmobile-revenue-technology.html">Open the full T-Mobile case study</a>
</div>
</div>
</div>
</div>
</section>
<section aria-labelledby="routes-heading">
<div class="section-inner">
<p class="section-kicker">Then the patterns · walkthroughs</p>
<h2 id="routes-heading">Generalized walkthroughs you can follow end to end.</h2>
<p class="lead">Client-safe walkthroughs of how ambiguous work becomes decided, owned, and reviewable — the operating patterns abstracted from the engagements above. They run in portfolio-lifecycle order, from intake to realized value, then the cross-cutting governance walkthroughs.</p>
<div class="grid-3">
<a class="card-link" href="walkthroughs/messy-demand-to-executive-review.html">
<article class="card">
<h3>Messy demand to executive review</h3>
<p>Rough portfolio demand becomes intake signal, triage evidence, and a decision path.</p>
</article>
</a>
<a class="card-link" href="walkthroughs/tradeoffs-to-executive-decision.html">
<article class="card">
<h3>Tradeoffs to executive decision</h3>
<p>Scorecards, constraints, and risk become a clear, sponsor-ready decision.</p>
</article>
</a>
<a class="card-link" href="walkthroughs/approved-intent-to-chartered-delivery-start.html">
<article class="card">
<h3>Approved intent to chartered delivery</h3>
<p>An approved idea becomes investment logic and a build-ready charter.</p>
</article>
</a>
<a class="card-link" href="walkthroughs/delivery-readiness-to-value-realization.html">
<article class="card">
<h3>Delivery readiness to value realization</h3>
<p>Readiness gates, sign-offs, and evidence become tracked, realized benefits.</p>
</article>
</a>
<a class="card-link" href="walkthroughs/ai-idea-to-governed-artifact-lifecycle.html">
<article class="card">
<h3>AI idea to governed artifact lifecycle</h3>
<p>An AI prototype idea moves through governed synthesis to an accountable artifact.</p>
</article>
</a>
<a class="card-link" href="walkthroughs/artifact-source-to-public-safe-proof-review.html">
<article class="card">
<h3>Artifact source to client-safe proof</h3>
<p>Source material becomes a generalized, client-safe proof without exposing internals.</p>
</article>
</a>
<a class="card-link" href="walkthroughs/partner-ecosystem-governance.html">
<article class="card">
<h3>Partner ecosystem governance</h3>
<p>Partner and ecosystem work becomes governed, reviewable delivery.</p>
</article>
</a>
</div>
<p class="lead">Reusable starting templates for these patterns live on <a href="modules.html">Workflow Systems</a>.</p>
</div>
</section>
<section aria-labelledby="scope-heading">
<div class="section-inner">
<p class="section-kicker">Scope of the claim</p>
<h2 id="scope-heading">What is public, and what stays private.</h2>
<p class="lead">The split is deliberate, not a gap. Experience evidence shows real category-level context; walkthroughs show generalized patterns; exact sensitive evidence stays private or interview-only.</p>
<div class="grid-3">
<article class="card">
<h3>Human-owned AI workflow</h3>
<p>AI supports synthesis, review, drafting, and classification. People own approvals, commitments, risk acceptance, funding, and final communication. Model ownership, ML engineering, and production AI platform governance are outside the claim.</p>
</article>
<article class="card">
<h3>Client-safe examples</h3>
<p>Examples are synthetic, generalized, or scrubbed, so the public work can demonstrate judgment without exposing client, employer, or proprietary detail.</p>
<div class="repo-links">
<a href="https://github.com/policani/Policani/tree/main/wiki" target="_blank" rel="noopener noreferrer">Review portfolio artifacts</a>
</div>
</article>
<article class="card">
<h3>Software engineering scope</h3>
<p>The repositories show workflow architecture, operating design, local tooling, and structured artifacts. Production software engineering ownership is outside the claim.</p>
<div class="repo-links">
<a href="https://github.com/policani/policani.github.io" target="_blank" rel="noopener noreferrer">Inspect website source</a>
</div>
</article>
</div>
<div class="review-sequence" aria-label="Recommended review sequence">
<a href="pmo-portfolio-governance-leader.html">1 Role Fit</a>
<a href="operating-history.html">2 Case Studies</a>
<a href="artifacts.html">3 Walkthroughs</a>
<a href="modules.html">4 Workflow Systems</a>
<span class="current">5 Evidence</span>
</div>
</div>
</section>
<section id="next" class="section-white" aria-labelledby="contact-heading">
<div class="section-inner two-col">
<div>
<p class="section-kicker">Next sections</p>
<h2 id="contact-heading">Use the evidence, then judge the fit.</h2>
<p class="lead">Return to the executive portfolio for role fit, the case studies for the full record, or the modules page for the reusable structures behind the walkthroughs.</p>
</div>
<div class="proof-box">
<h3>Continue the evaluation</h3>
<div class="repo-links">
<a href="portfolio.html">Executive portfolio</a>
<a href="operating-history.html">Case studies</a>
<a href="artifacts.html">Walkthroughs</a>
<a href="modules.html">Workflow Systems</a>
</div>
</div>
</div>
</section>
</main>
<footer>
<div class="section-inner">
<p>Marco Policani | <a href="index.html">Portfolio overview</a> | <a href="resources.html">Other resources</a> | <a href="https://github.com/policani" target="_blank" rel="noopener noreferrer">GitHub</a> | <a href="https://www.linkedin.com/in/marcpolicani" target="_blank" rel="noopener noreferrer">LinkedIn</a></p>
</div>
</footer>
<script src="assets/hero-parallax.js" defer></script>
<script src="assets/portfolio-signal-field.js?v=20260613-signalfield" defer></script>
<script src="assets/portfolio-hero-filament.js?v=20260613-signalfield" defer></script>
<script src="assets/site-concierge.js?v=20260703-contact" defer></script>
<script data-goatcounter="https://policani.goatcounter.com/count" async src="//gc.zgo.at/count.js"></script>
<script src="assets/count-up.js" defer></script>
</body>
</html>