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
"Only one designer exists for every 43 developers in many large enterprises."
Surya VankaUnleashing Swarm Creativity to Solve Enterprise Challenges
June 10, 2021
"We had precise metrics built on false assumptions, so we had to shift to more contextualized signals."
Patrick Boehler Madison KarasThe service shift: transforming media organizations to create real value through design
November 19, 2025
"We used virtual sketching where users could move components into spaces representing their actual workflows on the platform."
Andreas Huebner Amy Takata Craig BrookesWhat Is It Like To Be Part of The UX Team at Compass?
March 11, 2021
"It’s less about processes and more about the business value of design."
Patrizia Bertini Alexandra Mengoni LeónPushing DesignOps’ Influence into New Global Markets
September 9, 2022
"IBM Design Thinking is about collaborating around artifacts and frameworks, not prescribing the process teams must follow."
Phil GilbertA Consistent Culture of Design
May 14, 2015
"I wouldn’t leave AI tools to juniors because it’s crucial to have your own experience to evaluate outputs."
Yulya Besplemennova[Demo] Stress-testing GenAI in user research synthesis
June 4, 2024
"The best way to understand something is to become part of it."
Sarah RinkRemote User Research: Dos and Don'ts from the Virtual Field
June 11, 2020
"Adding a senior researcher, Izzy, in field meant we could have more, smaller research tracks and better support for research newbies."
Mujtaba HameedThe new horizon of ethnography: using AI to unlock the full potential of in-person research
March 11, 2026
"Today's problems come from yesterday's solutions."
Sheryl CababaLiving in the Clouds: Adopting a Systems Thinking Mindset
June 6, 2023
