Try a live scenario

Make your call. Register free to see the full reveal.

CB Mid

Arjun is a product manager at an early growth consumer app. He owns the retention roadmap and the sprint slot allocated to it.

The sprint review ran about twenty minutes over schedule. The Head of Growth had one slide up for most of the second half a bar chart showing 18 % week on week new user growth, with a title that read "Retention Initiative Validated by Duolingo Playbook."

Head of Growth: "We've been sitting on the retention slot for two sprints waiting for the right moment. This is it. Duolingo ran this exact mechanic at scale and it improved D30. We're at the right stage to do this. I've already flagged to the leadership team that something is coming before the board review, so we need to lock this by end of week."

Engineer: "Do we have enough returning users to generate meaningful streak data yet?"

Head of Growth: "The cohort will build into it. That's the point of shipping it now you build the habit loop while the user base is still forming."

The PM noted the question and moved on to scope estimates. The notification feature two sprints back had outperformed every benchmark pulled from industry podcasts, so the team's instinct on sourcing calls had been pretty solid lately.

The roadmap slot was confirmed before the meeting ended. Another team was waiting for the same slot.

You are the Product Manager in this sprint review. The Head of Growth has locked the retention initiative into the roadmap based on the Duolingo reference and the growth data on screen. The engineer's question has been addressed. The slot closes at end of sprint.

What do you do?

A Arjun confirms the roadmap slot because the board review is six weeks out and the team has no other retention item ready. The Duolingo reference gives the initiative enough credibility to hold. He plans to validate cohort size once the feature is scoped. The slot is locked and the competing team is deprioritized.
B Arjun does not revisit the engineer's question after the Head of Growth responds. The Head of Growth has already signaled something is coming to the leadership team. Raising the cohort precondition now means asking a senior stakeholder to walk back a public signal, and the engineer's question was discussed but not backed by data.
C Before the slot is finalized, Arjun tells the Head of Growth that the engineer's cohort size question was not answered with data, that the Duolingo comparison assumes a returning user base they have not confirmed exists, and that he wants to verify that precondition before committing. The cost: the slot may be lost to the competing team, and the Head of Growth's commitment to the Chief Product Officer is now visibly incomplete.
D Arjun notes that the notification feature two sprints back also came from an external benchmark and outperformed. He treats that outcome as evidence that the team's instinct on sourcing external practices is calibrated. He locks the slot and assigns the engineer to define a cohort size threshold during implementation planning.