Originally published on Leadership System Book.

19 minute read

TL;DREvery organisation runs on a theory of the business, and its operating model is that theory made structural. Once the theory is embedded in the six surfaces of the operating model (value discovery, work and feedback flow, organisational work design, decision authority, execution infrastructure, and organisational economics), it governs what work is possible regardless of which framework the teams use. This is why practice adoption, coaching, training, and AI produce local gains that do not persist, and why the useful diagnostic is not maturity but movement, whether work moves, waits, learns, or decays.
This piece argues
  1. Once embedded in the six structural surfaces, a theory of the business governs what work is possible regardless of which framework the teams use. see why — jump to the section that argues this
  2. When practices are present and people are capable, the operating model is the least‑examined and likely explanation for disappointing delivery outcomes. see why — jump to the section that argues this
  3. Accountability without matching authority is a structural defect that cannot be corrected by intent or individual behaviour changes. see why — jump to the section that argues this
What to do
  • Run the four diagnostics this week on the span you control: does work move, does it wait, does the organisation learn, does the system decay.
  • Take the six operating‑model questions into your next leadership meeting and leave with one name and one date per question or treat the meeting as failed.
  • Stop treating culture as a lever; read culture as diagnostics about structure and change structural operating‑model constraints instead of launching culture change programmes.

Most of the engineering leaders I work with have already done the work. Scrum is in place. Teams are cross functional and mostly stable. There is a platform team, a pipeline that builds and deploys, a dashboard with four metrics on it, and now an AI assistant on every desk. The practices are not missing. The people are not weak.

And yet delivery is still slower than anyone expects, less predictable than anyone will admit in a board meeting, and more expensive to change than it was three years ago.

That gap is what this is about. My argument is easy to state and uncomfortable to act on. The frameworks and practices your teams adopt cannot overcome the operating model your organisation runs them inside. Engineering is not a set of team practices. It is a leadership system.

Your operating model is a theory of the business

Every organisation runs on what Peter Drucker called a theory of the business: a set of assumptions about the environment, about who the customer is, about what that customer values, and about what the organisation has to be good at in order to win. Most of those assumptions were never written down, and almost none of them are revisited. They were correct once. That is usually why nobody questions them.

Two things make this worse than it sounds. First, a theory of the business does not become obsolete because it failed. It becomes obsolete because it worked, and success is what stops it being questioned. Second, and sharper: for many organisations the theory never matched the realities of their environment at all. But when every company in your competitive arc makes the same mistake, it is not noticeable. Nothing in the market punishes an error everyone shares. The mistake becomes institutional.

There is one exception worth naming. A personality, or a group, can through sheer force of will make an organisation override the implications of its theory of the business. But it is almost always departmentally local, and it rarely outlives the person. Heroics are not a structure, and this piece is about what persists.

An operating model is that theory made structural. It is the assumptions converted into six structural surfaces (value discovery, work and feedback flow, organisational work design, decision authority, execution infrastructure, and organisational economics), so that they no longer have to be argued. They become the way things are done here. Governance is what the operating model becomes in practice, through how those surfaces are set.

THEORY OF THE BUSINESS Assumptions environment · customer value · capability → OPERATING MODEL Structure value discovery · work and feedback flow organisational work design decision authority · execution infrastructure organisational economics → PROCESSES / PRACTICES “How things are done here” no longer argued, inherited tested? The loop that goes missing

Drucker’s requirement was never just that the theory exists. It was that the theory be tested constantly, because it is a hypothesis, not scripture. That dashed return arrow is the piece almost nobody builds, and it cannot build itself: a theory made structural has no sensor. Nothing inside the structure can detect that its founding assumptions have lapsed, because the structure exists precisely so those assumptions no longer get argued. Detection is a job, and in most organisations it is an unowned job.

This is why operating models are simultaneously so powerful and so hard to see. A framework is something you adopt, and you can point at it. A theory of the business is something you inherit, and it points at you. Scrum can be installed in a quarter. The assumption that work can be specified up front, approved centrally, and then executed to plan is installed in your budget cycle, your capitalisation rules, your job architecture, and your promotion criteria. One of those two things is going to win, and it is not the framework.

The distinction between a predictive operating model and an adaptive one is not a moral one, and it is not modern against traditional. Predictive structures work extremely well when their assumptions hold: stable demand, knowable work, long product lifecycles, advantage from efficiency and consistency. They fail when the environment changes faster than the planning cadence that governs it. Most organisations I see are not badly run. They are running a theory of the business that stopped matching their environment some years ago, and nobody was accountable for noticing. I have written about that distinction at length elsewhere.

The two theories are mutually exclusive. They make contradictory claims about the same environment, so at most one is true of yours. That does not make organisations pure: an adaptive theory of the business freely uses predictive practices wherever the work is knowable, in payroll, in regulated execution, in any known-good procedure. The practices serve; the theory governs. If you believe your organisation holds both theories, look at what your budget process does when the two collide. That is your theory.

When this is not your problem

I should say this plainly, because the argument reads as universal and it is not.

If your demand really is stable, your work really is knowable in advance, and your product lifecycle is measured in years, a predictive operating model is not your constraint. It is the correct design, and changing it would cost you the advantage you have.

If your teams genuinely cannot do the work, structure will not save you. Genuine means absent: nobody in the system has the skill yet, and the work would fail even with every gate removed. That is fixed by hiring, training, and time. But if skilled people keep leaving, or mastery never gets funded time, that is not a capability gap. That is the organisational economics surface wearing a skills costume, and you are back in this article. My claim is narrower than it sounds. When the practices are present and the people are capable, the operating model is the explanation you have least examined, and it is the only one this piece gives you a way to test.

And if you can answer the six questions at the end of this piece with evidence rather than opinion, you are not the reader I wrote this for.

Where the theory is actually written down

If you want to find an organisation’s real theory of the business, do not read the strategy deck. Read six things instead. These are the surfaces where the theory stops being an idea and starts governing behaviour. They are the levers that make up the operating model, and governance is not a seventh. Governance is what the operating model becomes in practice, through how these six are set.

Two things sit inside every surface rather than beside it. The first is what is measured there. Measurement determines what leaders are able to see, and therefore what they are able to decide. When the measures are outputs, and the people being measured cannot change the system that produces those outputs, the measures stop describing reality and start describing what people need reported. Signal integrity, the degree to which the signals reaching leadership reflect operational reality, degrades quietly, and it degrades first in exactly the places where you most need the truth. The diagnostic is not whether your metrics are good. It is what happens when a metric reveals a structural problem rather than an execution one. Organisations that change the metric have told you where their accountability actually sits.

The second is who carries the consequence there. The most common structural defect I find is accountability without authority. A team is held to an outcome it does not control the conditions for. Engineers are asked for quality by an organisation whose funding, deadlines, and measurement all penalise the behaviour that produces it. Nobody in that arrangement is behaving badly. They are behaving rationally, given the system they have been handed. Where accountability and authority sit apart, no amount of intent closes the gap. It is a structural property, and it is fixed structurally or not at all.

Each surface below is also somewhere its founding assumptions can lapse unnoticed. Ask all three of each: what is measured here, who carries the consequence here, and what would tell us this has expired.

Value discovery: what you decide is worth solving

Value discovery decides how an organisation finds problems worth solving and tests them before it commits to delivery. When discovery collapses into upfront requirements followed by execution, a decision cannot be tested until it has been approved, and by then it has usually also been committed. The property being destroyed here is what I call decision testability: the ability to validate a decision against reality before the commitment becomes irreversible.

The second half of this surface is the capacity to stop. When the operating model prevents abandonment, every experiment quietly becomes a commitment, and the organisation accumulates commitments instead of learning from them.

Work and feedback flow: how quickly work becomes evidence

Work and feedback flow decides how quickly work moves from idea to evidence. Batch size, feedback latency, and the amount of work in progress are set by the operating model, not by a team’s choice of framework, which is why a team can follow every practice it was taught and still wait. Where work moves in large batches, feedback arrives late and learning arrives with it. Where batches are small and feedback is fast, evidence reaches a decision while changing course is still cheap. This is the surface the four questions below read most directly: does work move, does it wait, does the organisation learn, does the system decay.

Organisational work design: how capability and knowledge are organised

Organisational work design decides how capability and knowledge are organised for execution: how teams are composed, and how their boundaries relate to the systems they work on. Stable teams with an adaptive strategic direction accumulate context. Restructure teams every time strategy shifts, or disband them at the end of a project, and the context goes with them. Where team boundaries and technical boundaries do not match, handoffs accumulate and context fragments, whatever the capability of the individuals.

Decision authority: who may decide without asking

Decision authority answers one question: what may a person do without asking. Every approval gate is a recorded statement that the organisation does not trust the information held at the point of work, and would rather pay delay than accept variance. That is sometimes a sound trade. It is rarely a conscious one, because approval gates are added one incident at a time and removed almost never. Every gate lowers decision testability.

Context does not survive travel. Every layer it crosses on the way to a decision maker strips detail and adds interpretation. When authority sits several layers above where the information is generated, the organisation has designed decision latency into itself, the time between recognising a need for change and having the authority to act, and the delay is not a behaviour anyone can be coached out of.

The compounding cost is not slowness. It is that by the time a decision reaches the person entitled to make it, the option to reverse it cheaply has usually already expired.

Execution infrastructure: what a team can change and observe without asking

Execution infrastructure decides what a team can build, release and observe without waiting on someone else: deployment pipelines, observability, self-service environments. When it is centralised, infrastructure teams become approval authorities rather than capability providers. Deployment waits for a change advisory board or a release window, batches grow to justify the cost of each release, and feedback lengthens in proportion. Teams are held accountable for outcomes they cannot deploy, observe or validate without permission. Infrastructure design is not a technical concern isolated from operating model design.

Organisational economics: what you buy, and for how long

Funding decides what an organisation is structurally able to change its mind about. Fund a project and you have bought a scope, a date, and a team that disbands at the end, which means learning that arrives late has nowhere to go and no one to carry it. Fund a product, or a long-lived team that owns an outcome, and you have bought a capability that can absorb what it learns.

There is a third rung. Fund an outcome, and the money is attached to the result rather than the plan, so learning redirects the work instead of being defended against. A project buys a plan. A product buys a capability. An outcome buys a direction. The chain should run downward from the vision: the vision defines the outcomes, outcomes drive the products, each product hosts a capability, and projects, if you use them at all, are batches of work inside a product, never the unit of funding.

Annual funding cycles in a market that moves monthly do not just slow the organisation down. They make it structurally rational for everyone in it to defend a plan they know is wrong, because the plan is the thing the money was attached to. The book calls this surface organisational economics.

Why frameworks, coaching, training and AI change so little

Once you see those six surfaces, the disappointing return on transformation investment stops being mysterious.

Frameworks, coaching, training, and tooling all operate inside the constraint. The operating model is not a layer above the work. It wraps it. They can make a team better at working within the system. They cannot change the system, because the levers that define it (budget, structure, policy, decision rights) are outside everything they touch. This is why improvement arrives, holds for a while, and then regresses. The operating model reasserts its constraints, and everyone concludes the framework did not work.

Operating model: budget · structure · policy · decision rights the constraint is not above the work, it is around it Frameworks · coaching · training · tooling make teams better at working inside the system Teams doing the work

AI is the sharpest current example, and it is worth being precise about why. AI does not create a new operating-model requirement. It accelerates execution, and in doing so it removes the technical effort that used to disguise where the real constraint was. When writing the code was the slow part, governance delay and context decay were hidden inside the estimate. When writing the code is fast, they are all that is left. The queue does not disappear. It just becomes visible.

There is a second effect that is easier to miss. AI output arrives quickly and looks precise, which means an invalid assumption can survive longer under AI than it did under manual work, because nothing about the output signals that it was built on the wrong premise. Where context quality is poor, AI does not compensate. It multiplies. This is why I treat AI as a diagnostic rather than an intervention: it will tell you, faster and more expensively than anything else you could buy, exactly what your operating model was already doing.

The tell: stated intent against the operating model

Almost every organisation I work with has a stated intent that is genuinely held and an operating model that contradicts it. The contradiction is not hypocrisy. It is usually that the intent was updated and the structure was not.

The tells are consistent, and you can look for them this week:

  • You have asked for empowered teams, and every decision above a fixed value goes to a forum that meets fortnightly.
  • You have asked for faster feedback, and you fund in annual cycles against fixed scope.
  • You have asked for quality, and the only measure with consequences attached is date adherence.
  • You have asked people to surface problems early, and the last person who did is still explaining it.
  • You have asked for experiments, and there is no mechanism to stop one, so every experiment quietly becomes a commitment.

Where stated intent and structure conflict, structure wins, because structure is the thing with consequences attached. It wins without a meeting. People are reading the system, not the memo, and they are reading it correctly.

This is also why culture change programmes fail. Culture is the shadow the structure casts on the wall, cast by the structure, which was formed from the theory of the business. You cannot change a shadow. You can only move the thing that casts it. Culture is a read-out, not a lever: read it, because it is excellent diagnostics about your structure, and stop pulling on it.

Move, wait, learn, decay

The most useful diagnostic I know is not a maturity model. It is four questions about what your system does with work, and you can answer all four this week from things you already have.

Does work move? Take ten items you shipped last quarter. For each, write down the date work started and the date a customer could use it, then subtract the days anyone actually touched it. What is left is waiting. In the organisations I look at, the waiting is usually the larger number.

Does work wait? Walk your board and find everything that is done but not released, or decided but not authorised. Count them, and note what each one is waiting for. If most are waiting for a person rather than for work, you have found where authority sits relative to information.

Does your organisation learn? Look at the last five problems that reached your desk and ask what changed afterwards. A new rule, a new report, a new dashboard, or a new approval is a reaction. A removed approval, a moved decision, or a changed budget line is learning. Count the two. Most people are surprised by the ratio.

Does the system decay? Find one approval, one report, and one recurring meeting that exist because of an incident nobody in the room can now date. Then ask who is accountable for removing them. If the answer is nobody, this is not entropy and it is not the market. It is an unowned job.

Six questions worth answering honestly

If you take one thing into your next leadership meeting, take these. They are diagnostic, not rhetorical, and the answers are usually already known by someone who has not been asked.

The four questions above tell you what your system does with work. These six tell you where that behaviour is written, one per surface. The order matters: run the four yourself, this week, on the span you control. No permission needed. Take the six to your next leadership meeting once you have the numbers, and leave that meeting with one name and one date per question, or the meeting produced nothing.

  1. Value discovery. How do we decide which problems are worth solving, and what can a team do when the evidence says to stop?
  2. Work and feedback flow. What sets the size of our batches and the length of our feedback loops, and who can change it?
  3. Organisational work design. Which teams have we reorganised or disbanded in the last two years, and what context did we lose when we did?
  4. Decision authority. What decisions currently require permission, and what evidence would tell us that permission is buying us more than the delay costs? Where is the largest gap between where information first appears and where the decision about it is made, and what is that gap costing us in reversibility?
  5. Execution infrastructure. What can a team change, release and observe in production without asking anyone, and what does that do to the size of what it ships?
  6. Organisational economics. What are we funding that we would not start today, and what is our standing mechanism for stopping it? Drucker asked the first half of that question in 1954, and his version was not a question but a calendar entry. Most organisations still cannot answer the second half.

Then ask two more of every one of the six, because they sit inside each surface and not beside it. When a measure there last revealed a structural problem, did we change the structure or the measure? And who is currently accountable for an outcome there whose determining conditions they do not control?

Not one of these questions is about your teams. That is the point.

Subscribe to Martin's articles

Writing since 2001

Articles, usually weekly on Mondays. One click to leave.

By subscribing you agree to the terms and privacy policy.

This work does not finish

The uncomfortable part of treating engineering as a leadership system is that it removes the possibility of completion. There is no target state. Operating models degrade through accumulation and through decay, continuously, and the work of removing obsolete commitments, realigning decision rights, and refreshing the assumptions the model rests on is permanent executive work. It cannot be delegated to a transformation office, because the levers are not there.

What changes when leaders take this on is not that delivery becomes fast. It is that problems arrive while they are still cheap, decisions get tested before they become irreversible, and leadership attention stops being consumed by crisis response and retrospective justification. That capacity is the real return, and it is structural rather than heroic.

If your organisation has adopted the practices and is still disappointed by the results, the constraint is very unlikely to be your engineers. Start with the six surfaces. The theory of your business is written there, and so is the reason your work moves, waits, learns, or decays.

Engineering as a leadership system means two things, and I mean both. Engineering, the function, is a leadership system: its performance is produced by structures leaders own. And the leadership system is what needs engineering: your operating model is an engineered artefact, designed once, by someone, under assumptions that were true at the time. It deserves what any engineered system deserves. Instrumentation. Testing against reality. Maintenance. Refactoring when its assumptions expire.

The engineering problem in your organisation was never the code. It is the company. Go engineer it.

Everything above is diagnosis. It will let you recognise your own organisation and tell you where to look, but it deliberately stops short of two things. It does not give you the mechanism by which each of these structures produces its outcome, and it does not tell you what evidence would prove the argument wrong. Both matter, because a diagnosis you cannot falsify is only a strongly held opinion. That is the work the book does.


I wrote this alongside my session for The Future of Work in Scotland, on engineering as a leadership system and what lies past framework adoption. You can watch the session recording.

Read Engineering as a Leadership System on Leanpub, where the ebook comes with free updates for life and you set the price. Paperback and Kindle are on Amazon.

Was this useful?

Checking…

Read 281 times. Enjoyed it? One click, no account.

Checking…
Checking… Subscribe

Questions this answers

Why hasn’t adopting Scrum, DevOps practices, and AI made my engineering organisation faster or more predictable?

Because team‑level frameworks and tooling operate inside a larger constraint: your organisation’s operating model, which is a structural expression of its underlying ‘theory of the business.’ If that theory is outdated or misaligned with a fast‑changing environment, it governs funding, decision rights, governance and incentives in ways that override agile practices, so improvements briefly appear then regress as the operating model reasserts its constraints.

How can I diagnose whether my operating model is the real constraint on engineering delivery, and where it’s written into my organisation?

You diagnose it by examining six structural ‘surfaces’—value discovery, work and feedback flow, organisational work design, decision authority, execution infrastructure, and organisational economics—and by running four simple diagnostics on current work (does work move, does it wait, does the organisation learn, does the system decay). The organisation’s true theory of the business is encoded in how these surfaces are set, what they measure, who bears consequences there, and how they respond when metrics reveal structural problems.

Why doesn’t AI meaningfully accelerate my software delivery, even though it makes coding faster?

AI speeds up execution work like coding, which exposes rather than fixes the real constraint: governance delay, approval gates, and context quality embedded in your operating model. When code is fast to write, queues, decision latency, and invalid assumptions become more visible; AI can even let bad assumptions persist longer because its precise‑looking output hides that the premise was wrong, so it acts as a diagnostic of operating‑model problems rather than a cure for them.