Sprints: A Faster, More Focused Way to Tackle Difficult Business Challenges
I have been in plenty of leadership meetings where the same important challenge keeps returning.
Everyone understands that it needs addressing. There is no shortage of discussion, expertise or good intent. Documents are circulated, individual workstreams begin and actions are agreed. Yet several weeks later, the underlying decision still feels unresolved.
I know how easily this happens.
The most difficult business challenges rarely sit neatly within one function. Marketing sees one part of the picture. Operations sees another. Technology introduces dependencies. Finance needs confidence in the commercial case. External partners bring their own expertise, priorities and recommendations.
Each perspective may be valid, but nobody holds the complete picture.
Day-to-day pressures make sustained attention difficult too. Leadership meetings are busy, diaries are fragmented and strategic questions are repeatedly squeezed between more immediate demands.
A well-designed sprint can create the focus, structure and shared understanding needed to make progress.
What is a sprint?
A sprint is a structured, time-bound process that brings the right people together to work on a clearly defined challenge.
Jake Knapp’s book Sprint popularised a five-day approach that moves from understanding a problem through to generating ideas, making decisions, creating a prototype and testing it.
The exact format can vary depending on the organisation and the challenge. Most sprints run over several consecutive days. Others combine focused workshops, research and development work across a slightly longer period.
The useful disciplines remain consistent:
Define the question clearly
Bring together the people who understand different parts of it
Create space for evidence, challenge and exploration
Make choices visible
Develop something tangible
Agree what happens next
This structure can be applied to product development, customer experience, digital strategy, technology decisions, service propositions, operating models and wider commercial challenges.
Why leadership teams get stuck
Complex decisions rarely become stuck because people lack ideas. The difficulty usually comes from the number of competing considerations involved.
A leadership team may be trying to improve a customer journey while working around legacy technology, supplier contracts, operational limitations, commercial targets and different stakeholder priorities.
Each conversation uncovers another dependency. New ideas are added before earlier questions have been resolved. People leave meetings with different interpretations of what has been agreed.
Over time, the challenge grows broader and harder to contain.
A sprint creates a boundary around the work. It establishes the specific question being considered, the people who need to contribute and the decision or output required at the end.
That boundary is one of its greatest strengths.
Creating a shared view of the challenge
Leadership teams frequently begin with different understandings of the same issue.
One person may see a technology problem. Another sees a customer experience problem. Someone else believes the priority is commercial performance or internal capability. A sprint allows these perspectives to be brought together and examined.
This process often reveals that the original question needs refining. A brief focused on selecting a new platform may uncover a more fundamental issue around customer data, internal ownership or the way services are structured.
Reaching a shared understanding early prevents teams from investing time and money in solving the wrong part of the problem.
It also creates a stronger foundation for the decisions that follow. People can see the evidence, assumptions and constraints behind the chosen direction.
Giving an important issue proper attention
Strategic thinking needs concentration. That is difficult to achieve through a series of disconnected meetings, particularly when several weeks pass between each discussion. Context has to be rebuilt, actions lose momentum and changes elsewhere in the business introduce further complications. A sprint protects time around one important challenge.
Participants have the opportunity to explore the issue in enough depth, while the structure prevents the conversation from expanding indefinitely. Questions are recorded, choices are prioritised and the work continues towards a defined outcome.
This concentrated attention can move an organisation forward faster while maintaining the quality of the thinking.
Improving the quality of decisions
Many business decisions are shaped by whoever speaks first, presents the most confidently or holds the greatest seniority.
A structured sprint gives people different ways to contribute. Individual thinking can happen before group discussion. Options can be assessed against agreed criteria. Operational knowledge and specialist expertise can be considered alongside leadership priorities.
This creates a more balanced process. It also makes trade-offs clearer.
Most meaningful decisions involve some form of compromise. A new approach may improve the customer experience while creating additional operational demands. A faster route may carry more technical risk. A broader proposition may be attractive commercially but harder to communicate.
A sprint provides the space to examine these choices directly, rather than allowing them to remain hidden inside general agreement.
Turning discussion into something tangible
Leadership discussions can remain conceptual for too long.
People may agree that a customer journey needs improving, a proposition needs simplifying or a digital ecosystem needs modernising. The difficulty begins when those broad intentions have to become something people can review and act on.
A sprint works towards a tangible output.
Depending on the challenge, that could include:
A prototype
A prioritised roadmap
A future customer journey
A service or proposition model
A set of strategic options
A decision framework
An outline operating model
A clear list of priorities, owners and dependencies
Tangible work improves the conversation. Teams can react to something specific, identify weaknesses and refine the direction before committing to full delivery.
Building shared ownership
Execution becomes harder when a strategy arrives as a finished answer.
People may understand the recommendation without fully understanding the thinking behind it. Concerns emerge late, important operational details have been missed and teams feel little ownership over the outcome.
A sprint involves the people who will influence, support or deliver the eventual direction.
Participation alone does not guarantee agreement, and complete consensus is rarely a sensible objective. It does create greater understanding of how the decision was reached and which alternatives were considered.
This helps leaders build commitment around the chosen route and reduces the risk of the same debate reopening during delivery.
Learning before making a larger commitment
A sprint can also reduce risk. Creating an early prototype, model or roadmap allows assumptions to be challenged while the cost of changing direction remains relatively low.
Questions that might otherwise emerge several months into delivery can be identified much earlier:
Does the proposed experience make sense to customers?
Can the operational team support it?
Is the required data available?
Are the technology dependencies understood?
Does the commercial case remain credible?
Which capabilities are missing?
What needs to be validated with suppliers?
A sprint will not remove uncertainty. It can identify where that uncertainty sits and help leaders decide how to address it.
Lessons from recent work
I recently helped lead an innovation sprint focused on a complex operational challenge. The work involved people with different responsibilities, expertise and perspectives. The process moved from understanding the current reality through to exploring possible approaches, selecting a direction, developing a prototype and testing the thinking.
The final concept was valuable, but the wider benefit came from how quickly the group developed a shared view of the challenge. Ideas became visible, assumptions could be questioned and the team had a clear basis for deciding what should happen next.
Other recent consultancy engagements have used a longer format, although many of the same principles have proved useful.
In one case, the challenge involved clarifying several propositions, audiences and commercial priorities across a growing organisation. In another, a leadership team needed to make sense of a complicated digital ecosystem involving customer journeys, internal systems, data, suppliers and future investment decisions.
Both required structured discovery, clear framing and the involvement of people who held different parts of the picture. Progress accelerated once the evidence was brought together and the key decisions were made explicit.
When a sprint is particularly useful
A sprint is worth considering when:
The challenge is strategically or commercially important
Several teams, stakeholders or partners are involved
The organisation has more than one credible route available
Progress has slowed because discussions keep expanding
A decision is needed before significant investment can begin
The cost of choosing the wrong direction is high
Leadership needs a tangible recommendation or plan within a defined period
The organisation also needs someone with the authority to make or sponsor the necessary decisions.
Without leadership involvement, a sprint can produce interesting ideas that have nowhere to go. The strongest sprints connect participation with genuine decision-making authority.
What a good sprint requires
The quality of the outcome depends heavily on how the sprint is designed.
A clear challenge
The question must be specific enough to guide the work while leaving enough room to explore possible answers.
The right participants
The group should include people with relevant knowledge, authority and responsibility. Larger groups do not automatically create better results.
Good preparation
Existing evidence, customer insight, performance data, constraints and previous work should be gathered before the main sessions.
Independent facilitation
A facilitator protects the process, ensures different voices are heard and keeps the group moving towards the required outcome.
A clear decision process
Participants need to understand who will decide, how options will be assessed and what the sprint is expected to produce.
Follow-through
The final output should connect to owners, priorities, validation work and the wider delivery plan.
A practical tool for leadership teams
Organisations have access to more data, expertise, technology and possible routes forward than ever before. That abundance can make decisions harder, particularly when the issue crosses functional boundaries.
Sprints provide a disciplined way to bring the relevant knowledge together, focus attention and create movement around an important question.
At Saurce, I see particular value in applying sprint principles to digital, marketing and commercial challenges. These might include defining a growth strategy, improving a customer journey, reviewing a technology ecosystem, clarifying a proposition or agreeing where investment should be prioritised.
The format should always be shaped around the problem and the organisation involved.
Done well, a sprint helps a leadership team reach a clearer view of the challenge, make better-informed choices and leave with a practical route forward.
