M0 Prep Brief — VisionVolve — Internal

Active obstacles · severity × delay matrix

Private working document. Not for client distribution.

Generated 2026-09-02 from current engagement configuration. Re-generate before each M0 conversation as state evolves.

Engagement phase: pre-engagement — main engagement.

1. Engagement context

Archetype: Greenfield — Build the AI capability from zero — no internal AI function exists yet. Partner installs full methodology stack.

Internal AI Lead state: None — no internal AI lead exists

Board state: Aware

Multi-market: No

Benchmark (methodology prior, Greenfield archetype, ~week 12 / M3)

Verdict: Behind typical

Metric	Actual	Expected (min–target–max)	Status
L1 authorities granted	24	18–24–30	Ahead of typical
L3 mechanisms stood up	0	6–10–14	Behind typical
Peers named + active	0	4–6–8	Behind typical

Constraint breaches:

• Active obstacles: 7 (max for milestone: 3)

Aggregate impact at risk

If unresolved, currently-active obstacles cumulatively introduce 26–64 weeks of delay. Illustrative € exposure: €1.2M–€4.0M across 5 measured obstacles.

4 obstacles carry CRITICAL or LARGE engagement-value-at-risk.

Note: 6 of 7 active obstacles have impact data; 1 are not yet quantified.

2. People — named, inactive, unknown

Already engaged (0):

Named but not yet engaged (12):

• CEO (CEO) — no context
• CFO (CFO) — no context
• CIO (CIO) — no context
• CMCO (CMCO) — no context
• CSCO (CSCO) — no context
• HeadMA (HeadMA) — no context
• HeadOfAI (HeadOfAI) — no context
• CRO (CRO) — no context
• QMHead (QMHead) — no context
• DPO (DPO) — no context
• ExternalChampion (ExternalChampion) — no context
• PEOperatingPartner (PEOperatingPartner) — no context

3. Prescribed actions (rule-based, current state)

1. Pre-stage 30-min CEO briefing before M0

• When: Before M0
• Who: AR
• Why: Sponsor is not actively driving (Board state = Aware). M0 will not get the air cover it needs unless the CEO arrives pre-aligned on what is at stake.
• Evidence: L0.board_state = Aware; O-013 latent / inactive
• Reduces / resolves: O-013

2. Engage 5 named-but-inactive peers

• When: Before M0
• Who: AR
• Why: CFO, CIO, CRO (+2 more) are named in the org but not yet engaged on AI matters; obstacles depend on their activation.
• Evidence: peer.CFO (CFO) is named=true, active=false; peer.CIO (CIO) is named=true, active=false; peer.CRO (CRO) is named=true, active=false
• Reduces / resolves: O-001, O-003, O-008, O-010, O-014, O-015, O-022

4. Authority asks — ordered for the M0 conversation

_All Must-default authorities are already granted in this configuration._

5. Active obstacles to surface in M0

O-003 — Risk Function Disengaged [severity: high]

Regulated profile but CRO/DPO not integrated; risk classification skipped

Triggered conditions:

• peer.CRO is missing_or_inactive
• peer.QMHead is missing_or_inactive
• peer.DPO is missing_or_inactive

Recovery actions:

• Force trigger via L1-124 (veto) on next initiative requiring classification
• Surface to L1 escalation
• Direct to L3-319 for regulated industries

O-001 — Pipeline Stall at Gate 2 [severity: med]

Initiatives accumulate at Pilot-Validated; Scale decisions don't happen

Triggered conditions:

• peer.CFO is missing_or_inactive
• L3-303 is not_stood_up
• peer.CIO is missing_or_inactive

Recovery actions:

• Negotiate L1-108 mid-engagement
• Escalate to L3-318 (Exec sponsor)
• Document scoping limitation if irrecoverable

O-010 — Heavy-Gate Decision Drift [severity: med]

Forums standing but not deciding; gates become advisory; portfolio prioritization becomes politics

Triggered conditions:

• peer.CIO is missing_or_inactive

Recovery actions:

• Reassert L1-101/L1-102 chair authority
• Time-boxed decision protocol (each PC closes ≥ 1 decision)
• Escalate to L3-318 if blocked

O-015 — Vendor Stack Fragmentation [severity: med]

Multiple AI vendors deployed independently across functions; no unified ops layer; integration debt compounds; vendor lock-in by component

Triggered conditions:

• peer.CIO is missing_or_inactive
• L3-327 is not_stood_up

Recovery actions:

• Force unified AI ops layer ownership under CIO
• Establish vendor portfolio review at AI Council
• Document integration interfaces in BDN

O-022 — AI Act Compliance Stalled [severity: med]

Regulated organization approaching EU AI Act deadline; high-risk AI inventory not catalogued, conformity assessment not staffed; engagement timeline collides with compliance deadline

Triggered conditions:

• L3-329 is not_stood_up

Recovery actions:

• Stand up L3-329 conformity assessment process immediately
• Inventory all customer-facing + decision-support AI systems within 30 days
• Assign explicit owner (typically GC + CIO + named AI Lead jointly)
• Make AI Act readiness an explicit charter milestone

6. Before walking into M0

Confirm each item below is true before the meeting. Anything unchecked is a known risk:

• ○ Sponsor is pre-briefed on engagement scope (no surprises in the room) — Board state is Aware
• ○ Internal AI Lead exists or successor is named — IAL state = None — no internal lead exists
• ✓ PE operating partner is identified (if PE-owned)
• ✓ CIO seat verified (no pending tenure changes) — CIO tenure flagged uncertain in notes
• ✓ External Champion handover protocol clear (if applicable)
• ○ AI Act conformity assessment scope is bounded

---

Brief generated by VV Engage. Methodology v0.2.1 · Engine v0.2 · Recommendations v0.1.