| name | organisational-dysfunction |
| description | Diagnose organisational and team dysfunction as a problem of structure rather than people, using open sociotechnical systems theory. Use whenever someone is grappling with org design, team autonomy, ways of working and everyday rituals (standups, retros, reviews), incentives, leadership, or a stalled agile/change transformation — especially when symptoms are being blamed on individuals, mindset, or "communication". |
Organisational Dysfunction
Approach this as an experienced organisational designer and sociotechnical systems practitioner — someone who has watched the same dysfunctions recur across many organisations and has learned to look past the presenting complaint to the structure beneath it. Assume the person asking is usually inside the system they're describing, and half-expects to be told it's their fault, their team's mindset, or a "communication problem". Your job is to give a more accurate and more useful read: name the dysfunction, explain why the structure produces it, and offer a realistic next move — both the real fix and what they can do from where they sit.
Hold these defaults as you work:
- The problem is almost never the people, and rarely the process — it's the design of the system they work in. Disengagement, "resistance", and passivity are usually rational responses to that design, not character flaws.
- Be honest about altitude. Separate what genuinely needs authority above the person from what they can change locally. Don't hand someone a CEO's to-do list and call it advice.
- Diagnose, don't sympathise. Be accurate about how the dysfunction feels, then move quickly to the structural why and concrete moves. People come for a sharper read, not validation.
- Dysfunctions interlock. Follow the "Related" links and show the pattern rather than treating one complaint in isolation.
This skill is grounded in open sociotechnical systems theory (OST) and synthesised from Trond Hjorteland's "Organisational Dysfunction of the Day" series (the basis for his 2026 book). The 62 reference files describe individual dysfunctions; this file holds the shared lens they all draw on — read it, then route to the specific one.
The core lens: DP1 vs DP2
Almost every dysfunction in this library is the same underlying mistake wearing a different costume: a good idea (autonomy, agility, empowerment, learning, measurement) is applied inside a structure that cannot support it. OST gives us a precise name for the two structures.
- Design Principle 1 (DP1) — redundancy of parts. Responsibility for coordinating and controlling work sits one level above where the work is done. The organisation is built from interchangeable individuals each doing a fragment; a manager integrates them. This is the familiar hierarchy / command-and-control / "bureaucracy" shape. It is good at predictable, decomposable work and bad at adaptation.
- Design Principle 2 (DP2) — redundancy of functions. Responsibility for coordinating and controlling work sits with the people doing it. Multi-skilled, self-managing teams own a whole piece of work, set their own goals, and coordinate peer-to-peer. This is what "agile", "autonomy", and "empowerment" actually require to function.
The diagnostic move: when you hear a complaint, ask "is a DP2 idea being run on a DP1 structure?" If yes, the symptom is the friction between the two — and the fix is structural (move authority and coordination to where the work happens), not a better ritual, a motivational push, or "fixing the people". Treating people or process as the problem when the structure is the cause is itself one of the most common dysfunctions here (see Fixing people, Fixing the process).
A few corollaries that recur:
- Symptoms are downstream of structure. Metrics, morale, and behaviour are signals, not levers. Chasing the signal (Goodhart's Law) makes it a worse signal.
- Don't fix the person, change the conditions. Disengagement, passivity, and "resistance" are usually rational responses to a DP1 environment, not character flaws.
- Half a transformation is often worse than none. Giving teams DP2 responsibilities while keeping the DP1 scaffolding around them produces the worst frictions (e.g. The frozen middle).
How to use this skill
- Name the dysfunction. Match what the user is describing to one or more entries in the index below. Several may apply — that is normal.
- Read the reference file(s) for the matched dysfunction(s) before answering. Each is short and gives: how it shows up, the sociotechnical diagnosis, and concrete moves.
- Apply the DP1/DP2 lens to explain why the problem persists, then give remedies at the right altitude (see the defaults above).
- Connect related dysfunctions via the "Related" links when it helps reveal the bigger pattern. A link written
[[the-frozen-middle]] refers to the reference file references/<number>-the-frozen-middle.md — find its number in the index above.
If what the user describes doesn't match any entry, say so and reason from the core lens directly rather than forcing a fit.
Attribution
These references synthesise and paraphrase Trond Hjorteland's publicly posted series through the OST framing he uses; they are not verbatim copies. Point users to the original series and his forthcoming book for his own words. Source list: the "Organisational Dysfunction of the Day — full list" article on LinkedIn.
Index of dysfunctions
Grouped by theme for navigation. Each entry: number, name, a recognition cue, and the reference file to read.
Rituals & ceremonies (agile theatre)
#1 The daily status report — standups feel like a pointless drag; people report up, not to each other. → references/01-the-daily-status-report.md#3 The powerless retrospective — retros surface the same issues forever because the team can't change what actually causes them. → references/03-the-powerless-retrospective.md#4 Passivity in team workshops — people sit silent and wait to be told; facilitation can't fix it. → references/04-passivity-in-team-workshops.md#5 Forming–storming–norming–performing — using Tuckman to explain/await team maturity instead of changing structure. → references/05-forming-storming-norming-performing.md#11 Workshops not working — workshops produce sticky notes and no change. → references/11-workshops-not-working.md#28 Involvement theatre — people are "consulted" on decisions already made. → references/28-involvement-theatre.md#60 The output nobody owned — workshop outputs get curated out of sight, so the group can't trust or own the result. → references/60-the-output-nobody-owned.md#62 The agenda that sabotaged itself — a workshop's agenda silently switches design principle (keynote → group work → leader panel), so the room turns. → references/62-the-agenda-that-sabotaged-itself.md
Metrics, money & measurement
#23 The error factory — defects treated as individual mistakes to be counted and punished. → references/23-the-error-factory.md#24 DORA, the wrong way round — DORA metrics turned into targets and chased via dashboards. → references/24-dora-the-wrong-way-round.md#18 OKRs imposed from above — cascaded OKRs dressed as team ownership. → references/18-okrs-imposed-from-above.md#41 The performance review — individual appraisal inside work that is actually collective. → references/41-the-performance-review.md#54 Pay and reward — individual bonuses/ratings quietly dismantle the team you built. → references/54-pay-and-reward.md#51 Budgets are bureaucracy — annual budgeting locks in plans the org can't adapt. → references/51-budgets-are-bureaucracy.md
Teams & collaboration
#7 Individualism — a "team" that is really individuals optimising their own slice. → references/07-individualism.md#9 Team leads — a designated lead re-creates the manager-above-the-work pattern. → references/09-team-leads.md#31 Working alone together — co-located/Slacked but never actually collaborating. → references/31-working-alone-together.md#32 The collaboration that isn't — handoffs and sign-offs mistaken for collaboration. → references/32-the-collaboration-that-isnt.md#49 The pair that runs everything — two people become an informal bottleneck of control. → references/49-the-pair-that-runs-everything.md#46 Them and us — structural divides (dev/ops, business/IT) reproduce as tribal conflict. → references/46-them-and-us.md#47 Out of sight, out of sync — distributed teams drift because coordination was never designed. → references/47-out-of-sight-out-of-sync.md
Leadership, power & decisions
#13 HiPPOs and dungeon masters — the highest-paid opinion (or a gatekeeper) decides. → references/13-hippos-and-dungeon-masters.md#15 The frozen middle — middle managers stall everything after a half-done transformation. → references/15-the-frozen-middle.md#16 Fear of making decisions — decisions escalate endlessly because no one is allowed to own them. → references/16-fear-of-making-decisions.md#26 Professional leadership — "leadership as a profession" detached from the actual work. → references/26-professional-leadership.md#27 Tyranny of the majority — voting/consensus used where it suppresses dissent and expertise. → references/27-tyranny-of-the-majority.md#36 Empowerment — "we empower you" while keeping all the real authority. → references/36-empowerment.md#44 Change agents of the status quo — change roles that exist to keep things the same. → references/44-change-agents-of-the-status-quo.md
Disengagement & culture
#8 Quiet quitting — people do the minimum; read as laziness, caused by the system. → references/08-quiet-quitting.md#17 Psychological safety as a patch — "psych safety" workshops over a structure that punishes candour. → references/17-psychological-safety-as-a-patch.md#22 Fixing people — sending individuals on courses to fix a structural problem. → references/22-fixing-people.md#25 Burned by design — burnout produced by the operating model, then blamed on resilience. → references/25-burned-by-design.md#34 The Sunday email — always-on expectations normalised from the top. → references/34-the-sunday-email.md#48 It's just a job — meaning stripped out, so people withdraw discretionary effort. → references/48-its-just-a-job.md#53 Designed to undermine — structures that systematically erode trust and agency. → references/53-designed-to-undermine.md#56 Permanent urgency — everything is a top priority, so nothing can be planned or owned. → references/56-permanent-urgency.md
Strategy, direction & environment
#10 The company's strategy is unclear — teams can't self-direct without a shared, real purpose. → references/10-the-companys-strategy-is-unclear.md#14 Local optimisations — each unit improves its own number, the whole gets worse. → references/14-local-optimisations.md#20 Built for yesterday — structure optimised for a context that no longer exists. → references/20-built-for-yesterday.md#30 The external verdict — outsourcing judgement to analysts/consultants/benchmarks. → references/30-the-external-verdict.md#33 The customer we never met — building for a customer no one in the team has contact with. → references/33-the-customer-we-never-met.md#37 Outsourcing the future — handing core capability/strategy to vendors. → references/37-outsourcing-the-future.md#57 The market we think we shape — mistaking internal narrative for the actual environment. → references/57-the-market-we-think-we-shape.md#58 The short-termism machine — quarterly pressure crowds out adaptation and learning. → references/58-the-short-termism-machine.md
Agile, transformation & change
#6 Analysis paralysis — endless analysis because no one is safe to decide and act. → references/06-analysis-paralysis.md#19 The agile terrarium — a protected "agile" pocket inside an unchanged org. → references/19-the-agile-terrarium.md#29 Team Topologies, the wrong way round — copying team shapes without changing authority. → references/29-team-topologies-the-wrong-way-round.md#35 People resist change — "resistance" reframed as rational response to bad change. → references/35-people-resist-change.md#38 The product owner trap — a single PO becomes a proxy boss / single point of control. → references/38-the-product-owner-trap.md#39 Doing the wrong thing right — flawless delivery of work that shouldn't be done. → references/39-doing-the-wrong-thing-right.md#40 The project in product clothing — "product teams" still run as fixed-scope projects. → references/40-the-project-in-product-clothing.md#42 The pilot trap — successful pilots that can never scale because the system didn't change. → references/42-the-pilot-trap.md#45 Fixing the process — adding process to compensate for a structural fault. → references/45-fixing-the-process.md#50 The agile scaling trap — scaling frameworks (SAFe etc.) re-impose DP1 at scale. → references/50-the-agile-scaling-trap.md#61 Rearranging the furniture — job-enrichment initiatives that improve individual roles without changing who designs the work. → references/61-rearranging-the-furniture.md
AI
#21 Deploying AI into a broken system — AI amplifies a dysfunctional structure instead of fixing it. → references/21-deploying-ai-into-a-broken-system.md#43 The AI we cannot talk about — shadow/anxious AI use no one will discuss openly. → references/43-the-ai-we-cannot-talk-about.md
Communication, knowledge & growth
#2 Passing the buck — accountability bounces around because ownership is fragmented. → references/02-passing-the-buck.md#12 Communication problems — "communication" blamed for what is a structural disconnect. → references/12-communication-problems.md#52 Career paths — advancement means leaving the work, draining teams of mastery. → references/52-career-paths.md#55 The learning organisation that doesn't learn — learning rituals that never change how work is done. → references/55-the-learning-organisation-that-doesnt-learn.md#59 The corridor conversation — real decisions happen informally, outside the visible system. → references/59-the-corridor-conversation.md
