Hypothesis-Driven Analysis: Ask First, Analyze Second
Start with a specific question, then use data to find a clear yes/no answer. This approach is perfect for A/B testing or diagnosing metric changes, but watch out for confirmation bias—seeking data that only proves your initial belief.
Why it exists
To give data analysis focus and avoid wasting time on irrelevant explorations or finding meaningless correlations. It makes decision-making more scientific by forcing you to test specific, falsifiable statements before acting.
The mental model
Think of it as the scientific method applied to business data. You start with a clear, testable question ('Will this new button increase clicks by 10%?') and then collect data to get a definitive answer, rather than just 'looking at the data' for something interesting.
How it works
The process is structured. First, you state a clear, measurable hypothesis. Second, you identify the exact data needed to test it. Third, you collect and prepare the data. Fourth, you perform a statistical analysis to evaluate the evidence. Finally, you conclude whether the data supports or rejects your initial hypothesis.
When to use it
It's best when you have a specific question to answer or a decision to make. Use it for A/B testing product changes, performing root cause analysis on a metric that has changed, or validating a business strategy before committing significant resources.
When not to use it
Avoid it for initial, open-ended discovery where the goal is to generate new ideas or understand a domain broadly. In these situations, exploratory data analysis is more appropriate for finding interesting patterns that can become hypotheses later.
One canonical example
A marketing team hypothesizes that emails with emojis in the subject line have a higher open rate. They create two versions of an email—one with an emoji, one without—and send them to two random segments of their user base. They then analyze the open rates for both groups to determine if their hypothesis was correct.
Interview question
For which situation is a hypothesis-driven analysis LEAST appropriate?
- a.Evaluating the impact of a new product pricing strategy on sales.
- b.Confirming if a website's redesigned checkout flow improves conversion rates.
- c.Uncovering novel insights and potential trends within a newly acquired dataset.Correct
- d.Diagnosing the cause of a recent, significant drop in customer retention.
Why? this is the answer
Hypothesis-driven analysis is designed for testing specific, falsifiable statements. Uncovering novel insights from a new dataset is an open-ended discovery task, which is better suited for exploratory data analysis rather than hypothesis testing.
Just read this? Test yourself on what you have been reading.
Read the original → en.wikipedia.org
- #data science
- #analytics
- #a/b testing
- #decision making
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on data science — each one lists the topics its interview covers.
See open roles