See into the future
Imagine you had the ability to look into the future… to glance over months and months of work, to witness the diminishing of the budget you laboured to secure, the hopes and dreams of the business resting on your shoulders…
At the end of all of this, there you sit with a group of users, observing them as they try out the fruits of this effort. Exciting? Nerve-wracking? Very much so.
Light-speed problem solving
What if the users don’t like what the team has produced? After all this time and effort, can you really afford to go back and make changes that will have significant impact? How much more time, money and people-power are you going to throw at it the project to salvage a last-minute pivot?
What if you could get here in one week, instead of months and months?
This is the beauty of the Design Sprint.
What is a Design Sprint?
The basic approach here is side-stepping all the debating, politics, lead times, and waffling that often accompany the product development process. The sprint uses high impact activities to encourage teams to pool their resources and knowledge and tackle daunting problems quickly.
The process is comprised of five steps; exploring the problems, creating solutions, deciding on the one you want to test, creating a prototype and testing with users.
Each step comes with its own set of high-impact activities, which on their own would be a boon to anyone facilitating discussions of any kind, but together form a powerful tool for, as they say, “seeing into the future”.
How does a Design Sprint work?
Give us a team of your people for two days, and we’ll do the rest. That’s it.
We guide your team for two days to explore solutions to your most pressing issues. We create a prototype and test it with users. And by the end of it, you'll get to see if you have a workable solution!
We also want to meet your team before the two-day sprint starts, just so we don’t lose any time getting buy-in or explaining the process. We will feedback to the team after we have collated relevant information, typically in the next week.
Who gets involved?
An ideal team is cross-functional, made of people with hands-on experience of the problem under scrutiny.
Board-level strategic thinkers tend not to have a good grip on what will work for your business at a functional level. This range of perspectives is what we rely on to form a balanced solution that satisfies everyone in the room. It is this rich variety of perspectives that often powers the most elegant solutions.
When do you use
a design sprint?
You are about pitch to someone to unlock budget or funding - you can show them the whole thing worked out and tested.
Recurring problems with your existing product are taking too long to solve - it allows your team to focus on the solution.
Alignment issues in your organisation are taking too long to work out - it brings together disconnected ideas and conversations.
You are taking a big risk or making a big ‘bet’ - you get quick feedback to reduce uncertainty.
You need to validate a new business model or idea.