Checklist

Data Strategy for Discovery — Instrumentation & Governance Checklist (Interactive)

Interactive checklist to verify telemetry, instrumentation, and lightweight governance for discovery, experiments, and AI prototyping. Includes guided checks, quick-fix suggestions, and a small prioritized instrumentation backlog template you can save.

Interactive Tool

Data Strategy for Discovery — Instrumentation & Governance Checklist

Use this checklist to confirm your team has the minimal, practical data practices needed to explore, experiment, and reuse trusted datasets for discovery work. The form is intentionally lightweight: focus on enabling safe experimentation, reproducible results, and a prioritized instrumentation backlog rather than heavy governance. Save the results so your team can track progress and hand off fix items.

How to use: Answer each yes/no question, add short notes where helpful, mark quick fixes you intend to apply now, and add up to five backlog items with priority and effort estimates.

Who is filling out this checklist?
YYYY-MM-DD or natural date
Are the core metrics for your highest-value experiments identified and documented?
List the key metrics or link to the doc (brief).
Consistent event names and properties make experiment analysis reliable.
Briefly describe convention or paste a link to the spec.
Are owners and access roles clear for datasets used in discovery?
Name owners or note unresolved ownership questions.
Minimal privacy and retention rules should be in place before opening data for experiments.
List any compliance constraints or required approvals.
Is sampling documented so experiment results are reproducible and not biased?
Describe sampling strategy or known limitations.
Are there automated checks or alerts for missing/invalid telemetry that would invalidate experiments?
List key checks or current gaps.
Does dev/test have suitable non-production data when needed?
Describe fixtures, pipelines, or gaps.
Can you reconstruct key events after an experiment or incident?
List log types or recent examples where logs helped.
Common inexpensive fixes that reduce risk and accelerate discovery.
Use this to indicate how many of the backlog slots below you will fill.
Short title for the instrumentation gap or task (leave blank if none).
One-sentence description of the task or gap.
Choose priority to help triage work.
Estimated effort to fix: helps prioritize (small <1d, medium 1-5d, large >1w).
(Optional)
(Optional)
(Optional)
(Optional)
(Optional)
(Optional)
(Optional)
(Optional)
1 = low, 5 = high
1.0 10.0
Summarize immediate actions, owners, or blockers.
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.