Skip to content

← Applied Labs

Meridian Cross-Chapter Capstones & Incidents

Status: Roadmap established; detailed execution packages are built only when the 00C route reaches them and the necessary chapter foundations exist.

Authoritative formatted roadmap: Google Doc · PDF

Drive folder: https://drive.google.com/drive/folders/1wFauMYRFBEJmAkmQKl1GrYJBwqgvSeXo

Purpose

Chapter labs deliberately focus attention. Capstones remove some of that scaffolding and require the learner to decide which Data Management areas lead, which support, what evidence is needed, and what order of response is defensible.

A capstone is not “all chapters at once.” It is a realistic cross-domain business problem with bounded acceptance criteria.

Capstone roadmap

CAP-01 — Customer 360 Trust Crisis

Meridian wants a trusted enterprise customer view, but CRM, POS and Service disagree on identities, definitions and quality.

Likely areas: Governance, Data Modeling & Design, Integration & Interoperability, Reference/Master Data, Metadata, Data Quality, with Security/ethics where appropriate.

Core evidence: definitions/decision rights, source comparison, match/survivorship reasoning, lineage/metadata, quality evidence, trusted-view design and explanation.

CAP-02 — Revenue KPI Cannot Be Traced

Finance challenges an executive revenue measure and the organization cannot quickly reconstruct its source, transformations, business definition and analytical logic.

Likely areas: Data Architecture, Integration & Interoperability, Data Warehousing/BI, Metadata, Data Quality, Governance.

Core evidence: source-to-target path, definition comparison, transformation logic, lineage, reconciliation and controlled KPI decision.

CAP-03 — Restricted Customer Data Exposure

A reporting/analyst path exposes synthetic sensitive customer attributes beyond the role’s business need.

Likely areas: Data Governance, Data Security, Metadata/classification, Organization/Roles, Data Quality/lineage where needed to understand exposure.

Core evidence: classification, access/CRUD analysis, role/privilege evidence, least-privilege correction, governance/approval record and retest.

CAP-04 — Product & Reference Definition Split

PIM, reporting and local spreadsheets disagree on product/category definitions and controlled codes.

Likely areas: Governance, Reference/Master Data, Metadata, Data Quality, Integration, Modeling.

Core evidence: definition/reference comparison, decision rights, controlled code set/hierarchy, mapping/remediation and downstream validation.

CAP-05 — Meridian Data Management Transformation

Use the accumulated lab evidence to propose and defend a coordinated next-stage Data Management operating model and improvement roadmap.

Likely areas: enterprise synthesis across Governance, Architecture, Quality, Metadata, Master/Reference, Security, Organization/Roles, Maturity and Organizational Change.

Core evidence: maturity/evidence assessment, priority decisions, dependencies, operating roles, roadmap, adoption/change plan and executive explanation.

Capstone execution standard

For every capstone:

  1. Diagnose the business symptom before naming a tool.
  2. Select a lead DMBOK Knowledge Area for the current problem and justify supporting areas.
  3. State required evidence before changing the environment.
  4. Use the minimum necessary technology.
  5. Preserve before/after evidence.
  6. Record key decisions and accountable roles.
  7. Test a changed fact or counterexample.
  8. Finish with an integrated DMBOK debrief.
  9. Rebuild/defend the reasoning with reduced scaffolding.

Source gate

The roadmap may name future cross-domain work, but a detailed capstone package must not invent DAMA rules from chapters that have not yet been read/source-checked. 00C controls when each capstone becomes executable.