Beyond Autonomous Teams in Software Product Development

Ben Linders · rss · 2026-09-10 source ↗ Reader 🖥️

Durable, Domain-Owning Teams (vs. Fluid Teams)Agency Organizational Coherence Sociotechnical Architecture Software Design Fundamentals Team Autonomy Team Topologies Value Streams & Verticals Viable Systems Model (Management Cybernetics)

Because a team's contribution in a complex organization is really a share of an ever-shifting web of value dependencies rather than a discrete 'product,' organizations should replace 'autonomous product team' thinking with 'value center' thinking, in which every unit at every level (person, team, team-of-teams, org) answers the same five recursive questions and trades off autonomy against coherence according to the shape of the value it carries, not according to ideology.

theoretical · conference-talk report with follow-up interview (InfoQ news article) — Ben Linders reports on Simon Rohrer's Craft Conference talk and interviews him afterward. The argument is Rohrer's, filtered through Linders' summary plus direct quotes; it is a conceptual reframing (a new vocabulary and a management-cybernetics justification) rather than an empirical study — no data, case outcomes, or before/after comparison are offered.

Structure

Part	Role
Opening reframe: from product to value stream to value center	Establishes the thesis that 'autonomous teams' is dogma and introduces 'value center' as the replacement unit of analysis
'Value designs organization': the autonomy/coherence trade-off	States the central causal claim — the shape of value (its dependency web) constrains achievable organizational structure and the autonomy-coherence balance
The five questions and their cybernetic pedigree (Viable Systems Model)	Supplies the operational framework and its theoretical authority (Stafford Beer's management cybernetics)
Purpose-as-what-you-do and the Stacey order/disorder quote	Grounds 'who are we' (one of the five questions) in a non-aspirational, descriptive notion of purpose, and frames coherence as the more urgent pole given real-world disorder
Closing summary: products→value, autonomy→agency+coherence, autonomous teams→nested/networked org	Restates the thesis as three paired shifts and adds the claim that networking lets value flow without traversing hierarchy
Interview Q1: visualizing value shapes via the molecule metaphor	Illustrates essential vs. accidental dependency with a worked example (simple cloud services vs. a trading platform)
Interview Q2: applying the five questions in practice	Walks each of the five questions through a concrete team-level example (Scrum backlog, sprint goal, conceptual integrity) and asserts they recur at every organizational level

Key terms

value center Viable Systems Model (Management Cybernetics)
Rohrer's replacement for 'product team': a unit at any level of the organization whose identity is that it delivers value, not that it owns a product — because what counts as 'the product' shifts every quarter/project/feature while the value contribution persists.
value stream Value Streams & Verticals
An unstable, constantly-changing flow (attributed to 'Chris Mats') rather than the durable, mappable entity implied in most Lean/value-stream-mapping literature.
agency (vs. autonomy) Agency
The capacity to act and contribute purposefully within constraints — contrasted with 'autonomy,' which implies independence from those constraints.
essential vs. accidental dependencies
Some of the connections between value-delivering units are inherent to the value itself (essential — cannot be removed without destroying the value, e.g. pricing-risk-trading coupling in a trading platform) while others are artifacts of how the org happens to be arranged (accidental).
the five questions (Viable Systems Model)
A recursive diagnostic — what value am I delivering, how do we coordinate, how do we fit together, what's out there for us, who are we — meant to apply unchanged at every level from individual to whole organization, derived from Stafford Beer's Viable Systems Model.
nested and networked organization
An alternative organizational topology to 'autonomous product teams,' in which value flows peer-to-peer between value centers without needing to traverse the formal hierarchy.

Propositions

explicitcontestedAutonomous teams are treated as an unexamined article of faith in modern software development, and this framing should be replaced by 'value center' thinking.conf: high
contradicts ←Team Topologies: Organizing Business and Technology Teams for Fast Flow · p14 — This book's case for long-lived, bounded, ownership-holding teams is precisely the 'autonomous team as unexamined article of faith' framing that the value-center piece argues should be replaced.
explicitIn a moderately complex organization, what an individual team delivers is not a stable 'product' but a share of a value stream that changes every quarter, project, initiative, and feature.conf: high
explicitEvery team in an organization should be understood as a 'value center' — valuable in itself because of what it delivers — rather than as an owner of a product.conf: high
explicitThe shape of an organization's value (its web of dependencies) determines and constrains what organizational structures are possible, including the achievable trade-off between team autonomy and organizational coherence.conf: high
extendsCoherence, Connections, and… Spacetime Crystals · p6 — Both locate a 'coherence ceiling'/constraint on autonomy in structural properties external to the team itself; this doc names the source of that ceiling explicitly as the shape of value dependencies.
explicitSome dependencies among value-delivering units are essential to the value itself (cannot be removed without destroying it), while others are accidental artifacts of organizational history — mirroring Brooks' essential/accidental complexity distinction from software design.conf: high
explicitEvery value center, at every organizational level from an individual to the whole organization, should be able to answer the same five recurring questions: what value am I delivering, how do we coordinate, how do we fit together, what's out there for us, and who are we.conf: high
supports10) Una Aamodt Mathisen om å lede når du ikke har fasiten · p4 — Both argue that team autonomy needs a structuring frame (direction-setting / the five VSM questions) rather than standing alone as unqualified independence.
explicitThe five questions are derived from Stafford Beer's Viable Systems Model, a 1960s management-cybernetics framework.conf: high
explicitAn organization's or system's purpose is not aspirational or self-declared — it is defined descriptively by what it actually does.conf: high
explicitcontestedBecause today's environment contains substantially more disorder than order, managers should lean toward preferring coherence even though they are more comfortable dealing with order.conf: medium
contradictsTBM 434: How Maps Can Hide Problems · p9 — Rohrer frames 'preferring coherence' as the right response to disorder without qualification; the TBM source explicitly argues perfect/maximal coherence is undesirable because it requires stasis or over-constraint — a tension this doc doesn't acknowledge.
explicitOrganizations should shift from autonomous product teams to a nested and networked structure, in which value can be delivered without needing to traverse the formal hierarchy.conf: high
extends1) Torbjørn Larsen: Det nærmeste vi kommer Steve Jobs · p16 — Extends reverse-Conway sequencing (design architecture first, then place organization on top) with a networked/nested alternative topology for coordination without hierarchy traversal.
explicitThe 'how do we fit together' question extends beyond backlog/sprint-goal coordination to a system's conceptual integrity (Fred Brooks) — i.e., whether resourcing and focus choices serve a coherent whole rather than a series of disconnected tickets.conf: medium
supportsTBM 423: Why Defining Teams Is So Hard · p3 — Both treat architectural/value coupling as a hard constraint on team structure that org-design ideology (autonomous teams / reverse Conway) can understate.
implicitThe piece implicitly treats 'autonomous teams' as an oversimplified industry orthodoxy that has calcified into unreflective dogma, making the article fundamentally a corrective/critique rather than a neutral report.conf: medium
implicitNetworked, hierarchy-bypassing coordination is implicitly assumed to have lower or comparable coordination cost than hierarchical coordination, since the piece presents 'not needing to traverse the hierarchy' as an unqualified benefit.conf: medium

Arguments

Organizations should replace 'autonomous product team' thinking with 'value center' thinking, structured around five recursive Viable-Systems-Model questions applied at every level. strength: medium

Explicit premises:

Teams in complex organizations do not deliver stable products; they deliver value within an ever-shifting value stream.
The language of 'products' is the wrong language for what teams actually do.
The shape of value (its dependency web) constrains what organizational structures are achievable, including the autonomy/coherence trade-off.
The five questions are grounded in an established, decades-old cybernetic model of viable systems (Stafford Beer).

Implicit premises:

'Team as value center' is a more accurate and more actionable unit of organizational analysis than 'team as product owner.'
A model built for describing viable biological/organizational systems in the abstract (VSM) transfers validly and without loss to software product-development teams specifically.
Naming and reframing (new vocabulary) is itself sufficient to change organizational behavior, independent of incentive, resourcing, or accountability structures.
The recursive property of the five questions (same questions, every level) is actually true rather than asserted; no counter-example or failure mode is considered.

Inferences:

Argument from authority/pedigree: invoking Stafford Beer's Viable Systems Model and Ralph Stacey lends theoretical weight without independent verification of transfer-validity to software teams.
Argument from analogy: the molecule metaphor (simple vs. complex chemistry) stands in for an argument about when decoupling is possible.
Enumerative generalization: the five questions are claimed to hold 'at all levels' based on a single worked example at the team level, with no worked example at the whole-organization level.

Narratives

The molecule metaphor: AWS/Azure-style standalone cloud services (S3, EC2) as simple molecules ('metals or water') with minimal dependencies, versus Rohrer's own workplace — an integrated trading platform where pricing, risk analytics, and trading capability are inseparable in value even though separable technically — as complex organic molecules ('proteins, DNA').
→ Makes the essential-vs-accidental dependency distinction concrete and justifies differentiated autonomy prescriptions: high autonomy is safe for simple/decoupled value, but not for value that is technically decomposable yet value-inseparable.

Questions addressed

✅ How should organizations think about team structure when a single, stable 'product' doesn't really exist in a complex value stream?
Replace the product frame with 'value center' framing: every team is valuable because of what it delivers, not because it owns a fixed product.
✅ How can teams and leaders visualize or reason about the dependency structure of value across an organization?
The molecule metaphor: map dependencies as simple vs. complex molecules to distinguish essential from accidental coupling.
⭕ How should teams balance autonomy against coordination/coherence needs?
The piece names the trade-off and asserts it is constrained by value shape, but offers no mechanism, process, or worked example for actually navigating or measuring the trade-off in a real organization.
⭕ What happens when the five questions yield conflicting or incompatible answers at different organizational levels (e.g., a team's own sense of 'who we are' versus the team-of-teams' framing of the same team)?
⭕ How, concretely, does an organization currently built around autonomous product teams transition to value-center/nested-networked structure — what changes first, who decides, what does it cost?

Gaps

incomplete'Value designs organization' is presented as a one-way causal claim (the shape of value determines organizational structure), but the piece never addresses the converse feedback loop — that existing organizational structure and political incentives shape which value flows are even recognized, funded, or pursued in the first place. This is exactly the two-way causality the reverse-Conway-maneuver literature grapples with (deliberately using Conway's Law in either direction).
Read next: extract-heis-01-torbjorn-larsen-naermeste-vi-kommer-steve-jobs#p16 (reverse Conway: design architecture first, then place org on top) and extract-korbacher-platform-engineering-product-mindset#p18 (deliberately using Conway's Law to reshape org)
incompleteNo account of transition mechanism or cost: the article stays entirely at the level of naming and reframing ('call it a value center, ask these five questions') without describing how an organization currently structured around autonomous product teams and stable roadmaps would actually migrate — what changes first, who has authority to redraw team boundaries, or what the migration costs in disruption and rework.
Read next: extract-structured-empowerment-decisions#p4 and #p8 (structured empowerment's enabling conditions: double-loop learning systems, empowering culture) as a model for what an implementation-level account would need to specify
incompleteThe claim that the five questions apply unchanged 'at all levels: team, team-of-teams, department, whole organisation' is asserted but only ever demonstrated with a single team-level worked example (Scrum backlog, sprint goal); no worked example is given at the team-of-teams, department, or whole-organization level, so the universality/recursiveness claim is untested within the piece itself.
illogicalThe closing claim that networking lets teams 'deliver value without needing to traverse the hierarchy' risks conflating informal lateral coordination with actual decision rights, budget authority, and accountability, which typically remain hierarchical even when day-to-day coordination becomes networked. The piece treats bypassing hierarchy as an unqualified good without engaging the possibility that hierarchy persists for reasons (accountability, resource allocation) that a purely networked value-delivery model doesn't replace.
Read next: the corpus's hierarchy concept, esp. framing of hierarchy as structurally inevitable in groups rather than an artifact that networking simply dissolves
incompleteRohrer's 'prefer coherence, because there's a lot more disorder than order' reads as an argument for maximizing coherence, but elsewhere in this reader's corpus the same coherence concept is explicitly qualified: perfect/maximal organizational coherence is not a desirable goal because it would require stasis or over-constraint. The piece doesn't engage this diminishing-returns or over-coupling risk of coherence-seeking.
Read next: extract-tbm-434-how-maps-can-hide-problems#p9 (perfect organizational coherence is undesirable — requires stasis) and extract-nordic-apis-coherence-spacetime-crystals#p10 (perfect coherence is unattainable; the realistic goal is understanding degree of fit, not maximizing)
uninformedThe piece covers almost identical territory to Team Topologies (stream-aligned teams, team-level cognitive load, dependency-driven team design) without engaging that vocabulary at all — a well-known adjacent framework whose terms (e.g., 'stream-aligned team' vs. 'value center') could sharpen or challenge Rohrer's coinage, or reveal it as a rebranding of existing ideas.
Read next: extract-tbm-423-defining-teams and extract-tbm-434-how-maps-can-hide-problems (Team Topologies material already in the corpus)