Product Thinking: Before You Build, Think.

In March 2021, a listener sent Melissa Perri a question with an awkward little twist. How do you measure an internal product when its users are forced to use it? The usual commercial yardsticks did not fit. There was no familiar customer acquisition calculation to reach for. Attendance, in this case, was compulsory. Success was something else.

That question captures the appeal of Product Thinking. Software can be delivered, adopted, and still leave the important problem untouched. Perri’s show makes room for the questions that disappear when a product meeting becomes a tour of the backlog. What are people trying to accomplish? What evidence would show that this helped? Who gets to change direction?

The question behind the question

The name sounds like a general interest podcast for people who build things. Its center of gravity is more particular: the organization that tells those people what to build. Interviews with practitioners sit alongside “Dear Melissa,” where listeners bring career dilemmas, internal products, legacy systems, and confusing leadership mandates. The introductory episode appeared in January 2021.

Consider the internal-tool problem. When use is compulsory, usage alone tells you little about whether the product works well. The interesting inquiry moves toward the job being performed and the trouble encountered along the way. For a product manager, that change in question can be useful before a budget is approved. It is also useful after everyone has congratulated themselves on the launch.

Product Thinking’s audience therefore extends beyond the person whose title contains “product.” A designer investigating customer needs, an engineer wondering about priorities, or a founder wearing several hats can enter the same discussion. Senior leaders have a particular reason to listen: some of the difficulties described are created above the team’s authority to fix them.

A microphone attached to a classroom

Product Thinking is a media brand inside Product Institute. Perri is the institute’s founder and CEO, the author of Escaping the Build Trap, and co-author, with Denise Tilles, of Product Operations. She has also taught product management in Harvard Business School’s MBA program. The podcast translates that educational focus into conversations that people can access without enrolling.

The business surrounding the microphone sells self-paced courses, team training, coaching, and leadership programs. Product Management Foundations contains 77 lessons and 26 templates and tools. It moves from goals and customer problems into experiments, solutions, and prioritization. Enterprise training adds coaching and progress tracking so that the classroom material can meet an organization’s actual work.

The paying audience includes companies developing product capability across teams. Product Institute features testimonials from UKG and athenahealth, among others. These are customers of the training business; their presence should not be mistaken for a count of podcast listeners. The distinction matters because an educational company and a popular show can support one another while serving different needs.

There are other places to hear product leaders, including Lenny’s Podcast and Mind the Product’s The Product Experience. Product Thinking’s recognizable emphasis is the machinery around product work: leadership choices, operating practices, discovery, and the questions listeners submit. It gives the ambitious product manager a reason to look beyond personal technique.

“Should we build this?”
“Why?”

The two questions at the heart of Product Institute’s Foundations course.

The experiment should be smaller than your ego

In the May 2026 discovery compilation, Teresa Torres explains a progression from the result a team wants, to customer needs, to possible solutions. Christina Wodtke discusses making playtesting a weekly habit. Julia Austin warns against skipping the foundation work because AI makes construction feel easy. Her argument is pointed: a product later blamed on marketing may have gone wrong in discovery first.

What can a reader copy? Put a customer conversation on the calendar each week. Write down the result you want before defending a feature. Make the next test small enough to change your mind without writing off a quarter’s work. These are practical starting points drawn from the show’s teaching, rather than a promise that any particular experiment will succeed.

Amy Edmondson’s 2024 appearance adds discipline to the idea of failure. An intelligent failure pursues a goal in unfamiliar territory, follows preparation, and keeps the experiment appropriately small. That offers a useful distinction for the next retrospective. A preventable mistake and a carefully bounded attempt to learn should not receive the same explanation.

AI makes the old question louder

The latest listed episode, dated June 24, 2026, discusses research co-published by Product Institute and Product Circle. The survey collected 309 responses. It found widespread use of AI coding assistants, alongside much less confidence that AI was improving the operating model. Perri describes the findings as supporting concerns she already had about how organizations make decisions.

The survey is concentrated among senior product practitioners and is not a representative census of every company. Still, its tension is worth discussing. Faster construction leaves teams needing judgment about priorities, customer evidence, and review. Perri’s recommended response includes revisiting workflows and making strategy concrete enough for product managers to use in daily decisions.

Listening is the inexpensive part

The archive is free. For a senior leader considering structured training, Product Institute’s CPO Accelerator lists a $5,000 fee for a three-month program, with nine hours of live sessions with Perri and a cohort of up to 20. It is designed for scaling technology companies. The advertised program includes applied assignments, case studies, and an alumni community.

The harder investment is organizational permission. As a practical matter, weekly research helps little if nobody can act on an uncomfortable finding. Training faces limits when priorities cannot change or leaders reward completed features regardless of results. Product Thinking gives listeners questions and methods; applying them still requires access to customers and authority to make choices.

Perri announced a pause in new episodes in June, citing other commitments. That leaves a substantial archive to explore. A sensible place to begin is with the problem already sitting in your next meeting. Find a relevant conversation, bring one question back, and see whether the answer changes what your team decides to build.