
The fastest teams don’t leave gaps
Whenever I can, I’m out on a bike. Anyone who’s ridden in a fast bunch, or watched a team time trial or the end of a sprint stage at a grand tour, knows that a team working well together will almost always beat a group of strong riders who aren't.
There’s a clear plan. The riders take turns on the front, the changes are smooth, and whoever’s strongest in that moment pulls a little longer so the others can rest. The whole team goes much faster than any one rider could on their own. When it isn’t working, you get gaps and surges, and riders burning matches just to keep up.
A digital project is a race too, and the same rules apply. You can have a good strategy and a strong team that are keen to get stuck in, but if you aren’t working together tactically, time and good intentions drift away until you’re dropped before you know it.
The pyramid problem
Most agencies are built like a pyramid. A few senior people win the work, account and project managers coordinate it, and a bigger group of junior people deliver it. I’ve run agencies in exactly this way, so I’m not throwing stones. It’s the obvious way to make the margins work, and plenty of those junior designers and developers are very good at what they do. But is it the best way to run a project?
Follow even a simple client question through it. You ask the account manager, who passes it to the project manager, who takes it to the designer. The designer needs a steer from someone senior, who’s in workshops until Thursday. The answer then makes its way back to you, and suddenly a week’s gone.
Each of those handovers makes sense on its own. But add them up and it’s like a bunch ride with messy, slow changes on the front. Gaps open up, the pace drops, and you’re the one left burning energy to close them just to get an answer. That matters more now than it did five years ago. Competitors are shipping faster, and AI has shortened the time between “we should try this” and “someone else already has”. If your team keeps losing time at every change, the bunch rides away from you.
What bugs me most is that you often pay for senior thinking and only really see it in the pitch. After that it thins out.
Five questions to ask any partner
Before you sign with anyone, I think you ask these questions. You’ll learn more from the answers than from any credentials deck.
Who, specifically, will do the work? It’s unlikely any agency can lock in a full team before the work is won. Even pro teams don’t confirm their grand tour line-up until close to the start, but you always know who they’re riding for. You should be able to get the names of the people likely to be on the project, and meet whoever’s leading it before you commit. If nobody from the pitch will be on the project, I’d want to know why!
How many people sit between me and the person making the decisions? Ask them to walk you through the last time a client needed a senior call on something. Who did the question go to, and how long did the answer take? A real example tells you far more than a promise of “direct access”.
How much time will your most senior people spend on my project each week? I mean once the work starts, not in the pitch. If the answer’s vague, push on it.
How quickly can you start, and what does “start” actually look like? Anyone can promise a start date, especially to win the work. Ask what happens in week one and week two. You want to know which workshops will be booked and how quickly they’ll mobilise. Onboarding documents and a team still being pulled together are the neutral zone. Everyone’s moving, but the race hasn’t started yet.
(By now you’re probably wondering how many cycling analogies I can squeeze into one piece. Don’t worry, there are more.)
What happens when someone on my project gets moved or goes on leave? It’ll happen at some point. The answer tells you whether the knowledge sits in people’s heads or in how the team shares it.
Some of these questions might feel a bit awkward to ask across the table in a pitch. Jens Voigt had a 3-word answer for that kind of discomfort: ‘Shut up, legs.’ Ask them anyway, because the answers show you how the work will actually flow.
How we do it at Journey
I’ll use Journey as an example, mostly because it’s the one I now know best. It’s only one way of doing it, and there are others, but it’s working well for us.
Our team is senior-only, which in cycling terms means everyone is ready to take a turn on the front. The person you meet in the first conversation is the one doing the thinking and the work afterwards. Greg LeMond said of cycling, “It never gets easier, you just go faster.” I think this work is kind of the same. It never gets easier, you just get better at it, and a team that’s done it many times over can tackle even complex problems quickly.
It has its downsides. A senior-only team can’t stretch forever, so we’re very picky about the work we take on, and our hourly rate is probably higher than you’d pay with a pyramid. Where you should save is the time between asking a question and getting an answer. In my experience, that’s where most of the cost hides.
The projects I’m proudest of all had one thing in common. The client could ring someone who knew the work inside out and get straight answers immediately.
Back to the race
Whoever you go with, it’s worth asking what kind of team you’re lining up with. Is it a group that rides together and shares the work, understands strategy and tactics, or one that’s going to leave gaps you have to close yourself?
If those five questions leave you unsure, it’s better to find out before you’ve paid for the first sprint (in the project, not on the bike).
And if you’ve got a story about a handoff that cost you more than it should have, I’d like to hear it. I’ve got a few of my own, usually told over a coffee after a long ride.
Hayden Judd
Director of Strategy and Performance
