Write a Full PRD for a New Feature
Part of the Product Management Roadmap
In short
This project ties the phase together: research a real problem, write a full PRD with stories and metrics, and get it reviewed. It's proof you can think like a PM.
The core practice project for this phase — take a real feature idea from problem statement through to a complete, engineer-ready PRD.
Think of it like this
Planning the college fest
A fest needs a theme, a budget, a list of events, who handles what, and a backup if it rains. Miss one and the day falls apart. A full PRD makes you think through every one of those before the big day.
Watch it happen
The project plan
1/6Pick a real product and a feature it lacks, like group expense splitting in a payments app.
The big ideas
What you need to know
Real evidence
Quotes and data from actual users make your PRD believable to reviewers and recruiters.
Metrics with targets
One primary metric, a guardrail, and a target you can defend.
Stories and criteria
Five to eight user stories, each with testable acceptance criteria, including edge cases.
Clear non-goals
Say what v1 won't do. It shows judgement, which is what hiring managers look for.
See it in code
Walk through the code
1# Group Expense Split: PRD21. Problem (with user quotes)32. Goals & success metrics43. Users & personas54. User stories + acceptance criteria65. Scope: in / out of v176. Edge cases & non-functional requirements87. Open questions & risks98. Launch plan & changelog1/3Start with why: the problem and what success means.
A skeleton for your PRD. Fill each section in order; if one is hard to write, you probably need more research there.
Save yourself the pain
Common mistakes
Oops
Choosing a giant feature like "add AI to everything".
Do this instead
Pick a focused feature you can explain in one sentence and research properly.
Oops
Skipping review because it feels finished.
Do this instead
Reviews from an engineer and a designer will find gaps. Include what changed in your portfolio.
Your mission
First milestone: problem and goals
Quick check
A reviewer asks, "What happens if one person in the group never pays?" Where should the answer go?
Go deeper
- 1Choose a feature idea for a product you know well, ideally with a real problem behind it.
- 2Include: problem, goals, success metrics, user stories, edge cases, and out-of-scope items.
- 3Get feedback from someone technical and revise based on the questions they ask.
Stuck on this topic? Ask an Insider
Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.
