From curiosity to validated scope — Discovery playbook

A practical, staged playbook that helps teams convert curiosity into a validated, high‑impact research scope. Includes clear activities, timeboxes, scoring rubrics, a one‑page scope canvas, a rapid evidence checklist, pilot planning guidance, and decision‑gate templates that reduce wasted effort and build early alignment.

Welcome

Use this playbook when an idea or curiosity feels promising but the path to useful research is unclear. The goal is a compact, testable research scope that fits your resources and has clear impact criteria. This playbook keeps things focused, reduces wasted effort, and helps teams align before they invest in experiments.

When this helps

  • You're juggling several candidate questions and need a quick way to prioritize.
  • You want to avoid running expensive pilots before core uncertainties are tested.
  • You need a one‑page artifact to align stakeholders and secure modest resources.

Desired outcomes

  • A validated scope statement that describes the question, why it matters, and how success will be measured.
  • A short ranked list of hypotheses with simple novelty/feasibility/impact scores.
  • A micro‑pilot plan that tests the core uncertainty with minimal time and cost.
  • Clear go/no‑go criteria for next steps.

Stages

  1. Problem framing

    Map users and stakeholders, define the undesired gap or opportunity, and describe desired outcomes. Identify one or two success metrics you can measure quickly (e.g., adoption rate, measurement sensitivity, time saved).

    Activities: stakeholder map, outcome statement, 1–2 measurable success metrics.

    Artifacts: one‑page scope canvas (template provided below).

  2. Quick literature & data scan

    Spend a short, timeboxed scan (15–60 minutes) to surface existing evidence: recent papers, preprints, internal data, patents, or product notes. Look for direct contradictions, supporting signals, and practical gaps you could address.

    Use the rapid evidence checklist to capture what you find and how confident you are.

  3. Hypothesis shortlist

    Create a short list of candidate hypotheses. Score each against three practical dimensions: novelty (how new is this contribution?), feasibility (can we test it with our resources?), and impact (would success change decisions, outcomes, or value?). Use a simple 1–5 scale and compute a summed score to help prioritize.

  4. Feasibility checks

    Quickly verify constraints that might stop the work: required equipment, personnel, ethical or regulatory approvals, data access, and timeline. If any constraint is blocking, note mitigations or decide to pause the idea.

  5. Pilot plan

    Design the smallest experiment that directly tests the core uncertainty. State the objective, the minimum intervention or measurement needed, the primary metric, the expected effect size that would change your decision, estimated duration, and required resources.

    Timebox pilots to reduce sunk costs—short, focused tests create learning fast.

  6. Decision gates

    Set clear go/no‑go criteria before running the pilot. Record what evidence will count as success and what follow‑up will occur if the result is ambiguous. Define next steps for both positive and negative outcomes.

Templates & tools (inline)

One‑page scope canvas (use to align stakeholders)

Title / Short question: __________

Why it matters (pain, opportunity, outcome): __________

Key stakeholders / users: __________

Core uncertainty (what we don't know): __________

Primary success metric: __________

Quick evidence summary (1–3 bullets): __________

Top hypothesis (short): __________

Estimated effort & resources: People: ____ Time: ____ Cost: ____

Decision gate / target evidence for go: __________

Rapid evidence checklist

  • Is there a recent peer‑reviewed result directly relevant? (Yes / No)
  • Are there internal data that can be quickly queried? (Yes / No)
  • Are there known patents or IP constraints? (Yes / No)
  • Any obvious fatal flaws or ethical/regulatory blockers? (Yes / No)
  • Confidence in the evidence (Low / Medium / High) — short note:

Hypothesis scoring (example)

For each candidate hypothesis, score 1–5 on:

  • Novelty: 1 (well‑known) to 5 (clearly new)
  • Feasibility: 1 (unlikely with available resources) to 5 (straightforward)
  • Impact: 1 (minor) to 5 (transformative)

Sum the scores and prioritize hypotheses with higher totals and clear, testable core uncertainties.

Pilot plan template

Objective: What question will this pilot answer?

Core measure: Primary metric and how it is measured.

Minimum intervention / instrument: What is the smallest change or measurement needed?

Sample / scope: Who or what will be included?

Duration: Estimated time to collect interpretable evidence.

Resources: People, data, equipment, approvals.

Success threshold (go criteria): Predefined value or effect size that will trigger continued investment.

Decision gate checklist

  • Was the primary metric measured reliably?
  • Did results meet the success threshold?
  • Are there secondary signals that change interpretation?
  • Is there a clear next experiment or scale plan if successful?
  • Is there a documented stop/abandon plan if results are negative?

Attachments & suggested artifacts

  • One‑page scope canvas (printable PDF / interactive form)
  • Rapid evidence checklist (spreadsheet or form)
  • Hypothesis scoring worksheet
  • Pilot plan template
  • Decision‑gate template

How to use and tailor this playbook

Keep the playbook timeboxed and pragmatic. For low‑risk internal questions, compress the stages into a single workshop (1–2 hours) and capture the one‑page canvas live. For regulated or high‑risk work, expand feasibility checks and involve compliance early. Adapt the scoring weights to match organizational priorities (e.g., weight feasibility higher for small teams).

Common pitfalls to avoid

  • Chasing fashionable topics without clear user or decision impact.
  • Designing a pilot that proves the obvious rather than the core uncertainty.
  • Skipping stakeholder alignment so results cannot influence decisions.
  • Failing to predefine stop criteria and acceptance thresholds.

Next steps

Run a brief framing session with the one‑page canvas, do a 15–60 minute evidence scan, shortlist hypotheses using the scoring rubric, and design a micro‑pilot that tests the core uncertainty. Capture the canvas and pilot plan so the team can reuse learnings and avoid duplication.


Discussion

Comments and conversation will live here.