Core building blocks

Delays

The gap between doing something and seeing what happens - the source of most bad decisions in systems.

Also known as: Time lag, System latency

What it is

Every system has delays built into it. You turn up the heating and the room doesn’t get warmer for twenty minutes. You hire someone and they don’t become productive for six months. You launch a strategy and it takes two years before you can tell whether it worked.

Delays are the gap between an action and its effect. They’re everywhere, and they’re one of the biggest reasons people make poor decisions in complex systems. Not because people are foolish, but because the feedback they need to learn from arrives too late to connect to the thing that caused it.

The trouble is that most people make decisions as if the world responds immediately. When it doesn’t, they do more of the same thing - or give up too early - because they can’t see the effect of what they’ve already done.

What this looks like in organisations

A company notices declining customer satisfaction. They launch a training programme. After three months, satisfaction hasn’t improved, so they scrap it and try something else. But the training was working - it just hadn’t had time to show up in the numbers yet. They’ve abandoned the right approach and replaced it with a wrong one, and they’ll do the same thing again in three months.

A government introduces a tax incentive to boost housing construction. New homes take years to build, but the political cycle demands results in months. The policy gets judged a failure and reversed before a single house is finished.

A team invests in better documentation. Productivity dips initially because people are spending time writing things down. Leadership sees the dip and pulls the plug. The payoff - fewer repeat questions, faster onboarding, less duplication - never arrives.

How to use this

Before judging whether something is working, ask: how long should it take before we’d expect to see results? Write that number down before you start. Then hold your nerve until that date arrives.

When you’re designing a system or a process, map the delays. Where are the longest gaps between action and feedback? Those are the places where people will make the worst decisions, because they’ll be flying blind. Shorten the delays if you can. If you can’t, make them visible - put them on the wall, in the dashboard, in the project plan.

When someone proposes a quick intervention for a slow problem, that’s a signal. The mismatch between the speed of the fix and the speed of the system is where things go wrong.

The thought to hold onto

The delay between action and result is invisible, which is why it’s so dangerous. By the time you see what happened, you’ve forgotten what caused it.

When you’re seeing this

When an initiative gets cancelled before it’s had time to work. When the same problem keeps returning despite constant intervention. When leadership keeps switching strategies every quarter. When someone says “we tried that and it didn’t work” about something that was never given enough time.

timing decision-making policy organisations planning