Time for Organisation Design

Most organisation design focuses on structure: roles, reporting lines, governance, spans, accountabilities and operating models. Those things matter. But they are not enough.

Exploring pace, timing, AI, sustainability and the operating model as design questions.

Many organisations do not fail because the boxes are wrong. They fail because the timing is wrong. Markets move faster than decisions. AI accelerates work faster than review and governance can absorb it. Sustainability demands longer horizons than financial cycles encourage. Strategy changes faster than the organisation can reconfigure around it.

The result is familiar: good people working hard inside systems that cannot adapt at the pace required. This is the territory I am exploring under the heading Time for Organisation Design.

Organisation design has always been better at structure than at timing, because structure is easy to see — you can draw a reporting line, map a process, fix an accountability. Time is harder: it lives in the relationships between parts, not the parts themselves, and won’t sit still long enough to be put in a box.

The central question

How should organisations be designed so they can create value, make decisions and adapt at the pace their environment requires?

That question sits behind much of my current work on operating models, organisation design, AI, sustainability and transformation. It is also the foundation for my emerging thinking on Requisite Pace: the idea that different parts of an organisation need to operate at different speeds, and that many performance problems arise when those speeds are poorly matched.

Why time matters

Every organisation contains multiple cycles of value creation. Some are fast: customer interactions, incidents, sales conversations, operational decisions. Some are medium-paced: product development, resource allocation, capability building, performance management. Some are slow: strategy, investment, culture, infrastructure, brand, sustainability and institutional trust.

The problem is not that some parts are fast and others are slow. They have to be. The problem comes when they are coupled badly: a fast customer cycle depends on a slow approval cycle, a fast technology cycle runs into a quarterly funding cycle, or a team is asked to move quickly while the organisation around it still decides slowly.

These are not just execution problems. They are design problems.

What becomes visible

Looking at organisations through time changes what we notice. It helps explain why transformation programmes create activity but not adaptation; managers become overloaded as the human buffer between fast work and slow decisions; AI increases organisational strain rather than simply improving productivity; and sustainability struggles when long value cycles collide with short planning horizons.

The issue is rarely speed in general. It is whether the right parts of the organisation are fast, slow, buffered, linked or deliberately kept apart.

Current themes

Requisite Pace — How fast different parts of an organisation need to sense, decide, act and adapt.

Coupling — How timing mismatches between interdependent parts of the organisation create delay, overload and fragility.

Pace debt — The accumulated cost of temporal misalignment: delayed decisions, repeated work, management overload, missed opportunities and slow adaptation.

Value cycles — The repeated cycles through which organisations create, deliver, capture and renew value for customers, employees, suppliers, partners, owners and wider stakeholders.

AI and the operating model — How AI changes the speed of some work without automatically changing the pace of judgement, governance, coordination or accountability.

Sustainability and circularity — How organisations handle tensions between short-term performance cycles and longer-term ecological, social and system constraints.

Why this matters for leaders

Leaders are often told they need to make their organisations faster. But speed is not always the answer. Some things need to move faster. Some need to move slower. Some need better rhythm. Some need buffering. Some need to be decoupled. Some need to be brought into tighter cadence.

The leadership challenge is not simply acceleration. It is temporal design.

That means asking: where does the organisation need to sense change more quickly? Where are decisions arriving too late? Where is work being generated faster than it can be absorbed? Where are short-term and long-term cycles working against each other? Where are managers acting as manual buffers between misaligned parts of the system? Where is the organisation accumulating pace debt?

Where this work is heading

Time for Organisation Design is an emerging body of thinking, not a finished framework. I am developing it through writing, case analysis, diagnostics and conversations with leaders, practitioners and researchers. The aim is practical: to help leaders see a class of organisational problems that are often misdiagnosed as culture, capability, execution or change management issues, when they are better understood as problems of timing, coupling and design.

If organisation design has traditionally asked, “How should the work be organised?”, this work adds another question: at what pace must the work, decisions and learning happen — and how should the organisation be designed around that?

The work so far

This page is the overview. The work itself lives in the writing, research and diagnostics below — some developed, some in progress, some still open questions.

Requisite Pace

The central idea: different parts of an organisation need to move at different speeds, and the design problem is how those speeds fit together. A diagnostic and design framework, currently in active development.

Research in progress

Your organisation doesn’t have a speed problem

Choose the Clocks

Make the Gears Mesh

Could you change gear in time?

The Thrashing Middle

AI and the operating model

How AI changes the speed of work without automatically changing the pace of judgement, governance, coordination or accountability — and what that asks of the operating model.

Writing in progress

AI Didn’t Break Your Operating Model. It Changed Its Clock Speed.

AI Sped Up Your Work. It Didn’t Speed Up You.

AI Is Now Your Team’s Loudest Clock

Diagnostics

The Requisite Pace diagnostic — a structured way to find where decisions are arriving too late, where work is being generated faster than it can be absorbed, and where short and long cycles are working against each other. In development.

Open questions

The thinking is still forming. These are the questions I’m actively working through with leaders and researchers: where does temporal design genuinely extend organisation design, and where is it just better OD by another name? Can pace debt be measured, or only recognised? What does an organisation deliberately designed around different speeds actually look like — beyond the metaphor? Where does AI relieve temporal strain, and where does it simply move the bottleneck downstream to human judgement?