Think Like a Product Manager: Pitch a Feature and Survive the Grilling
Maps to: Product Manager · Founder · Engineering Manager · UX Researcher · Strategy Consultant · Designer
You're going to write a real plan for one new thing a product should do. Here, product just means something like an app, a website, or a business, something people already use. Your plan will say what the new thing is, who it's for, and how you'd know it worked. This kind of plan has a name, a PRD, which stands for Product Requirements Document, but really it just means a written plan that says exactly what to build and why. Then AI plays three people who each question your plan hard: the person who would build it, the person who would design it, and the person who pays for it. You decide which complaints you agree with and which you argue with, then you rewrite the plan. That's the real job: choosing what to build, and being able to explain your choice when smart people disagree.
You're done when: A plan you published online that got questioned hard by three different people, and that you then rewrote because of what they said. Each person's exact words (the reviewers, the people who questioned it) are shown right next to your plan, and you can point to which complaints you agreed with, which you argued against, and why. What matters isn't just that you wrote a document. It's that you made real decisions yourself and can explain them.
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.
When you finish you have the thing itself, plus a Common App activity description Sidequest drafts from what you actually built.
Not sure yet? Play 5 minutes as a product manager first and see how the work feels.
See what this career pays and what it takes to get in.
The plan
- 1
Step 1
Pick what to build, and get it onto one page
Every product starts as a fuzzy idea in someone's head. Your first job is to make it clear: pick one new thing a real product could do (your school's site, your favorite app, a parent's business, an app you wish existed) and get it onto one page: three lines, and every later decision comes back to them. The problem it solves, the ONE person it's for, and the one number you would watch to know it worked, something like 'people use it twice a week instead of once.' If you've already spent a day on this site deciding what gets built and what gets cut, this is that same one page, done at full size, and this time the idea is yours.
- 2
Step 2
Write the full plan
Now grow that single page into the full plan: the document that tells a team exactly what to build and why, clear enough that one person could build it and another could design it from your words alone. The boring headings are where a plan earns its keep, so give the weird-but-real situations and the things that could go wrong real effort.
- 3
Step 3
Take the hard questions, then decide what to change
Time to face three people who each care about a different part of your idea, and who could help it move faster or get it stuck. Have AI play them one at a time: the person who would build it (can this even be built? what will it cost?), the person who would design it (does it actually help anyone? can people figure out how to use it?), and the person who pays for it (why build this, why now, and what do we gain from it?). Each one questions your plan hard, but only about their own part. Then YOU decide: which complaints you agree with, which ones you argue with, and what you cut.
- 4
Step 4
Publish the plan, with what the reviewers said
Put the finished plan online with the reviewers' words next to it. A tidy document with no scratches on it looks like homework; one that shows three tough reviewers, your answers and what changed looks like the work of someone who makes decisions. Then send it to an actual person who does this job for real (a product manager), if you can find one.
