I recently attended a Pollenizer Academy course – The “Lean Product Manager” by Pollenizer’s very own Michael Dijkstra. One of the most useful sessions for me was “The MVP”, where Michael showed the class how to write effective Hypotheses, Success Metrics, User Stories and Acceptance Criteria. For every feature on every business we build at Pollenizer, it’s crucial that we follow these guiding principles. By following the below approach, we don’t have to think about how to express a new feature, we know what we’re aiming for as an outcome of the build and we know what we’re looking for to validate it’s success or failure. In addition, the entire team are on the same page in regards to the benefit the user will experience and exactly how that benefit is realised (or not) in the resulting feature.
Hypothesis
We believe [target market] will [perform action] for [this reason]
Success Metric
This will be successful when [quantity] of [target market] [perform action]
User Story
In order to [achieve benefit] as a [target market] I want to [perform action]
Acceptance Criteria
Scenario 1: [title] Given [context] And [additional context (optional)] When [event] Then [outcome] And [additional outcome (optional)]