New Feature Template

Owned by Matthew Hall
Last updated: Sept 28, 2023
1 min read

The documentation on each feature should

  • have a clear problem that it is trying to solve

    • The problem should be support by conducting user research

  • have a hypothesis statement that includes:

    • description of the experiment you want to run

    • how you will measure success

 

Hypothesis Statement

We believe <this capability>

What functionality we will develop to test our hypothesis? By defining a ‘test’ capability of the product or service that we are attempting to build, we identify the functionality and hypothesis we want to test.

Will result in <this outcome>

What is the expected outcome of our experiment? What is the specific result we expect to achieve by building the ‘test’ capability?

We will have confidence to proceed when <we see a measurable signal>

What signals will indicate that the capability we have built is effective? What key metrics (qualitative or quantitative) we will measure to provide evidence that our experiment has succeeded and give us enough confidence to move to the next stage.