Beyond Product Centricity: Embracing Value Center Thinking to Navigate Organizational Complexity

In the rapidly evolving landscape of modern software engineering, the industry-standard mantra of "autonomous product teams" is facing a critical re-evaluation. While the concept of autonomous teams has long been an article of faith for organizations seeking agility, recent discourse suggests that the prevailing focus on "products" may be a misnomer that obscures the true nature of value delivery. At the recent Craft Conference, an international software development gathering known for exploring the cutting edge of engineering culture, Simon Rohrer argued that the rigid adherence to product-based silos often creates accidental complexities that stifle organizational coherence. By shifting the focus from product-centric models to "value center" thinking—grounded in the principles of management cybernetics—organizations may find a more sustainable path to managing the inherent paradox of stability and disorder.

The Evolution of Organizational Design

The Craft Conference, held annually in Budapest, has long served as a bellwether for shifts in software development methodologies. In recent years, the conversation has moved away from simple process frameworks like Scrum or Kanban and toward deeper, systemic questions about how structure influences output. Rohrer’s presentation, titled "Essence and Accident in Product Development Complexity," challenged the audience to reconsider how they define their work.

For decades, the industry has operated under the assumption that if you decompose an organization into autonomous product teams, you will naturally achieve speed and efficiency. However, Rohrer posits that in complex environments, individual teams are rarely delivering a standalone product. Instead, they are contributing to a fluid, ever-changing value stream. As organizations grow, the "web of dependencies" between these teams becomes the defining shape of the business. When managers treat these streams as static products, they fail to account for the essential versus accidental dependencies that emerge as initiatives, features, and market requirements shift every quarter.

Defining the Value Center

The core of Rohrer’s proposal is the transition to the "value center" model. This framework suggests that a team’s existence is justified solely by the value it provides to the wider system. By abandoning the restrictive label of "product team," organizations can better conceptualize their work as part of a nested, networked structure.

This shift is not merely semantic. It addresses the fundamental tension between agency and coherence. In a strictly product-focused model, teams often prioritize their own autonomy to the detriment of the whole. In a value-centered organization, autonomy is balanced with the understanding that the "shape of value" dictates the necessary constraints on how teams interact. If a team is building a component that is essential to the conceptual integrity of the larger system, their autonomy is naturally bounded by the need for coherence with other value centers.

Applying Management Cybernetics

To provide a structured approach to this, Rohrer draws upon the Viable Systems Model (VSM), a management theory developed by British cybernetician Stafford Beer in the 1960s. VSM focuses on the recursive nature of organizations, where each part of the system must mirror the requirements of the whole to remain viable. Rohrer adapted this theory into five fundamental questions that every value center—from an individual developer to a department lead—should ask:

1. What value am I delivering? This ensures alignment between individual contributions and the broader organizational goals, preventing the "ticket-filling" mentality that often plagues agile teams.
2. How do we coordinate? This shifts the focus from siloed execution to collaborative planning, acknowledging that dependencies require active, synchronized management.
3. How do we fit together? This addresses the "conceptual integrity" of the system, ensuring that individual efforts form a coherent whole rather than a fragmented collection of features.
4. What’s out there for us? This encourages teams to look beyond their current sprint, focusing on the "there and then" to anticipate future shifts in the business environment.
5. Who are we? An existential question that defines the team’s purpose, responsibilities, and the boundaries of their influence.

Case Study: Simple vs. Complex Molecules

In an interview following his presentation, Rohrer utilized a scientific metaphor to explain how these value shapes manifest in real-world organizations. He distinguished between "simple molecules" and "complex organic molecules."

A large-scale cloud provider, such as Amazon Web Services (AWS) or Microsoft Azure, operates primarily through simple molecules. A service like S3 or EC2 is largely standalone; it has minimal dependencies on other teams and can be developed, deployed, and scaled independently. These represent discrete products that are easily decoupled.

Conversely, a trading platform or a highly integrated financial system functions like a complex organic molecule—a protein or DNA sequence. In these environments, individual components such as pricing engines, risk analytics, and trade execution modules are technically distinct but exist in a state of value-interdependency. You cannot "decouple" the value of a trade if the pricing data is unavailable. Organizations in this category must accept that while they can technically decouple development, they cannot—and should not—attempt to decouple the inherent value flow.

Broader Implications and Industry Analysis

The movement toward value-centered organization reflects a maturing industry. For years, the "two-pizza team" model—popularized by Amazon—was the gold standard. However, data from large-scale organizational transformations suggests that while small teams are effective, they often create massive integration debt when they lose sight of the "system of systems."

According to industry analysts, the failure to address these dependencies often leads to "architectural drift," where the software system eventually becomes too rigid to support new business capabilities. Rohrer’s focus on nested, networked organizations aligns with contemporary research into Team Topologies, which argues that organizations should evolve their structure to match the cognitive load of the software architecture (Conway’s Law).

The implication for leadership is clear: the role of a manager in a complex system is no longer to command and control, but to cultivate an environment where teams understand their place within the network. This requires a departure from traditional hierarchical reporting lines. Networking—the ability for teams to communicate and coordinate horizontally without traversing the entire vertical hierarchy—is becoming the most critical competency for modern enterprises.

Conclusion: The Future of Organizational Design

As organizations continue to grapple with the paradoxical demands of stability and rapid change, the "product-only" mindset appears increasingly insufficient. By reframing the organization as a collection of value centers, businesses can create a more resilient structure that embraces its own complexity rather than fighting it.

The transition from a collection of autonomous product teams to a nested, networked organization is not a trivial task. It requires a fundamental shift in how teams perceive their purpose and their connections to one another. However, as the work of Simon Rohrer and the discussions at the Craft Conference indicate, those who successfully navigate this transition may be the only ones capable of delivering value at scale in an increasingly chaotic, interconnected world. The future of development lies not in the independence of the team, but in the strength and clarity of the connections between them.