# STAR: acting on customer feedback

> Write a STAR about a time you changed a roadmap based on a single customer signal. Address how you knew it would generalize.

Canonical: https://learn.significanthobbies.com/curriculum/drills/star-customer-feedback

Write a STAR about a time you changed a roadmap based on a single customer signal. Address how you knew it would generalize.

## The mechanism

Customer obsession is not saying yes to whatever they ask. It is taking their underlying problem seriously, sometimes by shipping something they did not ask for. One customer's complaint is a hypothesis, not proof — go check whether it generalizes.

## Expected evidence

starStory() returns { situation, task, action, result, metric: { name, unit, before, after }, generalizationEvidence (array of 2+ pieces of disqualifying-or-confirming evidence) }. The checker enforces structure only: four distinct sections of 20+ words, action the longest, 150+ words total, before ≠ after, and the result section must name the metric and state its after value. Aim for 250-350 words — that is the interview bar, not the checker’s.

## Hints

- n=1 is a hypothesis, not a conclusion.
- Talk to the customer, then look at the data.

## Sources and practice

- [STAR interview method (Wikipedia)](https://en.wikipedia.org/wiki/Situation,_task,_action,_result)
- [Know Your Customers' Jobs to Be Done (Christensen et al., HBR)](https://hbr.org/2016/09/know-your-customers-jobs-to-be-done)
- [Opportunity Solution Trees (Teresa Torres)](https://www.producttalk.org/2016/08/opportunity-solution-tree/)
- [Study Customer Obsession](https://learn.significanthobbies.com/curriculum/concepts/customer-obsession)
- [Try the interactive drill](https://learn.significanthobbies.com/drills/star-customer-feedback)
- [All practice briefs](https://learn.significanthobbies.com/curriculum/drills/)