In the previous articles in this series we first provided you with a foundation of what design sprints are and why they’re invaluable to companies trying to solve important problems. In the second article, we shared a behind-the-scenes look at a design sprint we recently ran for an early stage startup.
In this article we’re going to focus on two related topics that will help you prepare your sprint team:
- Generating support from your company to conduct a sprint.
- Putting the right sprint team together to execute.
Engage Your Company
Once you’ve decided that a design sprint will benefit your company, your next step is getting others around you committed. These people may include co-founders, board members, designers, engineers, marketers. They may be peers, managers or junior members.
Depending on your team’s progress-to-date + outside pressure (e.g. board, investors, customers), getting everyone to agree to a design sprint may be the easiest decision you’ve made since opening your doors. Alternatively, it may require a bit of finessing, in which case we’ve laid out 3 options for rallying everyone together.
Good news: We’ve already tested and validated each of these options time and again. We’ve also experimented with others, but none had as much success.
Option 1: Distribute copies of the Sprint book + pitch it
Ask the team to read the book. In the meantime, break out Keynote, organize your compelling pitch about the benefits of a design sprint versus what you’ve failed to deliver on historically (and likely for a lot more time & money), call a meeting and do your best Jordan Belfort impersonation.
Note: For the ultra lazies, you can prompt your team to skip the book and review this Sprint Checklist. Or, they can just read through this series.
- If they share your passion, they should be at least mildly stoked to give it a shot.
- This is about as low risk / low cost as it gets.
- People are not to be trusted + people are lazy = people may not read the book, nor take you seriously.
- Your pitch bombs, people throw stuff at you and you’re never asked to participate in another sales call.
Option 2: Run a 1-day sprint
With this approach you’ll run a hyper-condensed version of the design sprint in 1 business day.
If we pretend the typical business day is a true 8 hours, you’ll leave 1 hour first thing in the morning for the team to take care of their administrative duties + 1 hour for lunch. The other 6 hours are to be used to work through the sprint.
- This highly collaborative environment is contagious. Expect for it to boost confidence and team dynamics.
- 6 hours should be easy to sell.
- The abbreviated schedule could back-fire if not laser focused. Consider bringing in some outside help (see option 3).
Option 3: Get some outside help
The other options assume you have the team & chops to create your own momentum. However, some of you reading this may be a company of 1. Some of you may simply not be up to the task nor have the time to rouse the team. In these instances, you might consider bringing in some outsiders that have the experience required to get others excited & engaged.
- Outsiders with vetted experience tend to carry more influence.
- Pros who have run many sprints will be able to better speak to the benefits (and challenges) — certainly they’ll have more examples to share.
- Some companies prefer to keep everything locked down and in-house.
- Options will be slim for finding good, experienced, trustworthy vendors.
In the end, the goal is for you to get your existing team on board with a running a 5-day design sprint. Consider your team dynamics, roadmap and pressures so you can get them over that hump with as little friction as possible. And if you discover a better option, please let us know in the comments.
Your Sprint Team
Once your company is enacted to run a sprint, the next order of business is selecting and rallying your sprint team. You’ll want to assemble a balanced team that can 100% commit to the process. But you’ll also need a good mix of personalities, skills and disciplines.
Google Ventures recommends a team no larger than 7. We agree. Otherwise, you go from managing a sprint to managing an unruly mob.
Below are the 5 roles we’ve found to be absolutely necessary in running a quality sprint.
Product Chief (the Shot Caller)
This is the person with the most sway (and largest voting stickers). Though it’s often the case, this won’t always be the boss / owner / VP of Product. In some cases we’ve seen heads of customer service, lead engineers and sales execs charter this role. What’s most important is that this person has the most tangible exposure to the problem you’re trying to solve.
If your product chief doesn’t have immersive, daily interaction with your customers, be sure to recruit this role onto your sprint team. They’ll often be the ones to cut through the sales & marketing hype you’ve tried ad nauseam, while pinpointing the precise issues your customers are challenged by.
In the first article we talked about creating Goldilocks-quality prototypes. The importance of having a designer involved in the sprint process is not only because they’ll have the expertise to make things look just right, but they’ll be able to move quickly through sketching and related concepts.
While you don’t need to be a technology company to run a sprint, the majority of prototypes you’ll be testing will require some kind of engineering talent. The engineer on the team may produce software, hardware or some other real world product prototype.
The words used to describe and market your product as well as the words within the product itself are just as important as the form and function of your prototype. Make sure someone is present that’s blessed with the ability to effectively wordsmith.
There are a lot of moving parts to a design sprint. Don’t forget that you have to book conference rooms, organize lunch (and maybe dinner), capture notes, set timers, interview customers and constantly keep the group on-task. You’ll want to make sure 1 person on the team is designated as the Facilitator, whose primary role is ensuring the team keeps up with the aggressive pace of a 5-day sprint.
Design sprints will require a true commitment from your team. Once they’re in, you’ll want to mobilize a team that’s willing to clear their schedules and charge through the sprint. And hopefully you now have the structure to accomplish those 2 objectives.
In the next and final article in this series, we’ll provide guidance on the biggest challenges / questions / pushback we’ve faced while leading design sprints.