I was on a call a few months ago with the COO of a 250-person professional services firm. She'd just come out of a board meeting where the partners had - for the third consecutive quarter - agreed that "something needs to happen with the website and the client portal." Third quarter. Same conversation. No decision, no budget, no one willing to go first.
Her frustration was pretty hard to miss. "We know there's a problem," she said. "We just can't agree on what the problem actually is. Marketing thinks it's the CMS. The partners think it's the design. IT thinks the whole thing needs ripping out and starting again. And I'm sitting here thinking we're about to spend six months arguing about scope before anyone lifts a finger."
I told her she didn't need a six-month strategy exercise. She needed two weeks.
There's a pattern I see constantly, and it drives me a bit mad. A firm recognises it has a digital problem - the platform is creaking, enquiries have dried up, a competitor's just launched something that makes them look dated. So they do the "responsible" thing: they commission a big piece of work. An agency audit. A transformation roadmap. A thorough review of the entire digital estate.
Three months and a hefty invoice later, they've got a 60-page PDF full of recommendations. Some of them are good. Most of them are obvious. And none of them are specific enough to act on without commissioning another piece of work to figure out the detail.
We don't need another assessment - we need someone to actually deliver something.
Fair enough. And if you've been through that cycle before, the scepticism is completely earned. But the reason those big assessments feel like a waste of time isn't because assessment is the wrong idea. It's because they tried to assess everything at once, which means they assessed nothing with any real depth.
A diagnostic sprint is a different animal.
A diagnostic sprint is a focused investigation of a specific question, delivered in a fixed timeframe - typically two weeks. No 80-page decks. No boiling the ocean. You go in with a defined question, and you come out with a clear answer, evidence to support it, and a set of prioritised recommendations specific enough to act on immediately.
It's not a generic audit. It's not a discovery phase - though it often precedes one, and I've written elsewhere about why skipping discovery is the most expensive decision you'll make. And it's definitely not a disguised sales process where someone wanders around your building for a fortnight and hands you a proposal for a £400k programme.
What you get at the end: a clear problem statement that everyone in the room can actually agree on, recommendations ranked by impact and feasibility, and enough evidence to make a confident investment decision. That last bit matters most. Because the real cost of indecision in most mid-market firms isn't the money they spend on the wrong thing - it's the months and years they spend not doing anything at all while the problem quietly compounds.
The most common trigger is a major investment decision looming. You're about to commit serious budget to a platform migration, a website rebuild, or a CRM implementation, and you want to be sure you're solving the right problem before you write the cheque. We worked with a 400-person professional services firm that had been quoted over £400k for a full website and CRM rebuild. Their COO had a nagging feeling they were about to spend a lot of money on the wrong thing. Fourteen days later, we'd established that roughly 60% of the original brief was unnecessary. The real issue was a broken enquiry-to-onboarding handoff - nothing to do with the website design. The fix cost around £80k. They saw a 22% improvement in enquiry-to-client conversion within 90 days and avoided £320k of wasted spend.
The second situation is a stalled project. Something was started, enthusiasm was high, and then it ran into the sand. Requirements kept shifting, the vendor relationship went sideways, internal priorities changed and the project quietly lost its champion. A sprint can cut through the accumulated confusion and tell you whether to restart, restructure, or just walk away.
Then there's the divided-opinions scenario - which is exactly what the COO I mentioned was stuck in. Marketing blames the CMS, IT blames the design, the partners blame marketing. Everyone has a theory. Nobody has evidence. A sprint brings data to a conversation that's been running on opinion, and it does it quickly enough that people haven't had time to entrench further. (They will entrench, given long enough. I've seen it.)
And sometimes the problem itself is genuinely unclear. You know something's wrong - client satisfaction is drifting, the pipeline has softened, your bounce rate has quietly doubled - but you can't pinpoint why. A sprint takes the symptoms seriously and works backward to the actual diagnosis.
I should be specific about this, because "two weeks" sounds either impossibly short or suspiciously vague depending on your prior experience with consultancies.
The first few days are about understanding the landscape. Stakeholder interviews - not the polite, everyone-agrees-on-the-vision kind, but the honest ones where you ask awkward questions and get different answers from different people. That divergence is the useful bit. If your Head of Marketing and your CTO describe the same problem in completely different terms, that tells you something important about where the real friction lives. We had one engagement where the marketing director said the problem was "lack of content" and the CTO said the problem was "too much content nobody could find." Both were right. That tension took about forty minutes to surface and it reframed the entire brief.
After that, there's a review of what actually exists. Platform architecture, analytics data, content estate, user journeys, integration points. Not everything - just the things relevant to the question you're investigating. This is where the discipline of a sprint matters. If you don't constrain the scope upfront, you end up doing a mini version of the big audit nobody wanted.
The second week is synthesis and recommendations. What's actually broken? What's working but underperforming? What should you do first, second, and not at all? And - this is the part that gets overlooked - what does the evidence actually say, as opposed to what everyone in the building assumed going in?
At the end, you sit down with the leadership team and walk through the findings. Not a presentation. A conversation. Here's what we found, here's what it means, here's what we'd recommend, and here's roughly what it'll cost and how long it'll take.
There's a secondary benefit to diagnostic sprints that I think is actually more valuable than the recommendations themselves: they create momentum.
Most mid-market B2B firms I work with aren't paralysed because they lack ideas. They're paralysed because previous attempts at digital investment have been painful, over-budget, or underwhelming - often all three. There's scar tissue. The board remembers the last website project that went sideways. The partners remember the CRM implementation that nobody adopted. Every new proposal gets filtered through a lens of "Why should we believe this will be different?"
A sprint breaks that cycle because it delivers something tangible in two weeks. Not a promise of future progress. Actual answers, actual evidence, actual recommendations. When the COO walks back into the board meeting with a clear problem statement, a costed set of options, and a recommendation backed by data, the conversation changes completely. You're not debating whether to invest anymore. You're debating which option to choose and when to start.
I've seen this with a mid-market consulting firm that had been stuck for over a year. The partners couldn't agree on what to prioritise. The sprint identified that their 40+ published articles and frameworks were essentially invisible online - good thinking, zero distribution. It gave them a specific, costed plan to fix it. Within six months, inbound enquiries went from three a month to over thirteen. The sprint cost a fraction of what the firm had been quoted for a full strategy engagement, and it unlocked £1.2m in pipeline.
A diagnostic sprint doesn't replace a proper discovery phase. If you're embarking on something significant - a platform migration, a major redesign, a CRM overhaul - you'll still need thorough discovery work. There's a companion piece on why skipping discovery is so expensive that covers this in more detail.
But a sprint makes the discovery phase dramatically more effective. Instead of going into discovery with a vague brief and a list of things that "might" be in scope, you go in knowing exactly what the problem is, what the priorities are, and what you're trying to achieve. The sprint de-risks the discovery, and the discovery de-risks the delivery. Each step earns the right to take the next one.
And sometimes - genuinely - the sprint tells you that you don't need to do anything major at all. That the £300k programme someone was about to propose can actually be addressed with a £50k targeted fix. Or that the problem isn't your platform - it's your content. Or your process. Or the fact that three teams are duplicating effort because nobody ever mapped the workflow. Those findings save real money and real time, and they only surface when you look at a problem with enough focus and enough honesty.
Distinction offers diagnostic sprints. We've built our 14-day assessment model specifically around this approach, and a lot of the examples I've referenced here come from our own engagements. So yes, I have a commercial interest in you thinking this is a good idea.
But here's why I'm comfortable saying that out loud: we've also told firms not to engage us after a sprint. More than once, the honest answer has been "you don't need external help for this - here's what to do internally." A sprint only works if the outcome is genuinely independent of whether or not you hire the people who ran it. The moment it becomes a vehicle for selling a bigger programme, it loses the very thing that makes it valuable.
If you're weighing up a significant investment and want clarity before committing, a sprint might be the right first step. Not because I'm selling one, but because spending two weeks and a modest budget to make sure you're solving the right problem is almost always cheaper than spending six months discovering you weren't.
That COO I mentioned at the start? She ran the sprint. What we found wasn't glamorous. The partners weren't entirely wrong about the design, and IT wasn't entirely wrong about the platform - but neither of those was the actual problem. Thirty percent of inbound leads were being lost between the website form and the CRM. A routing issue. Boring, unglamorous, and completely fixable in a few weeks. Nobody had spotted it because everyone was too busy arguing about the bigger stuff.
She fixed that first. Everything that came after was built on solid ground.