In the early years of endurance racing, a pit stop took a minute or more. Mechanics worked hard, in the way that people work hard when the task is obvious and the tools are simple. Today a Formula 1 crew changes four tires in about two seconds.
It’s worth being precise about where that time went, because the obvious explanation is wrong. The modern crew is not stronger than the old one. The wheel gun is faster, but not thirty times faster. Almost all of the gain came from somewhere else: the crew removed the gaps between the handoffs.
Twenty people around a car, each with one job, each knowing exactly when their job begins and what signal starts it. The gunner doesn’t wait to be told the car has stopped. The tire carrier is already in position before the car arrives. Nobody is deciding anything in those two seconds, because every decision was made weeks earlier, in a practice bay, by people arguing about tenths of a second.
Effort is not the constraint
Most account teams are working hard. That’s not the differentiator, and it hasn’t been for a long time. Five capable people covering one large account, each doing good work in their own lane, produce five efforts. What they rarely produce is a sequence.
The difference matters because large accounts do not move in response to effort. They move in response to a set of things happening in an order. A clinical conversation lands differently after an operational barrier has been removed. An advocate is worth more when they are deployed after the economic objection has been answered, not before. A blocker is easier to flip when three people they trust have already changed position.
None of that is harder work. It’s the same work, arranged. And it’s the one thing a competitor with an equally good product and equally capable people can’t easily copy, because it’s not a capability, it’s a choreography.
Where plans actually fail
Ask a team to review a plan that didn’t work and they’ll usually point at a step. We did not get the meeting. The data came back late. The truth is usually less dramatic: the plan failed between two steps, in a handoff that both people assumed the other was holding.
This is why the most valuable sentence in an operating plan is rarely the objective. It’s the one that reads: when this happens, this person hands this to that person, and here’s how they’ll know it arrived. It’s a boring sentence. It’s also the sentence that separates the plan that executes well from a plan that just gets discussed.
A related failure is over-sequencing. Teams draw a plan as a chain, because chains are easy to draw, and the plan then runs at the speed of its slowest link. Most moves in a real account plan don’t depend on each other at all. Marking only the genuine dependencies, and starting everything else immediately, is often the single largest speed gain available to a team, and it costs nothing.
Every plan meets a safety car
A race plan is built around an expected sequence of events. Then a car stops on the circuit, the safety car comes out, and the entire field bunches up. The teams that gain in that moment are not the ones that react fastest. They’re the ones that decided in advance what they would do when the unexpected happens.
Account plans meet the same thing, and the mechanism is almost always a reaction rather than an event. A blocker loses control, budget or standing when your plan works, and they respond. A competitor notices and moves. Or, most commonly, your own organisation does something structural: a territory changes, an internal champion is promoted, a quarter closes and priorities move.
The cheapest way to find these is to move forward in time and look back. Assume it’s ninety days from now and the plan produced nothing, then write the sentence that explains why. Working backwards from a stated failure surfaces things that a forward-looking risk list never does, because it takes away the option of hedging. A risk list produces eleven items and no action. An obituary produces one, and it’s usually the right one.
What follows should be a counter-move rather than a contingency. A contingency is a plan for after it goes wrong. A counter-move is what you do differently starting this week so that it doesn’t.
The timing screen, not the flag
The last piece is measurement, and the trap here is familiar. The number everyone cares about arrives last. Revenue, volume, share: these are the flag at the finish line. By the time they tell you something, the race is over and the information has no operational value.
Racing teams solve this with telemetry. Tire temperature, fuel flow, sector times. None of these is the result. All of them move first, and a team that reads them well knows how the race ends while everyone else is still watching the cars.
The account equivalent is unglamorous and specific: how long an approval now takes, whether a dormant site has booked anything, whether a referral pathway has been agreed, whether one named person has changed position. These move in weeks. They belong on a scorecard alongside the lagging numbers, not instead of them, and each needs a baseline. A number with no starting point can’t show change.
There is a third category that teams routinely leave off, and it’s the one that proves the coordination thesis: how many sequenced moves involving more than one stakeholder were completed, with a named owner on each side. That’s not a proxy for the result. In a large account, it’s the result, arriving early.
Building it deliberately
A pit crew practises the stop hundreds of times before the season starts. Account teams almost never practise anything. They meet, they align, and they go back to their lanes.
The practical version of practice, for a team that will never get a rehearsal bay, is a rhythm short enough to survive a bad week. Fifteen minutes, same day, same time: what moved, what’s stuck, what changed about the account. A longer monthly meeting against the scorecard. One agreed escalation path. Every commitment written as a trigger rather than an intention, so it fires on a signal instead of on somebody remembering.
It’s not sophisticated. Neither is a wheel gun. What makes two seconds possible is that the sequence was decided in advance, the handoffs were named, and the same people ran it until it stopped requiring thought.
Effort alone will not distinguish your team. Everyone in your category is trying hard. The gap that’s still available, in almost every large account, is in the space between your people, and it’s the one place your competitors are probably not looking.
