Product in Practice: Opportunity Mapping Led to a 20% Lift in LTV at Grailed

Grailed's Discovery team spent eight months building a curated feed that barely moved the business. After adopting continuous discovery habits and an opportunity solution tree, they reframed the problem in customer language, realized users wanted algorithmic relevance rather than manual curation, and iterated with small tests. The feed then drove four to five times more discovery and GMV, with users who activated through it showing roughly 20% higher LTV. The case shows that grounding opportunities in real customer language and building evidence incrementally can turn an underwhelming launch into a measurable business win.

01Key takeaways

• Ground opportunities in the words customers actually use, not in business-outcome language.
• Map your assumptions before building solutions, since first attempts at framing are often wrong.
• Build evidence cumulatively over weeks and months rather than expecting a single decisive answer.
• Use small, low-lift tests to validate customer-stated opportunities before committing to full builds.
• Visual diagrams communicate intent more clearly and efficiently than long documents.
• As a PM, facilitate team idea generation rather than owning every idea, which improves both outcomes and team engagement.

02Key sections

Starting point and the underwhelming feed

The team invested eight months in a user-curated feed that only broke even after launch. This failure prompted them to rethink how they approached discovery.

Visualizing assumptions with an opportunity solution tree

The team dumped their collective assumptions into a first draft tree and then validated them through customer conversations. The tree evolved as they learned what users actually said.

Reframing opportunities in customer language

Users did not ask to curate feeds; they asked for more of what they liked and less of what they didn't. Framing opportunities in these words enabled small, targeted tests.

Business and user results

Feed-driven discovery and GMV grew four to five times, and feed-activated users showed about 20% higher LTV with higher retention. Users also began praising the feed unprompted.

Practical learnings from the team

The team recommends mapping assumptions before jumping to solutions, working together in person, communicating through diagrams, and treating the PM role as facilitation rather than order-giving.

03From the post

“What do your customers care about? This seems like a simple enough question, but many product teams struggle to answer it honestly. Often the first instinct is to frame an answer in terms of what your business cares about. But remember: Your customers don’t care about your business outcomes.”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.