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
"We have the Big C and the Little C: our external customers and our salespeople using the tools every day."
Emily EagleCan't Rewind: Radio and Retail
June 3, 2019
"Widgets encapsulate a user task with associated user interface and back end service functionality."
Dawn ResselFull-Stack User Experiences: A Marriage of Design and Technology
June 9, 2016
"We’re not just translators between different ways of thinking, but architects of shared reasoning processes."
Kurt McCullochFaster alone, further together: Rebuilding collaboration in the age of AI research
March 10, 2026
"The organization’s website structure often mirrors its internal organizational structure and decision-making."
Sheryl Cababa Alexis OhThinking in systems to address climate with Sheryl Cababa
June 12, 2024
"Engineering’s number one goal should be to enable learning."
Bill ScottLean Engineering: Engineering for Learning and Experimentation in the Enterprise
May 14, 2015
"That seven-foot-wide diagram was our product, not just the cleaned-up UI screens—this artifact triggered a whole new conversation."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"Improving developer experience starts with understanding users and their technical contexts."
Ed MullenDesigning the Unseen: Enabling Institutions to Build Public Trust
November 16, 2022
"Nobody wants to be told to do your thing unless it’s clear that it helps their thing. It’s just human nature."
Maria GiudiceBecoming a Changemaker by Leading with Design
March 29, 2023
"Share your story vulnerably and in a neutral setting to open connection."
Tutti TaygerlyVideconference: How to Work with Difficult People with Tutti Taygerly
June 25, 2020
