<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Designing an Experiment on DATATWEETS</title><link>https://datatweets.com/courses/ab-testing/designing-an-experiment/</link><description>Recent content in Designing an Experiment on DATATWEETS</description><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2025 Datatweets</copyright><lastBuildDate>Sun, 28 Jun 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://datatweets.com/courses/ab-testing/designing-an-experiment/index.xml" rel="self" type="application/rss+xml"/><item><title>Lesson 1 - From Question to Hypothesis</title><link>https://datatweets.com/courses/ab-testing/designing-an-experiment/lesson-1-from-question-to-hypothesis/</link><pubDate>Fri, 20 Feb 2026 09:00:00 +0200</pubDate><guid>https://datatweets.com/courses/ab-testing/designing-an-experiment/lesson-1-from-question-to-hypothesis/</guid><description>An experiment can only answer a question that&amp;rsquo;s sharp enough to be wrong. This lesson turns a fuzzy product goal into a testable hypothesis — specific, directional, falsifiable — and introduces the null and alternative hypotheses that frame every A/B decision.</description></item><item><title>Lesson 2 - Choosing Your Metrics</title><link>https://datatweets.com/courses/ab-testing/designing-an-experiment/lesson-2-choosing-your-metrics/</link><pubDate>Fri, 20 Feb 2026 09:00:00 +0200</pubDate><guid>https://datatweets.com/courses/ab-testing/designing-an-experiment/lesson-2-choosing-your-metrics/</guid><description>Every experiment needs a metric hierarchy: one primary metric that drives the decision, guardrail metrics that must not get worse, and secondary metrics for context. This lesson defines each tier, lays out what makes a good primary metric, and computes real metrics from seeded Lumen data so you can see conversion, ARPU, and a p95 latency guardrail side by side.</description></item><item><title>Lesson 3 - The Randomization Unit</title><link>https://datatweets.com/courses/ab-testing/designing-an-experiment/lesson-3-the-randomization-unit/</link><pubDate>Fri, 20 Feb 2026 09:00:00 +0200</pubDate><guid>https://datatweets.com/courses/ab-testing/designing-an-experiment/lesson-3-the-randomization-unit/</guid><description>The randomization unit is what you flip the coin on, and it&amp;rsquo;s easy to get wrong. This lesson compares randomizing by user, by session, and by cluster; explains the two properties the unit must satisfy — consistency and independence; and shows how a deterministic hash gives each user a stable assignment across every visit.</description></item><item><title>Lesson 4 - The Minimum Detectable Effect</title><link>https://datatweets.com/courses/ab-testing/designing-an-experiment/lesson-4-the-minimum-detectable-effect/</link><pubDate>Fri, 20 Feb 2026 09:00:00 +0200</pubDate><guid>https://datatweets.com/courses/ab-testing/designing-an-experiment/lesson-4-the-minimum-detectable-effect/</guid><description>Not every real effect is worth shipping, and not every experiment can afford to chase a tiny one. This lesson defines the minimum detectable effect (MDE) as a design choice grounded in practical significance, separates absolute from relative effects, and shows — with real scipy code — how a smaller MDE explodes the sample size you need.</description></item><item><title>Lesson 5 - Guided Project: Design Lumen's Pricing Experiment</title><link>https://datatweets.com/courses/ab-testing/designing-an-experiment/lesson-5-guided-project-design-lumens-pricing-experiment/</link><pubDate>Fri, 20 Feb 2026 09:00:00 +0200</pubDate><guid>https://datatweets.com/courses/ab-testing/designing-an-experiment/lesson-5-guided-project-design-lumens-pricing-experiment/</guid><description>Put Module 2 together into one design doc for a real Lumen experiment. You&amp;rsquo;ll write a specific hypothesis, choose primary, guardrail, and secondary metrics, pick a randomization unit, set an MDE, and compute the exact sample size with scipy — the full contract you fix before a single user is bucketed.</description></item></channel></rss>