| 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 |
Why is it important?
Problem definition and broader context as needed.
Customer value: Who are the users. What is the pain-point or opportunity?
*Business Value: How does this align with team goals and priorities?
A condensed version of this very document that provides a high-level overview of the project's goals, scope, and requirements. The executive summary should be written in a way that is easily understood by both technical and non-technical readers.*
*Few executive summary examples *here**.
What are other companies doing for this feature?
We make some basic assumptions about the workings and need of this feature.
Goals are what will be achieved by having the feature. Non-goals are things we aren't concerned about (E.g. If conversion improvement is a goal, load time improvement can be a non-goal and you just want to avoid regressions there.