Summary
Generative workshops are a critical generative component of any product development process. But in my 20+ years conducting product user research, I have seen more product harm come from so-called "workshops" or "design sprints" than good. In this tutorial, I will share more about my experience and what I've found are critical components of generative workshops -- whether they last five hours or five days. Contrary to popular belief, a design sprint is a highly structured and carefully designed series of exercises, not a brainstorm, design jam or free-for-all. The whole point is to drive a cross-functional team to the right outcome, and this requires a set of structured exercises which weave the thread of user needs, behaviors and attitudes throughout. This involves more than reviewing the research at the start and then moving on to create without that research in context. A true design sprint takes us from user insights -- even broad user insights -- to user-evaluated concepts or designs. The generative phase of a product is deeply impactful, and design sprints are a fantastic tool for driving this needed impact. However, many are practicing brainstorms or design jams rather than true design sprints. One can make a mismatched concept extremely usable throughout the product development process, but that will not remedy the fact that it is not the right concept. Researchers are ideal design sprint organizers and facilitators, but researchers are sometimes not even considered a critical component of the sprint. It's important for knowledgeable researchers to drive design sprint impact.
Key Insights
-
•
Many generative workshops fail due to fundamental mistakes more often than they succeed.
-
•
The 'Sprint as theater' mistake occurs when workshops are done for appearances or political reasons rather than genuine product development.
-
•
Well-structured workshops with specific exercises are crucial to move from research data to human-centered product concepts.
-
•
Integrating research both before and after a workshop grounds concepts in real human needs and allows recovery if initial research is missing.
-
•
Excluding key decision-makers leads to surprise blockers after workshops and risks misalignment with product goals.
-
•
Facilitation is a distinct, practiced skill essential to managing group dynamics, pacing, and adapting exercises during workshops.
-
•
Scaling back workshops too much compromises their effectiveness and the quality of resulting concepts.
-
•
Explicit communication about workshop outcomes and quality is necessary to help stakeholders appreciate the method's value.
-
•
Training facilitators in focused, incremental sessions delivers practical skills necessary for leading effective workshops.
-
•
Ensuring equal participation requires setting clear engagement rules and providing tool training to accommodate varying skill levels.
Notable Quotes
"The outcome of this method really makes the difference between lightning and a lightning bug."
"Sprint as theater is not going to result in a product concept that really represents human needs, behaviors, and attitudes."
"If there is no structured way to move from data to concept, you often end up with just a brainstorm, not a grounded concept."
"Lack of research before or after the workshop can be recovered from but at some cost to the concept’s validity."
"Excluding key people might save time but it often leads to surprise blockers and misaligned decisions later on."
"Facilitation is a skill that takes real practice; it’s about managing personalities, stamina, and knowing when to adapt exercises."
"There is a point where scaling back a workshop too much will make it ineffective and that trade-off must be explicit."
"Many stakeholders don’t inherently understand the difference in quality outcomes from workshops, so we must be explicit."
"Getting to know what people care about in the organization helps tailor workshops to support those goals and gain buy-in."
"It’s important to create a sincere environment where everyone feels they can equally participate, regardless of title or skill level."
Or choose a question:
More Videos
"Behavior begets behavior – by modeling sharing and documentation, others start adopting those habits."
Boon Yew ChewMaking Sense of Systems—and Using Systems to Make Sense of the Enterprise
June 6, 2023
"A centralized model for design systems can be problematic because it distances the team from end users."
Dan DonaldDesign Systems as a Vehicle for Systemic Change
June 1, 2023
"Research ops should elevate beyond processes and support to become a strategic partner reflecting critically on our work."
Fatimah RichmondThe Future of ReOps as a Strategic Function: A Roadmap for Getting There
March 25, 2024
"Design shares are more about presenting finished work and practice defending it, not about peer-to-peer feedback."
Joseph MeersmanSweating the Pixel: Scaling Quality through Critique
June 10, 2021
"Jennifer quit because the feedback loop was too fragmented and overwhelming."
Melinda BelcherBridging the Gap: Making the Most of the Differences Between Agency and Enterprise
January 8, 2024
"Designers are theorists whether they realize it or not — they create solutions that have intended and unintended consequences."
Uday Gajendar Adam RichardsonFrom AI to Zeitgeist: Theory as the design antidote to AI hype
March 27, 2025
"Service design isn’t about the tools but the way of thinking to approach any problem with a humanist approach."
Laura Smith Tom GaylerEmbedding Service Design and Agile Practice within UK Planning Teams to Create Services that Last
December 3, 2024
"Staff and principal designers need to balance zooming in on execution and zooming out to define strategic vision and minimize risk."
Catt Small Micah Bennett Brian Carr Jessica HarlleeWhat's Next for ICs: Exploring Staff and Principal Designer Roles
February 22, 2024
"Creativity, accountability, and authenticity are going to be the new markers of humanity."
Katie JohnsonDisrupting generative AI products with just-in-time consumer insights
June 4, 2024
