Many companies are now becoming software driven and they need to deliver genuine value, build useable, intuitive and desirable interfaces so that people can operate them quickly and effectively with their mobile and other devices. This is harder than it seems and takes a great deal of time, skill and talent to achieve.
Design sprints bring people of various backgrounds together to collaboratively find solutions within a highly complex system of business, technical, and human context to ultimately result in products and services that people need and desire and are happy to make part of their lives.
How to succeed in delivering a design sprint and wherein lies the value of design sprints to begin with?
I recently had the chance to skim through a few excellent books on this topic. In “Sprint – How to Solve Big Problems and Test New Ideas in Just Five Days”, Jake Knapp, John Zeratsky and Braden Kowitz from Google Ventures explain and outline the Google 5-day Sprint method.
It all begins by setting the stage – outlining the big issue you wish to solve in a week, getting your sprint team together and scheduling a sprint room for the five days.
As for the sprint team or the group of people participating, no more than seven people, with the facilitator not included, is recommended for the sprint. Based on my own experience, this is the ideal group size.
Who then, is needed to participate in the sprint? Knapp and others recommend, that the group includes these people, in addition to the Facilitator:
- Decision Maker – such as the CEO, Product Manager or Chief Design Officer
- Finance Expert – such as the CFO, or a Business Development Manager
- Marketing Expert – such as the CMO, or other qualified person in Marketing
- Customer Expert – one who regularly meets or chats with customers
- Technology Expert – such as the CTO or any other person with expertise on technology
- Design Expert – such as the Design Strategist, the Designer or the Product Owner of the software
Sometimes, some of these roles can be combined. But Knapp and others emphasize, that a Facilitator must be the one that keeps things running, keeps track of time and tasks, and leads the sprint on. It makes sense to hire one or two professionals for this task. Also, some extra experts can be invited to participate and give their views and insights on the issue on the very first day.
It is highly recommended by Knapp and his colleagues that each day, 7 hours with a 1-hour lunch break is spent on the sprint. This will allow for 6 working hours for the group each day, divided between various scheduled tasks.
Knapp recommends starting the sprint each day no earlier than by 10 a.m., so that everyone is present having already checked their emails for the day, as well as being very persistent that no laptops, phones or tablets are allowed in the room. If anybody needs to take a call, they can take it outside the sprint room.
Sometimes, the group may have to reframe the original issue to be solved with human perspective and empathy. For the very first day of any sprint, Knapp and others suggest setting and agreeing to a long-term goal is needed. Challenge mapping is recommended, but picking a target for the sprint is equally important.
Before setting out to pick the target for the sprint, it is paramount to ask the group of people participating, where the company wishes to be in six months, a year, or even five years from now. Sometimes, there may be a long-term strategy involved, but it is recommended to allow for some time for discussion on this topic.
In “The Design Studio Method”, Brian Sullivan emphasizes that preparation largely determines success when it comes to sprints, and suggests scheduling a Problem-Definition Meeting, before the sprint. I find, based on my own experience in facilitation, that this method might work better besides or alternatively combined with the Google 5-day sprint.
Arranging a Problem-Definition Meeting before the design sprint incorporates several benefits:
- Defining and outlining the original issue, problem or opportunity you wish to solve during the sprint, before the sprint team gets together for the first time
- Understanding any prior existing requirements or commitments
- Explaining the methodology of the sprint to the key stakeholders
- Identifying any such pieces of information you may need to do some research on beforehand
- Securing alignment between the key stakeholders of the company
- Committing key people to participate in the sprint beforehand
- Determining the schedule and scope of the sprint
Sullivan also lists the various advantages of a cross-functional team:
- Diversity – With a variety of people from different departments, you will have unique perspectives based upon each person’s expertise.
- Cohesion – Participants complete assignments together using their individual talents to further the bigger goals of the team.
- Synergy – With a variety of perspectives, the interactions of the group should lead to a greater creativity, as people build upon the ideas of others.
- Consensus – Your project will have a final plan for execution, or at least a product vision set in place.
The core mission of design is to seamlessly translate business efforts and technology into products and services that deliver human value. At the end of the day, products are simply tools and services that are part of a human ecosystem of tasks and much deeper — almost spiritual — human drivers. Products and services empower humans and enhance human abilities.
There still remain organizations that see design thinking as unnecessary rather than essential to driving organizational change and innovation. Without doing proper research on the customer’s lifestyles and needs and then generating and evaluating various design ideas in a group of people with diverse expertise, in design sprints, however, your product or service might fail in delivering value to the target customers.
This, to me, sums up the value of professionally prepared and facilitated design sprints.
Read more in an article “How Using Design Thinking Will Fix Design Thinking” by Bert Brautigam:
Get “Sprint – How to Solve Big Problems and Test New Ideas in Just Five Days”, 2016, by Jake Knapp, John Zeratsky and Braden Kowitz”, or “The Design Studio Method”, 2016, by Brian Sullivan on Amazon:
Contact Iiris via LinkedIn: https://www.linkedin.com/in/iiriskonttinen/
Visit the Steps Helsinki website (only in Finnish): https://stepshelsinki.fi/