The situation
A $1.5B+ data and analytics company had nine separate transformation workstreams running in parallel — each with its own ROI case, vendor relationships, and timeline. Individually, each value stream had a defensible business case. Collectively, leadership couldn't tell which workstreams were compounding, which were duplicating effort, and which were underwater on Cost of Doing Nothing.
The board needed one cross-chapter view. The CEO needed a way to govern AI investment across the program, not just per-workstream. The CFO was starting to ask the CODN question.
What I built
A nine-value-stream chapter system. Each chapter:
- Independent business case with bounded ROI and bounded CODN — high case, low case, midpoint, pressure-tested against external benchmarks.
- Standardized governance instruments (CODN snapshot, AI-readiness diagnostic, vendor-consolidation map).
- Cross-chapter dependency map showing which workstreams compound on which others.
- Quarterly governance cadence with CODN as the standing agenda item.
The CEO-level synthesis layer translated nine technical workstreams into one board-grade narrative. Where workstreams compounded, that became investment justification. Where they duplicated effort, that became consolidation logic.
What changed
- Investment governance shifted from per-workstream to program-level. The board approved a multi-year envelope, not nine separate vendor decisions.
- CODN became the quarterly governance instrument. Every chapter reports CODN drift quarter over quarter; rising CODN triggers escalation.
- Three workstreams were quietly consolidated based on dependency-map findings — saving on overlapping vendor commitments without removing capability.
What I'd do differently
The chapter system worked, but a meaningful portion of the value emerged only after the second quarterly review — not the first. Future engagements should sequence the first three months as "establish the baseline" rather than "produce a synthesis." Board patience for the second-quarter inflection was critical.
Stack used
Discovery + synthesis: Claude Code + custom MCP servers for proprietary chapter data + Supabase for cross-chapter dependency tracking. Governance instruments delivered as exec-friendly dashboards.
Where this engagement shape fits
This was a fractional advisory engagement — multi-month, embedded with CEO and CFO. Best fit when transformation has already started but governance hasn't caught up. See engagement shapes →
Methodology
Run by the CODN framework. Engagements delivered through Stravonvale.