| 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 |
What are we trying to achieve by doing this feature.
Who are we trying to address via this feature - It could be internal teams, it could be external folks, core customers(ie end users), drivers etc
| --- | --- | --- | | Age | | | | Tier of City | | | | Income Bracket | | | | Profession | | | | Apps Most Consumed | | | | Goals/Job to be done | | | | How do they discover your product? | | | | Decision making factors (Eg: Money, Location, other blockers) | | | | Pain Points | | |
What does the above persona need that we are trying to solve here.
Explain in user words, what are we trying to achieve here. And then try to map those with feature to make sure your features cover all user painpoints.
User Objective: As a user X , I want to achieve goal Y for some reason Z