Help the audience understand the context behind why we are doing this project.
- I am
<who>
. I am trying to<outcome/job>
. But<problem/barrier>
because<root cause>
which makes me feel<emotion>
.
- Goal / What success looks like
- Goal / What success looks like
Non Goals
- Non Goal
Hypothesis:
If we <achieve/enable X>
, then <user behavior Y changes in this way>
leading to positive metrics Z
. Include guesses for size of the win on specific metrics, using past launches as a baseline.
Tell your use cases in story format, starting before the user encounters your feature and including their thoughts and motivations. Show how the feature fits into the users' lives and has a big impact.
At a high level, what's included in V1 vs. later versions? How big of a project is this? What's the roll-out / testing plan? Consider the major pieces of functionality, Mobile, Platform, Internationalization, Entry Points, User Onboarding.
- For example, were there any alternatives considered? Are there any constraints known at the time of project assignment?
- List of articles, documentation, how-to guides etc. to support the project
- List of teammates and/or Stakeholders, Partners with direct interest in the project and its success/completion
Include some mocks or a prototype to illustrate the concept. Similarly, you can list what will be included in the end-product or completed artifacts.