hypothesis-drivenlisted

# Hypothesis-Driven Problem Solving ## Concept Don't boil the ocean. Start with a hypothesis — a specific, falsifiable claim about why the problem exists — then identify exactly what data would confirm or refute it. This is how consultants avoid running 40 analyses when 2 would do. The visual trick: a comparison table that shows **what you'd expect to see if the hypothesis is true** next to **what the data actually shows** (or what data is required if not yet collected). The point of divergence is where the answer lives. ## Required output format 1. A one-sentence falsifiable hypothesis prefixed `**Hypothesis:**`. 2. A Markdown table with columns: Variable | Expected (if hypothesis true) | Actual / Required Data. ```markdown **Hypothesis:** [One-sentence falsifiable claim.] | Variable | Expected (if hypothesis true) | Actual / Required Data | |---|---|---| | Variable 1 | Expected pattern | What we observe / need | ``` ## Defaults & flex points | Default | When to flex | |---|---| | 4–7 variables | If only 3 truly diagnostic variables exist, use 3. Don't pad. | | At least one control row | Don't flex this — confirmation bias is the most common failure mode. | | One hypothesis per table | If multiple hypotheses, output multiple tables. | | Variables are measurable | Don't flex this — unmeasurable variables aren't testable. | **The control row test:** at least one row should describe something that should NOT match if the hypothesis is true. If everything in your table