#orgdesign

Trond Hjorteland @trondhjort@hachyderm.io · Jul 22, 2026

Every time an organisation tries to democratise its work, the same three-layer dynamic plays out. The first layer is the people closest to the experiment. They work hard, they believe in it, and results follow. The pilot succeeds. The case study is written up. Leadership is encouraged. The second layer is the people one step removed — the middle of the organisation, the managers and coordinators who were not part of the experiment. Something odd happens here. They do not actively oppose the change. They slow it down, quietly, without quite meaning to. Their formal role has lost its purpose, but nothing has replaced it. They are neither coordinating in the old bureaucratic way nor participating as peers in the new one. OST calls it paradoxical inhibition: the structural response of a layer that has been made redundant without being redesigned. The frozen middle is not a people problem. It is what happens when the design principle changes in one layer and not the others. The third layer is the people furthest out — other organisations watching. They see the success story. They copy the topology, the roles, the vocabulary. They do not see the structural conditions that produced the results because those are invisible from the outside. The Spotify model spread across the industry this way. Team Topologies is spreading the same way now. Both describe what good looks like. Neither changes the design principle underneath. The copies produce the original's surface without its substance. All three layers follow structurally from the same thing. The pilot works because DP2 conditions were created locally. The middle freezes because DP1 remains intact above and around it. The copies fail because the form is adopted without the principle. The only way to avoid the pilot trap is not to pilot. OST methods are designed to change the whole system at once, for exactly this reason. You cannot sneak DP2 past DP1 one team at a time. Three dysfunctions from the book cover a layer each: The pilot trap (https://hachyderm.io/@trondhjort/116696304124043996) The frozen middle (https://hachyderm.io/@trondhjort/116475267077470990) and Team Topologies, the wrong way round (https://hachyderm.io/@trondhjort/116594341102988605) www.organisationaldysfunctions.com/ #OpenSystemsTheory #SocioTechnical #OrgDesign

Quoting

Trond Hjorteland @trondhjort@hachyderm.io

Organisational Dysfunction of the Day The pilot trap Context: The organisation wants to test a new way of working before committing to it fully. A pilot team is selected. They get more autonomy, a flatter structure, and direct access to the people they serve. The experiment is watched closely. Leadership visits. Consultants evaluate. Progress is tracked and reported. The team delivers well. They are energised and proud of what they have built together. Then the question of scaling comes up. Resistance appears, not from people far away, but from those closest to the experiment. The managers whose teams were not selected. The HR department asked to create exceptions for the pilot. The architects whose standards the pilot bypassed. The steering committee that was promised a clear verdict. The experiment ends, or quietly returns to normal. The organisation concludes that the approach works in theory but is not right for them. OST explains: Merrelyn Emery identified this dynamic as paradoxical inhibition, drawing on Pavlov's research on conditioning: the people and areas closest to structural change feel most threatened by it and develop the strongest resistance, while those at a safer distance are more likely to adopt it. Norway lived this in the 1960s. The Industrial Democracy Programme experiments worked. The experiments did not spread. Sweden picked up the ideas and ran with them instead. Treating change as a pilot produces exactly this effect. Those around the pilot are confronted daily with a visible alternative to their own way of working. That is not a neutral situation. It is a structural provocation. Partial DP2 in a DP1 organisation is inherently unstable, not because the experiment fails on its own terms, but because the surrounding system has every structural reason to absorb or eliminate it. This is not cynicism or politics. It is the immune system of DP1 doing exactly what it was designed to do. The only way to avoid the pilot trap is not to pilot. You cannot sneak DP2 past DP1 one team at a time. The fence will hold. #OpenSystemsTheory #SocioTechnical #OrgDesign #changemanagement

Open quoted post

10

0

4

0

Trond Hjorteland @trondhjort@hachyderm.io · Apr 10, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day Passivity in team workshops Context: Workshops are for many a unique opportunity for people to get together and collaboratively work on a problem or a design of something they care about, be it EventStorming, Retrospectives, Design Sprints and such sessions. In larger groups, involving the whole team or even people from different teams, you frequently see people with more formal power join in, be it a team leader, department head, or even a intervening and controlling facilitator, and that often creates an unfortunate dynamic where the participants feel limited and restricted, so much so that many become inactive and passive, and not contributing in a way a way that they could have. Even though they probably really wanted to. OST explains: This dynamic is very common in autocratic hierarchies, where power over something, be it people directly or even a certain subject like architecture, creates a dynamic where people often submit themselves to that person simply because of their position in the hierarchy. And not because of their expertise or good arguments. These emotional anxieties, often unconscious, can take different forms, in this case a dependency on the leader, but can also be a fight/flight reaction or subgroups forming. These are referred to as Bion's basic assumptions, "bas", and the only way to get rid of them and replace it with real productive work is not having an appointed leader present. Always go for DP2 in workshops, regardless of how you are organised otherwise. #OpenSystemsTheory #SocioTechnical #OrgDesign

3

0

2

0

Trond Hjorteland @trondhjort@hachyderm.io · Apr 13, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day Forming–storming–norming–performing Context: When putting together a new team or making big changes to an existing one, many recommend using Tuckman's "forming–storming–norming–performing" model to turn the team into a coherent and well-oiled unit. It begins with Forming (orientation), moves to Storming (conflict), progresses to Norming (cohesion), and ends with Performing (high productivity). Leaders are advised to manage this process closely as progress is not linear; teams may slip back to previous stages if new members join or goals shift. And conflict is regarded as necessary, as the "Storming" phase is essential to growth. OST explains: Tuckman's model only makes sense in an autocratic bureaucracy, especially those of the Theory X type, and aligns with Taylor's view that people must be managed to perform properly. This is classic DP1 thinking, whereas in the DP2 style, McGregor's Theory Y is the model, which assumes employees are self-motivated, enjoy work, and thrive under trust, empowerment, and autonomy. Grouped into self-managing groups that have designed themselves using Participative Design. No need for either storming or norming; the teams jump right to performing after forming. #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

10

0

6

0

Trond Hjorteland @trondhjort@hachyderm.io · Apr 14, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day Analysis paralysis Context: An agile team is working on a rewrite of an existing legacy solution and feels that its success depends on the function parity it must have with the old one. They therefore end up doing a detailed and extensive analysis to account for as much as possible, even tracking down former developers to get details on some of the more obscure parts. And, even more problematic, they have to figure out which business people own which parts and who all their users are. This drags out in time, and although they have started the work, the extensible analysis prevents them from releasing anything. They are stuck. OST explains: Agile as a concept is pretty much designed to handle these kinds of situations; at least that is what many may think. It focuses on small increments and puts things in front of the users as soon as possible to tighten the feedback loop, so it makes sense. The thing, though, is that this is not product discovery, as it is an existing product with external product owners and users, both internal and external, and the team has no real product ownership of the app apart from the technical bits. They are not a self-managing product team as a DP2 style should be. Only when they have end-to-end ownership of the whole product, not just a part, can they take full responsibility and accountability so that they can manage it as they please. #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

5

0

1

0

Trond Hjorteland @trondhjort@hachyderm.io · Apr 15, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day Individualism Context: Often, there is a large disproportion in how much people are celebrated for their achievements and when blame is placed for accountability when something goes wrong. This feels natural in most parts of the world, as we want to take care of the people and make them feel as good as possible so that they'll feel well and stick around. Being human, as we say. Even toward the people who clearly take on the accountability, and are even paid good money to do so, often leading to few or no consequences. We value the individual when celebrations are due, when heroes are praised, but hide them when there is not. Typically, hero cultures are also a power play, as the ones praised become stretch goals for the rest, showing what lengths they have to go to feel respected and truly valued. OST explains: This focus on the individual is almost anathema in OST, not because the individual is not valued, but it realises that the group is the basic unit of life, be it your family, your friends or your colleagues. It's founded on the belief that people have both the need for autonomy and homonomy; be able to self-govern and fit in with the group. Actually, valuing individuality as an acontextual thing hides a vital paradox, as it inevitably isolates people as the problem because there is nothing else to blame. It even goes beyond blaming the victim; it creates them. By instead focusing on the group, and having it take responsibility and accountability, it can take both the praise AND the blame. The individual is protected in the group, and it can jointly grow and learn from successes and failures. As it takes them to their shared goals. #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

6

0

4

0

Trond Hjorteland @trondhjort@hachyderm.io · Apr 16, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day Quiet quitting Context: During the COVID-19 pandemic, many things were exacerbated in the population, including how people feel about work. A major trend in America was referred to as the Great Resignation, in which many cited the quality of work as a reason for leaving. Another trend that surfaced about the same time was Quiet Quitting, where employees who are fulfilling their job requirements, but not taking initiative, working overtime or volunteering for extra projects or responsibilities. In short, people are not engaged at work, something the Gallup's State of the Global Workplace report confirms, saying that only 20% of are engaged and 16% are actively disengaged. So not only are sick leaves and absenteeism a problem; when people are at work, just a small minority are actually enjoying it. OST explains: The reason for these dreadful numbers drops right out of OST and all the research it builds on since the 1950s. Given that the extrinsic motivators for work are satisfactory, such as security, work hours, and pay, the defining reasons for people enjoying work are how well their intrinsic motivators are being fulfilled. A minimal set of six psychological job requirements is the basis and they measure how well a job design works, be it the processes, the technology, the organisation, or the colleagues. If people score well on things like ownership, learning on the job, variety, support and respect, meaningfulness, and career path, they will not only enjoy work, be engaged and produce better results; they will also get a better quality of life. #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

3

0

Trond Hjorteland @trondhjort@hachyderm.io · Apr 17, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day Team leads Context: Most teams in modern agile organisations may not formally have a manager in the same sense as before. Many still have someone they report to as an employee, dealing with yearly reviews, career development, and any job issues, but they are not formally involved in the daily work. It should therefore be possible to have leaderless teams, where all members are peers and have the same say in everything. No ranking. Still, many teams end up being appointed a team lead, often because the organisation wants one contact point and one person in charge of the work done. Many in this position try to deal with this dissonance by taking on a coaching type role, seeing themselves as a "servant leader," giving space to the team and protecting them from the outside. Some even try to switch, being directive sometimes, supportive at other times (aka situational leadership). Not only is this a tricky job to have, but it also creates so much confusion in the team about who really decides and is in charge. OST explains: DP1-type organisations require personal leadership positions, as that is how control, coordination and alignment are managed. Agile tries to counter that for efficiency, having teams take more control of the work, in an attempt to shorten the feedback loop and the learning. This is similar to DP2, with self-organising teams, while adding team leaders is not and is an attempt to adapt them to the existing bureaucratic DP1 model. The problem with this is that DP1 and DP2 fit together like oil and water; they are fundamentally so different that no matter how good the adapters are, they will lead to confusion and operational problems. You can remove the need for this adapter by ditching DP1, having teams everywhere and letting them take responsibility for their own goals and the integration needed to work with other teams. Teams may decide to appoint a leader, though, for their own needs, either permanently or when needed, but it is not a formal position of power. It is a participative democracy through and through. #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

4

0

1

0

Trond Hjorteland @trondhjort@hachyderm.io · Apr 20, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day The company's strategy is unclear Context: "What we've got here is failure to communicate." A common quote used to describe a lack of understanding of and commitment to the company's strategy. Top management is frustrated by the lack of alignment, projects and departments not seeing the bigger picture clearly drawn up in the strategy document. At the same time, the people at the coalface constantly report back that they miss a clear and concise direction to follow when making decisions. All attempts to hold town hall meetings, clearly visible pages on their intranet, middle management sharing it frequently in their weekly status meetings, and even motivational phrases posted on the office walls seem to help. OST explains: There are many explanations for this dynamic, like a strategy not really being a strategy but rather a lofty goal that provides no clear guidance, or poor communication lines between the top and the bottom. Let's focus on something often missed instead. A strategy must make operational sense to people; it should give them a clear, relevant purpose for their work, feel relevant and relatable in a way that inspires and motivates. Cool and fancy wording is not the point, not even how and how often it is communicated, but how engaging it is. The best way is for people to take part in its creation, but that is not feasible in large organisations, so at least it must have agents in all parts of the organisation who do, someone the people trust and can relate to. This is what middle management ought to be doing: making the company strategy relevant and actionable for people. #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

1

0

Trond Hjorteland @trondhjort@hachyderm.io · Apr 21, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day Workshops not working Context: You have probably seen and even experienced being invited to workshops that you may or may not have that much interest in, but still obligated to join, and although it was carefully planned and executed by the facilitator, it still felt forced, unengaging and maybe even like a waste of time. This is an unfortunate situation as workshops are really the place where important and constructive work ought to happen, where people really feel energised and collaborate at the top of their game. Is it the participants that's the issue, or could it be something else? OST explains: It is rarely the participants who cause this issue, even when workforce engagement has reached rock bottom. Systemic problems like this have different causes, ranging from the larger structural issues of autocratic hierarchies that inhibit collaboration and put people up against each other to simply bad facilitation. Let's focus on the latter now, as that is an easier adjustment to make. Make sure the facilitators are only in charge of managing the process; they should not own the decision to run the workshop, the technique or process to use, or be involved in the content. The reason for this is that the point of a workshop is for people to own the content and the output, and any attempt to lead will result in Bion's basic assumptions: dependency on the facilitator, just doing what they're told; fight/flight, opposing the whole thing or just not participating; or creating factions that do their own thing instead. Suspect many have experienced these, and they can only be avoided by removing the leader and letting the facilitator serve the group, not the other way around. DP2 instead of DP1. #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

1

0

Trond Hjorteland @trondhjort@hachyderm.io · Apr 22, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day Communication problems Context: A common trope in larger organisations is that the root cause of so many problems and dysfunctions is bad communication. That people are not talking to each other and conveying information properly and promptly. Things are taking too long because of all the people that have to be involved and such. People are therefore often seen as the cause of this problem, and a common way of attempting to deal with these problems involves giving people additional communication skills. Something that fuels a huge training industry. Another is to simply limit the communication needed, for example, by setting a cap on team size (often citing Metcalfe's law) or by putting up human adapters/bottlenecks as the team leads mentioned in another post. OST explains: OST states that these types of communication problems are endemic in DP1 structures and that it has nothing to do with people's ability to communicate. It is not even the primary human property, so why try to fix that first? Many situations can be observed where communication channels exist but are not used at all. What is a determining factor is the organisational structure, having one that is motivated to use the skills and where the number of channels is as few as possible. In DP1, each person is connected with the policy makers through intermediaries, in a non-reciprocal manner, while in DP2, this is reduced to real reciprocal connections between teams that do productive work. Not only is the number of connections fewer, but so is the quality of communication, as all relations are negotiations between peers, far from the asymmetrical relations between the superior and subordinate found in DP1. Think async vs. sync communication; the former is chatty, the latter is not. Also, Metcalfe's does not fit, as people communicate well and efficiently with peers who share the same goals and purpose as themselves. #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

1

0

Trond Hjorteland @trondhjort@hachyderm.io · Apr 23, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day HiPPOs and dungeon masters Context: In bureaucratic organisations, the formal ranking of people is usually well known and clear, where people higher up in the hierarchy have certain mandates over people they manage and/or that reports to them. Anything else would be chaos in that world. Still, there is also a lot of informal power, ranging from age difference and gender to more subtle things like years of experience and size of salary, regardless of formal power. This is problematic when decisions are to be made, as these informal power structures end up trumping data and expertise. OST Explains: Facilitators especially try to counter these tendencies in workshops, for example, by using different types of techniques. A common one is sometimes called Silent Writing, where people are asked to work on the problem alone first, at the start of the workshop, so that all voices are heard. Sometimes this is taken a step further, as in 11-2-4-all, where the next step is joining a colleague to draw up a joint design, before joining up with another pair to create one they all agree on, and so on, before all get together and decide. This works well to get input from everyone, but does not silence the one with rank, as they will dominate regardless. And potentially lead to failure. In the techniques developed in OST, the focus is instead to create a community from the start of the session, instead of fortifying the differences, as these techniques do focus on the individuals. The Search Conference does this by focusing first on the shared goals and wishes for the future, showing that they all agree on more than they disagree on. And, if they do agree on something, put that to the side immediately and focus on what joins them instead of what separates them. The assumption is that we share the we all share the values that lead to the desirable future. #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

0

1

0

Trond Hjorteland @trondhjort@hachyderm.io · Apr 24, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day Local optimisations Context: Any work group of people want to improve their way of working if they could, removing unnecessary work, resources or waste, as Lean calls it. Agile gave the teams that ability, at least to a large extent. Some may only be able to adjust technical issues, while others may even be empowered to decide how they want to do work. For example, one team decides they want to move to an event-driven architecture, while another wants to replace Scrum with Kanban. All great local optimisations that they should be able to do, but often are prevented from doing so, as they need to interact with other teams and are not able to get them to adjust. Or management may not let them because of the impact it has. Again, teams are stuck. OST explains: This issue is not directly related to OST necessarily, but more to the parts-to-whole relation that comes out of systems thinking, which OST clearly is. Local optimisations in a part are perfect if it does not affect anyone else, which is rarely the case as parts are interconnected with other parts, often even through the shared relation they have to the whole. In a purposeful social system, even more so, as not only must the changes physically fit, but they must also align with the shared purpose of the system as a whole. Most organisations deal with this paradox, the interest of the parts vs. the whole, by designing top down, creating guardrails for the parts to operate within, giving them limited freedom. OST, on the other hand, replaces this centralisation of command and control by distributing it to the parts, where they can design their own work as long as they make sure it aligns with the goals of the system as a whole, like business goals and strategic plans, and, just as importantly, coordinate with all the affected parties. This enables local optimisations for the benefit of the whole. #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

3

0

2

0

Trond Hjorteland @trondhjort@hachyderm.io · Apr 27, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day The frozen middle Context: Assuming you are a team member in an organisation that has gone through an agile transformation. Your team have been given more autonomy and is expected to self-organise, make decisions, and deliver value faster. Yet somehow, almost everything still takes forever. Decisions get stuck, information does not flow, and initiatives die quietly without explanation. The teams are doing their part, but something above them seems to absorb all energy and momentum like a sponge. Middle managers are busy, always in meetings, always promising to follow up. But nothing moves. A frequent excuse is Things Take Time. OST explains: This is one of the most predictable side effects of a partial DP2 transition to self-managing teams. When teams are given more autonomy while the surrounding DP1 structure remains intact, middle management gets caught in the middle. They lose their traditional role of passing work down and status reports up, but gain no new meaningful function. The result is a layer of people who are neither coordinating in the old DP1 way nor participating as peers in a DP2 fashion. They become a dampening layer, unconsciously protecting the existing power structure while appearing to support the change. This is not a people problem; it is a structural one. In a full DP2 organisation, the coordination is managed by the self-managing teams themselves, coordination work between peers, and not through proxies. The frozen middle is not resistant to change; it is simply a DP1 organ that has lost its purpose but not yet been replaced by anything coherent. Until the whole system transitions, it will continue to insulate the top from the bottom and slow everything down. The bottleneck has shifted. #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

3

0

2

0

Trond Hjorteland @trondhjort@hachyderm.io · Apr 28, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day Fear of making decisions Context: One issue many teams in an agile organisation face is the stalemate that frequently happens when they need to make a decision that will impact other teams or other parts of the organisation. They have been empowered and given autonomy to decide for themselves, but they still want to be good players and are afraid to do something that could negatively impact others. Some may even be worried whether the change is allowed at all, like changing their work process or tools to use for things like ticketing, or changing the technical architecture by using a different data storage platform. Good ideas and suggested improvements are often shelved or even abandoned. OST explains: This is another predictable side effect of a partial DP2 transition to self-managing teams, where the teams are given autonomy to self-manage, but do not feel able to. Or, maybe now they are not really empowered, as they know all too well, there are DP1 (bureaucratic) structures still in place that can and will stop them. And, even if they were in a pure DP2 setup, they still need tools to coordinate. One that works well is referred to as the "advice process" and was first described by Dennis Bakke, later by Laloux and Harmel-Law. In it, anyone can make any decision provided they follow this simple rule: first seek advice from 1) everyone who will be meaningfully affected, and 2) people with expertise in the matter. So instead of drawing up everything and then getting approval from someone who cannot possibly understand it properly, or going rogue, you formulate the decision as best as you can and then seek advice on it and adjust it to your liking based on that. Not only do you make better decisions, but you also own them. No more blame game, which DP1 creates, and no chaos, which the mixed mode induces. Participative democracy in practice. #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

12

46

9

0

Trond Hjorteland @trondhjort@hachyderm.io · Apr 29, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day Psychological safety as a patch Context: Your organisation may have realised that psychological safety is of the essence for good collaboration. Maybe it came out of a retrospective, maybe someone read the Google re:Work study and Amy Edmondson contributions, or maybe it was a leadership initiative after too many people stopped speaking up in meetings. Either way, there are now workshops on it, a section in the onboarding, maybe even a survey to measure it. Leaders are coached to create it. Teams are encouraged to demand it. And yet, somehow, people are still not speaking up, still not taking risks, still not challenging the decisions made above them. The patch does not seem to be holding. OST explains: Psychological safety is real, and it matters a lot, but what is often missed is that it is an emergent property of the structure people work in, not something you can install. In a DP1 organisation, people are inherently in a dependent, subordinate position, and the rational response to that is to be careful about what you say and to whom. That is not a personal failing; it is Bion's basic assumptions playing out exactly as expected: dependency, fight/flight, and factionalism are the natural human response to autocratic hierarchies. You cannot train people out of that while the structure that causes it remains intact. In a DP2 structure, on the other hand, psychological safety is not a programme or a value on the wall; it is simply what happens when people are peers designing and owning their own work. They speak up because it is their job to, and because there is no hierarchy of dominance to be careful around. Demanding psychological safety in a DP1 organisation is a bit like applying a patch to a system with a structural bug. It might cover the symptom for a while, but the underlying code has not changed. #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

3

0

3

0

Trond Hjorteland @trondhjort@hachyderm.io · Apr 30, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day OKRs imposed from above Context: Many organisations have adopted OKRs, but a common way of doing them is like a cascade: company OKRs are set by leadership, then broken down into department OKRs, then into team OKRs. Everyone has objectives and key results. The teams go through the quarterly ritual of setting them, reviewing them, and scoring themselves at the end. Some teams engage genuinely, while others may treat it as a compliance exercise. A common complaint is that the team-level OKRs are effectively dictated by the level above, with little to no room to define what matters to them. The framework says teams should own their goals, but the structure says otherwise. OST explains: OKRs are a good idea applied in the wrong structure. In DP2, goal-setting is one of the core functions of the self-managing group; it is not something done to them. When goals are cascaded down from above, even with good intentions, the team is not really setting its own objectives; it is translating management's objectives into local language. That is a DP1 (bureaucratic) function dressed in DP2 clothing. The quarterly scoring ritual then becomes a performance review proxy, which is about the last thing a self-managing team needs. In a genuine DP2 structure, the team's goals emerge from its understanding of its own work, its environment, and the shared organisational purpose it has participated in defining. That is a fundamentally different starting point, and it produces fundamentally different commitment. #OpenSystemsTheory #SocioTechnical #OrgDesign #strategy

2

0

2

0

Trond Hjorteland @trondhjort@hachyderm.io · May 04, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day The agile terrarium Context: Agile transformed how software is built. Iterative delivery, short feedback loops, cross-functional teams, and continuous improvement. These were genuine advances over the heavyweight waterfall projects they replaced. The lean movement provided much of the intellectual scaffolding: eliminate waste, optimise flow, respect the people doing the work. And yet, decades on, the research is clear that agile has not delivered the engaged, self-managing, high-performing teams it probably hoped. The process works reasonably well. The organisation around it largely does not. @einarwh@mastodon.social described agile teams as terrariums: self-contained ecosystems that look alive and healthy from the inside but are sealed off from the real environment around them. Most people working in agile organisations will recognise that image immediately. OST explains: The terrarium image is more precise than it might seem. A terrarium is a closed system; it regulates its own internal conditions but does not transact with its environment. That is exactly what agile teams are often designed to be: protected from the turbulence outside, given a stable backlog and told to focus. An open system survives by engaging with its environment, learning from it, and actively adapting to it. Sealing it off does not make the turbulence disappear; it just accumulates outside the glass until something breaks. The agile founders identified "structure" as the problem and removed supervision, but left coordination undefined and control in the hands of individuals. The result was not a move to self-managing groups, what we call DP2, but laissez-faire: an industry lost in the wilderness between DP1, the bureaucratic structure most people work inside, and the self-managing alternative. Research surveying the software industry found 55.7% of respondents were predominantly high laissez-faire, more than either DP1 or DP2. Agile is not failing because the process is wrong. It is failing because a closed system cannot adapt, and the industry has been trying to solve an open systems problem with a delivery methodology. #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

4

43

4

0

Trond Hjorteland @trondhjort@hachyderm.io · May 05, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day Built for yesterday Context: The strategy keeps changing. The market shifted, then shifted again. A competitor emerged from an unexpected direction. AI is rewriting the economics of the industry faster than anyone predicted. The three-year plan written eighteen months ago is already obsolete. Leadership responds with more planning, tighter governance, and faster decision cycles at the top. The organisation is working harder than ever and adapting less than ever. People at the coalface can see what needs to change, but cannot get decisions made quickly enough. By the time something is approved, the situation has moved on. The organisation is not slow because people are lazy or misaligned. It is slow because it was designed for a world that no longer exists. OST explains: Emery and Trist identified four types of organisational environment, which they called causal textures. The third, disturbed reactive, is the competitive industrial world that DP1, the bureaucratic structure, was designed for, with large, similar organisations whose moves continually disturb one another. The fourth, turbulent fields, is categorically different: the environment itself is in motion, driven by forces in the field itself, like technological disruption, social change, and ecological pressure. In turbulent fields, the variety generated by the environment exceeds the capacity of any hierarchy to process and respond to it. DP1 is actively maladaptive here, because concentrating perception and decision-making at the top creates exactly the bottleneck that makes the organisation slow when speed matters most. DP2, the self-managing-group structure, distributes that capacity across the whole organisation, with every group actively scanning its environment, adapting, and feeding learning back into the system. We have been in turbulent fields for decades. AI has just turned up the intensity several orders of magnitude. To 11. #OpenSystemsTheory #SocioTechnical #OrgDesign #strategy

3

42

0

Trond Hjorteland @trondhjort@hachyderm.io · May 06, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day Deploying AI into a broken system Context: The organisation is deploying AI: copilots, automated pipelines, intelligent triage, and decision support. The pilots look promising; the broader rollout is patchy, with some people embracing the tools and others routing around them. A few raise concerns about deskilling, about oversight, about what happens when the AI gets it wrong. Leadership frames this as change resistance. The change management programme is expanded. Meanwhile, the tools are also being used to monitor output, flag underperformance, and justify headcount decisions. The people who were concerned start to understand why they were concerned. OST explains: This pattern is not new. Sociotechnical systems research emerged in the 1950s precisely because organisations kept introducing new technology with enormous focus on technical capability and almost no attention to the social system. The result was that technology failed to deliver its potential, workers became alienated, and productivity gains were short-lived. The core insight applies directly to AI: you will not get the benefit by optimising the technical system alone. In DP1, the manager-led structure, people are defined by the task they perform. One person, one job, one replaceable part, so when the task can be automated, the person becomes redundant by the organisation's own logic. In DP2, the group owns the whole task, and each person brings judgment, context, and adaptability that no tool replicates; AI becomes an extension of the group's capability rather than a replacement of it. In a DP1 structure, AI is almost inevitably used as a tool of control, monitoring output, flagging underperformance, and surveilling the parts. We are in the middle of the fourth industrial revolution and making exactly the same mistake as the third. #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

2

1

0

Trond Hjorteland @trondhjort@hachyderm.io · May 07, 2026

Replying to @trondhjort@hachyderm.io

Organisational Dysfunction of the Day Fixing people Context: "No matter how it looks at first, it's always a people problem." Gerald Weinberg's Second Law of Consulting is good advice. It is a reminder that the human dimension is always present, that purely technical diagnoses miss something essential, and that the people involved always matter. Most managers and HR professionals would recognise themselves in it. Someone on the team is struggling. Maybe they are disengaged, not delivering, clashing with colleagues, or just not showing up in the way they used to. The organisation's response is to fix the person: a performance improvement plan, a coaching programme, a personality assessment, or a quiet word from HR. Sometimes it works for a while. But the same problems keep reappearing, often with different people in the same role. The carousel of interventions never quite stops. OST explains: Weinberg is right that it is always a people problem; people's experience, motivation, and well-being are always at stake. OST does not disagree; it adds the next step. When the same dysfunction shows up repeatedly across different people in the same role, the problem is not those individuals; it is what the system does to whoever occupies that position. DP1 structures (manager-led), with their competition for recognition and dependency on management for decisions, produce exactly the disengagement and avoidance that organisations then try to coach out of people. Fixing the individual while leaving the structure intact contains a deep paradox: elevating the individual as the problem, isolated from the structure shaping their behaviour, goes beyond blaming the victim; it creates them. So yes, it is always a people problem. The question OST asks is: what is the structure doing to the people? #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

1

0

About This Hashtag

#orgdesign

Related