Simon Rohrer Proposes Value Center Thinking Over Autonomous Teams in Software Development

Rethinking Autonomous Teams

Simon Rohrer, speaking at the Craft conference, discussed the limitations of autonomous teams in complex software development environments. He argued that the traditional product-focused approach is insufficient, proposing a shift towards "value center" thinking. This new perspective emphasizes that individual teams contribute to value streams rather than delivering complete products.

From Products to Value Centers

Rohrer stated that in complicated organizations, an individual team's output is not a product but a component of a larger value stream. He introduced the concept of a "value center," where each team's existence is justified by the value it provides. This framework acknowledges that value delivery is complex and involves a web of dependencies, some essential and some accidental.

Organizational Design and Dependencies

According to Rohrer, the "shape of your value" dictates an organization's structure and the balance between autonomy and coherence. He highlighted that dependencies are inherent to value delivery. Rohrer also presented five questions for every value center, based on Stafford Beer's Viable Systems Model, to help define purpose, coordination, fit, external context, and identity.

Purpose and Coherence

Rohrer explained that a system's purpose is defined by what it does, not what it intends to do. He also referenced Ralph Stacey's view on managers navigating both stability and instability. Rohrer expressed a preference for coherence in today's environment, given the prevalence of disorder.

Key Takeaways

The presentation concluded with a call to move from product-centric views to value-centric ones, from autonomy to a combination of agency and coherence, and from isolated autonomous product teams to nested and networked organizational structures. Networking is emphasized as a way to deliver value without relying solely on hierarchical traversal.