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
"Screen readers let us jump from one heading to another, replicating the experience of skimming a page visually."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
"Government is seven plus years behind industry – not bleeding edge, more like the dull butter knife edge."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"We had to push through analysis paralysis and trust our guts as customer-facing teams that knew the business."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Leadership doesn’t only mean managing; it can be mentoring, product leadership, or technical influence."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"If you’re managing over 100 design practitioners, it makes sense to start looking at a chief of staff role."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"What if product and business actually manage designs and deliver digital communications?"
Amy EvansHow to Create Change
September 25, 2024
"Teleportation lets us move throughout the organization by building tools that gather disparate data for real-time decision making."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"The higher up you are in an organization, the more distorted your reality is likely to be."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"We wanted a living network of knowledge so yesterday’s insight connects to today’s evidence and tomorrow’s learning."
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020
Latest Books All books
Dig deeper with the Rosenbot
How do Kate’s and Jake’s books complement each other on the topic of scaling research operations?
What are successful strategies to overcome resistance to UX research within product teams?
What are effective first steps for starting research operations in a large organization with limited resources?