Product teardowns: one product, taken apart together.

Product Circle runs a product teardown every two weeks: members take one product apart together and sort what they find under three labels, "Works", "Doesn't" and "Steal this". It's a practical way to build product sense, because you're looking at real products with people who will question your reasoning.

Why Product Circle teardowns happen in a group

A product teardown is a structured look at a product to understand why it's built the way it is; our guide on how to do a product teardown has the full method and a template. Product Circle sessions are about doing it together.

Done with a group of PMs and founders, a teardown gets sharper. Someone spots the pricing trick you missed. Someone else has shipped the same flow and knows why it looks that way. Your "this is obviously wrong" gets challenged by someone who knows the constraint behind it.

How Product Circle teardowns work

The format is simple:

1. One product. Each session looks at a single product, not a category.
2. Taken apart together. Members work through it as a group.
3. Three labels. Every note goes under one of them.

The three labels keep the conversation honest. "Works" stops the session turning into a list of complaints. "Doesn't" stops it turning into fan mail. "Steal this" makes sure everyone leaves with something to use.

Which product is picked, and when and where each session runs, is shared with members.

Who product teardowns are for

• PMs building product sense. Product sense is mostly pattern recognition, and teardowns give you patterns quickly. They're also good practice for the product design questions in PM interviews.
• Founders who want fresh eyes on decisions in their own category, and ideas they can ship next sprint.
• Designers, engineers and others moving into product, who want to practise thinking about trade-offs rather than just screens. Our guide on how to become a product manager in India covers the wider path.

How to get the most from a teardown

Use the product before the session

Go through the core flow yourself first: sign up, do the main thing, try to pay. You'll notice far more in the session if you've already felt the friction.

Take screenshots as you go

A screenshot of the exact screen makes a "Doesn't" note concrete. "The second screen asks for location, notifications and contacts at once" beats "onboarding is annoying".

Write one note under each label

Arrive with at least one "Works", one "Doesn't" and one "Steal this". It forces you to be balanced, and gives you something to contribute even if you're quiet in groups.

Ask why, not just what

The best teardown notes include a guess at the reason. Why might a delivery app show delivery time before sign-up? Probably because speed is the promise, and showing it early lowers the effort of trying. Guessing the reason is how you learn to make the call yourself.

Take one "Steal this" back to work

Pick one idea and write down where it would fit in your product. If it doesn't fit, write down why. Either way, you've practised the judgement.

An example teardown, in three notes

Here's an illustrative example of how notes look, using the three labels. It's an example of the format, not a record of a real session.

Imagine a teardown of a food delivery app's first order flow:

• Works: Address saved in one tap. The app reads your location, suggests the address and lets you confirm it without typing. Less effort at the moment of highest drop-off.
• Doesn't: Six permission prompts before the first order. Location makes sense. Notifications, contacts and others before you've ordered anything ask for trust the app hasn't earned yet.
• Steal this: Delivery time shown before sign-up. You see the promise before you're asked to commit. A B2B tool could do the same by showing a sample report before asking for a work email.

Notice the shape: what happened, why it matters, and how it transfers. That's the habit teardowns build.

How teardowns connect to the rest of membership

Teardowns sit alongside the weekly AMA, where PMs and founders talk through the decisions behind products like the ones you take apart, and member intros, which help you find the person in the circle who has built something similar. The full list is on the membership page.

Frequently asked questions

How often are Product Circle teardowns?

Every two weeks. Each one looks at a single product.

What are the three teardown labels?

"Works", "Doesn't" and "Steal this". Every note goes under one of them, which keeps the session balanced and makes sure you leave with ideas to use.

Who picks the product?

How products are chosen, along with the schedule, is shared with members.

Do I need to be a senior PM to join a teardown?

No. Teardowns are useful at every level. If you're newer to product, come with one note under each label and ask why decisions were made.

What should I prepare before a teardown session?

Use the product's core flow yourself first, take a few screenshots, and arrive with at least one note under each label. That's enough to contribute, even if you're quiet in groups.

Join the next teardown

If you'd like to practise product sense with PMs and founders who will push back, the next teardown is never more than two weeks away. Start with a short application on the how to join page.