Scenarios 11–15

Scenario 11 — Executive Wants Level 5 Now

Situation: leadership wants every KA at L5 within twelve months from current L1–L2 evidence.

Primary problem: unrealistic acceleration/targeting.
Leading KA: DMMA.
Supporting: Data Governance; Organizational Change.
Roles: executives, assessment team, roadmap owners.
Best action: explain ordered progression, prerequisites, cost/benefit/impact; create staged targets.
Weaker response: agree to skip stages.
Changed fact: a specific capability already exhibits L4 characteristics and has justified need/resources → L5 may be realistic there.
Source: pp. 503, 507–508, 515.

Situation: most architecture/policy evidence is 18 months old; participants claim it still reflects current practice.

Primary problem: stale-evidence risk.
Leading KA: DMMA.
Supporting: Data Architecture; Metadata Management.
Roles: assessors, repository owners, governance.
Best action: flag age/uncertainty, balance rating, seek current corroboration.
Weaker response: official repository automatically equals current truth.
Changed fact: current execution evidence proves old documents remain active/accurate → they can support rating with corroboration.
Source: p. 518.

Situation: workshops collapse into system debates because participants lack shared Data Management vocabulary.

Primary problem: communication/readiness risk.
Leading KA: DMMA.
Supporting: Data Governance; Organizational Change.
Roles: assessment lead, sponsor, participants.
Best action: orient participants to concepts and concrete business problems before detailed rating.
Weaker response: push ahead; criteria will be interpreted inconsistently.
Changed fact: vocabulary is shared but evidence missing → shift to evidence collection.
Source: p. 518.

Situation: maturity model requires one vendor platform and dictates implementation.

Primary problem: framework-selection misfit.
Leading KA: DMMA.
Supporting: Data Governance; technology strategy.
Roles: assessment lead, procurement, executives.
Best action: prefer neutral, technology-neutral, non-prescriptive, repeatable framework fitting objectives.
Weaker response: tool alignment equals maturity integrity.
Changed fact: objective is specifically vendor-platform adoption readiness, not general DM maturity → tool-specific assessment may fit, but it is a different objective.
Source: pp. 516–517.

Situation: selected framework is mapped to DMBOK KAs, activities, deliverables to identify hot spots.

Primary problem: appropriate DMBOK-supported assessment planning.
Leading KA: DMMA.
Supporting: all mapped KAs.
Roles: assessment designers, DM practitioners.
Best action: use DMBOK as structured checklist/mapping aid while preserving selected framework/method.
Weaker response: replace framework with ad hoc DMBOK scoring.
Changed fact: if an internal maturity framework is deliberately built from DMBOK, it must define levels, scoring, repeatability, governance; a checklist alone is not a maturity model.
Source: p. 517.