Why Organizing Product Teams Around Value Streams Beats Architecture, According to Melissa Perri

In a recent LinkedIn post, Melissa Perri discusses a common pitfall in product team organization: structuring teams around technical components like APIs and databases rather than customer value streams.

Perri, a prominent voice in product thinking, highlights that this architectural-centric approach often leads to inefficiencies and the invention of work. She notes:

“When you put a product owner around every API or database component, they’ll optimize it to death just to keep their job.”

The Pitfalls of Architecture-Centric Team Structures

Melissa Perri argues that organizing product teams by technical architecture, such as individual APIs or database components, can inadvertently create an environment where team members feel compelled to invent tasks to justify their roles. This can lead to a misallocation of resources and a focus on optimizing components that are already functioning adequately, rather than on delivering tangible customer value.

According to Perri, this can result in situations where product owners dedicate significant time to perfecting an API that doesn’t necessarily require such intensive focus, simply because it’s their assigned area of responsibility.

“I’ve seen product owners spend months ‘improving’ an API that was perfectly fine a year ago, simply because they needed something to do.”

This tendency to invent work, as Perri points out, is a direct consequence of aligning team structures with system architecture rather than with the flow of value to the end-user.

Structuring for Customer Value Streams

Perri advocates for a fundamental shift in how product teams are organized, emphasizing the importance of mapping out the entire customer journey and the value delivered at each stage. She suggests that teams should be structured around these complete customer value streams, which cut across multiple technical components.

Examples provided by Perri include organizing around concepts like the “user onboarding experience” or the “payment processing flow.” These represent end-to-end journeys that deliver clear value to the customer and require cross-functional collaboration.

In Melissa Perri’s view:

“Your team structure should mirror your value streams, not your system architecture.”

This approach, she explains, allows organizations to scale effectively without creating artificial silos that can hinder progress and lead to individuals feeling the need to constantly justify their existence through unnecessary work.

Connecting Architecture to Value

While advocating for value stream alignment, Perri does not dismiss the importance of technical components. Instead, she stresses the need to connect these underlying platforms and people back to the customer value they enable. The key is to ensure that the technical structure serves the value delivery process, rather than dictating it.

Perri concludes by posing questions to her audience, asking about their current team organization and whether they recognize the “architecture trap” within their own companies. This engagement encourages further reflection on team structures and their impact on delivering customer value. The insights shared in this post are also a key topic from a recent episode of the ‘Product Thinking with Melissa Perri’ podcast.