Checklist

Data Infrastructure & Instrumentation Checklist for Learning

An actionable, savable checklist teams can use before experiments, KPI huddles, or data-product handoffs. Covers event taxonomy, ownership, instrumentation verification, test data, schema versioning, retention, discoverability, and a lightweight data product contract capture.

Interactive Tool

Data Infrastructure & Instrumentation Checklist for Learning

Use this checklist to confirm the events, metrics, and datasets needed for experiments, huddles, and measurement-driven decisions are instrumented, verified, and discoverable. Complete the checklist as part of experiment readiness, data-product handoff, or pre-huddle preparation. Save a copy of each submission so teams can track progress, surface recurring issues, and demonstrate signal trustworthiness.

Tips: Be concrete about dataset identifiers and evidence. If an item is blocked, note the blocker and an owner so the next huddle can remove the obstacle.

Check each item that is true and supported by evidence or links below.
Person responsible for ongoing correctness and escalation.
Useful for rapid follow-up in huddles.
List dataset names, table paths, streams or topic names. Include prod/test separation.
Links to dashboards, test results, logs, or screenshots that prove items checked above.
Has the instrumentation been validated with test data and smoke tests?
E.g. v1.2.0 or schema ID used in the registry.
How breaking changes are managed.
How long raw and derived data are retained. Leave blank if policy is link-only.
Are dataset permissions and RBAC rules documented and enforced?
Has the consumer and producer agreed to a lightweight contract (owner, freshness, SLA, expected semantics)?
Link to the contract document or ticket. Leave blank if none.
Be explicit (e.g., flaky ETL, missing producer, partial historical coverage). Include mitigation or next step.
How much would you trust this signal for a decision right now?
1.0 10.0
YYYY-MM-DD or relative (e.g., in 2 weeks). Useful for huddle agendas.
Anything else the huddle should know (links to runbooks, escalation paths, contact on-call).
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.