The Optimal Team Setup for Successful Design Sprints

Who should participate in a Design Sprint? A guide to the perfect Sprint team composition.

English edition — originally published in German as Die optimale Teamkonstellation für erfolgreiche Design Sprints.

The Team Makes the Difference

A Design Sprint is only as good as the team that executes it. The right composition determines success or failure. In this article, we show what the ideal sprint team looks like.

The Ideal Team Size

Google recommends 7 participants, plus or minus 2. Our experience confirms this:

• Too small (< 5): Too few perspectives, risk of groupthink
• Optimal (5-9): Diverse perspectives, still manageable
• Too large (> 9): Difficult to coordinate, not everyone gets a say

The Core Roles

The Decider

The most important person in the sprint. The Decider:

• Has decision-making authority
• Resolves stalemates
• Commits resources for implementation
• Is ideally a CEO, product owner, or similar

Without a Decider with real authority, a sprint cannot be successful.

The Facilitator

The process owner:

• Guides through the methodology
• Ensures timeboxing
• Moderates discussions
• Is often an external consultant

The Experts

Relevant depending on the problem:

• Tech Expert: Understands technical possibilities and limitations
• Design Expert: Contributes UX/UI expertise
• Business Expert: Knows the market and customers
• Customer Expert: Understands the user perspective

The Sprint Week

All participants should be available for the entire week:

• Monday: Build problem understanding
• Tuesday: Sketch solutions
• Wednesday: Decide
• Thursday: Build prototype
• Friday: Test with real users

Part-time participation does not work. The sprint requires full attention.

External vs. Internal

A mix of internal and external participants is often ideal:

Internal brings:

• Domain knowledge
• Historical context
• Implementation capability

External brings:

• Fresh perspectives
• Methodological expertise
• Impartiality

Common Mistakes

What you should avoid:

• Not involving the Decider
• Only inviting like-minded people
• Deliberately excluding critics
• Letting hierarchy dominate

Conclusion

The composition of the team is not a minor detail – it is crucial for the success of the Design Sprint. Invest time in selecting the right participants, and the rest will be much easier.