Template

Opportunity Intake & Triage Template

A one-page interactive intake and triage form to capture, score, and stage new discovery opportunities for the backlog. Collects structured data, records triage scores, suggests next steps, and preserves handoff notes for backlog owners.

Interactive Tool

Opportunity Intake & Triage

Use this single-page intake to capture promising ideas, run a quick team triage, and record a recommended next step so opportunities flow into your discovery backlog with context and evidence. The form collects concise problem framing, impact and evidence notes, technical/regulatory flags, a proposed initial experiment, and a standard triage scorecard. Follow the quick triage guidance below to keep decisions consistent.

Quick triage (5–10 minutes)

  1. Read the brief problem statement and target persona.
  2. Ask whether there is any existing evidence or data — note it in Evidence Brief.
  3. Each reviewer scores feasibility, desirability, viability, and time-to-learn (1=low, 5=high). Higher time-to-learn lowers priority.
  4. Compute the triage score using the simple formula in the help text or rely on the recommended thresholds to choose a next step.
  5. If accepted for discovery, leave clear handoff notes and a first experiment suggestion.

Scoring guidance

Suggested quick formula: (Feasibility + Desirability + Viability) / 3 minus (Time-to-learn - 1) * 0.5 — or simply use thresholds: score ≥ 3.5 = Run discovery experiment; 2.5–3.5 = Quick check or spike; <2.5 = Defer or Reject. See the HelpText on triage_score and triage_decision fields for mapping.

A concise name that helps others find and recognize this idea later.
Who submitted this? Include team or contact for follow-up.
Describe the problem or opportunity in one to three sentences. Focus on the customer or operational pain and the desired outcome.
Who benefits? Name the customer segment, internal role, or stakeholder most affected.
Estimate the potential upside if this succeeds. Use 1 for low/limited impact, 5 for strategic or large financial/operational impact.
1.0 10.0
Summarize any existing evidence, data, customer feedback, or quick experiments that support this claim. Link or attach artifacts where available.
What data would help validate this opportunity? Note accessibility, owners, and any quick checks to run.
List systems, APIs, platforms, skills, or people required to run an experiment or build a solution.
Select any flags that require compliance, legal, privacy or security review.
Describe a small, fast experiment (week(s) to month) that would produce useful learning. Include metrics or success criteria.
Select the action you recommend after quick triage. Use the triage scorecard and thresholds below to guide this choice.
Can the idea be executed with current skills/tech within a reasonable time? 1 = unlikely, 5 = straightforward.
1.0 10.0
How much do customers/stakeholders want this? 1 = little demand, 5 = strong demand or strategic alignment.
1.0 10.0
Is there a plausible business, operational, or mission case? 1 = weak, 5 = strong.
1.0 10.0
How long until a meaningful learning experiment could return useful evidence? 1 = &lt;1 week, 5 = many months. Higher values lower priority.
1.0 10.0
Suggested manual calculation: ((Feasibility + Desirability + Viability) / 3) - ((Time-to-learn - 1) * 0.5). Use this to guide decisions: ≥3.5 = Run discovery experiment; 2.5–3.5 = Quick check or spike; &lt;2.5 = Defer or Reject. (Platform automation can compute this later if enabled.)
Choose the human-reviewed outcome. Use the triage_score as guidance but include context in Handoff Notes.
Who should take ownership next, what needs to happen first, and any suggested timeline. Include links to tickets, calendars, or relevant documents.
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.