It started with one Design Sprint: How StepStone built a self-sustaining innovation practice

There's no single right entry point

Organizations that want to build internal Design Sprint capability don't all start the same way — and they shouldn't.

Some go straight to training. The World Bank brought multiple IT teams through Problem Framing and Design Sprint Training without a facilitated sprint as a prerequisite. The mandate was clear, the teams were ready, and training first was the right call for their context.

Others start with a facilitated sprint. Not because training first is wrong, but because their specific situation calls for organizational evidence before the training investment is made. Sometimes leadership needs to see the method work on a real challenge before approving a capability program. Sometimes the teams themselves need that firsthand experience to understand what they're being trained toward.

StepStone was in the second camp. Before investing in training internal facilitators, they ran a sprint first — and that choice shaped what followed.

How StepStone entered the process

StepStone is one of Europe's leading digital employment platforms. Their product teams operate in a fast-moving market where getting a direction wrong isn't an abstract risk — it has real consequences for development timelines, user experience, and competitive positioning.

When they decided to explore Design Sprints as a methodology for tackling complex product challenges, they started with a live sprint, facilitated end-to-end by Design Sprint Academy on a real challenge their team was actively navigating.

A facilitated sprint with a real challenge does something a training simulation can't: it produces an actual output — a validated prototype, a clearer direction, a set of tested assumptions — that leadership can evaluate against the investment made. The question "did this work?" gets a concrete answer, not a theoretical one.

For StepStone, the four-day sprint produced a validated prototype and strategic clarity on the challenge they'd brought into the room. Leadership didn't just hear that Design Sprints work. They watched one work on something that mattered to them.

That direct experience shaped the conversation that followed. With the method demonstrated on a real internal problem, the path to a capability-building investment was clear.

Building the capability: what the training actually covered

StepStone moved into a structured five-day training program for a handpicked core team. The program covered three distinct modules in sequence, and the sequence was intentional.

Module 1: Problem Framing Training

The program opened with Problem Framing — a deliberate choice that reflects a principle the facilitated sprint had already reinforced: the quality of a Design Sprint is determined by the quality of the problem that enters it.

Problem Framing training teaches teams to diagnose the right challenge before any solution work begins. For StepStone's product teams, this meant learning to slow down at the point where the instinct is to accelerate — to question whether the problem being brought to a sprint is actually the problem worth solving, rather than the symptom closest to the surface.

The output is practical: a Problem Statement that is specific, stakeholder-agreed, and testable. That statement becomes the foundation the sprint is built on. Without it, even technically well-run sprints can produce solutions to the wrong challenge.

Module 2: Design Sprint Training

With the problem framing foundation in place, the program moved into an accelerated version of the full Design Sprint — every phase, compressed into two days, using real challenges from within StepStone rather than generic training scenarios.

Participants moved through the complete arc: mapping the challenge, generating ideas individually before sharing them with the group, making decisions as a team, building a prototype, and testing it. The emphasis was on doing rather than observing. Understanding a method theoretically is different from having run it yourself, and the training was designed around that distinction.

For a digital product team, several Design Sprint principles landed with particular force. The "Together Alone" structure — individual idea generation before group discussion — directly addressed the tendency for senior voices to shape early thinking before quieter participants have had space to contribute. The time constraints changed the group's relationship to decision-making: not every decision needed to be perfect, but every decision needed to be made.

Module 3: Advanced Facilitation Training

The third module is where most capability-building programs stop short. Training teams to understand a method is one investment. Training them to facilitate it — to manage group dynamics, hold the time structure under pressure, handle the moments when a room goes sideways — is a different and more demanding one.

StepStone's facilitators didn't just learn to run the process. They practiced leading it, in live simulations where the challenges of real facilitation were present and had to be managed: the resistant participant, the executive who wants to skip steps, the team that can't converge.

By the end of the training, participants weren't just certified in a method. They were prepared to facilitate it in front of opinionated, intelligent colleagues who would have no patience for a facilitator who was figuring it out in real time.

Equipping the team to actually deliver

Training that isn't backed by practical tools creates a specific failure mode: people who understood the method in the training room but face a logistical gap when they try to apply it independently. Setting up a sprint from scratch — building the digital boards, preparing the materials, managing the facilitation scripts — is a significant overhead on top of already demanding schedules.

To close that gap, StepStone's facilitators were equipped with facilitation kits covering both in-person and remote sprint formats: ready-to-use digital boards, facilitation scripts, role cards, planning checklists, and stakeholder preparation materials.

The practical value of this is easy to underestimate. When the administrative overhead of running a sprint is low, facilitators spend their energy on the facilitation itself. When it's high, the first few sessions are partly about logistics rather than the method. The kits removed that friction and let the team focus on what the training had prepared them for.

Coaching through the first real sessions

The fourth phase is the one most organizations skip entirely: structured coaching support through the first sprints after training.

The logic behind skipping it is understandable. Training has been delivered. The team has the tools. The expectation is that people apply what they've learned and improve through practice. The problem is that practice without feedback is slow. The mistakes that compound — the facilitation habits that work in a training room but fall apart with a real team, the moments where a decision should be pushed but isn't — can take months to surface and correct without someone watching.

StepStone's facilitators ran their first sprints with access to regular coaching calls. Sprint plans were reviewed before sessions. Live feedback was given afterward. Specific challenges — a difficult room, a sprint that lost momentum mid-way, a prototype that didn't test cleanly — were worked through with someone who had seen those situations before.

The result was that the team's capability compounded faster than it would have through unsupported practice. Each sprint was a learning event, not just an application of what was already known.

Within weeks of completing the program, StepStone's trained facilitators were running sprints independently across teams — solving product challenges, accelerating alignment, and validating directions before committing development resources.

What made this program work

The StepStone case isn't a story about a great training program.

It's a story about a sequence of decisions that turned a good program into an embedded practice.

The entry point — a facilitated sprint before the training investment — gave leadership direct experience of the method on a real problem. That's specific to StepStone's context. Other organizations reach the same training investment from a different starting point, and that's equally valid. What mattered here was that by the time the training began, there was no internal debate about whether the method was worth learning.

Training that covered facilitation, not just methodology, produced people who could lead sessions rather than just understand them. The Advanced Facilitation module is the step most organizations cut when budgets tighten. StepStone's experience suggests it's the step that determines whether trained facilitators actually use what they've learned.

Post-training coaching closed the gap between knowledge and confidence. And equipping the team with practical tools removed the operational friction that causes even well-trained facilitators to default back to familiar formats.

The combination of these conditions produced something specific: a self-sustaining practice, running independently, led by internal talent, without ongoing external support.

What this means if you're thinking about building internal capability

The question worth asking isn't "should we start with a facilitated sprint or go straight to training?" It's "what does our organization need in order to commit to this capability — and what's the fastest path to that commitment?"

For some organizations, training first is the right answer. The mandate is clear, the teams are ready, and a facilitated sprint would be an unnecessary intermediate step. For others, seeing the method work on a real internal challenge first is what makes the training investment possible.

What holds across both paths: the training itself needs to cover the full arc. Understanding the method is the starting point. Developing the facilitation skills to lead it in front of challenging rooms is what actually determines whether trained people go on to use it. And the period after training — when facilitators run their first real sessions without the safety net of a trainer present — is where the capability either beds in or quietly retreats. Coaching during that window closes a gap that practice alone doesn't.

StepStone built all of those conditions deliberately, in a sequence that made sense for where they were. That's why the practice is self-sustaining.