Toolbox

Hypothesis Workshop Kit — Agendas, Templates & Interactive Hypothesis Form

Facilitation guides, 30/60/90-minute agendas, a reusable IF / THEN / BECAUSE hypothesis template, feasibility checklist, dependency mapping prompts, and an interactive form to capture, score, and prioritize hypotheses for experiments.

Interactive Tool

Hypothesis Workshop Kit — Interactive Hypothesis Template

Welcome to the Hypothesis Workshop Kit

This kit helps teams generate clear, falsifiable hypotheses, rapidly assess feasibility, and prioritize work that balances novelty, impact, and practicality. Use the workshop agendas (30/60/90), facilitation notes, and the form below to capture each hypothesis as a repeatable submission. Submit one hypothesis per form entry so the team can score and compare results.

Why this matters

Vague goals waste experiments. A tight hypothesis (IF / THEN / BECAUSE) produces measurable outcomes and clearer learning. The scoring fields below are designed to surface trade-offs so you can pick experiments that accelerate learning and impact.

Quick examples

  • IF we add a reminder email 24 hours before a clinic appointment THEN no-show rates will drop by at least 30% BECAUSE patients forget appointments and a reminder reduces missed visits.
  • IF we switch to lower-viscosity solvent in compound X THEN yield will increase by 8% BECAUSE the new solvent reduces incomplete reactions observed in prior batches.

Facilitation tips

  1. Use the dedicated agendas to frame the session and limit time spent per hypothesis.
  2. Encourage concise IF / THEN / BECAUSE phrasing; force measurable outcomes.
  3. Score independently, then discuss differences to reveal assumptions.
Which agenda length did you run for this session? (Used to align facilitation style and timebox expectations)
Optional: identify the team or project that owns this hypothesis.
Who contributed to this hypothesis during the workshop?
Describe the change or condition you will introduce. Keep it specific.
Describe the measurable effect you expect to observe. Include the metric if possible.
State the key assumption or mechanism that connects the IF to the THEN. This highlights what must be true for the hypothesis to hold.
Name the metric you will measure (e.g., click-through rate, yield %, no-show rate). Include units where helpful.
If known, record the current metric or estimate to make the expected change concrete.
Example: "reduce by 30 percentage points" or "increase by 8%". Be explicit about direction.
Selecting 'No' suggests you should split the idea into more focused testable parts.
Quick checklist to surface practical constraints and readiness.
List any external teams, equipment, approvals, or data that this experiment depends on.
Rough order of magnitude helps prioritize experiments by cycle time.
Optional: a rough budget estimate to assess resource trade-offs.
How new or unique is the idea relative to existing solutions?
How meaningful would the expected change be for the product, process, or outcome?
Based on resources, timeline, and technical risk, how feasible is the experiment?
Reflects how certain the team is that the BECAUSE assumption is true.
After scoring, capture discussion notes, conflicts between scorers, or a suggested priority rank. You may use your own weighting to compute a composite score outside the form.
Capture quick workshop observations, action items, or follow-up tasks tied to this hypothesis.
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.