3 — Assess Value/Risk & Trace Lifecycle Responsibilities
← Predict & Inventory · Lab Home · Next → Requirements Before Technology
Lab B — Assess value, risk, and management priority
Important nuance: Chapter 1 does not prescribe one universal data-valuation formula. This lab uses consistent qualitative High / Medium / Low ratings as a Meridian training method, not a DAMA standard.
For the same six assets from your inventory, rate and justify:
- operational dependency;
- decision/revenue benefit;
- replacement difficulty;
- quality-loss impact;
- privacy/security/misuse risk;
- enterprise reuse; and
- overall management priority.
Every rating needs a one-sentence reason. A rating without a reason is not evidence.
Revisit your prediction
What changed from your original predictions? Which asset moved up or down in priority, and what evidence caused the change?
Save as CH01-B — Value & Risk Assessment.
Lab C — Trace lifecycle responsibilities, not just lineage
Choose Customer plus one other asset. Map what happens across these management stages/events:
- Plan / define
- Create / obtain
- Store
- Move / transform
- Use
- Maintain / enhance
- Share
- Retain / dispose
At every stage, record at least one relevant Data Quality, Metadata, or risk responsibility.
Suggested working structure:
| Lifecycle stage | Customer — what happens? | Quality / Metadata / risk concern | Second asset — what happens? | Quality / Metadata / risk concern |
|---|---|---|---|---|
| Plan / define | ||||
| Create / obtain | ||||
| Store | ||||
| Move / transform | ||||
| Use | ||||
| Maintain / enhance | ||||
| Share | ||||
| Retain / dispose |
🔑 Deciding distinction
- Lifecycle asks what management stages/events data passes through across its life.
- Lineage asks where a particular data set came from, how it moved or changed, and where it went.
- SDLC is the development lifecycle of a system or solution.
Save as CH01-C — Lifecycle Management Map.