Market research
Tell me about a time when customer research led you to a completely unexpected insight that changed your strategy.
Pick a story where you started with a hypothesis the research proved wrong, and say so early. Describe what you expected, what customers told you instead in specific detail, and how you checked the surprise against data before acting.
Then explain what changed, who you had to convince, and the result. Close with what you would do faster next time.
5 min read
Free 10-minute mock
Practice “An unexpected research insight” free
Your first mock interview is free (10 minutes). No card needed.
What an unexpected-insight story has to prove
Research that confirms what everyone believed is easy to report. This question wants the harder case, where you held a hypothesis loosely enough to let customers overturn it. The story has to prove that you noticed the surprise, that you checked it before believing it, and that it changed a decision someone acted on.
Market expertise carries most of the score. The rubric’s Exceptional level talks about spotting emerging customer needs before they’re obvious. A well-told surprise is one of the few ways to show that inside a forty-five-minute interview.
Picking a research surprise that changed a decision
- A named wrong hypothesis. You can state what you and the team expected, and why it was reasonable.
- A specific surprise. Something a listener can picture, such as a person, a moment, or a workaround.
- A verification step. Data or extra conversations that turned an anecdote into a finding.
- A strategy change. Positioning, targeting, pricing, or the product itself, and more than a new email subject line.
- A result you can defend. A modest honest number beats a large vague one.
The STAR method works as a checklist here. The order below follows the insight more closely than the four letters do.
Telling it from wrong hypothesis to result
- The hypothesis, stated plainly, and the business problem behind it.
- How you set out to test it.
- The surprise, with one concrete detail.
- How you checked it against data or more conversations.
- What changed and who you had to convince.
- The result, and the one thing you would do faster.
A tutoring-marketplace story, spoken
“We ran a marketplace matching high school students with tutors, and too many families cancelled after the first month. Everyone, me included, assumed it was price. So I set up twenty calls with parents who’d cancelled, mostly to test a cheaper plan. About halfway through, a mother said something that stuck. She’d have paid double, but her son refused to go back after the first session. I started asking every parent who had decided to stop, and in most families it was the student. Before I believed it, I went to the data. Families whose student rated the first session below five stars cancelled at about three times the rate of everyone else, regardless of price tier. So the problem was the first match, and our marketing talked only to parents. We added a free rematch after session one, asked students two questions about how they like to learn before matching, and rewrote onboarding for the student. First-month cancellations fell from twenty-eight to nineteen percent over two terms. I’d have checked the ratings data before the calls, which would have saved three weeks.”
The mother’s line makes the story memorable, and the ratings check makes it credible. An answer with only the first sounds like an anecdote. An answer with only the second sounds like a dashboard report.
Three ways an insight story falls flat
The surprise nobody would find surprising
An insight such as “customers care about ease of use” surprises no one. If the interviewer could have guessed it, choose another story or sharpen the detail until it is specific.
The unverified anecdote
“One customer told us she only used the product on her phone, which completely changed how we thought about the market, so we rebuilt the onboarding around mobile.”
It may well be true, and it rests on one person. Add a sentence about the check, such as the share of active users on mobile, before describing the change.
The finding nobody acted on
A surprising readout that sat in a deck shows research skill without impact. If your best insight didn’t change anything, say what blocked it and what you did with it in your own work. Honesty about the gap scores better than stretching the ending.
Follow-ups that test whether the surprise was real
| Follow-up | What they’re really asking | How to answer |
|---|---|---|
| How many conversations before you believed it? | Whether you rushed | Give the count and the data check that settled it |
| Who pushed back? | Influence | Name the person, their reason, and the evidence that moved them |
| What if the data had disagreed with the calls? | Rigor | Say you would have looked at which group the calls represented before acting |
| How do you avoid overreacting to loud customers? | Judgment | Explain your threshold, such as a pattern across segments backed by behavior |
| What did the insight cost? | Honesty about trade-offs | Name what you stopped doing, like the discount plan you had been building |
More questions in this category
Frequently asked questions
- What if my best insight story has no big number?
- Use the strongest evidence you have, such as a shift in win rate for one segment or a change in how sales describes the buyer. A modest, honest number lands better than an inflated one.
- Does the insight have to be dramatic?
- It needs to have surprised your team and changed something. A small reversal you acted on makes a better story than a big one you only reported.
- Can the insight come from another team’s research?
- Yes, if your part is clear. Interpreting another team’s data, spotting the implication, and driving the change is a legitimate role to describe.
Guides that help with this question
All guidesFree 10-minute mock
Practice “An unexpected research insight” free
A Mokk session asks this question, follows up on your answer, and scores it on five competencies. Your first mock is 10 minutes, scored like a full interview. No card needed.
Your first mock interview is free (10 minutes). No card needed.
Practice “An unexpected research insight” free
10 minutes · no card needed