When Google's golden child grew up
In 2016, Google Ventures published Sprint, pitching a five-day process for solving big problems. The design world ate it up. Finally, a recipe. Companies adopted sprints religiously. Consultants made fortunes. Post-it makers had a great year.
Nine years later, the hangover has set in. The teams that sprinted their way through 2020 are quietly admitting what most designers always suspected: speed without strategy is just expensive chaos. The design sprint, once treated as a fix-all, turns out to work better as an occasional tool than a default mode.
The seductive promise of speed
Sprints promised to compress months into days. Monday: understand the problem. Friday: validated prototype. What's not to love? In a culture obsessed with acceleration, the format felt like a cheat code for innovation.
The appeal went beyond speed. Sprints promised democratic design. Everyone's voice heard, ideas flowing, decisions made together. They broke down silos, energised teams, created momentum. When they worked, they felt incredible. The problem? They often didn't, and most companies refused to admit it.
The hidden casualties of compression
What sprints compress isn't time. It's thinking. Real innovation needs marination. Ideas that connect unconsciously, problems that resolve in the shower, references that surface days later. Sprints kill those gaps. They force linear progression through phases that naturally overlap and loop.
Take the Monday "understand" phase. A few hours to grasp problems that deserve weeks. Teams default to whoever speaks loudest or has the most convincing story. Genuine user insight, the kind you only get from patient observation, gets sacrificed to the timeline.
Friday's prototype suffers the same way. "Validated" usually means "nobody hated it on the spot". Real validation requires a range of users, multiple contexts, and time to watch what they actually do versus what they say. Sprints test hunches, not hypotheses.
The facilitation industrial complex
The sprint boom created a cottage industry. Every agency offered sprint services. Every consultant became a sprint master. Process became more important than outcome.
That industrialisation diluted quality while inflating expectations. Original Google Ventures sprints involved senior designers and product specialists. Commercial sprints often feature junior facilitators reading from a script. The difference between a great sprint and a five-day meeting is expertise, and you can't download that from a template.
When sprints actually work
Sprints aren't useless. They're just usually misapplied. They shine in specific cases: when the problem is clearly defined but the solution isn't, when teams are stuck and need momentum, when stakeholders need to see something instead of hearing a deck, when the deadline is real rather than artificial.
The startup world figured this out the hard way. Sprints work for narrow product decisions. They don't replace strategy. They don't substitute for research. And they're not a substitute for hiring people who actually know the domain.
The slower path forward
The teams shipping the best work today aren't sprinting through every problem. They're matching pace to need. Some bets get a week. Others get a quarter. The skill is knowing which one is in front of you.
Speed is still a competitive advantage. But speed without depth is just being early to a wrong answer. The companies that win in the long run are the ones that learn when to compress and when to slow down. Sometimes the fastest path is the one that takes its time.
