Write a PRD and Let AI Grill You
Maps to: Product Manager · Founder, Engineering Manager, UX Researcher, Strategy Consultant, Designer
You're going to write a real Product Requirements Document for a feature you care about, then have AI play three people who tear into it from their own angles: an engineer, a designer, an exec. You decide which objections to take and which to push back on, then revise. That's the actual product-manager muscle, deciding what to build and defending the call when smart people disagree, and doing one tells you fast whether owning that kind of decision is your kind of work.
The plan
0/4 doneYou're 20% in just for starting, the hardest part. Mark your first step done to keep the momentum.
Pick a real feature for a real product: your school's site, your favorite app, a parent's business, an app you wish existed. Write the one-pager: the problem, the target user, and the one success metric. This is the spine everything hangs on.
Objective: A one-page problem statement: problem, target user, success metric.
- 1
Pick the feature. Real product + real problem beats a made-up one.
- 2
Write the one-pager: what problem, for whom, and the one metric that says it worked.
Your call
Choose the feature and write the problem, target user, and one success metric, yourself.
The feature, and the one success metric.
What good looks like: Your one-pager names the problem, the user, and one success metric clearly enough that someone else could tell whether the feature worked.
- If you can't name the one success metric, you don't have the problem clear yet.
- 1
The bar to look back against
A published PRD that survived challenge from three angles and was revised in response, with the reviewer dialogue included, and you can point to which objections you accepted, which you pushed back on, and why. The judgment is the work: not 'I wrote a doc,' but 'I made the prioritization calls and can defend them.'
Finish the final step, then submit what you built. Your progress is saved.
Tools you'll use
Step 1 · Pick a feature + write the one-pager
Step 2 · Write the full PRD
Step 3 · Survive the stakeholder grilling + decide what to change
How this shows up on a resume or college app
I wrote a PRD for [feature] and had AI stakeholders pressure-test it from three angles (engineering, design, and executive), then decided which objections to accept, which to push back on, and what to cut. I learned that product management is mostly anticipating the questions you don't want to be asked, and owning the call when smart people disagree.