<aside> 🔍 Interrogate turns observations into tested knowledge. Every assumption gets a hypothesis. Every hypothesis gets an experiment.
</aside>
Objective: Surface hidden beliefs the project depends on and prioritize which to test first. Every untested assumption is a bet; this database makes the bets visible.
When to use: Start of Interrogate, when the team has a proposed solution but has not validated the beliefs underlying it.
Inputs: Proposed solution from Witness, Playbook with documented constraints and open questions, access to team members who contributed to the solution design.
Position: Scout owns. Full team contributes during brainstorming.
How to fill out: One row per assumption. Categorize (User, Technical, Organizational, Solution). Rate confidence and impact-if-wrong. Prioritize: low confidence + high risk = test first.
<aside> 💡 Have team members write assumptions individually before sharing. Prevents anchoring on the first ideas voiced. If every assumption has "High" confidence, require evidence for the rating.
</aside>
Objective: Document every experiment so learnings survive the people who ran them. Every assumption gets a hypothesis. Every hypothesis gets a test.
When to use: Throughout Interrogate. Create the entry before the experiment starts. Update with results the same day it concludes.
Inputs: Prioritized Assumption Inventory, selected experiment type for each assumption, resources allocated for testing.
Position: Scout owns the log. Whoever runs the experiment updates their entry.
How to fill out: Fill in hypothesis, test design, and success/failure criteria before running. After: record results immediately and make a decision: Proceed (validated), Revise (partially validated), or Pivot (invalidated). Link to the assumption being tested.
<aside> ⚠️ If every experiment confirms what the team wanted to believe, you are not testing hard enough. Seek disconfirming evidence. No experiment should end without updating the Playbook.
</aside>