Product Discovery with Internal Customers - All Things Product Podcast with Teresa Torres & Petra Wille

This podcast episode tackles a common trap for internal product teams: gathering requirements through stakeholder meetings instead of observing how real users actually behave. The hosts argue that when colleagues are both the users and the people requesting features, the lines blur, and teams end up building what was asked for rather than what solves the underlying problem. They recommend mapping stakeholders to separate end-users, informed parties, and sponsors, and using story-based interviews to uncover real pain points. Internal teams, they note, have a valuable advantage in proximity and access to users that they often fail to exploit. The conversation also covers the sensitive politics of process optimization and how outcome thinking can redirect stakeholder debates toward results.

01Key takeaways

• Treat internal stakeholders' feature requests as hypotheses about problems, not as final requirements.
• Map who uses the product, who is informed, and who sponsors it before planning discovery.
• Use story-based interviews asking about recent specific experiences to uncover real behavior.
• Exploit your proximity to colleague-users to run continuous discovery rather than one-off requirement sessions.
• Redirect stakeholder debates toward desired outcomes instead of prescribed solutions.
• Clarify who owns internal process improvements before changing them to avoid stepping on toes.

02Key sections

The requirement trap

Internal teams often default to collecting requirements in meetings, which produces solutions that miss the real need. The hosts explain why this pattern persists in internal tooling.

Stakeholder mapping

Separating users, informed stakeholders, and sponsors helps teams understand whose input shapes decisions and whose experience matters most.

Story-based interviews

Asking people to recount specific recent experiences reveals actual behavior and hidden friction better than asking for opinions or feature wishes.

Leveraging internal access

Proximity to users makes continuous discovery easier inside a company, yet internal teams frequently assume they are exempt from standard discovery practices.

Navigating process and politics

Improving internal processes raises questions of ownership and responsibility, and outcome-focused conversations help reduce friction with stakeholders.

03From the post

“Listen to this episode on: Spotify | Apple Podcasts In this episode of All Things Product, hosts Petra Wille and Teresa Torres dive into a common challenge faced by internal product teams—relying on stakeholder meetings instead of proper discovery practices. Why do so many teams collect requirements through meetings rather”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.