You'll Never Keep Up (and That's Fine): Why Finishing Beats Starting

Focus wasn't the problem

You can do everything in the last chapter right, and your team can still stall. They know the mission, they're focused and yet things don't quite get finished. For a long time I assumed this was a focus problem. It wasn't. In a field this fast, attention is fragmented not just by interruption but by opportunity: there's always a new model or solution, a new capability, each one whispering that what you're doing is already a little out of date. So people drift off the current work before it's done. The bottleneck shifts. Once you've earned focus, the thing that protects it is closure.

Anchor the mission to the slow clock

There are two clocks running, and you may be paying more attention to the wrong one. The technology clock, models, tools, agents, runs incredibly fast. The value clock, the customer problem your mission exists to solve, runs far slower. In my field, a security leader's core anxieties have barely changed in years, we hear this all the time from CISOs: Do I understand my exposure? Can I prove control? Will this survive an audit? The tooling has reinvented itself several times; the questions are remarkably stable. A customer-anchored mission only protects attention if you actively resist the fast clock, sampling it deliberately, but keeping the team pointed at what will still be true in twelve months. I believe it's the leader's job to be the person who knows which clock to read, and when.

Closure is the discipline some teams skip

It's not only the interruption that hurts, it's the unfinished work it leaves behind. The researcher Sophie Leroy named this attention residue: when you switch away from a task before it's complete, part of your mind stays stuck on it, and that residue measurably degrades whatever you do next. It connects to a much older finding, the Zeigarnik effect, from 1927, that the brain keeps an open loop running for unfinished work. That loop quietly consumes the attention you need for the task in front of you. Research summarised by the American Psychological Association suggests the tax of constant switching can reach as much as forty per cent of productive time. Think about all the thoughts you have across a typical day, how much of your thinking time is consumed by unfinished work? Your team feels the same.

There's an operational truth alongside the psychological one. Little's Law, a principle of flow that has held for over half a century, tells us that the more work you have open at once, the longer everything takes to finish, because output is set by throughput, not by how much you cram in. Put the two together and the conclusion is uncomfortable for a fast-moving culture: starting more work is how you finish less of it. The discipline some teams miss is simple to say but harder to hold, finish before you start. Closing work isn't tidiness, although we were told as kids to tidy our bedrooms before we can go out to play! It's how you reclaim the attention the next thing deserves.

Be the filter, not the firehose

You cannot read everything (other than this!), and neither can your team. When the overwhelming majority of new things being released will never touch your customer's problem, the most valuable thing a leader can do is decide what the team will deliberately not track this quarter. This is strategic ignorance as a feature, not a flaw. One curated signal beats ten unfiltered firehoses. Your job isn't to forward more; it's to absorb the noise on your team's behalf and pass on only the fraction that changes what they should do. You are the filter.

So how do you run several things at once?

Every busy leader will be asking this, and the answer resolves the apparent contradiction between "stay focused" and "we have ten things on." For the individual, the answer is: don't. Keep people as single-threaded as you can, because that's where closure lives. But for the organisation, you absolutely can run parallel bets, through what scholars since James March (1991) call ambidexterity: some of the team exploring the new while others scale what already works. In simple speak this is called effective teamwork. Each person owns a clear lane; the team holds the breadth. Parallelism is a property of the system. Multitasking is a tax on the person. I would argue great leaders build the former and protect their people from the latter.

The shift

Clarity sets the target; closure is how you hit it. A mission tells your team what matters. The discipline to finish, subtract and ignore is what protects that mission from a world that won't stop accelerating. If your team struggles to say no, I would recommend an approach I was taught and have used a lot. Michael Bungay Stanier's prompt from The Coaching Habit works beautifully: "If you're saying yes to this, what are you saying no to?" The "no's" make room for the "yes's".

Test this for yourself. Add a fourth question to last week's five-minute test: what have you or your team started that you haven't finished, and what would it take to close it before you start anything new?

The foundations are now set, direct your team's attention, then protect it. Next week’s article will cover how AI reshapes the work itself, starting with the skill that suddenly matters more than any other: judgement.