How Your Organization's Generative Workshops Are Probably Going Wrong and How to Get Them Right
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 had to convince our director and executives by showing how the repository added real value for the product team."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"Not everyone has the same capacity to aspire to a future; this is critical when working with marginalized communities."
Nicole AleongFuture Orientations to Everyday Life: Futures Anthropology as a Methodology
March 26, 2024
"The innovation studio bakes in strategic vision, leadership, funding, and ownership."
Jeff GothelfInnovation Studios: the Engines of Enterprise Experimentation
May 14, 2015
"Accessibility ownership should never fall on just one person but be understood and shared across entire product teams."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility
May 26, 2022
"Design ops folks meet the habit of catering so much to everybody’s increasingly trivial whims that it takes us away from the real meaty ops work."
Tess DixonC'mon Get Happy
September 29, 2021
"Mastery is achievable, whether you have 10,000 hours or not—it’s about building that portfolio and case studies."
Liam ThurstonWhy Your Design Team Is Quitting, And How To Fix It
June 10, 2022
"Communication matters—sending an email to an executive with spelling mistakes can ruin your respect."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"If you make rules, put numbers in them, and say them confidently, sometimes people actually do them."
Leisa ReicheltOpening Keynote: Operating in Context
November 7, 2018
"Over-enforced design system adoption bred resentment and low morale, despite good adoption metrics."
Rachael Greene Alison DavisBuilding a Design Ops Practice that Really Works (Most of the Time)
October 2, 2025
