This was inspired when working at Atheneum, we wanted something a bit lighter but still could be used as a jumping off point. Before you begin
This is an evergreen document, as your thinking changes please update it. If you have other docs, don’t copy and paste everything into here - just link out to it. Think of this as your dashboard.
Summary of the problem
Brief description of:
What problem does this solve? Supporting insights
Qualitative, quantitative and competitor research that provides context on the problem we’re trying to solve.
If you have quotes from stakeholders “this will save as 20% time” please note it down.
Impact estimate
Back-of-envelope calculation or “what would need to believe for this to be worth building” type sensitivity analysis.
Please do not just but the metrics that are going to be moved, this is actual values. Often monetary or time saved is what you would look to have here.
Also have a think about what leading and lagging metrics you would use to measure this and note them down!
Metrics
Put some idea’s down for metrics
Expected approach & scope
Current high level thinking on how we might solve the problem, if known. This could include links to technical diagrams, potential phases to deliver value.
What is out of scope?
Maybe a rough idea of phases (which could change as you get into the detail, and that’s ok.)
Effort to get to the first phase
RACI
Who are the key stakeholders involved?
Prototype link (optional)
You may have scamped something up on a napkin
Links (optional)
Any links to supporting documents (e.g. designs, Miro boards, stand alone research, Trello, etc)
Outcome of discovery
Are we going to do this