MKT 202 · Unit 1 · Lesson 1 of 5
Turning Decisions into Research Questions
Research Strategy
Lesson
The expensive answer to the wrong question
BrightBrew's Head of Growth, Sam Rivera, walked into a Q3 planning meeting with a 40-slide deck showing that email open rates rose 12% after a creative refresh. The VP (vice president) of Marketing, Elena Okonkwo, asked the only question that mattered: "Did retention improve among subscribers acquired through email?" Silence. The team had answered a comfortable metric question while the business decision, whether to scale email spend ahead of holiday acquisition, remained untested.
Marketing organizations burn budget when business questions (what should we do?) are confused with research questions (what evidence would change our minds?). A business question is allowed to be broad because leadership is diagnosing under pressure. A research question must be narrow enough that two analysts could pull comparable data and reach a decision-grade conclusion. BrightBrew's 142,000 subscribers and 4.2% monthly churn create real dollars on the line: every mis-scoped study delays fixes to onboarding, pricing, or product mix.
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.
This lesson teaches translation: how to climb from a leadership problem to testable research questions with explicit population, metric, time window, and comparison group. If you skip translation, you will deliver polished charts that do not change allocation.
Business questions versus research questions
A business question names a strategic or operational problem in plain language: "Why is churn stuck at 4.2%?" "Should we launch espresso pods nationally?" "Is our referral program worth the discount cost?" These questions are legitimate starting points. They are not yet research-ready because they hide population, comparison, and decision thresholds.
A research question specifies who you study, what you measure, over what period, against what baseline, and what outcome would trigger action. Weak research: "How do customers feel about pods?" Strong research: "Among subscribers who added Espresso Pod in the first 60 days, does 90-day retention differ from Classic Bag subscribers matched on signup month and acquisition channel?" The second version can be answered with BrightBrew's cohort dashboard and survey panel.
Managers do not need to run regressions themselves. They need to recognize when a request is still a business question wearing a chart costume. Before approving analyst time, ask: Who exactly is in scope? What number would convince us to act? What would we do if the number were higher or lower? If those answers are missing, the work is not ready.
Use this vocabulary consistently in briefs and meetings:
| Term | Plain meaning |
|---|---|
| Business question | Leadership problem stated in strategy language |
| Research question | Testable question with population, metric, time, and comparison |
| Population | The complete set of entities the decision cares about |
| Metric | Defined calculation (churn, conversion, NPS, Net Promoter Score, likelihood to recommend) |
| Comparison group | Baseline or control that defines "changed" or "better" |
Translation is iterative. Your first research question may be impossible because data does not exist. That forces a choice: collect new data, proxy with a weaker metric, or narrow the decision. Each iteration is progress, not failure.
The translation ladder
Think of translation as climbing down a ladder. Each rung adds specificity. Skipping rungs produces analysis that feels responsive but does not connect to action.
Top rung: "Why are we losing subscribers?" One rung down: "What is churn?" Still too weak: one number with no mechanism. Next rung: "How did monthly churn among Espresso Pod subscribers change from Q1 to Q2?" Better, but silent on cause. Solid rung: "Among subscribers who churned in June, did product usage (brews logged in app), support contacts, or price changes in the prior 60 days differ from subscribers who renewed, matched on plan and signup cohort?"
The ladder also applies to growth decisions. "Should we expand podcast advertising?" is a business question. "What is podcast audience size?" is trivia. A decision-grade question: "Among households exposed to BrightBrew podcast ads in test markets, does trial signup rate per 1,000 listeners exceed paid social benchmark CAC of $42 in the same weeks?" That connects channel to unit economics.
Hypotheses before hunting
Data exploration without hypotheses is a fishing expedition. With enough variables, you will find patterns that look meaningful by chance. Business data is rich in spurious correlations: gift subscriptions spike in December and support tickets spike in January; both follow holidays, not causation.
A hypothesis is a plain-language claim you intend to support or refute. For "Did the new onboarding email sequence reduce early churn?" list competing hypotheses before pulling data:
H1: Shorter time-to-first-brew reduces 30-day churn versus old sequence. H2: Seasonality explains any lift; January always shows better retention. H3: The lift is driven by grinder add-on revenue, not email content. Each hypothesis maps to a different research question, metric, and comparison.
| Hypothesis | Research question | Primary metric |
|---|---|---|
| H1: Email content | 30-day churn: new vs old onboarding cohorts | Churn rate by signup week |
| H2: Seasonality | Retention vs same calendar week prior year | Cohort retention index |
| H3: Add-on economics | Churn conditional on grinder purchase | Churn rate by add-on flag |
BrightBrew's growth team should reward falsification of pet theories. Sam may want the new emails to win; Priya should still run the seasonality check before holiday budget is locked.
SMART research questions and decision triggers
A practical checklist for testable research questions is SMART: Specific, Measurable, Actionable, Realistic, and Time-bound. Specific means explicit who and what: not "customers" but "U.S. Classic Bag subscribers acquired via referral in H1." Measurable means the metric has a written definition: churn equals no payment 30 days after expected billing date.
Actionable means different answers trigger different decisions. If churn is concentrated among subscribers who never logged a brew in the app, the decision may be product onboarding, not price. Realistic means data exists within the decision clock. Time-bound means the period is stated: Q2 2026, not "historically."
Before any study, write two columns: possible answers and decisions they trigger. If every outcome leads to the same policy, deprioritize the work. BrightBrew's leadership should demand this table in a one-page brief before survey fieldwork or experiment launch.
Population, time window, and comparison group
Three elements appear in every serious research question. Getting any one wrong invalidates the rest.
Population defines membership rules. "Subscribers" might mean ever paid or active in last 30 days. BrightBrew mixes Classic Bag, Espresso Pod, and Starter Kit; blending without labeling creates averages that help nobody. Write inclusion and exclusion rules: include U.S. paid plans; exclude corporate gift accounts and fraud-flagged cards.
Time window defines when events count. Measuring post-redesign conversion from launch to today while measuring pre-redesign as only the week before launch compares unequal windows. State anchors: redesign launch date, analysis freeze date, calendar month versus rolling 28-day windows.
Comparison group defines what "good" means: same group before, similar group without treatment, peer segment, or external benchmark. BrightBrew's onboarding A/B test compares exposed versus holdout signup cohorts. Without a comparison, you can describe but not attribute.
Worked example: BrightBrew onboarding email decision
Elena must decide whether to roll out a redesigned welcome email sequence globally. Sam claims open rates rose 12%. Priya needs research questions, not applause metrics.
Part A: Business question and decisions
Business question: Should BrightBrew roll out the new onboarding email sequence to all new subscribers?
Decisions on the table:
- If early churn falls → roll out and reallocate creative budget to retention
- If only opens rise → keep test localized; fix message-to-behavior link
- If grinder add-on drives all lift → adjust offer placement, not email copy alone
Part B: Hypotheses and research questions
| Hypothesis | Research question | Metric |
|---|---|---|
| H1: Sequence reduces early churn | Among July signup cohort, does 30-day churn differ: new vs old sequence? | 30-day churn rate |
| H2: Seasonality | Does July 2026 retention match July 2025 for matched channels? | Retention index |
| H3: Add-on confound | Among new sequence group, does churn differ by grinder attach? | Churn by attach flag |
Population: U.S. direct subscribers excluding gift and corporate accounts. Comparison: A/B cells from onboarding test with n ≥ 5,000 per arm.
Part C: Results sketch and check
| Group | n | 30-day churn | Median days to first brew |
|---|---|---|---|
| Old sequence | 5,200 | 5.1% | 9 |
| New sequence | 5,400 | 4.4% | 6 |
| New + grinder add-on | 1,100 | 3.2% | 5 |
| New, no add-on | 4,300 | 4.9% | 7 |
Check: 5,200 + 5,400 = 10,600 eligible July signups in test ✓. Open rate +12% noted but not used as primary decision metric.
Part D: Managerial read
Roll out the sequence globally only after confirming H2 seasonality check and isolating grinder attach. If add-on drives retention, product and pricing teams co-own the decision, not email alone. Board question: "Did we improve subscriber LTV (lifetime value, total margin expected from a customer relationship) or merely shift margin to hardware attach?"
Worked example: NorthTrail Gear: metric theater
NorthTrail Gear, a fictional outdoor subscription box, celebrated a 22% lift in landing page clicks after a hero image change. The CEO rolled out globally. Three months later, paid conversion and 90-day retention were flat because clicks rose from low-intent mobile traffic. The research question had been "Did clicks rise?" while the business question was "Did profitable subscribers rise?" BrightBrew avoids this failure mode by tying onboarding tests to churn and first-brew behavior, not email opens alone.
Managerial read: name the decision first, then design the study. Clicks are a diagnostic; churn and contribution margin are decision metrics.
Common mistakes beginners make
| Mistake | Reality |
|---|---|
| Starting with available data instead of the decision | Write the business question and decision triggers before opening the dashboard |
| Treating email opens as proof of onboarding success | Behavior metrics (first brew, 30-day churn) test whether messaging changed habits |
| One research question per business question | List competing hypotheses (content, seasonality, add-on) before fieldwork |
| Undefined population labels like 'customers' | Specify plan, geography, channel, and exclusion rules explicitly |
| No comparison group | Use holdout, prior period, or matched cohort before claiming lift |
Practice problem
BrightBrew debates expanding Espresso Pod nationally. Current data: 8,400 pod subscribers in test markets, 4.6% monthly churn versus 4.2% company average. Referral signups show 3.8% churn.
Tasks: (1) Write the business question Elena faces. (2) Draft two competing hypotheses. (3) Write one SMART research question for each hypothesis with population, metric, time window, and comparison. (4) State what decision each answer would trigger.
Solution
Business question: Should BrightBrew expand Espresso Pod nationally given churn and margin tradeoffs?
H1: Pod attracts a stickier segment (lower churn once matched on channel). H2: Pod churn looks low because test markets are affluent early adopters; national rollout will revert to company average.
RQ1 (H1): Among subscribers acquired Q1-Q2 in test markets, does 90-day churn for Espresso Pod match Classic Bag when matched on acquisition channel and signup month? Decision: If pod churn ≤ classic − 0.3pp with similar CAC, expand.
RQ2 (H2): Among national waitlist signups (non-test), does stated willingness to pay translate to 60-day retention ≥ 85% of test-market pod cohort? Decision: If waitlist cohort underperforms, stage rollout by DMA (designated market area, geographic ad region).
Check: each RQ names population, metric, window, comparison ✓
Key takeaways
- Business questions motivate work; research questions make evidence decision-grade.
- Climb the translation ladder: population, metric, time, and comparison before fieldwork.
- List competing hypotheses so one surprise metric cannot hijack the narrative.
- SMART questions link possible answers to different actions, not one predetermined story.
- BrightBrew ties onboarding tests to churn and first-brew behavior, not vanity opens.
After this lesson
- Take one live decision at your company. Write the business question, three hypotheses, and one SMART research question per hypothesis.
- Audit a recent marketing report: which metrics answer business questions versus comfortable activity metrics?
- Continue to Lesson 2: Primary and Secondary Research.
Applying Turning Decisions into Research Questions at BrightBrew scale
When BrightBrew evaluates turning decisions into research questions, 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 turning decisions into research questions 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.
Lesson exercise
40 minApply: Turning Decisions into Research Questions
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