--- title: "Product Storytelling Practice Exercise" description: "Diagnose three failed investor pitches for the same product and rewrite one that lands in this product storytelling practice exercise for product managers." canonical_url: "https://builderscamp.com/guides/challenges/product-storytelling-investor-pitch-rewrite" date_published: "2026-09-16" date_modified: "2026-09-16" author: "Andre Albuquerque" publisher: "Builders Camp" guide_class: "challenges" --- # Product storytelling practice exercise for product managers **TL;DR:** This is Builders Camp's Product Storytelling practical challenge: diagnose why three PMs each failed to land the same investor pitch, find the real hero of the story, and write the version that works. It runs about 90 minutes and is rated intermediate. ## What is the challenge scenario? The product is Memo, an async voice note tool for managers to communicate with their direct reports: short voice clips instead of walls of Slack text, sent on your own schedule, received when it works for the other person. Three product managers from the same cohort pitched Memo to the same early stage investor at the same demo day. All three walked out without a term sheet. Jordan opened with low latency audio encoding and a serverless architecture, and called it a technical moat. Priya opened with a feeling, the friction between what you mean and what you typed, but never turned that feeling into a concrete fix. Marcus had the right structure, a clear problem, real traction data, 200 signups in two weeks, but made the manager receiving the messages the hero of the story instead of the direct report actually drowning in text. One led with tech nobody asked about. One led with feelings and never landed. One had the right structure but picked the wrong hero. Your job is to figure out what went wrong in each, then write the version that works. ## What are you asked to do? Rank the three pitches from strongest to weakest, and for each one, write what it did well and the specific thing that killed it. Identify the real hero of Memo's story: who actually suffers, what their day looks like, and what problem they cannot escape. Write an 80 word opening with no architecture and no feature list, that starts with the person and makes the investor want to know what happens next. Expand that opening into a full pitch using the hero's journey structure: the world before, the catalyst, the product, the world after, the market, and the traction and ask. Finish by adapting the same story for your first engineering hire, without using the word users anywhere. ## What does a strong answer cover? This bootcamp does not publish a rubric for its practical challenge, so check your own draft against the curriculum's own questions instead of a worked solution: - Does the diagnosis name the specific line or choice that lost the investor in each version, rather than a general verdict that it was weak? - Does the rewritten story center on the person who actually suffers from the problem, not the person who happens to be in the room? - Does the 80 word opening lead with that person and their situation, with no architecture and no feature list? - Does the full pitch keep the same emotional thread running through traction and the ask, rather than dropping it once the numbers appear? - Does the engineering version make the person real without ever using the word users? ## Skills this exercise practises Diagnosing why a pitch fails even when parts of it are strong, identifying the correct hero for a product narrative, building a hero's journey structure that carries through to traction and the ask, and adapting one core story for a different audience. ## Which bootcamp does this challenge come from? This is the practical challenge from [Product Storytelling](https://builderscamp.com/bootcamps/product-storytelling), Builders Camp's one week bootcamp on crafting product narratives that align teams and drive adoption, led by Andre Albuquerque across two 90 minute live sessions. Completing it counts toward that bootcamp's certificate. The [one-pager template](https://builderscamp.com/guides/templates/one-pager-template) guide is a useful next step for turning this exercise's pitch into a document you can actually send, and [how to get promoted to senior PM](https://builderscamp.com/guides/path/how-to-get-promoted-to-senior-pm) covers why this kind of persuasion skill matters beyond a single pitch. The [data storytelling practice exercise](https://builderscamp.com/guides/challenges/turning-data-into-storytelling-netflix-narrative) elsewhere in this series practises the numbers-driven side of the same skill. Builders Camp runs live and self paced bootcamps in product management and AI product building. [See the Product Storytelling bootcamp](https://builderscamp.com/bootcamps/product-storytelling?utm_source=guide&utm_campaign=product-storytelling-investor-pitch-rewrite) for current cohort dates and the full self paced curriculum. ## Frequently asked questions ### Why did all three pitches in the scenario fail, even the one with real traction numbers? Version A led with architecture nobody asked about, Version B stayed at the level of feeling and never landed on a fix, and Version C had real data and structure but made the wrong person the hero of the story, the manager instead of the person actually suffering the problem. ### What does the exercise mean by finding the real hero of the story? It means identifying who actually wakes up frustrated and works around the problem every day. In the Memo scenario that is not the manager receiving the message, it is the person who dreads writing it, and the pitch only lands once that person is named. ### Why does the exercise ban the word users in one of the steps? The final step asks you to tell the same story to an engineering team, with the constraint that you cannot use the word users anywhere. The point is that engineers build for specific people, not an abstract category, and naming the person keeps the stakes real. ### Is the 80 word opening supposed to mention the product's features? No. The exercise is explicit that the opening should have no architecture and no feature list. It should establish who is hurting, what it costs them, and why existing tools fail, so the investor wants to know what happens next. ### How long does this practical challenge take? Builders Camp lists it at 90 minutes and rates it intermediate difficulty. Diagnosing all three pitches honestly, not just picking a favorite, takes real time before you even start writing your own version. ### Does completing this exercise count toward a certificate? Yes. It is the practical challenge for the Product Storytelling bootcamp, and submitting it counts toward that bootcamp's completion and its LinkedIn integrated certificate. ## Sources - [Builders Camp: Product Storytelling bootcamp](https://builderscamp.com/bootcamps/product-storytelling) ## How this guide was made Researched from Builders Camp's bootcamp, track and masterclass material and the sources listed on this page, drafted with AI, and fact-checked against every source cited.