Dr. Max — Day 0 (current reality)
Elevation install · GroupWide · multi-market
OBSTACLES · 19 ENGAGEMENT-KILLER PATTERNS?
Obstacles
Engagement-killer patterns. Each obstacle has trigger conditions across configuration; when conditions fire (any/all), the obstacle becomes active. Active obstacles paint affected downstream nodes red in META-BDN.8 active · 2 latent — clear the red list to ship
Each card shows the trigger conditions firing, diagnostic signals to look for, and recovery actions. Filter by status above. Click any condition row → opens the configuration tab where you can fix it.
Validate with Kateřina
For each ACTIVE obstacle: is this real for Dr. Max? Are the recovery actions sensible? For each INACTIVE: should it actually be active (something we missed)? Anything missing entirely (Dr. Max-specific patterns we don't model)?
O-001HIGHPipeline Stall at Gate 2active
Initiatives accumulate at Pilot-Validated; Scale decisions don't happen
Business impact
Medium VaR4–8w delay€100K–€300Kschedulecostscope
Initiatives accumulate at Pilot-Validated; pilot budgets are spent without scale-up commitment. Engagement loses credibility within 60 days as the Sponsor sees outputs but no decisions.
On a €1M Elevation engagement, 10–30% of pilot value is at risk if Gate 2 stalls; assumes 3–5 pilots in flight.
Trigger (ANY) · 4/4 met
Diagnostic signals
- Initiatives accumulate at Pilot-Validated
- Scale decisions deferred ≥ 2 cycles
Recovery actions
Affected downstream (5)
L4-401L5-504L6-603L7-702L7-703
O-003HIGHRisk Function Disengagedactive
Regulated profile but CRO/DPO not integrated; risk classification skipped
Business impact
Large VaR8–16w delay€250K–€750Kcompliancerelationshipschedule
Risk classifications skipped; one bad initiative kicks off and blows up audit/regulatory window. Pharma-high regulatory profile makes this catastrophic — potential SUKL / EMA exposure.
Compliance remediation in pharma typically takes 4–6 months and €250–750K; reputational tail can extend.
Trigger (ANY) · 3/5 met
Diagnostic signals
- Risk classifications not happening at Scoped
- Vendor due-diligence skipped
- We'll do it later pattern
Recovery actions
Affected downstream (3)
L4-405L6-604L7-704
O-013HIGHSponsor Escalation Stalledactive
Engagement begins with a sub-C-suite sponsor; CEO never engages substantively; engagement stays advisory and never reaches structural authority
Business impact
Large VaR8–20w delay€300K–€800Kscoperelationshipschedule
Engagement begins with sub-C-suite sponsor; CEO never engages substantively; engagement stays advisory and never reaches structural authority. Outcomes degrade to slide-decks.
Without CEO escalation, ~30–60% of expected engagement value is unreachable; Elevation archetype amplifies this risk.
Trigger (ALL) · 3/3 met
Diagnostic signals
- Sponsor cannot make decisions requiring CFO/CIO sign-off without escalation
- CEO has not attended any Configuration or Portfolio Council session by M2
- Major decisions deferred or routed around Partner
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)
Affected downstream (4)
L1-129L4-401L6-601L7-701
O-014HIGHMulti-Market Parity Driftactive
Multi-market engagement; one market advances 1+ track maturity levels ahead of another; cross-market AI capability becomes fragmented
Business impact
Medium VaR6–12w delay€150K–€400Kscopecost
Markets diverge — different vendors, different decision cadences, different KPIs. Re-alignment cost grows quadratically with time-to-correct.
Multi-market parity drift in 6 markets typically costs €25–65K/market/quarter to re-align; Dr. Max scale.
Trigger (ANY) · 2/3 met
- ●Right to interview anyone (incl. cross-market)·is absent or deniedL1-113→
- ●Cross-market sync forum·is not stood upL3-326→
- ○track.parity_stddev·is above thresholdtrack.parity_stddev
Diagnostic signals
- Track 3 maturity gap between markets > 1 level by M3
- Initiatives originated in one market not propagated to others
- Country MDs not represented on Portfolio Council
Recovery actions
- Stand up cross-market sync forum (monthly)
- Rotate Champions across markets
- Mandate seat for each market MD on AI Council
Affected downstream (3)
L4-401L4-403L7-702
O-008HIGHVV Commercial Captureactive
Recusal protocol breached; Partner advocates for VV scope expansion; ethics violation
Business impact
Critical · engagement-killing0–4w delayrelationshipscope
Recusal protocol breached; Partner advocates for VV scope expansion; ethics violation. Potential to be told to leave the engagement entirely.
Engagement-killing. Full engagement value at risk. No € band defensible.
Trigger (ANY) · 1/3 met
- ○Recusal protocol (commercial)·is not enforcedL3-321→
- ○partner_in_commercial_conversations·is truepartner_in_commercial_conversations
- ●peer.CIO·is missing or inactivepeer.CIO→
Diagnostic signals
- VV proposals discussed in operational forums
- Partner advocates for expanded VV scope
- Conflict-of-interest disclosure not happening
Recovery actions
- Reset recusal explicitly with client commercial counterpart
- Document case in conflict log
- Replace Partner in extreme cases
Affected downstream (2)
partner_credibilityethical_exposure
O-010HIGHHeavy-Gate Decision Driftactive
Forums standing but not deciding; gates become advisory; portfolio prioritization becomes politics
Business impact
Large VaR4–12w delay€200K–€600Kschedulequality
Forums standing but not deciding; gates become advisory; portfolio prioritization becomes politics. Engagement output quality drops as the methodology is used for theatre.
Decision drift typically delays 4–12 weeks of pilot/scale advancement at €50–100K/week opportunity cost.
Trigger (ANY) · 1/4 met
- ○L3-302_chair·is not partnerL3-302_chair→
- ○decisions·is deferred routinelydecisions
- ○Decision register·is sparse or missingL3-325→
- ●peer.CIO·is missing or inactivepeer.CIO→
Diagnostic signals
- 'We'll decide next month' pattern at Portfolio Council
- Decision register sparse
- Initiatives advancing without explicit gate decision
Recovery actions
Affected downstream (1)
pipeline_integrity
O-022HIGHAI Act Compliance Stalledactive
Regulated organization approaching EU AI Act deadline; high-risk AI inventory not catalogued, conformity assessment not staffed; engagement timeline collides with compliance deadline
Business impact
Critical · engagement-killing4–12w delay€500K–€2Mcomplianceschedulecost
EU AI Act conformity assessment skipped or delayed. With 3–6 month pressure, the legal exposure window closes. Potential market access loss + regulatory penalties.
AI Act non-compliance penalties up to 7% of global turnover (Annex IV). For Dr. Max (€2.9B revenue), even a partial finding is materially significant.
Trigger (ANY) · 1/3 met
- ○EU AI Act deadline pressure·is Months under 3L0-010→
- ●AI conformity assessment process·is not stood upL3-329→
- ○ai_act_inventory·is absentai_act_inventory
Diagnostic signals
- EU AI Act high-risk applicable but no inventory of AI systems by M2
- No named owner for conformity assessment
- Compliance work seen as Legal/IT-only, not engagement workstream
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
Affected downstream (4)
L1-130L4-405L6-606L7-703
O-015MEDVendor Stack Fragmentationactive
Multiple AI vendors deployed independently across functions; no unified ops layer; integration debt compounds; vendor lock-in by component
Trigger (ANY) · 2/3 met
- ●peer.CIO·is missing or inactivepeer.CIO→
- ●Vendor portfolio governance·is not stood upL3-327→
- ○vendor.unified_ops_layer·is absentvendor.unified_ops_layer
Diagnostic signals
- More than 3 distinct AI vendors in deployment without integration plan
- Each vendor reports to a different business owner
- No common observability / data layer across vendors
Recovery actions
- Force unified AI ops layer ownership under CIO
- Establish vendor portfolio review at AI Council
- Document integration interfaces in BDN
Affected downstream (3)
L4-403L5-504L6-603