The Fifteen-Minute Fence: Two Weeks of Not Rushing Straight Into the Next Thing

Most small firms do not have a meeting problem so much as a spacing problem. The diary looks reasonable enough until you notice that one call ends at 10:30 and the next begins at 10:30, leaving no room for notes, a glass of water, or the small mental gear change that stops you answering the second call as if it were still the first.

So a small UK consultancy — eight people, a mix of client work and internal projects — tried something deliberately unglamorous for two weeks. After every client call and internal meeting, they booked a 15-minute buffer. No agenda, no catch-up, no sneaky extra meeting. Just a fence around the end of one thing and the start of the next.

The trial was not about adding slack for its own sake. It was about finding out whether the working week feels less like a relay race when people are given a moment to pass the baton properly.

The rules were boring on purpose

The firm kept it simple. Every scheduled client call and internal meeting got a 15-minute block after it. The buffer belonged to the person coming out of the meeting, not to the next person in the diary. It could be used for notes, a loo break, checking a figure, or simply staring out of the window while the kettle boiled.

There were two exceptions. External calls that were already followed by a natural gap did not get a second buffer. And the Friday afternoon team wrap — a 20-minute standing item — kept its usual finish time because everyone agreed that adding a buffer there would just turn it into a 35-minute meeting with a cup of tea in the middle.

The firm tracked three things: how often meetings overran, how often the next thing started late, and how often the last task of the day spilled into the evening. They also asked people to jot down a one-line note after each buffer: what they actually did with it. That last part turned out to be more revealing than the timings.

Week one: the diary looked oddly empty

The first reaction was suspicion. A 15-minute gap after a client call felt like a luxury, and in a small firm luxuries tend to get quietly deleted. One account manager admitted she spent the first buffer checking whether she had missed something. Another said it felt like leaving a shop without buying anything.

By Wednesday, though, the pattern started to show. The overruns did not vanish, but they stopped cascading. A call that ran seven minutes long no longer pushed the next call into a rushed start. The buffer absorbed it. The day still had friction, but the friction had somewhere to go.

The late starts were more stubborn. The firm found that most late starts were not caused by meetings overrunning at all. They were caused by people trying to cram one more small task into the gap before a meeting — answering a quick email, checking a quote, replying to a message from a client. The buffer made that visible. It was not a meeting problem. It was a "just one more thing" problem.

Week two: the evening spill started to shrink

By the second week, something quieter changed. The last task of the day stopped spilling into the evening as often. Not because people were working faster, but because the day had fewer loose ends. The notes were written. The follow-up email was sent. The next step was clear. The buffer had become a small closing ritual scattered through the day rather than saved for the end.

One of the directors put it well: "We were treating the end of a meeting as the start of the next thing. Now we treat it as the end of the meeting." That sounds obvious written down. In practice, it required a diary change and a bit of discipline.

The firm also noticed that the buffers were not equally useful. After a difficult client call, 15 minutes was barely enough to reset. After a routine internal check-in, five minutes would have done. The trial did not produce a universal rule. It produced a better question: which meetings actually need a transition, and which ones just need a tidy finish?

What the firm changed afterwards

They did not keep every buffer. That would have been the wrong lesson. What they kept was a 15-minute buffer after client calls, and a 10-minute buffer after internal meetings that involved a decision or a handover. Routine updates lost their buffer entirely because they did not need one.

They also stopped booking meetings back-to-back across the lunch period. That was not part of the original plan, but the trial made the cost obvious. A 12:30 call followed by a 13:00 call meant somebody was eating a sandwich at their desk while pretending to listen. The buffer gave them permission to notice.

The most useful change was smaller than any of that. The firm added a single line to its meeting template: "What needs to happen in the next 15 minutes?" It is not a profound question. But it turns the end of a meeting into a deliberate handover rather than a scramble.

The 168-hour view

A 15-minute buffer sounds trivial until you count it. Five buffers a day is 75 minutes. Over a five-day week, that is more than six hours — a full working day, more or less, spent on transitions rather than tasks. That is not wasted time. It is the infrastructure that stops the rest of the week from collapsing into a series of rushed handovers.

Not every firm needs the same version of this. A two-person operation might find that a five-minute gap is enough. A team with lots of client calls might need the full 15. The point is not the number. The point is deciding, deliberately, that the space between things is part of the work rather than an accident that happens when the diary is kind.

The firm in the trial did not end up with a perfect week. They ended up with a week that felt less like a relay race and more like a series of finished conversations. For a small UK business trying to make 168 hours go further, that is not a bad place to start.