“A Design sprint is a time-constrained, five-phase process that uses design thinking to reduce the risk when bringing a new product, service or a feature to the market.”
If you’re thinking about doing your first sprint ever, follow this article when talking with clients, developers, and even designers.
Use the accompanying documents, and practice how to introduce, frame, and pitch Design Sprints — both to internal team members and to prospect new clients.
Make the case to Clients
- “Sprints reduce waste — time and money.”
It may seem like a bigger investment going into the project, but looking at the total cost of bringing the MVP to market (start to end, strategy to post publish), you will, wait for it — save money.
- “Everyone understands (and follows) business goals from project start.”
Maybe obvious, but it’s really important for everyone in the project (and there are usually a bunch of stakeholders) to understand why we’re building this product, who is it for, and how success will be measured.
- “Sprints help build products people will actually use.”
Business goals are first and foremost, but without end users and real customers, the product is bound to fail. Sprints allow the team to define the customer, plot out a user journey, and validate the concepts with real users on the final day of the Sprint.
- “We bring everyone working on the project together.”
A lot of times, this is success enough. Big companies have a large number of projects with team members across multiple locations (and also new members that never met before). This brings everyone to the same room for five days — and that helps with the project going forward.
- “Jobs said Sprints are much better than focus groups.”
On the last day of the Sprint, devoted to user testing, we show the built prototypes to users and get actual feedback. Much more rewarding and valuable than any kind of focus group.
“It’s really hard to design products by focus groups. A lot of times, people don’t know what they want until you show it to them.” — Steve Jobs
Make the case to Developers
- “You will be involved in building the product from day 1.”
A developer is one of the most important stakeholders to be present this week. The workshop needs someone that will keep the group honest in terms of existing and future engineering capabilities. Participating, you’ll actually help in steering the product the right way.
- “Sprints will allow you to switch gears for a week.”
This will come as a positive change. For one week, there will be less coding and code-reviewing, and more product definition and development. The following week, it’s going to be much easier to jump into the routine.
- “This is the counterpart to agile in development.”
You already do (and know everything about) sprints. The Design Sprints is the product design equivalent to development sprints.
- “Preparation (think API spec) will go much smoother.”
When everyone sketches and presents solutions, you’ll validate in real time what’s feasible and come out of the workshop armed with next steps — preparing that API way before the actual development starts.
- “There will be fewer changes when development actually starts.”
There will be fewer change requests mid development. Solutions will be explored, bad ones flushed out, designed, prototyped and tested. Once you go into development it will be much more streamlined.
Make the case to Designers
- “You’ll crunch weeks or even months into days.”
What could have been a project kickoff that lasted for weeks of back and forth with a bunch of meetings and failed Skype calls is suddenly crunched into days. Decisions are made on the spot, assumptions tested and going into the project that follows is much easier.
- “You will understand why you’re actually designing this.”
Often times, internal communication is not at its best. For instance, not everyone is included in every meeting, project briefs are missing relevant information and things get misplaced. If a project lands on your table, you’re probably going to miss some context. If you’re part of a Sprint, this will not be an issue.
- “You will actually get a seat at the table.”
A popular phrase in the Design community, about designers getting a seat at the table. When we’re discussing the visual aspect of a product, it’s mostly not going to happen. But when we’re discussing the actual product, customers and most importantly — business goals — you’ll have everyone’s ear.
- “You’ll hear real users giving feedback.”
The last day of the Sprint is the most rewarding and painful at the same time. You’ll actually watch real people interacting with your one day design. Don’t be emotionally connected, just listen. You’ll start creating much better designs when you do.
- “Sprints will force you to brush on your skills.”
Let’s think about this: Building prototypes in one day? Every time for a different client, on a different platform? Using different tools? Yes — this will help you brush on your organizational, design, prototyping skills as well as thinking, structuring thoughts and ideas and presenting them clearly to the rest of the team.
You’re now fully equipped to convey the value of Design Sprints to a broader audience. If you’ve encountered convincing arguments that are not included here — let me know and I’ll update the list.
This article was originally published on Tin’s Medium page.