A lot of this like the type of release should have been aligned upon in the Concept Review before we started coding to avoid blow-ups and restarts later down the line.

It's important the PM clearly states the things they need feedback on upfront to make sure they walk out with what they need to move forward.

The outcome of the Product Review is to green-light shipping in some capacity (5% to 100% of users). There are a bunch of reasons why it might not pass approval.

The quality of user experience doesn't hit the bar.

We haven't instrumented the right things in order to measure impact.

We've built the wrong type of solution - for example, an experiment test when we had decided on building an MVP.

The biggest mistakes that surfaced in Product Reviews were when what the team had built drifted meaningfully away from what we agreed on in the Concept Review.

There are reasons that it should change like new insights from customer research, but otherwise, it should be pretty close.

PMs need to think ahead to the Results Review. What evidence do they plan on showing to show whether or not something was successful? We need to make sure we have those things outlined and that we can measure them before shipping.

Naishi Zhang

Casey Winters

This Product Review template is part of a system of reviews for the product team that we used at Eventbrite. The system consisted of three types: Concept Review, Product Review, and Results Review.

Product review presentation template from Eventbrite

Overview & outcome

Review the experience

Goals & success metrics

Sign up to see more