| Date | Name | Role | Version | Comments |
|---|---|---|---|---|
| @January 23, 2023 | John Doe | Founder | 0.1 | Initial draft |
| Name | Project Role | Contact for |
|---|---|---|
| John Doe | Project lead | Clarifications on user flow, product design & strategy. |
| Isaac Hobb | Tech | Anything front end, back end or data engineering |
| Emma Crosby | Marketing & Admissions | Anything around email drips for admissions |
| Justice Hill | Onboarding & Experience | Anything around email drips for activation |
Get straight to the point. Inform, but don't bore.
Why are we doing this? How does this fit into the overall company objectives?
List the technical, business, or user assumptions you might be making.
List or link to the user stories involved. Also link to customer interviews, and include screenshots of what you've seen. Provide enough detail to make a complete story, and include success metrics.
Keep the team focused on the work at hand by clearly calling out what you're not doing. Flag things that are out of scope at the moment, but might be considered at a later time.