Use design sprints to create better products, faster.
Love design sprints because of their human value of unlocking trust, creativity, and performance.
Problem Framing is a 1-day process we’ll run 1-2 weeks before your design sprint to answer 2 questions:
What is the problem we’re being asked to solve? Is it clear enough that everyone empathizes and understands it?
Why is the problem worth solving? What is the impact it will have on your company? What value will it produce for your users?
Problem Framing provides the research, context, and alignment that allow us to accomplish the Understand, Ideate, & Decide phases of a design sprint in a single day.
Understand: Build cross-functional trust and alignment around your most critical business challenges.
Ideate: Everyone on the team has an equal chance to contribute their solutions ideas.
Decide: The group avoids bias and influence while voting on the most promising idea.
In order to get genuine feedback on our solutions, we need to make the experience of using our product feel real.
End result: We extend our most voted solution into a complete storyboard. The storyboard is then evolved into a hi-fidelity prototype.
By deploying qualitative user testing of our prototype we learn directly from the users experiencing the problem we’re trying to solve.
End result: Rapid user insights provide us the team-wide learning, validation, and confidence of what our product experience should and should not offer.
|Decision-making||Performed in a vacuum, based on assumptions||Inclusive and informed|
|Collaboration||Siloed and lacking trust||Co-creative and trustful|
|Innovation||Crazy ideas are dismissed||Crazy ideas can flourish|
|Design||Treated as a job title||Treated as a cross-functional process|
|Accountability||Slipping timelines and finger pointing||Committed to timelines and each other|
|Performance||Pressure leads to outbursts and breakdowns||Pressure rallies the team to win together|
|Perspective||Projects treated as projects||Projects treated with empathy and passion|