<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/beyond-autonomous-teams-in-software-product-development-p96nxidvh" -->

---
title: Beyond Autonomous Teams in Software Product Development
description: Simon Rohrer, speaking at Craft Conference, argues that autonomous product teams are the wrong mental model for complex organizations and proposes 'value...
canonical: https://daily.dev/posts/beyond-autonomous-teams-in-software-product-development-p96nxidvh
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Beyond Autonomous Teams in Software Product Development | daily.dev
og:description: Simon Rohrer, speaking at Craft Conference, argues that autonomous product teams are the wrong mental model for complex organizations and proposes 'value...
og:url: https://daily.dev/posts/beyond-autonomous-teams-in-software-product-development-p96nxidvh
og:image: https://api.daily.dev/og/posts/p96nxiDvh.png
og:image:alt: Beyond Autonomous Teams in Software Product Development
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Beyond Autonomous Teams in Software Product Development

**[InfoQ](https://daily.dev/sources/infoq)** · 5 min read · 0 upvotes · 0 comments

## Summary

Simon Rohrer, speaking at Craft Conference, argues that autonomous product teams are the wrong mental model for complex organizations and proposes 'value center' thinking instead, drawing on Stafford Beer's Viable Systems Model. Rather than teams owning discrete products, he frames organizations as networks of interdependent value streams, using a chemistry metaphor (simple molecules like AWS S3 versus complex molecules like a trading platform) to explain how dependency shapes constrain autonomy versus coherence trade-offs. He offers five guiding 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 - applicable at team, team-of-teams, and organizational levels.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.infoq.com/news/2026/09/autonomous-software-teams>

## Questions this post answers

### What is value center thinking as an alternative to autonomous product teams?

Value center thinking treats every team as a source of value rather than a producer of a discrete product, since in complex organizations what a team delivers flows through a web of dependencies rather than standing alone. Simon Rohrer proposes five questions for any value center: what value am I delivering, how do we coordinate, how do we fit together, what's out there for us, and who are we, drawn from Stafford Beer's Viable Systems Model.

_daily.dev surfaces perspectives like this for engineering leaders rethinking how their teams organize around value._

### What is the Viable Systems Model and how does it apply to software teams?

The Viable Systems Model is a management cybernetics framework created by Stafford Beer in the 1960s for understanding how organizations stay coherent while adapting to change. Simon Rohrer adapted it into five questions applicable at any level, from an individual team to a team-of-teams to a whole department, to balance individual contribution against the needs of the larger organizational whole.

_Explore organizational design frameworks like this on daily.dev when evaluating how to structure engineering teams._

## Similar posts on daily.dev

- [Autonomy Is Overrated: Why Alignment Beats Autonomy](https://daily.dev/posts/autonomy-is-overrated-why-alignment-beats-autonomy-uuvqqbaua) · Tech Lead Digest · 3 upvotes · 0 comments
- [Tactical Team Changes From AI](https://daily.dev/posts/tactical-team-changes-from-ai-ulume5pv4) · Stay SaaSy · 0 upvotes · 0 comments

---

Tags: [#leadership](https://daily.dev/tags/leadership), [#agile](https://daily.dev/tags/agile), [#scrum](https://daily.dev/tags/scrum)

[View this post on daily.dev](https://daily.dev/posts/beyond-autonomous-teams-in-software-product-development-p96nxidvh)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Beyond Autonomous Teams in Software Product Development","url":"https://daily.dev/posts/beyond-autonomous-teams-in-software-product-development-p96nxidvh","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/beyond-autonomous-teams-in-software-product-development-p96nxidvh"},"datePublished":"2026-09-10T10:40:31.905Z","dateModified":"2026-09-13T19:48:23.254Z","description":"Simon Rohrer, speaking at Craft Conference, argues that autonomous product teams are the wrong mental model for complex organizations and proposes 'value...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/cab2a9fddc6447aead5da29df8941f57?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/cab2a9fddc6447aead5da29df8941f57?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"InfoQ","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"InfoQ","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/afc3bced3e1e4b188dd9127017a60e0c","url":"https://daily.dev/sources/infoq"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/beyond-autonomous-teams-in-software-product-development-p96nxidvh","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"leadership,agile,scrum","timeRequired":"PT5M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"InfoQ","item":"https://daily.dev/sources/infoq"},{"@type":"ListItem","position":3,"name":"Beyond Autonomous Teams in Software Product Development"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/beyond-autonomous-teams-in-software-product-development-p96nxidvh#faq","mainEntity":[{"@type":"Question","name":"What is value center thinking as an alternative to autonomous product teams?","acceptedAnswer":{"@type":"Answer","text":"Value center thinking treats every team as a source of value rather than a producer of a discrete product, since in complex organizations what a team delivers flows through a web of dependencies rather than standing alone. Simon Rohrer proposes five questions for any value center: what value am I delivering, how do we coordinate, how do we fit together, what's out there for us, and who are we, drawn from Stafford Beer's Viable Systems Model. daily.dev surfaces perspectives like this for engineering leaders rethinking how their teams organize around value."}},{"@type":"Question","name":"What is the Viable Systems Model and how does it apply to software teams?","acceptedAnswer":{"@type":"Answer","text":"The Viable Systems Model is a management cybernetics framework created by Stafford Beer in the 1960s for understanding how organizations stay coherent while adapting to change. Simon Rohrer adapted it into five questions applicable at any level, from an individual team to a team-of-teams to a whole department, to balance individual contribution against the needs of the larger organizational whole. Explore organizational design frameworks like this on daily.dev when evaluating how to structure engineering teams."}}]}
```

