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
Personality and destiny [not-audio_url] [/not-audio_url]

Duration: 28:09
A summary of the "situationist" faction of personality psychology, which holds that behavior is strongly influenced by the situation. Knowing someone's personality type adds little value when predicting how they'll behav…
Legitimate peripheral participation: the book and the idea [not-audio_url] [/not-audio_url]

Duration: 22:58
"Legitimate peripheral participation" is based on observations about how novices learn in the presence of experts. The novel bits are that novices learn better from fellow novices than from experts, that we need to pay a…
/Seeing Like a State/, part 3: the users, the clients [not-audio_url] [/not-audio_url]

Duration: 33:03
In this episode, I hope to give you some helpful hints about *actually* improving the lives of the users of the software you create. Or, if you’re the kind of “change agent” or “coach” I used to be, the lives of the, uh,…
Interview: Glenn Vanderburg on engineering [not-audio_url] [/not-audio_url]

Duration: 29:36
In episode 12, I used the chapter in /Image and Logic/ about Monte Carlo methods to argue that analogies of software development to engineering are not helpful. Glenn Vanderburg pushed back: it's not *engineering* that's…
BONUS: Lord, preserve us from totalizing systems [not-audio_url] [/not-audio_url]

Duration: 26:22
Why *are* teams stuck in hierarchical and commercial exchange economies, when they'd be happier and just as productive if the example of the previous episode were the default? A discussion of totalizing systems and "syst…