Product Management line, station 9 of 11
Product Teardowns & Idea Lab
Take real products apart to see the decisions behind them, then find, size and pitch new software and feature ideas of your own.
- 6lessons
- 3.5 hto read and do
- Intermediatelevel
- 6podcast episodes
Tools you'll use in this course
The lessons open these with a template ready. They work for your own job too, no course needed.
About this course
Strong product managers learn as much from other people's products as from their own. This course gives you a reusable teardown method: start from a decision, walk the product as every side uses it, map the core loop and where it breaks, follow the money, and label every claim as a sourced fact, something you observed, or your own inference. You then apply it to products that changed how people pay, travel, eat and run a business: mobile wallets such as M-Pesa, bKash and the UPI apps; ride-hailing and food delivery such as Uber, Grab, Pathao and foodpanda; and business tools such as Square, Udaan, TradeDepot and Slack. Every fact is dated and sourced, and where a company's internals are private, the lesson says so.
The second half is an idea lab. You learn where real ideas come from (workarounds, spreadsheets and chat groups, unbundling, "X for Y", new technology and rule changes), how to turn one observation into several ideas of different sizes, and how to judge them: a pain, frequency and reach screen, bottom-up sizing with a flip point, willingness to pay from behaviour, the riskiest assumption, kill criteria with a state and a date, and a one-page pitch. Twenty practice prompts, from shop credit to voice ordering, give you material to work on.
Everything is worked through at Mangrove Market, a fictional grocery chain with 320 stores, 1,800 partner shops and 600 riders, where Imran, the PM for the Store app and the Partner app, decides what to copy from these products and which idea to pitch. Each lesson ends with a template you can copy into your own work, practice tasks with model answers, and a podcast episode.
What you will be able to do
- Break down any product into users and jobs, core loop, business model, metrics, growth and moat, with every claim labelled as fact, observation or inference
- Explain why leading mobile wallets, ride-hailing and delivery apps, and business tools are built the way they are, and which constraints make each design work
- Turn a teardown into copy, adapt and avoid decisions for your own product, with one cheap test
- Generate software and feature ideas from observed workarounds, unbundling, new technology and rule changes, and write them as idea cards
- Screen, size bottom-up and pitch an idea on one page, with its riskiest assumption, the cheapest test and kill criteria stated up front
Syllabus
6 stops, about 3.5 h in total. Each stop fills in when you complete the lesson.
How to break down any product
A teardown takes a real product apart to find the decisions behind it: who it serves, what loop keeps people coming back, how it makes money and why rivals struggle to copy it. This lesson gives you a method you can reuse on any product, a one-page template, and the habit that separates a useful teardown from a screenshot tour: every claim is labelled as a sourced fact, something you saw, or your own inference.
Product teardownsCore loopsBusiness modelsEvidence and inference
Teardown: sending money with a mobile wallet
Mobile money lets hundreds of millions of people send money with a phone number, many of whom never had a bank account nearby. This lesson applies the teardown method from pm-40 to three systems: M-Pesa in Kenya, bKash in Bangladesh, and the UPI payment apps in India. You will see how the money actually moves, why agents mattered more than the app, who pays when sending is free, and how trust and fraud shape every screen.
Product teardownsFintech productsTrust and fraudBusiness models
Teardown: ride-hailing and food delivery
A ride or a meal arriving looks like one app. It is really three apps, one for the customer, one for the driver or rider and one for the merchant, plus a control room, held together by four mechanisms: the ETA promise, dispatch, pricing and ratings. This lesson tears down Uber, Grab, Pathao and foodpanda with the method from pm-40, and ends with what Mangrove's Rider app should copy.
Product teardownsMarketplacesDispatch and ETAsDynamic pricing
Teardown: tools businesses run on
Business tools are chosen by one person, used all day by others, paid for from someone's budget and controlled by an admin. This lesson tears down three kinds with the method from pm-40: a point-of-sale system (Square), B2B ordering apps for small shops (Udaan and TradeDepot) and a team tool (Slack). You will see how each wins the buyer, keeps the user, and turns the admin side into the reason companies pay.
Product teardownsB2B productsBuyer and userAdmin and permissions
Idea lab: finding new software and feature ideas
Good product ideas rarely come from a brainstorm in a meeting room. They come from watching people work around a problem, from a general tool stretched to a job it wasn't built for, from a mechanism that works somewhere else, and from changes in technology and rules that make something newly possible. This lesson gives you six sources of ideas, a way to turn one observation into several ideas, and an idea card you can fill for each. Twenty prompts at the end give you material to practise on, and the next lesson shows how to judge them.
Idea generationWorkaround spottingOpportunity framingProduct sense
Idea lab: judging and pitching ideas
Most ideas should die early and cheaply, and the good ones need a clear case. This lesson gives you a sequence that does both: a quick pain, frequency and reach screen, a bottom-up size, evidence that someone will pay, the riskiest assumption and its cheapest test, kill criteria written before you start, and a one-page pitch a decision-maker can say yes or no to.
Idea evaluationMarket sizingWillingness to payPitching
Capstone: Teardown, then pitch an idea for Mangrove
A realistic project with a rubric and a model answer.
Final exam and certificate
10 questions drawn at random, 70% to pass.
Capstone project
Teardown, then pitch an idea for Mangrove
Start with a teardown, then generate and pitch an idea. Pick one product that matters to Mangrove Market: a mobile wallet like M-Pesa, UPI or bKash (for its 21,000 cash-on-delivery orders a day and its rider payouts), a B2B ordering app like Udaan or TradeDepot (for the Partner app, where about 1,500 orders a week still come by phone), or a POS like Square (for the 400 store tills that must keep selling offline). Tear it down with the pm-40 method, using sources you can cite with years and labelling every inference, and end with three things Mangrove should copy and one it must not. Then generate ten idea cards from workarounds you have seen in this course or earlier capstones, or from the 20 practice prompts, and screen them by pain, frequency and reach. Size the best one bottom-up, and pitch it on one page with its riskiest assumption, the cheapest test and kill criteria with a date.
You will hand in
- A one-page teardown with a decision question, the seven lenses, an evidence log labelling facts, observations and inferences, and copy, adapt and avoid
- Ten idea cards, each naming the person, the moment, the workaround and its cost, labelled evidence and why now
- A pain, frequency and reach screen of the ten ideas, with the side scored and one wild card justified
- A bottom-up size of the chosen idea with counted and assumed numbers marked, a sanity check and the flip point
- A one-page pitch with the riskiest assumption, the cheapest test, kill criteria with states and a date, and a specific ask
Check what you know
Already know some of this? Answer 6 quick questions, one from each lesson, and we will mark the lessons you can skim. It takes about 3 minutes and nothing is graded.
Questions
Do I need to know fintech or logistics to take this course?
No. Each teardown explains how the money, the orders or the riders actually move before analysing the product, with every term defined. You need the basics of problems, users and value from Product Thinking Foundations.
How do the lessons handle facts companies don't publish?
Every claim is labelled. Facts come with a source and a year, observations with a date, and anything about a company's internals that isn't public is marked as inference, with the reasoning. The course teaches you to do the same in your own teardowns.
Is this useful if I build internal tools rather than consumer apps?
Yes. The teardowns cover rider apps, agent networks, merchant tools and admin features, and the idea lab draws its ideas from store, warehouse and partner-shop workarounds. Sizing and pitching include how to value an internal tool and find who will fund it.
Will this help with PM interviews?
Yes. Product teardowns, 'improve this product' questions and market-sizing estimates are common in PM interviews, and several lessons have an 'In interviews' note on what a strong answer covers.
Are the companies in the teardowns endorsing the course?
No. The teardowns use public sources such as filings, help and pricing pages, engineering posts and press reports, read in 2025 and 2026. Products change often, so check the current pages before you quote a price or a number.
Is it really free?
Yes. Every lesson, podcast episode, exercise, quiz, final exam and certificate is free. The labs and their templates for real work are free too. Plus and Premium add every lab challenge, weekly extras and a mentor on top, and they never lock the tools or the courses.
How long does it take?
Each lesson shows an honest time for reading and doing. Most people finish a course in two to four weeks at three or four hours a week.