A COO at a 250-person professional services firm had just left the third board meeting in a row where partners agreed that something needed to happen to the website and client portal. Marketing blamed the CMS, partners disliked the design and IT expected a replacement. Nobody could define the shared problem well enough to release a budget.
The immediate need was a decision, rather than a six-month strategy programme.
That is the setting in which a diagnostic sprint earns its keep: several plausible explanations, a consequential investment ahead and enough accessible evidence to resolve a focused question quickly.
A decision tool, with a deliberate boundary
Large assessments disappoint when they examine an entire digital estate and produce recommendations that need another engagement before anyone can act. A diagnostic sprint takes the opposite approach. It begins with a specific decision and limits the investigation to evidence that could change it.
At Distinction, a sprint typically runs for about two weeks. The timetable is a working model, rather than a promise suitable for every problem. Scope, system access, stakeholder availability and data quality determine what can be concluded responsibly.
The intended outputs are:
- A precise problem statement and the evidence behind it
- Important uncertainties and limitations
- Findings ordered by commercial relevance
- Options assessed for likely effect, feasibility, cost and risk
- A recommended first move with indicative effort
- Measures that can test whether the diagnosis proves correct
This is different from a general audit and narrower than delivery discovery. A sprint may show that detailed discovery is justified; the article on the cost of skipping discovery explains that next stage. It may equally identify a contained fix or show that the proposed programme should stop.
Four situations where a sprint can change the outcome
A major commitment is approaching. A platform migration, redesign or CRM programme has reached business-case stage, and the sponsor wants to test whether the brief addresses the commercial problem. The sprint examines the chain from observed symptom to proposed investment.
A project has stalled. Scope has shifted, ownership has weakened or supplier relationships have deteriorated. The useful question becomes whether to restart, restructure or close the work. A short independent investigation can separate sunk-cost pressure from what remains valuable.
Departments have competing explanations. Marketing, technology, operations and partners all see a different cause. The sprint creates a common evidence base. Agreement is useful, although the real objective is a decision that acknowledges where evidence remains mixed.
The symptom is visible and the cause is unclear. Client satisfaction, pipeline or engagement has changed without an obvious reason. The team works backwards across journeys, content, process, data and technology instead of assigning the issue to the most visible system.
A sprint is a poor fit when the question is organisation-wide, essential data will remain inaccessible, or the answer depends on sustained behavioural research. Calling a broad discovery a sprint merely compresses the label.
What happens during the two weeks
The opening days establish the decision, constraints and competing hypotheses. Interviews are useful because disagreement shows where assumptions differ. One Distinction engagement began with Marketing describing a content shortage while the CTO described an excess of unfindable content. Both accounts contained part of the problem. Surfacing the tension changed the brief.
Interviews are then tested against what exists: analytics, user journeys, platform behaviour, content, integration points and workflow evidence relevant to the question. The team should record missing or unreliable evidence rather than smoothing over it.
During synthesis, observations become findings only when they affect the decision. The team distinguishes:
- What is broken
- What works and is underused
- What is assumed
- What needs a further test
- What should happen first
- What can be deferred or stopped
The final session is a working decision meeting. Leaders see the evidence, challenge the interpretation and agree ownership of the next action. A long presentation is less important than a traceable route from evidence to recommendation.
The value is confidence with limits
Many mid-market firms have digital scar tissue: a website project that exceeded budget, a CRM that users avoided or a promised transformation that did not change the client experience. The next proposal meets scepticism because leaders remember the last one.
A sprint can restore momentum by producing a bounded result quickly. Its credibility depends on limits. The team must be able to say which conclusion is strong, which is provisional and what would change the recommendation.
The source article included two impressive case accounts: one firm allegedly avoided £320,000 of spend and improved conversion by 22%; another reportedly created £1.2 million in pipeline after fixing distribution. Those claims may reflect real engagements, yet the article contains no evidence a reader can inspect. They should be verified against project records and client permissions before publication. Removing the numbers does not remove the lessons.
In the first case, a proposed website and CRM rebuild contained a large amount of unnecessary scope. The more immediate problem sat in the handoff from enquiry to onboarding. In the second, valuable published thinking was difficult to discover, so distribution took priority over a broad strategy programme. Both examples show the same discipline: fix the constraint revealed by evidence instead of funding the largest available brief.
How a sprint changes discovery
Significant delivery still requires discovery. The sprint improves its starting position by replacing a vague brief with a tested problem, priorities and desired outcomes. Discovery can then examine users, requirements, architecture, content, operations and delivery risk in the depth the programme deserves.
The sequence matters:
- Diagnose the consequential uncertainty.
- Define the response in proportion to the finding.
- Deliver and measure whether the diagnosis holds.
Each stage earns the next. Sometimes diagnosis shows that the organisation can act internally or that a small fix is enough. That is a successful outcome, even when it produces no larger Distinction engagement.
The routing fault beneath the platform debate
The COO's firm ran the sprint. Partners had legitimate concerns about design and IT had legitimate concerns about the platform. Neither issue explained the immediate commercial loss. The investigation found inbound leads disappearing between the website form and the CRM because of a routing fault.
That finding did not settle every question about the wider digital estate. It gave the firm a specific first action and stopped a broad platform argument from delaying it.
The source says 30% of leads were affected and that the repair took a few weeks. Those details should be confirmed internally. The durable insight is the order of work: repair the broken handoff, measure the result and use that evidence in the larger platform decision.
Distinction sells diagnostic sprints, so the commercial interest should be explicit. The deliverable must stand on its own, and the recommendation must remain valid if the client chooses another partner or no external support for the next step.
