When Not to A/B Test: Tess Rosania's Product Decision Frameworks
Learn two reusable frameworks (Quantify the Firing Squad, Hypothesis Tree) plus when to anchor a decision in company worldview rather than data, using real high-stakes decisions from Twitter and Slack.
4 sections ยท 7 lessons
Course outline
Not Every Decision Is a Data Question
- Slack's Do Not Disturb: Anchoring a Decision in Worldview, Not A/B Tests
- Why 'We Must A/B Test Everything' Is a Fallacy
Separating Logic From Emotion in Product Debates
- Quantify the Firing Squad: Turning Vague Opposition Into a Countable Group
- The Hypothesis Tree: Breaking a Belief Into Falsifiable Sub-Claims
Twitter's Ranked Timeline: A Case Study in Structured Reasoning
- Why Only 1 in 10 Tweets Mattered: The Logic Behind the Ranked Timeline
- While You Were Away: Using Dismissal Rate as a Validation Signal
Designing for Resistance
- Round-Trip Tickets: How Slack Threads Reduced Resistance to Structural Change