The Demo That Shaped the Roadmap: How First-and-Last Feedback Drove Misplaced Priorities
A real-world example of Serial recall effect in action
Context
A mid-stage software startup ran monthly customer demo sessions to gather feature requests and pain points. The product team relied on notes taken during these 90-minute calls to prioritize the roadmap.
Situation
During a particularly busy quarter, a product manager compiled a list of roughly 30 distinct customer asks captured across three demo sessions. To create the next-quarter roadmap, the manager used a quick pass through their meeting notes rather than a structured sorting process.
The bias in action
Because the manager reviewed the raw notes sequentially, features mentioned at the beginning or the end of each demo stood out more clearly than the dozens of items in the middle. When it came time to pick the top six items for the roadmap, four of them were requests that appeared first or last in the session notes. Middle-of-list items — including a recurring customer pain with measurable impact — were overlooked despite being raised multiple times across different clients. The team then treated the chosen items as data-driven priorities, unaware the selection was influenced by the serial recall effect rather than explicit customer weighting.
Outcome
The company built two highly visible features that pleased a subset of customers but failed to address the recurring mid-list problem causing customer support load. Over the next two quarters, support tickets related to that pain point rose by 22% and a handful of small customers churned after failing to receive promised improvements.