Thread by @shravantickoo23

1/ The story of a feature for Product Managers

A thread 🪡

A Short story of a feature update to be released 2 months from now

- Decision making in current context is important as the situation will have changed from the time we created the roadmap or the last quarter when the update plan was revised

2/ Fixing goals

Break down the goals

- Who is the customer segment we are targeting e.g spenders/non-spenders , New installs , D7 folks

- What are the metrics for the customer segment which will be affected e.g KPI 1 , KPI 2 , KPI 3

3/ Brainstorming w.r.t to goals

Collecting as many relevant ideas/hypothesis with bias or judgement

- Collecting 2 cents from people on the floor i.e product , design , analysts , QA.
- Cross project individuals e.g content /ops

Secondary research

- Data
- Anecdotal evidence
- Competitor analysis
- User interviews if possible

4/Coming up with top 3 possible designs

- Present top 3 to CXO's
- Keep iterating till you align to one

5/ For each feature , map the primary goals of the feature

- Take rough engineering estimations
- Do impact analysis of each feature broken down by KPI and priortize
- Move to representation : Sketch -> Wireframe -> Mockup -> Prototype

6/ Featured locked and foundation phase

Sprint 0 : High level Epics and stories
- PM design detail & User acceptance criteria
- Creating user stories and detailed PRD

7/ Development phase begins

Sprint cycles
- Tshirt sizing by devs
- Sprint planning
- Daily scrum
- Mid sprint review

8/Pre-release prep and limited release

- Plan release date and scope
- Limited segment release for KPI's

9/ Post release war room

- Stability of build monitoring
- Measuring performance of KPI's set
- Optimising and experimentation of feature
- Hot fix if any

10/ Gradual rollout

- Gradual rollout and switch off server feature if required
- Next roadmap Item