Innovation
Design Thinking Challenge
Run a complete design thinking process, from empathy to prototype, in one intensive session. This challenge compresses the five stages—empathize, define, ideate, prototype, and test—into a focused workshop. It builds problem-solving capability by experiencing the full cycle quickly; better than just reading about it.
Duration
4 hours
Group Size
4-8
Category
Innovation
Difficulty
Easy
- Practice the complete design thinking process end-to-end.
- Build team capability in user-centered problem solving.
- Generate a tangible prototype and tested solution in one session.
- Internalize an iterative approach to design challenges.
- A completed design thinking cycle from empathy to prototype.
- Team capability in user-centered problem solving.
- A tangible prototype with tested insights.
Timeboxing is essential. Each phase has a strict time limit. When time's up, move on, even if the team wants more time. The constraint forces decisions and prevents perfectionism. Real design thinking happens under constraint.
Embrace "good enough." Teams will want better research, more ideas, and a more polished prototype. Resist. The point is experiencing the complete cycle quickly. "Good enough" beats "perfect" when learning the process.
Real users are critical. Testing with teammates teaches nothing. You need someone who hasn't been in the room, hasn't heard the discussions, and brings a fresh perspective. Even one real user reveals what five team members miss.
Facilitator energy is important. Four hours is intense. The facilitator must maintain energy, enforce time boxes, push through resistance, and prevent tangents. If the facilitator gets passive, the workshop loses momentum.
Learning over output. The solution created in 4 hours won't be perfect, and that's fine. The goal is learning the design thinking process, not creating a production-ready solution. The value is in capability building, not deliverables.
Common failure modes: jumping to solutions without understanding the problem, a weak problem definition, groupthink during ideation, over-investing in prototype polish, testing with the team instead of users, and skipping reflection. It's a lot to juggle, and sometimes things don't go as planned. Don't be afraid to acknowledge that and learn from it.
Embrace "good enough." Teams will want better research, more ideas, and a more polished prototype. Resist. The point is experiencing the complete cycle quickly. "Good enough" beats "perfect" when learning the process.
Real users are critical. Testing with teammates teaches nothing. You need someone who hasn't been in the room, hasn't heard the discussions, and brings a fresh perspective. Even one real user reveals what five team members miss.
Facilitator energy is important. Four hours is intense. The facilitator must maintain energy, enforce time boxes, push through resistance, and prevent tangents. If the facilitator gets passive, the workshop loses momentum.
Learning over output. The solution created in 4 hours won't be perfect, and that's fine. The goal is learning the design thinking process, not creating a production-ready solution. The value is in capability building, not deliverables.
Common failure modes: jumping to solutions without understanding the problem, a weak problem definition, groupthink during ideation, over-investing in prototype polish, testing with the team instead of users, and skipping reflection. It's a lot to juggle, and sometimes things don't go as planned. Don't be afraid to acknowledge that and learn from it.
Start the conversation
Be the first to share your thoughts, experiences, or questions!