What is an innovation sprint (and when should your team run one)?
A sprint applies time pressure to a business challenge. Done right, it moves faster than months of committee deliberation.

A sprint is a time-boxed creative process. An innovation sprint applies that logic to a business challenge — a concentrated period of structured thinking, building, and testing designed to move faster than normal work allows.
How it works
- Day 1: understand the challenge, map the landscape, identify the most important question to answer.
- Day 2: generate solutions, prototype the most promising ones, test them against real criteria or real users.
By the end, you have something you didn't have before: a direction, a prototype, a decision. Not a plan to make a plan.
Where it came from
The format was popularised by Google Ventures' Design Sprint methodology, developed to help startups validate ideas quickly. The logic: five days of focused work beats five months of committee deliberation. Corporate teams have adapted it — often compressing into one or two days — with the same core principle: decide faster by building and testing, not by theorising.
When it's the right tool
- You have a specific challenge or question (not a general aspiration)
- The right people can be in the room for a full day or two
- There's genuine uncertainty about the right solution
- Someone has the authority to act on the output
When it's the wrong tool
Don't run an innovation sprint when the answer is already known and what's needed is execution. If leadership has already decided the direction, a sprint won't change that — and pretending otherwise wastes everyone's time.
What makes it work
The facilitator. The brief. The composition of the team. Get these right and a sprint reliably produces useful output. Get them wrong and it's an expensive afternoon of Post-its.
