MKT 202 · Unit 1 · Lesson 3 of 5
Exploratory, Descriptive, and Causal Research
Research Strategy
Lesson
Three research modes, three different promises
After a spike in cancellations, Sam suggested "run a survey." Priya asked whether the team was exploring unknown reasons, describing how churn varies by segment, or testing whether a new save offer causes retention to improve. Those are three different research modes with different methods, sample sizes, and truth claims.
Exploratory research generates hypotheses when you do not know what you do not know. Descriptive research quantifies patterns in defined populations. Causal research tests whether changing X changes Y, holding other factors as constant as practical design allows. Confusing modes produces expensive misfit: running a focus group when you need a randomized offer test, or launching an A/B test before you know which mechanisms to test.
BrightBrew is a direct-to-consumer (DTC) specialty coffee subscription company and the anchor company for MKT 202. As of the latest reporting period, BrightBrew serves 142,000 active subscribers with 4.2% monthly churn, average revenue per user (ARPU, average monthly subscription revenue per active subscriber) of $28, and customer acquisition cost (CAC, marketing and sales spend to win one new paying subscriber) near $42. VP Marketing Elena Okonkwo, Head of Growth Sam Rivera, and Director of Customer Insights Priya Nair run active-subscriber and churned-subscriber survey panels refreshed quarterly, A/B tests on onboarding (welcome email sequence, first-shipment timing, grinder add-on offer), and cohort retention dashboards by signup month, acquisition channel, and plan type.
You met BrightBrew in MKT 201 (Marketing Management) positioning and STP work on BrightBrew's value proposition. This course adds the evidence layer: how to translate marketing decisions into research questions, collect valid qualitative and quantitative data, analyze cohorts and funnels, run experiments, and present recommendations leaders can act on.
Exploratory research: learning the map
Exploratory work is appropriate when BrightBrew enters a new occasion (office coffee) or sees an unexpected metric move without a story. Methods include open-ended interviews, ethnography, analysis of support tickets, and reviewing churn verbatims. Output is hypotheses and language, not population percentages.
Exploratory research should be labeled exploratory in briefs. Executives who treat 12 interviews as proof of national demand overreach. The correct handoff is: "We heard compatibility anxiety in 9 of 12 pod churn interviews; next step is a 1,500-respondent survey on compatibility tools."
BrightBrew's qualitative sprint before pod expansion was exploratory. It should not have ended the conversation; it should have focused the next study.
Descriptive research: measuring what is
Descriptive research answers how much, how many, who, and where with defined metrics on defined populations. BrightBrew's cohort dashboard describing 4.2% monthly churn by signup month is descriptive. A survey asking "What percent of active subscribers brew more than four times per week?" is descriptive if the sample is representative.
Descriptive work does not prove that changing onboarding caused churn to fall. It can show that churn is higher among Starter Kit promos than referral signups, which narrows causal candidates.
Managers use descriptive research for monitoring, segmentation inputs, and baseline rates for experiment power calculations. Every causal test needs descriptive baselines: control churn, expected effect size, eligible population size.
| Mode | Question shape | BrightBrew example | Typical methods |
|---|---|---|---|
| Exploratory | What might be going on? | Why do pod triers leave? | Interviews, ticket coding |
| Descriptive | How much / who / where? | Churn by channel in Q2 | Cohort dashboards, surveys |
| Causal | If we change X, does Y move? | Does onboarding B reduce 30-day churn? | A/B tests, holdouts |
Causal research: attribution under skepticism
Causal claims require designs that address confounding: seasonality, selection, simultaneous campaigns. BrightBrew's onboarding A/B test is causal if randomization holds and sample sizes are sufficient. Survey recall ("Would you have churned if we offered a pause?") is weak causal evidence.
Randomized controlled trials (RCTs, experiments that randomly assign subjects to treatment or control) are the gold standard for marketing interventions when feasible. Quasi-experiments (difference-in-differences, matched markets) apply when randomization is impossible.
Elena should ask of any causal claim: What was the counterfactual? What would have happened without the change? If the team cannot answer, the claim is descriptive at best.
Choosing mode by decision stage
Early ambiguity → exploratory. Strategy sizing and monitoring → descriptive. Policy change and budget commit → causal. BrightBrew's research plan for referral program expansion might sequence: 10 exploratory interviews on gift-giving occasions, descriptive panel survey on referral intent by segment, causal test of double-sided incentive versus single-sided.
Skipping stages creates recognizable failures. Causal test on a hunch with no exploratory mechanism work wastes power on the wrong treatment. Endless exploration without descriptive baselines delays decisions past the holiday quarter.
Truth labels executives should enforce
Require labels on every slide: exploratory insight, descriptive estimate (with CI, confidence interval, range of plausible values), or causal effect (with test design noted). BrightBrew's leadership culture improves when Priya can say "exploratory only" without being treated as blocking growth.
Mixed-mode studies are fine if modes are separated analytically. A survey can include exploratory open-ends and descriptive scaled items. Analysis plan should pre-specify which is which.
Worked example: BrightBrew churn spike triage
June churn ticked from 4.2% to 4.7%. Elena wants answers in three weeks.
Part A: Week 1 exploratory
20 exit interviews + support ticket coding. Themes: price (8), pod compatibility (6), gift ended (4), moved (2). Output: hypothesis list, not prevalence.
Part B: Week 2 descriptive
Panel survey n=900 + warehouse pull. Price increase flag among churners 38% vs 12% stayers. Gift plan churn 6.1% vs 3.9% non-gift. Check: survey weights align to plan mix within 2pp ✓
Part C: Week 3 causal proposal
Randomized save offer: 15% pause vs 15% discount for price-flagged accounts. Primary metric: 60-day retention. Pre-register analysis; power calc in Lesson on Statistical Power.
Part D: Managerial read
Do not roll out discount globally from descriptive price correlation alone. Test save offer causally; monitor gift-plan descriptive rates separately with product policy.
Worked example: VeloRide scooters
VeloRide ran a citywide price cut and credited the subsequent ride increase to the cut. Exploratory interviews would have noted simultaneous university reopening. Descriptive ride counts by neighborhood would have shown campus spikes. Causal inference needed a holdout city or staggered rollout. BrightBrew applies mode labels before budget commits.
Common mistakes beginners make
| Mistake | Reality |
|---|---|
| Calling interviews 'validation' | Exploratory generates hypotheses; validation requires descriptive or causal designs |
| A/B testing before you know what to test | Explore mechanisms, then causal test prioritized treatments |
| Descriptive correlation as policy proof | Causal design or explicit quasi-experiment before changing prices |
| Mixing modes on one slide without labels | Label exploratory vs descriptive vs causal claims |
| Infinite exploration | Time-box exploration; predefine handoff to descriptive or causal |
Practice problem
BrightBrew wants to know if barista-style video tutorials reduce churn. Classify: (1) 15 subscriber interviews about learning preferences. (2) Dashboard comparing churn for tutorial viewers vs non-viewers. (3) Randomized prompt to watch tutorial at signup. Which mode is each? What is the main threat to validity for (2)?
Solution
(1) Exploratory. (2) Descriptive observational; threat: selection bias (engaged users watch tutorials and churn less for other reasons). (3) Causal RCT if randomization at signup. Check: mode sequence should be explore → describe selection risk → experiment ✓
Key takeaways
- Exploratory, descriptive, and causal research answer different questions; do not swap them.
- BrightBrew uses exploration to focus surveys and experiments, not to skip them.
- Descriptive cohort metrics monitor health; causal tests justify policy changes.
- Label truth claims on every executive output.
- Sequence modes by decision stage and time-box exploration.
After this lesson
- Take one current BrightBrew-style metric (churn, CAC, referral rate). Which research mode would you use next and why?
- Find a causal claim in a news article about a marketing campaign. Identify the missing counterfactual.
- Continue to Lesson 4: Research Ethics and Privacy.
Applying Exploratory, Descriptive, and Causal Research at BrightBrew scale
When BrightBrew evaluates exploratory, descriptive, and causal research, the team starts from operational facts: 142,000 active subscribers, 4.2% monthly logo churn, $28 ARPU, and $42 blended CAC. VP Marketing Elena Okonkwo, Head of Growth Sam Rivera, and Director of Customer Insights Priya Nair align research strategy and decision translation with Monday dashboard reviews and pre-written research plans. A lesson concept that sounds abstract becomes concrete when tied to signup cohorts, panel waves, and experiment cells logged in the warehouse.
Consider how a 0.5 percentage point change in monthly churn affects BrightBrew. At current scale, that shift moves roughly 710 subscriber logos per month before accounting for mix effects across Classic Bag, Espresso Pod, and Starter Kit promos. Contribution margin near 16.24 dollars per month per subscriber turns small rate changes into five-figure monthly impact. That is why exploratory, descriptive, and causal research is not an academic exercise for Elena Okonkwo's marketing org; it is how the company avoids scaling a channel that fills the top of the funnel while leaking high-churn promo cohorts at month three.
The research strategy and decision translation workflow at BrightBrew deliberately separates exploratory, descriptive, and causal claims. Priya Nair's analysts label outputs before they reach Sam Rivera's growth standups. Exploratory interview themes become survey items only after codebook review. Descriptive cohort spikes trigger pre-registered experiments rather than same-day pricing changes. Causal A/B wins still require guardrail checks on support tickets, refunds, and grinder attach rates so a churn win does not hide margin erosion. You should copy that labeling habit even if you work outside subscription coffee: name the mode, name the population, name the comparison, and name the decision date before numbers hit a slide.
Document definitions alongside every metric tile. BrightBrew's churn formula specifies grace days after failed payment, pause versus cancel handling, and exclusion of fraud flags. Funnel steps define eligible denominators for visit, signup, shipment, first brew, and month-two active status. Survey estimates document weighting targets by plan mix. Experiment readouts specify intent-to-treat estimands and pre-registered minimum detectable effects on 30-day churn. When definitions live in a shared dictionary, the company builds institutional memory instead of re-debating the same SQL every quarter.
Extended BrightBrew scenario: cross-functional read
Imagine BrightBrew's Q3 review for exploratory, descriptive, and causal research. Finance asks whether improved onboarding justifies higher podcast CAC. Product asks whether compatibility tooling belongs in mobile web or email only. Operations asks whether shipment forecast accuracy supports green coffee buys. A weak research strategy and decision translation answer addresses only one function. A strong answer shows how evidence flows: qualitative language from churn interviews becomes survey prevalence estimates, descriptive cohort curves localize the leak to Starter Kit promos, and a randomized onboarding test estimates causal churn reduction with confidence intervals translated into saved logos and monthly contribution.
Work the arithmetic on a conservative example. Suppose an onboarding test shows 30-day churn falling from 5.0% to 4.3% intent-to-treat among ten thousand assigns per arm. Absolute reduction 0.7 percentage points yields about seventy fewer churners per ten thousand signups. If BrightBrew adds forty thousand new subscribers in a month after rollout, a sustained effect near the point estimate implies roughly two hundred eighty retained logos in the first month cohort, with compounding value as retained subscribers continue billing. Multiply by monthly contribution near sixteen dollars to communicate magnitude to executives who do not live in p-values. Pair the point estimate with a confidence interval and a pre-written rule: roll out if the interval excludes zero harm on guardrails and includes materially positive churn impact.
Stakeholder conflict is normal. Sam Rivera may push to scale spend while the test is immature. Priya Nair may push to extend runtime for power. Elena Okonkwo must decide under calendar pressure from holiday inventory commits. Exploratory, Descriptive, and Causal Research gives you language to negotiate those tensions with evidence quality standards rather than charisma. If power is insufficient, the decision is extend or accept uncertainty, not pretend a noisy week-one lift is definitive. If qualitative sample is thin, the decision is fund ten more interviews, not quote three vivid anecdotes as national truth.
Translate lessons to your own context by replacing BrightBrew names while keeping structure. Pick one decision you face this quarter. Write the business question, three hypotheses, population rules, comparison group, primary metric, guardrails, and inconclusive outcome before collecting new data. If you cannot write those elements, you are not ready to field a survey or launch an experiment regardless of how easy the vendor dashboard makes clicks look.
Technical mechanics and checks (worked patterns)
For exploratory, descriptive, and causal research, BrightBrew analysts show work the way finance shows reconciliations. A cohort retention table prints signup month, eligible n, month-zero through month-three retention, and a check that weighted plan mix matches the dashboard within one percentage point. A funnel table multiplies step conversions and compares the product to observed month-two actives within rounding tolerance. A survey proportion reports weighted point estimate, ninety-five percent confidence interval, effective n, and exclusion counts from speeders or straight-liners. An experiment appendix lists assignment counts per arm, sample ratio mismatch p-value, intent-to-treat churn with interval, and support ticket guardrail delta.
Use plain-language hypothesis statements before formulas. Example for onboarding: null hypothesis states sequence B does not change 30-day churn versus sequence A; alternative states churn differs. Randomization creates comparable arms so differences after large n are plausibly treatment-related rather than channel mix artifacts. Still verify seasonality with year-over-year cohort comparisons and document concurrent campaigns that could violate independence assumptions.
For spreadsheet or SQL replication, write the grain first. Customer-month tables suit retention. Customer-level tables suit funnel conversion if timestamps exist for each stage. Survey tables suit respondent weights. Experiment tables suit assignment at signup with outcome flags thirty days later. BrightBrew forbids ambiguous one-word metrics like engagement without operational definition. Engagement might mean logged brew events, email opens, or app sessions; each definition implies different SQL joins and different managerial meaning.
Common executive questions (and disciplined answers)
Executives ask short questions that require long disciplined answers. "How sure are we?" maps to confidence intervals, power, and replication plans, not bravado. "What is the dollar impact?" maps to logos saved times contribution margin with explicit stationarity assumptions. "Can we ship faster?" maps to risk of rolling out biased assignment or underpowered tests that will reverse after holiday spend commits. "Why trust panel data?" maps to sampling frame, weighting, response quality rules, and consent governance. "Why not just ask sales?" maps to selection bias and absent counterfactuals in anecdote.
BrightBrew's credible answer format for exploratory, descriptive, and causal research is three bullets: decision recommendation, evidence strength label exploratory descriptive or causal, and next study if limitations matter. A fourth bullet lists what would falsify the recommendation within sixty days. That discipline prevents the analytics team from becoming either a bottleneck or a rubber stamp.
Practice the translation loop until it is habit. Business question to research questions to design to analysis plan to dashboard tile to memo ask. When the loop is complete, BrightBrew scales what survives skepticism. When the loop is broken, the company buys false confidence cheaply and pays for it in subscriber logos later.
Lesson exercise
40 minApply: Exploratory, Descriptive, and Causal Research
Deliverable
One-page workbook entry or memo section filed under MKT 202 Unit materials.
Rubric
- • Decision frame is specific and time-bound
- • Framework applied with auditable steps
- • Downside case is plausible, not strawman
- • Guardrail metric defined with owner
- • Recommendation links to evidence quality label