E29: Interview: Trond Hjorteland on a radical approach to organizational transformation

E29: Interview: Trond Hjorteland on a radical approach to organizational transformation

Author: Brian Marick April 10, 2023 Duration: 44:40

Open Systems Theory (OST) is an approach to organizational transformation that dates back to the late 1940s. It's been applied a fair amount, but hasn't gotten much mindshare in the software world. It has similarities to Agile, but leans into self-organization in a much more thoroughgoing way.

For example, in an OST organization, 

  • teams aren't given a product backlog, they create it themselves.
  • if a team decides they need to slow the pace of delivery to learn new things or to spend more time refactoring, their decision is final.
  • pay is based on skills, not productivity, so as to encourage multi-skilled people.
  • team work is organized so that there are career paths within the team, rather than advancement depending on leaving a team and rising up in a hierarchy.

OST is even more radical at the levels above the team. Unlike scaled-agile approaches like SAFe or LeSS, OST changes the jobs of the people higher in the org chart just as much – or more? – than people at the leaves of the tree. Specifically, the shift is from order-giving to coordination at different timescales. Individual "leaf" teams are responsible for the short term, the next level up is responsible for the medium term and external partners, and the CxO levels focus on the long term.

This episode is an interview with Trond Hjorteland, who – after experience with Agile – did an impressively deep dive into OST.

Sources
As noted in the podcast, there's not much accessible documentation about OST. However, Trond and his merry band of (mostly) Agilists have begun work on a new site. Trond has also written "Thriving with complexity using open sociotechnical systems design", originally published in InfoQ.

Trond's blog.
Trond is on Mastodon at @trondhjort.


Image credit
The image is from the cover of the Marvel Comics graphic novel Captain Marvel, Vol. 1: Higher, Further, Faster, More.


Brian Marick hosts Oddly Influenced, a podcast that digs into the unusual and often overlooked connections between software development and the wider world. Each episode starts with a concept, theory, or practice that originated far from the realm of code-perhaps in sociology, theater, history, or urban planning-and traces its journey into the hands of software practitioners. The focus is on the concrete application: how these borrowed ideas were adapted, what problems they aimed to solve, and what actually happened when people tried them. You’ll hear about the successes, the surprising failures, and the messy, fascinating reality of translating an abstract principle into working practice. This isn’t about generic inspiration or vague parallels; it’s a detailed look at cross-disciplinary pollination, examining the mechanics of how influence actually works. The conversations are grounded and specific, avoiding hype to explore what we can genuinely learn from fields that don’t think in loops and logic. For anyone in technology or education curious about how innovation often comes from the edges, this podcast provides a unique and thoughtful perspective. It’s for listeners who enjoy deep dives into the history and sociology of their craft, who appreciate hearing stories that aren’t the usual case studies, and who are open to having their own thinking oddly influenced by the end of an episode.
Author: Language: English Episodes: 55

Oddly Influenced
Podcast Episodes
E42: The offloaded brain, part 2: applications [not-audio_url] [/not-audio_url]

Duration: 34:10
Suppose you believed that the ecological/embodied cognitive scientists of last episode had a better grasp on cognition than does our habitual position that the brain is a computer, passively perceiving the environment, t…
E41: The offloaded brain, part 1: behavior [not-audio_url] [/not-audio_url]

Duration: 31:52
Embodied or Ecological Cognition is an offshoot of cognitive science that rejects or minimizes one of its axioms: that the computer is a good analogy for the brain. That is, that the brain receives inputs from the senses…
EXCERPT: Concepts without categories [not-audio_url] [/not-audio_url]

Duration: 15:38
This excerpt from episode 40 contains material independent of that episode's topic (collaborative circles) that might be of interest to people who don't care about collaborative circles. It mostly discusses a claim, due…
EXCERPT: Christopher Alexander’s forces [not-audio_url] [/not-audio_url]

Duration: 14:29
Software design patterns were derived from the work of architect Christopher Alexander, specifically his book A Pattern Language: Towns, Buildings, Construction. This excerpt (from episode 39) addresses a problem: most s…
E40: Roles in collaborative circles, part 2: creative roles [not-audio_url] [/not-audio_url]

Duration: 45:14
The last in the series on collaborative circles. The creative roles in a collaborative circle, discussed with reference to both Christopher Alexander's forces and ideas from ecological and embodied cognition. Special emp…
E39: Roles in collaborative circles, part 1 [not-audio_url] [/not-audio_url]

Duration: 32:19
Farrell describes a number of distinct roles important to the development of a collaborative circle. This episode is devoted to the roles important in the early stages, when the circle is primarily about finding out what…
E38: The trajectory of a collaborative circle [not-audio_url] [/not-audio_url]

Duration: 27:52
Collaborative circles don't have a smooth trajectory toward creative breakthrough. I describe the more common trajectory. I also do a little speculation on how a circle's "shared vision" consists of goals, habits, and "a…
E37: Resilience engineering with Lorin Hochstein [not-audio_url] [/not-audio_url]

Duration: 44:36
An interview with Lorin Hochstein, resilience engineer and author. Our discussion was about how to handle a complex system that falls down hard and – especially – how to then prepare for the next incident. The discussion…
E36: BONUS: One circle-style history of Context-Driven Testing [not-audio_url] [/not-audio_url]

Duration: 47:52
I was a core member of what Farrell would call a collaborative circle: the four people who codified Context-Driven Testing. That makes me think I can supplement Farrell's account with what it feels like to be inside a ci…