After running dozens of sprints, we realized that identifying the right problem up-front is crucial for any Design Sprint. We saw many ambitious Design Sprints fail when the stage was not set properly, or there was no common understanding of the actual problem if one at all.
A Problem Framing process identifies and captures stakeholders perspectives and expectations, makes sense of the customer needs and uncovers the most promising opportunities within the organization. Problem Framing is essentially the bridge between creative, innovative problem-solving processes like Design Sprints and the overall business strategy and objectives.
At the Google Sprint Conference, we will teach sprinters all about the mechanics behind it in a 2-hour deep-dive session.
Led by Design Sprint Academy and Google Design, this one-day exclusive event in London focuses on innovation, organizational transformation and design sprints.
Design Sprints for Change brought together 100+ executives, innovators, designers, consultants and design sprint ambassadors to tap into a broad diversity of perspectives, share success stories and learn cross-industry best practices.
Most Sprints fail when teams don’t have a clear understanding of the problem. Our Problem Framing workshop provides a framework on how to address the relevant aspects of a problem, to engage a team of stakeholders and to gain the confidence that you are tackling a problem worth solving.
Google invited us to San Francisco to share our knowledge on Problem Framing. Participants included their Design Sprint Masters and other Product Managers, Strategists and Designers from Adobe, PayPal, Boeing, SalesForce and Nike.
In partnership with Invision, and as part of the DesignBetter community, we facilitated the Berlin’ Design Sprint Workshop for more than 60 design sprint enthusiasts.
How can cognitive biases impact design sprints?
At the Google Sprint Conference in San Francisco, our Head of Training, Dana Vetan shared her perspective in a one-hour interactive presentation: