Discovery Backlog & Pipeline Template

Purpose

This template helps teams capture discovery ideas consistently, move candidates through predictable stages, prioritize using evidence-aware scoring, and preserve learning so insights are reusable rather than lost. Use it as a Kanban-backed backlog or a living spreadsheet that can be converted into an interactive form and stored submissions.

How to use this template

1. Capture every idea or opportunity as an intake record.
2. Use the framing and hypothesis fields to make the assumed value and intended learning explicit.
3. Score and prioritize so limited experiment capacity focuses on highest-value, highest-confidence learning.
4. Move cards across stages as experiments are designed, run, and evaluated.
5. Record outcomes and artefacts (evidence links, reports) so future teams can learn from past work.

Columns (fields) — name and purpose

• Intake brief: One-line title and short description (1–2 sentences). Use plain language a stakeholder can understand quickly.
• Framing summary: Context, target user or system, and why this idea matters. Capture customers, constraints, and strategic alignment.
• Hypothesis: A testable hypothesis stating expected outcome and measure ("If we X for Y, then Z will increase by N% over T days"), or the question you want to answer.
• Required evidence: Specific data, metrics, or qualitative feedback needed to validate the hypothesis (e.g., conversion lift, time saved, user interviews, technical feasibility artifact).
• Priority score: Numeric score used to rank items. See scoring guidance below (includes example calculation).
• Experiment owner: Person or small team responsible for designing and running the experiment and reporting results.
• Stage: Current pipeline stage (suggested stages listed below). Use Kanban columns to reflect stage state.
• Last update: Date and brief note of the most recent activity or decision.

Suggested optional fields

• Estimated effort (days) — for planning capacity.
• Customer segment — who benefits or is affected.
• Tags — see suggested taxonomy below.
• Links / attachments — prototypes, dashboards, tickets, research notes.
• Outcome / decision — keep a concise conclusion and next step (adopt, iterate, abandon, backlog).

Suggested tagging taxonomy

Use a small controlled vocabulary so filters are reliable. Examples:

• Opportunity type: product, process, research, cost-savings, compliance, safety
• Customer: consumer, enterprise, internal-user, clinician, student
• Technology: AI, automation, manual, integration
• Risk/Dependency: high-risk, legal, requires-data, dependent-on-team-X
• Strategic theme: growth, retention, efficiency, quality

Priority scoring (simple RICE-style example)

Use an evidence-friendly scoring formula that balances impact, confidence, and effort. This lightweight RICE variant works well for discovery:

1. Reach (R): scale 0–5 — how many users or processes are affected?
2. Impact (I): scale 0–5 — estimated upside if hypothesis is validated.
3. Confidence (C): scale 0–5 — how confident are we in the assumptions / existing evidence?
4. Effort (E): scale 1–5 — relative effort to design and run the experiment (higher = more effort).

Score formula (normalized): Priority = (R × I × C) / E. Rank items by descending priority.

Example: R=3, I=4, C=3, E=2 → Priority = (3×4×3)/2 = 18. Use tie-breakers such as strategic alignment or regulatory urgency.

Suggested stages (kanban-friendly)

• Intake — raw idea captured; minimal triage.
• Triage — quick validation of alignment, feasibility, and initial score.
• Design — experiment plan, success criteria, sample size, tooling identified.
• Running — experiment in progress; collect evidence and log anomalies.
• Analyze — evaluate results against required evidence.
• Decision — outcome recorded and next steps chosen (adopt/iterate/abandon/backlog).
• Blocked — external dependency preventing progress.

Sample row (compact example)

Governance and cadence

• Hold a regular intake & triage meeting (weekly/biweekly) to review new items and re-score priorities.
• Keep experiments small and timeboxed; prefer fast learning over perfect polish.
• Require an outcome artefact (short report or dashboard view) before moving a card to Decision.
• Archive decisions with a clear tag (adopted/abandoned/iterate) and link to related product or ops work.

Turning this template into an interactive backlog (opportunities)

This template is intentionally structured so it can be implemented as an interactive intake form and Kanban board. Implementing interactivity gives additional value:

• Save intake submissions as structured JSON so organizational memory is searchable and auditable.
• Render edit forms for fields like hypothesis, required evidence, score components, and attachments.
• Use tags and stage fields to drive Kanban columns and filtered views.
• Connect the backlog to dashboards to show experiment velocity, pass/fail rates, average cycle time, and learning reuse.

Notes for implementers

Keep the taxonomy small and stable to avoid fragmentation. If you convert this to an InteractiveForm or checklist, use stable field keys (e.g., intake_brief, framing_summary, hypothesis, required_evidence, reach, impact, confidence, effort, priority_score, experiment_owner, stage, last_update, tags, outcome) so analytics and automation can be built on top.

Use this template as a living artifact: tweak scoring weights, tags, and stages to match your team’s capacity and strategic priorities. The goal is repeatable learning, not bureaucracy.