4 — State the Business/Data Requirement Before Naming Technology

← Value/Risk & Lifecycle · Lab Home · Next → Charter, Scope & Roadmap

For each Meridian problem below, write the business/data requirement first. Only after the requirement is clear may you suggest supporting technology or an implementation technique.

Meridian problem	Business/data requirement — write first	Possible supporting technology later	Why technology alone is insufficient
MCG-002 — Active customer definition conflict
MCG-004 — Revenue KPI cannot be traced
MCG-006 — Over-permissioned analyst
MCG-009 — Weak Metadata

Reasoning rule

A valid requirement should describe the business meaning, quality, access, lifecycle, ownership, traceability, or risk outcome that must be achieved.

Examples of the kind of sequencing expected—not answers to copy:

First: define what “active customer” means, who decides, where the definition applies, and how disagreement is resolved.
Later: determine what catalog/master-data/governance technology could support that agreed requirement.

First: define what evidence is required to trace a KPI from report to source and transformation.
Later: determine what lineage/catalog/BI features could capture or display that evidence.

🚨 Application trap: “Install a tool” is not a complete Data Management requirement.

Evidence

Save your completed analysis as CH01-D — Business/Data Requirements Before Technology.

The important evidence is your reasoning order: requirement first, implementation second.