Product stories: failures, comebacks and what they teach
Most product lessons are easier to remember as a story. These are real ones, checked against the documents, not the legend. Each one covers how the idea was found, what went wrong or right, and the one or two things a product manager should take from it.
The baby sock that found its market, then ran into the FDA
A baby monitor that proved its demand for $220, then spent five years at odds with the FDA.
Pixar’s Braintrust: the room with no bosses
A room of peers with no power over the director, and the sequel it helped rescue.
Qwikster: the three weeks Netflix split itself in two
A price hike, a new brand and a U-turn in 23 days. What Netflix got right, and what it didn’t.
Why stories
A definition tells you what an MVP is. A story tells you what happens when a team gets it wrong, and that’s the version you remember in a meeting two years later. The course leans on stories for the same reason: every idea is easier to hold onto when a real company learned it the hard way.
How these are told
Checked against the documents
Company filings, regulator letters and the founders’ own words, all linked at the bottom of each story. Where the record shows a disagreement, the story says so instead of picking a side.
Told for learning, not blame
Each story ends with the one or two things a product manager should take from it, not a verdict on the people involved.
Read them with the terms
Each story links to the terms it shows in action. Owlet, for one, is a case study in proving demand before you’ve proven the product can do what it promises, which is right where the MVP and ideal customer profile pages pick up.
Learn it by doing it
Product Management is a course for curious teens, in five-minute lessons with something to play with in every one. Part I is free on iPhone, iPad and Android. No account, no ads.