Decoding Inbound vs. Outbound Product Management

In this episode of the Product Thinking Podcast, Melissa Perry addresses a common organizational dilemma: the distinction between "inbound" and "outbound" product management. While some companies segment these roles, Perry argues for a unified approach, emphasizing that the core principles of product management remain consistent regardless of the target audience.

Defining the Terms

Perry clarifies that when companies differentiate these roles, the common industry definition is:

• Outbound Product Management: Focused on products that face external customers. These are tools or interfaces that customers use directly or integrate into their own workflows.
• Inbound Product Management: Focused on internal-facing tools. These are platforms or applications designed for employees—such as bank tellers, sales teams, or HR departments—to facilitate their work.

The Unified Product Management Process

Perry strongly cautions against treating these as entirely separate disciplines. She asserts that the "overall process of product management stays the same." Whether a product is internal or external, a product manager must always:

• Define a clear strategy.
• Set OKRs and measurable goals.
• Conduct rigorous discovery to understand user needs.
• Execute effective delivery.

While the tools and tactics may shift based on the context—for instance, A/B testing is highly effective for external products but may be less relevant for specific internal tools—the fundamental objective of "solving a problem at the end of the day" remains identical.

Challenging the Stigma of Internal Tools

A significant portion of the discussion focuses on the dangerous stigma that internal (inbound) product management carries less risk than external (outbound) management. Perry refutes this notion, highlighting that internal tools often serve as the backbone for external customer experiences.

She provides two compelling examples:

1. Algorithmic Platforms: If a platform team building an algorithm considers themselves only "inbound," they may ignore the downstream ramifications. Perry cites the example of algorithms that mistakenly deny insurance claims, noting that a narrow internal focus can lead to disastrous external consequences.
2. Service Efficiency: If a Customer Relationship Manager at a bank is forced to use poorly designed internal tools, the end-user customer suffers. Perry emphasizes that if we fail to design internal systems with the same level of care, the "end-user customer is going to have a bad time too."

Value Streams and Holistic Thinking

Perry advocates for viewing product management through the lens of value streams. She argues that every component—from developer workflows and internal HR support systems to the final customer interface—must be considered as part of a connected ecosystem.

By ensuring that every step of the value stream is designed to "deliver great value to our customers," organizations can avoid the silos created by the inbound/outbound split. Whether dealing with traditional software or modern AI products (which may require specialized skills like "evals" or testing with "data structure"), the focus must always remain on the user's problem.

Ultimately, Perry concludes that while the methodology might require "tweaks along your discovery and delivery process" depending on the specific product type, the rigorous mindset of a great product leader is universal.