Skip to content

Evidence & Lab Journal Standard

← Evidence Home

This page translates the 00B Lab Execution, Evidence & QC Standard into a day-to-day evidence routine.

Minimum evidence package

For each meaningful lab, preserve evidence that shows:

  • Input / before state — source, initial condition, assumption, or problem.
  • Action / decision — query, script, diagram, policy, analysis, decision, or other work performed.
  • Output / after state — result, changed condition, metric, repaired state, or approved decision.
  • Interpretation — what the result means in business/Data Management terms.
  • DMBOK debrief — what concept the work made concrete and what nearby concept must not be confused with it.
  • Independent rebuild result — pass / partial / fail and what still needs support.
  • Error/repair note — only when a real mistake or weak pattern occurred.

Evidence types

Type Examples What it proves
Executable logic SQL, Python, validation query What operation/test was performed
Object/configuration schema/table definition, role/view DDL What the environment contains
Business artifact charter, decision log, glossary, RACI, retention rule How a management decision was operationalized
Result query output, reconciliation, DQ score, dashboard What happened or was discovered
Interpretation journal/debrief That you understand meaning, not only procedure

Lab journal questions

After a lab, answer concisely:

  1. What business problem was I solving?
  2. Which DMBOK concept was primary?
  3. Which supporting concepts appeared?
  4. What did I predict before doing the work?
  5. What did I actually observe?
  6. What surprised me or changed my thinking?
  7. What did I break/change/diagnose, if applicable?
  8. How did I repair or decide?
  9. Could I rebuild the learning-critical portion without the instructions?
  10. What evidence proves completion?
  11. What distinction do I need to remember?
  12. Did I make a real mistake that should enter Error Repair later?

Completion rule

Do not mark a lab complete merely because files exist. You must be able to explain, perform, interpret, transfer, and prove the work.