There’s a lot that goes into planning a Design Sprint. From the scope of the chosen problem, to your team’s time constraints, to even the physical location—there are many variables that can affect the week’s outcome. The reality is that not everything will run perfectly, and there will always be things you’ll want to improve the next time around (like don’t reserve the warmest room in the city and lock people in for a week. Ok, cool!).
These things are nothing to sweat about it—you live and you learn. However, if there is one thing you should overthink (yep, we said overthink) before going into your sprint, it’s who will play the roles of Facilitator and Decider.
Who is the Facilitator?
The Facilitator is responsible for managing the sprint and moving things along. Good facilitators set a positive tone for the week, lay out expectations, manage group time, guide conversations, ease friction, and remain impartial when hearing others’ ideas.
Choose a facilitator who is confident leading meetings, yet comfortable playing a silent or unbiased role in group discussions. He or she should know how to tactfully curb tangents and not be afraid to tell people when it’s time to move on. On the flipside, you’ll also want your facilitator to know when an idea needs further exploration, even if it means adjusting the agenda. Make sure your facilitator is willing and committed to steering the team all 5 days.
Without a strong facilitator, you run the risk of hosting a 5-day, open-ended brainstorm that discovers lots of questions, but no solutions.
Deciding on the Decider
The Decider is the one designated with the authority to ultimately select what goes into the prototype. In other words, they have final say.
Ideally, the CEO would play the role of the Decider. However, for larger companies where that’s often not possible, you’ll want someone who has budget authority and access to higher level executives. The more passionate about the problem the Decider is, the greater chance you have bringing the solution to life.
Without the commitment from a Decider (and the right Decider), it’s likely all momentum gained from running a sprint will quickly flatline. You might feel like you accomplished 10x the amount of a normal week, or that your prototype is too beautiful for words, but unfortunately, that’s not enough for a successful sprint. The work isn’t over on Friday; rather, a design sprint is meant to kick-start the development of the product. That’s why you need someone in the room who has both the budget authority and passion to see the idea to its fruition.
Once you’ve selected who your Facilitator and Decider will be, here are some tips to help make the most of the week, while being considerate of everyone’s time.
Give your team time to do their day job - During the sprint, don’t start days until after 9am. That way everyone will have time to tend to their email before the meeting, allowing them to be more focused the rest of day.
The Decider doesn’t have to be there all 5 days - If you’re trying to run a design sprint in a large company, it’s likely the Decider will have a great deal of trouble clearing their schedule for an entire week. That’s ok!
A delegated decision-maker should be in the room at all times to help move things along, but the one ultimately deciding what will go into the prototype doesn’t have to be. Bring them in when they can—maybe they can make a cameo appearance on Monday, listen to the presentation of sketch ideas on Wednesday, or if nothing else, simply make the decision after the final critique has been made.
(Note: If the Decider can’t even make a cameo appearance, that may be a sign you need to find a different problem. Try to talk to the Decider to determine a problem that he/she is excited to tackle.)
Give the Facilitator and Decider time to build rapport - It’s important that the Facilitator and Decider are on the same team. That’s not to say they agree on everything, but that their goals are aligned, they trust the expertise of the other, and they’re working together to push progress. The week will bear little fruit if one is undermining the other.
You don’t have to go through product development alone. Bring Differential along to help conduct a sprint around your team’s challenges.