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 you want a product to do: what it is, who it's for, and how you'd know it worked. Product managers call that a PRD. Then AI plays three people who tear into it: the person who builds it, the person who designs it, and the boss who pays for it. You decide which complaints to take and which to argue with, then rewrite. That's the actual job: deciding what to build and standing behind the call when smart people disagree.
You're done when: A published plan that took fire from three angles and got rewritten because of it, with the reviewers' words alongside, and you can point to which complaints you took, which you argued with, and why. The judgment is the work: not 'I wrote a document,' but 'I made the calls and can stand behind 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, BuildMe drafts your Common App activity description from what you actually built.
Not sure yet? Play 5 minutes as a product manager first and see how the work feels.
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 that everything else hangs on. The problem it solves, the ONE person it's for, and the one number that would prove it worked. If you played the product-manager day, this is Sofia's one page 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 the three people whose work or money your idea touches, and who can speed it up or slow it down. Have AI play them one at a time: the person who builds it (can this even be built? what will it cost?), the person who designs it (does it actually help anyone? can people work it out?), and the boss who pays (why this, why now, what do we get back?). Each tears into your plan from their own corner. Then YOU decide: which complaints do you take, which do you argue with, and what do you cut? Making that call is the job. If you did the product-manager day, you answered ONE complaint for Sofia; now you take all three live.
- 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 a real product manager if you can find one.
