M0 Prep Brief — Dr. Max — Day 0 (current reality)

Design invariants — pre-meeting check

Track baselines (per methodology §10 — current state, NOT "behind typical")

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 — in PE-2 (charter draft) / PE-3 (track baseline).

Five design invariants — pre-meeting check (v0.4 §1.3)

Each invariant must hold before the M0 conversation. Mark [x] only when verifiable, [!] if there's a known gap to surface in the meeting.

• ○ Real authority, fractional presence — Mandate scope (Q1) drafted; authority asks (Q2) listed; pending charter signature at M0.

- Why it matters: Without explicit board mandate + finance access + portfolio decision rights, Partner becomes another expensive advisor. Verify before committing.

• ○ System-setter, not daily decider — Partner role = Michal as Interim CAIO + VV delivery. Standing recusal on commercial framing.

- Why it matters: Partner designs forums + mechanisms others operate. If Partner is making daily calls, the engagement won't exit cleanly — successor will inherit Partner's decision queue.

• ✓ Successor-building from Day 1 — Internal AI Lead (Kateřina) named, internal, named+active. Authority Erosion × Elevation counter-mechanisms required throughout (visibility-elevation rituals; attribution discipline; recusal on Lead's domain decisions).

- Why it matters: Internal AI Lead (Kateřina) is the engagement's exit vehicle. Every week of weak mentorship buildup pushes exit readiness back. R4 — engagement is for the successor, not the Partner.

• ○ Exit criteria agreed upfront — 8 hard + 5 soft criteria drafted (Q6); pending sign-off at M0.

- Why it matters: Q6 hard + soft criteria signed at M0, non-negotiable thereafter. Without upfront agreement, "done" becomes a renegotiation at M5 — Partner loses leverage.

• ○ Clean commercial interface — 3-layer fee structure drafted (Q7); recusal SLA 5 BD; CFO Bornemann named as commercial counterpart when Partner recused. Pending charter signature.

- Why it matters: Recusal protocol (L3-321) + 3-tier fee structure (T1/T2/T3) keep Partner out of VV scope decisions. Without it, every VV scope expansion looks self-dealing.

1. Engagement context

Archetype: Elevation — Amplify an existing internal AI lead — capability exists but lacks authority, scope, or executional discipline. Partner extends, never replaces.

Internal AI Lead state: Senior, under-authority

Board state: Aware

EU AI Act pressure: 3–6 months

PE owner engagement: Active

Multi-market: Yes

Track baseline read (methodology v0.4 §10 application read)

Engagement is in pre-engagement (PE-3) — the state below is the methodology's expected baseline at this phase, NOT "behind typical."

Track	Current state (PE-3)	Target at exit
T1	Stage 1–2 (Captured exists, no flow)	≥ 80% stable-without-us
T2	A1 thin, B0–1 embryonic, C partial, D mixed	A2 ≥60%; B-stock ≥ pilot demand; D2 100%
T3	Level 0–1 (Absent / Chartered)	Level ≥ 5 (Self-running)
T4	Level 0–1 (Reactive / Anchor mapped)	Level ≥ 3 (group); Level 1–2 per-market acceptable
T5	Level 1 (Classified — some classification likely exists)	Level ≥ 4 (Monitored)
T6	Level 0 (Opaque)	Level ≥ 3 (P&L-linked); Level 4 strongly preferred

Aggregate impact at risk

If unresolved, currently-active obstacles cumulatively introduce 34–84 weeks of delay. Illustrative € exposure: €1.5M–€4.8M across 6 measured obstacles.

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

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

2. People — named, inactive, unknown

Already engaged (2):

• Miguel Martins da Silva (CSCO) — Already AI-active (VusionGroup, Geek+, Rinkai, dark warehouse).
• Kateřina Lesch (HeadOfAI) — Newly appointed Head of AI at Dr. Max (internal). Was the engagement introducer in her former Deloitte / EmbedIT role; now holds the seat we needed her to influence. Reports to CIO (likely; verify with Kateřina). Methodology implication: O-031 External Champion Conflict no longer applies.

Named but not yet engaged (6):

• Penta Operating Partner (PEOperatingPartner) — UNKNOWN — Penta operating partner not identified; open question for validation.
• Leonardo Ferrandino (CEO) — CEO since 2016, target sponsor.
• Thomas Bornemann (CFO) — Capex sign-off, Heavy Gate 2 counterparty.
• Luca Demarchi (CIO) — Per 2024 sustainability report; tenure UNCERTAIN — possible move to Bata Group.
• Dimitrios Tritaris (CMCO) — Owns 12.5M Benefit Card members, e-shop, marketplace, retail media.
• Ivo Šenkyřík (HeadMA) — Continuous M&A pipeline (Žalfija Q3 2025 + ongoing).

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

1. 7 high-severity obstacles firing — engagement risk profile is elevated

• When: This week
• Who: AR + Michal
• Why: When 5+ HIGH-severity obstacles fire concurrently, the engagement is structurally fragile. Consider whether this is the right week to commit to M0, or whether to invest 1–2 weeks in pre-mitigation.
• Evidence: 7 obstacles with severity=high are currently active

2. 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 (Sponsor Escalation Stalled) is active
• Reduces / resolves: O-013

3. Stand up L3-329 (AI conformity assessment process) within 30 days

• When: Next 30 days
• Who: CIO + GC
• Why: EU AI Act pressure is Months_3_to_6 and the conformity assessment process is not yet stood up. The legal exposure window is closing; this is a hard deadline, not a soft target.
• Evidence: L0.ai_act_deadline_pressure = Months_3_to_6; L3-329 state = not_stood_up; O-022 (AI Act Compliance Stalled) is active
• Reduces / resolves: O-022

4. Negotiate 3 authorities during M0

• When: Before M0
• Who: AR + Sponsor
• Why: 3 L1 authorities are currently Out and are gating active obstacles. These are the actual horse-trade items for the M0 conversation.
• Evidence: Authorities to negotiate: L1-108, L1-129, L1-113
• Reduces / resolves: O-001, O-003, O-008, O-010, O-013, O-014, O-015, O-022

5. Charter cross-market sync forum (L3-326)

• When: Next 30 days
• Who: IAL
• Why: Multi-market engagement with no cross-market sync mechanism. Markets will diverge (different vendors, different decision cadences) within the first quarter unless the sync is stood up early.
• Evidence: L0.multi_market = true; L3-326 state = not_stood_up; O-014 (Multi-Market Parity Drift) is active
• Reduces / resolves: O-014

6. Confirm Luca Demarchi still in seat (or identify successor)

• When: This week
• Who: AR
• Why: CIO is the structural reporting line for the Internal AI Lead and the convening counterparty for Track 3. If the seat changes during the engagement, the AI Council charter has to re-anchor.
• Evidence: people.CIO notes flag tenure uncertainty: "Per 2024 sustainability report; tenure UNCERTAIN — possible move to Bata Group.…"

4. Authority asks — ordered for the M0 conversation

Methodology says 5 authorities should be Must for an Elevation engagement. Currently all are Out. Order suggested by category for the conversation:

Information (1)

• L1-113 — Right to interview anyone (incl. cross-market)

- What: Authority to interview anyone in the organization (cross-market, cross-function) without permission gating.

- Why ask: Engagement diagnosis requires direct access to people — frontline, Initiative Leads, sponsors, peers. Permission-gated access slows everything to a crawl.

Hiring (2)

• L1-116 — Co-design Internal AI Lead role

- What: Authority to co-design the Internal AI Lead role — JD, scope, reporting line, target compensation.

- Why ask: Successor-building from Day 1 (design invariant #3) requires the Lead's role be designed properly. Co-design ensures it isn't just bolted onto an existing role.

• L1-117 — Veto on succession candidate

- What: Authority to veto succession candidates for the Internal AI Lead seat.

- Why ask: Wrong-fit Lead is a Realignment situation. Partner needs the ability to block a bad hire before it happens.

Communication (2)

• L1-129 — Direct board access on AI

- What: Direct authority to communicate with the board on AI matters (no IT/CIO gating).

- Why ask: Board literacy + sponsor coaching require direct access. Mediated communication dilutes the message and creates gatekeeper dynamics.

• L1-130 — Speak to regulators on AI

- What: Authority to speak to regulators on AI matters (or accompany Legal/CRO).

- Why ask: Regulator engagement is now AI-specific (EU AI Act, sectoral). Partner often has the deepest AI context; regulator wants to talk to who actually knows.

5. Active obstacles to surface in M0

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

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

Triggered conditions:

• L1-108 is absent_or_denied
• 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-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-008 — VV Commercial Capture [severity: high]

Recusal protocol breached; Partner advocates for VV scope expansion; ethics violation

Triggered conditions:

• peer.CIO is missing_or_inactive

Recovery actions:

• Reset recusal explicitly with client commercial counterpart
• Document case in conflict log
• Replace Partner in extreme cases

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

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-013 — Sponsor Escalation Stalled [severity: high]

Engagement begins with a sub-C-suite sponsor; CEO never engages substantively; engagement stays advisory and never reaches structural authority

Triggered conditions:

• peer.CEO is missing_or_inactive
• L3-318 is not_stood_up
• L1-129 is absent_or_denied

Recovery actions:

• Pre-stage CEO at one Configuration session before M0
• Use first decision requiring exec sign-off as natural escalation moment
• Make sponsorship escalation an explicit charter milestone (not implicit)

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
• ○ PE operating partner is identified (if PE-owned) — PE op partner identity unknown — ask Kateřina
• ○ 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 — AI Act pressure is tight; conformity scope must be defined before commitments

---

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