DP1 Briefing

Most of the patterns OD practitioners spend their careers trying to fix are not caused by the wrong people, the wrong culture, or the wrong leadership. They are produced by the design. This briefing explains the design.

Open Systems Theory distinguishes two underlying ways of organising work. Sociotechnical Systems theory was developed by Eric Trist and Ken Bamforth at the Tavistock Institute in the early 1950s, and Fred Emery extended that work with Trist into Open Systems Theory through the 1960s, with Merrelyn Emery joining the collaboration from the 1970s. They called the two organising logics genotypical design principles, meaning they describe the underlying structure of an organisation, not its surface form. The structure is what produces the behaviour. This briefing covers Design Principle 1, the design that almost every reader of this piece has worked inside.

What you already know about it

Most practitioners already know what DP1 produces, before they have a name for it.

They know organisations where capable people are quietly frustrated, not because the work is hard but because they are prevented from doing it well. Where bad news travels slowly upward, if at all, while good news moves freely. Where teams that should be working together are instead competing (for resources, for recognition, for the ear of whoever is above them). Where people who joined with broad skills are, years later, narrower than when they arrived. Where endless culture and leadership programmes produce real effort and modest, temporary change.

These are not random failures. They are consistent. They appear across sectors, sizes, and geographies. They appear in organisations with excellent managers and in organisations with poor ones. That consistency is the signal. Consistent patterns have structural causes.

The structure that produces them

Design Principle 1 organises work on the assumption that any person doing a job can be replaced by another person doing the same job. To make that possible, two things follow.

First, jobs have to be defined narrowly enough that substitution is practical, so roles are specified in detail, and people are hired and managed against those specifications. Second, someone has to coordinate the work across the people doing it, because the people doing it have been designed not to. So coordination authority sits one level above the work. The manager decides what gets done, in what order, to what standard, and by whom. The people doing the work are responsible for their task. The connection between tasks, and the goals the tasks serve, belong to the level above.

That is the whole architecture. Everything else (line management, role grades, escalation processes, planning departments, performance review cycles, HR business partners) follows from those two moves.

What it does to people

It makes cooperation structurally irrational. When the only path to better pay or progression runs upward through the hierarchy, people are in competition with the colleagues they sit alongside. Helping someone who is struggling is a rational act only if it does not improve that person's standing relative to your own. The result is an environment that produces competitive behaviour regardless of the values the organisation espouses, because the incentive structure runs in one direction only: up.

It strips people of skills they arrived with. Most people join organisations with more capability than their job description calls for. DP1 has no mechanism for using that surplus: the role specifies what is needed, and the rest is irrelevant. Over time, capabilities that go unused atrophy. People become progressively narrower than when they arrived. The organisation loses adaptability it once had; individuals lose professional range they once had. Neither outcome is intended; both are structural.

It blocks meaningful futures. When progression is controlled from above and the work itself is narrowly specified, most people reach a point where there is nowhere obvious to go. The experience of being stuck (capable, working hard, going nowhere) is common enough to seem like a personal problem. It is not. It is what the design produces for the majority of people inside it.

It creates groups that work against each other. Competition between individuals scales into competition between teams and functions. Each unit is measured against its own targets, and those targets are frequently in tension with each other. Functions optimise locally at the expense of the whole. Not because the people in them are self-interested or parochial, but because that is what their incentive structure asks them to do. In more entrenched cases, groups will actively obstruct each other. Ackoff's observation applies here: increasing the efficiency of a part will almost always reduce the efficiency of the whole.

It produces cliques as a survival response. When formal channels offer little influence and competition is built into the structure, people form informal protective groups. These cliques are not a dysfunction to be managed; they are a rational adaptation to an environment that offers no other way to feel secure. They tend to work against other groups. Where you find persistent inter-team rivalry or sabotage, look first at the structure.

It creates dependency. When people are trained by the structure (not by intent) to wait for instruction, to refer decisions upward, and to stay within their job description, they progressively lose the habit of autonomous judgement. By the time the organisation wants people to take initiative, it has spent years removing the conditions under which initiative develops. The dependency is not a personal trait. It dissolves reliably when the structure changes.

What it does to information

DP1 produces a characteristic and serious distortion in how information moves. Because status is asymmetric (workers depend on those above them, not the reverse), people at every level are incentivised to manage what travels upward. Good news moves freely. Bad news (errors, quality failures, emerging risks, customer complaints) is suppressed, minimised, or reframed before it travels up, because surfacing it reflects poorly on the people closest to it.

The result is that senior leaders in DP1 organisations consistently believe they have a more accurate picture of what is happening below them than they do. This is not a failure of management; it is what the design produces. As soon as status is unequal, communication is distorted in every direction. The gap between what is actually occurring and what leadership believes is occurring is a structural feature of DP1, and it widens as the organisation grows.

When the environment is changing fast, this becomes acute. Information about what is changing has to climb the hierarchy before anyone with decision authority sees it, and decisions then have to descend again. By the time a response arrives, the situation has moved on. The organisation is not slow because of its people. It is structurally late.

Why interventions inside it tend not to hold

The patterns described above are structural. They are produced by the design, and they will persist regardless of who is in the roles, how hard people work, or the frequency and quality of culture programmes, leadership development, or engagement initiatives. They persist until the underlying structure changes.

This is worth sitting with, because it reframes the practitioner's job. The people inside a DP1 organisation are not failing. They are, in most cases, behaving entirely rationally within the system they are in. The problem is the system. Changing behaviour without changing structure is therefore a low-yield strategy. Programmes that operate within the structure, however well designed, do not alter that structure. They can produce real and useful change at the margins. They do not address the cause.

Where DP1 works

The Emerys are explicit that DP1 has appropriate contexts. It works when the environment is stable enough to be planned for, the work is repetitive enough to be specified in advance, and reliability matters more than adaptation. High-volume manufacturing, routine processing, regulatory compliance, and the operational spine of any organisation that needs to scale all benefit from DP1 design.

DP1 is also the default design. It is well understood, supported by decades of practitioner technique, and legible across cultures and sectors. OST's argument is structural, not moral: DP1 has been applied across a far wider range of contexts than it can support, and the misapplication produces the patterns of strain that practitioners spend their careers trying to relieve.

Where DP1 fails

DP1 fails when one or more of three conditions holds. First, when the work is complex and contextual rather than routine, because the role specification cannot anticipate the situations the person will encounter. Second, when the environment is turbulent rather than stable, because hierarchical decision cycles are too slow. Third, when the value the work creates depends on the discretion and judgement of the person doing it, because DP1 is designed to remove discretion from the work and concentrate it above.

That third condition now describes most of the economy. Knowledge work, professional services, complex care, frontline customer experience, creative work, and most of the work currently being displaced or augmented by AI all turn on judgement. DP1 designs applied to these domains produce the familiar pattern: capable professionals constrained from doing the work they were hired to do, managed by performance systems that measure the constraint rather than the work.

What to do as a practitioner

Three moves are useful regardless of where you sit.

Diagnose the design before naming the intervention. Before recommending leadership development, capability uplift, culture work, or any other intervention aimed at the people inside the structure, name what kind of structure they are inside. If the structure concentrates decision rights above the work, the intervention will be partly absorbed by the design. Name that first.

Match the design to the nature of the work. Not all work in the same organisation has the same characteristics. The operational spine may belong in DP1 while the product, service, and customer-facing functions have moved into work that DP1 cannot support. The diagnosis is rarely "this whole organisation is bureaucratic and should change." It is usually "these specific parts are doing work that the structure is no longer carrying."

Be honest about what is and is not possible inside a DP1 design. Useful work is possible inside DP1: clarifying purpose, repairing relational damage, building manager capability, improving information quality. None of it changes where decision rights sit. Knowing the difference between what you can shift and what requires structural change is what separates an effective practitioner from one who keeps running the same programmes and wondering why the needle does not move.