VisionVolve· Engage
Methodology summary · v0.4 · 2026-09-02

AI Transformation at Scale — Engagement Methodology

Instantiated for: VisionVolve — Internal

VV's deep-engagement offering: a time-boxed, fractional, board-mandated Interim AI Transformation Partner role that installs a complete AI operating system in ~6 months and exits, leaving behind durable internal AI leadership, governance, strategy, policies, processes, a working PoC pipeline, and trained people.

1. The methodology in one paragraph

What we install, how we measure it, when we leave

Three lenses (process / system / logic) instantiated as six parallel tracks. A connective BDN layer ties initiatives, capabilities, benefits, and objectives. A META charter (CAIO Operating Charter Q1–Q8) defines how the Partner role itself operates. The framework is evidence-grounded: anchored on Cranfield/Ward & Peppard BDN, Gartner AI Maturity, NIST AI RMF, ISO/IEC 42001, EU AI Act, Cooper Stage-Gate.

Engagement archetype

Interim AI Transformation Partner — fractional (typically 2/5 days/week), time-boxed (typically ~6 months), board-mandated, exit-oriented. Not advisory. Not permanent. Authority-backed. Recruits VV delivery layer separately; preserves clean commercial interface.

Reading guide

The glossary in §2 below decodes forum names (Portfolio Council, AI Council, Scale Decision Forum), gate names (Heavy Gate 1/2), BDN levels, and engagement phases. Skim it once before the rest — every later section assumes these names.

2. Glossary · names you'll see

Decode forums, gates, levels, phases

Methodology vocabulary that appears throughout this document and on every Engage artefact (Charter Q1–Q8, M0 brief, dashboards). Each term is a load-bearing concept, not jargon for its own sake — the glossary entry explains what it does and why it exists.

Portfolio Council
Recurring forum (typically bi-weekly or monthly) where AI initiatives are reviewed, ranked, advanced, killed, or parked. The body that makes Heavy Gate 1 decisions. Track 1 (Pipeline) backbone.
AI Council
Central governance forum (typically monthly) where AI strategy, risk, vendor, and budget decisions converge. Track 3 (AI OS) backbone — the operating system that runs everything else.
Scale Decision Forum
Body that makes Heavy Gate 2 decisions (Pilot-Validated → Scaling). Different members + cadence from Portfolio Council because capex + operational change are at stake. CFO + COO + CRO must be present.
Heavy Gate 1
Formal Sponsorship → Pilot decision. The point where pilot capacity gets committed. Below it, cheap experiments. Above it, real resources allocated.
Heavy Gate 2
Formal Pilot-Validated → Scaling decision involving capex commit. Where AI investment becomes real money. Failure mode: pilots accumulate without crossing this gate.
4-Gate framework
VV-original early-phase evaluation framework: WHY → HOW → WHAT → WHERE/WHEN. Run at Scoped stage to test strategic fit, archetype, build feasibility, and timing before committing pilot resources.
BDN (Benefit Dependency Network)
Directed graph linking Drivers → Objectives → Benefits ← Changes ← Foundations (with Risk Constraints overlay). Methodology v0.4 §5. Three snapshot levels: Initiative-BDN, Portfolio-BDN, Strategy-BDN.
Initiative-BDN
BDN snapshot for one initiative. Versioned: v0 at Scoped, v1 at Pilot-Validated, v2/v3 in Realizing. The delta v3 − v0 is the organizational learning artifact.
Portfolio-BDN
Aggregate BDN across all active initiatives, with shared nodes merged. Quarterly cadence. Where critical-path detection (A2 analysis) and change-burden (A3) live.
Strategy-BDN
Highest-level BDN: board investment objectives → portfolio composition. Annual + on strategy events. Drives reallocation conversations.
Internal AI Lead (IAL)
Client-side counterpart to the Partner. Title varies (CAIO / Head of AI / VP AI / AI Director). Always elevated to senior + mandated by engagement end. For Dr Max: Kateřina Lesch.
Interim AI Transformation Partner
The fractional, time-boxed, board-mandated executive role VV provides. For Dr Max: Michal Lickó. ~6 months, ~25% FTE. Authority-backed, not advisory.
Day 0 / PE / M0 / M1-M6 / Advisory tail
Engagement phases. Day 0 = pre-engagement state captured but not contracted. PE = pre-engagement workstream (PE-1 to PE-5). M0 = configuration meeting where charter signs. M1-M6 = main 6-month engagement. Advisory tail = optional post-engagement support.
Track maturity index
Composite score across the 6 tracks at a given checkpoint. Q5 Partner KPI: monotonically increasing throughout engagement.
% stable-without-us
Per-track score 0-100 estimating how much the track would continue functioning if the Partner left tomorrow. Leading indicator of exit readiness. Target: ≥80% on Track 1, ≥70% on Track 2 by M6.
Healthy kill rate
Q5 Partner KPI. Target: ≥30% of initiatives killed before Pilot stage. Why: a too-low kill rate means Triage discipline is broken — bad ideas advancing.
3. Five design invariants

Non-negotiable principles

Every engagement must satisfy these. Stress-tested across all archetypes (Greenfield / Elevation / Realignment / Turnaround) and overlay dimensions (multi-market, regulatory profile).

1
Real authority, fractional presence
Board access + finance data access + decision rights on AI portfolio. Without explicit mandate, Partner becomes another expensive advisor.
2
System-setter, not daily decider
Partner designs mechanisms others run. Day-to-day decisions happen in the forums Partner stood up.
3
Successor-building from Day 1
Internal AI Lead identification (or elevation) is Week 1. Every Partner action prepares the successor (R4).
4
Exit criteria agreed upfront
Contract names "done." Q6 of the META charter is signed at M0, not negotiated at exit.
5
Clean commercial interface
Partner cannot approve VV's own scope expansions. Recusal protocol with named SLA. Three-layer fee structure (retainer + delivery + specialists) keeps trails independent.
4. Three-lens model (the framework's philosophy)

Funnels, stock & flow, BDN — three views of the same world

The methodology reasons about engagements through three complementary lenses. They are not redundant — each answers a different question and operates on a different object.

SAME ENGAGEMENT, THREE COMPLEMENTARY LENSES LOGIC LAYER · BDN Why moving X causes Y · snapshots at gates · mostly stable between snapshots causal chains PROCESS LAYER · FUNNELS Where each item sits · updated continuously as work happens per-item state SYSTEM LAYER · STOCK & FLOW Aggregate populations + rates · computed from funnel data populations + rates references sums to
Funnels
PROCESS · per-item state

Object: each individual thing (initiative, person, organization).

Question: Where does this one sit, and what moves it next?

Blind to: aggregate dynamics.

Stock & Flow
SYSTEM · populations + rates

Object: populations of things at scale.

Question: Are we accumulating enough of the right things, fast enough?

Blind to: item identity.

BDN
LOGIC · causal chains

Object: causal chains between things.

Question: If this changes, what else changes?

Blind to: time / process state.

The mental model

Same engagement, three views. BDN is the logic layer (snapshots at gates; mostly stable between snapshots). Funnels are the process layer (updated continuously as work happens). Stock & flow is the system layer (computed from funnel data; signals checked against BDN dependencies).

5. Six tracks · the operational dimensions

Six parallel dimensions of progress

Each track instantiates the three lenses to a specific domain. Tracks are not silos — six explicit cross-track couplings (§6 below) make engagement health a system property.

T1 Opportunity Pipeline funnel · funnel
Initiative motion from idea capture to value realization. Two-phase split: cheap experiments + heavy gates.
T2 People stock-and-flow · metro-map
Capability stocks across four paths. Stocks bound flows in Track 1.
T3 AI Operating System BDN · maturity-ladder
The governance backbone that runs everything else. Without this, tracks 1, 2, 4, 5, 6 are uncoordinated.
T4 Value Chain Coverage funnel · maturity-ladder
How much of the business value chain has AI initiatives mapped against it. Without coverage, pipeline starves at source.
T5 Risk & Compliance BDN · maturity-ladder
Defensible AI risk posture. Mandatory work; not optional.
T6 Value & Reporting BDN · maturity-ladder
How AI value gets measured + reported. Track 6 is the connective layer between AI initiatives and the P&L.
Multi-market overlay (§2.5)

When the engagement spans multiple markets/jurisdictions, an independent overlay applies on top of the base archetype. Per-market peer expansion, multi-DPO coordination protocol, group vs market decision split. Highest-profile market sets the regulatory floor.

6. Cross-track couplings · the wiring

Why tracks aren't silos

Engagement health is a system property. A weak Track 2 → Track 1 throughput collapses regardless of Track 1 design quality.

SIX TRACKS · CROSS-TRACK COUPLINGS · BDN CONNECTIVE LAYER (CENTER) BDN connective T1 Pipeline T2 People T3 AI OS T4 Value Chain T5 Risk T6 Value Solid lines = hard dependencies · dashed = soft (informational)
FromToMechanismWhat happens when broken
Track 4 →Track 1Map produces opportunities into Captured stagePipeline starves on inbound-only ideas; politics drives portfolio
Track 2 (B+D) →Track 1B-stocks bound Initiative Lead supply; D-stocks bound Sponsor supplyPipeline stalls at Sponsorship Gate; pilots run un-led or un-sponsored
Track 5 →Track 1Risk classification gates Scoped; re-check gates Pilot→ScalingHigh-risk initiatives slip through; regulatory exposure
Track 6 ⟲Track 1Realizing → portfolio reallocation → Sponsorship votesPipeline runs without consequence; theatre ensues
Track 3 →allForums + decisions = the OS that runs everything elseTracks operate as silos; coordination fails
Track 6 →Track 3Track 6 Level 3+ requires Track 3 Level 4 (CFO integration)Reporting cannot bridge to financial language
BDN ⤳Tracks 1, 6Snapshots inform gate decisions and benefits reviewGate decisions become opinion-driven; benefits untraceable
7. BDN connective layer (§5)

The logic layer that ties tracks together

Six node types (Drivers / Objectives / Benefits / Changes / Foundations / Risk Constraints) in a directed dependency graph. Three snapshot levels: Initiative-BDN (per initiative; v0 at Scoped, v1 at Pilot-Validated, v2/v3 at Realizing), Portfolio-BDN (aggregate, quarterly), Strategy-BDN (board investment objectives → portfolio composition; annual).

Seven named BDN-enabled analyses

  1. A1 Kill-impact — if we kill X, which benefits / objectives are hit? (at any kill decision)
  2. A2 Critical-path — which foundations/changes are shared by ≥3 initiatives? (quarterly Portfolio-BDN review)
  3. A3 Change-burden — which audience faces the most change requests across the portfolio? (quarterly + before adding new initiatives)
  4. A4 Reality-check — are claimed benefits proportional to foundations actually delivered? (at Pilot-Validated and Realizing snapshots)
  5. A5 Scarcity-event — capacity drops on resource X — which initiatives at risk? (on capacity event)
  6. A6 Strategy-pivot — objective changes — re-rank initiatives by alignment to new objectives (on strategy event)
  7. A7 Snapshot-delta — what was true at Scoped vs. Realizing — what did we learn? (at Realizing-Q4)
8. Pre-engagement workstream (§1.7)

The phase before the 6-month engagement

Distinct phase preceding the main engagement. Chargeable separately. Purpose: convert a verbal engagement commitment into a signed, executable Engagement Charter.

PRE-ENGAGEMENT WORKSTREAM · §1.7 Total: 6.5 weeks · ~35% Partner FTE · chargeable separately from main engagement retainer PE-1 Stakeholder map + in… 2.5w PE-2 Charter Q1–Q8 draft 1w PE-3 Track baseline asses… 2w PE-5 Charter signed; Day … 1w → Engagement Charter signed → 6-month main engagement (T1+T2) → optional advisory tail
StepDeliverableTypical duration
PE-1Stakeholder map + interview pass (IAL candidate, sponsor, board chair, key peer functions)2–3 weeks
PE-2Q1–Q8 META charter draft instantiated for the client1 week
PE-3Initial track baseline assessment using diagnostic matrices2 weeks
PE-4Obstacle Risk Profile run — which obstacles likely activate?Concurrent with PE-3
PE-5Engagement Charter signed; Day 1 calendar locked1 week

Total typical pre-engagement: 6–8 weeks of part-time work (~30–40% of a Partner FTE during this phase). Multi-market or high-regulation engagements extend toward the upper bound.

9. META layer · CAIO Operating Charter (§8)

How the Partner role itself operates — Q1–Q8

The META layer sits above the operational tracks. It defines how the Partner role operates: mandate, authorities, decision rights, escalation, KPIs, exit criteria, commercial interface, peer interfaces. Without META, the framework describes a transformation but not the role that runs it.

QuestionWhat it definesCalibration window
Q1 Mandate scopeGroup-wide unified / Methodology+standards central / HQ-focused / HybridPE-2 (charter draft)
Q2 Authority setMust-have / Nice-to-have / Out / Recused — by L1 IDPE-2 + M0 negotiation
Q3 Decision rightsDecide / Propose / Recommend / Recused — per decision typePE-2 + M0
Q4 EscalationBidirectional (R21) — Partner can escalate up; engagement can escalate Partner up. Recusal SLA.PE-2; signed at M0
Q5 Partner KPIsOperating-quality measures (track maturity index, healthy kill rate, decision register completeness)PE-2; reviewed monthly
Q6 Exit criteriaHard (8) + soft (5) criteria. Regulatory profile overrides Track 5 floor. Multi-market floor rule.Signed at M0; non-negotiable thereafter
Q7 Commercial interfaceThree-layer fee + pre-engagement + bonuses. Recusal protocol.PE-2; signed at M0
Q8 Peer interfacesPatterns + owned issues + conflict-prone areas per C-suite role. Multi-market expansion.PE-2; reviewed quarterly
10. Engagement velocity model (§7)

No fixed phases — adaptive parallel tracks + 4-weekly checkpoints

Phase-based plans (discovery month → design quarter) don't fit clients arriving with prior failures. Replaced by parallel tracks moving from Day 1 + 4-weekly velocity checkpoints. For each track: Where does it sit on stages/levels? Delta vs. last checkpoint? Current blocker? % stable without us (0–100; leading indicator of exit readiness)? Risks/issues + escalation flag.

Plus quarterly Portfolio-BDN review (A2 critical-path + A3 change-burden + A4 reality-check).

11. Authority Erosion × Elevation (§2.4) — dominant pattern

The risk every Elevation engagement must counter actively

Critical for Elevation engagements

In Elevation engagements, the existing Internal AI Lead's authority is the load-bearing structure of the entire transformation. Every Partner action is a stress on that structure. Authority Erosion is not a risk that may activate — it is the dominant pattern requiring active counter-pressure throughout the engagement.

Mandatory counter-mechanisms (Elevation)