Design sprints for teams

After the Design Sprint: Capture, Iterate, and Continue

Congratulations, you’ve finished your design sprint! Now what? The answer to that question depends on how much validation you received during your interviews with users. It’s time to reflect back on the entire initiative and see what worked, what didn’t, and how to move forward. Don’t limit yourself to considering the project itself; consider the entire design sprint process. We’ve mentioned repeatedly that this is a flexible framework and you can mold it to fit your needs. There are plenty of ways to do this given your constraints. Did it work? What could you change to make it better?

A sprint summary document can vary widely depending on the project and the organization. We have some very detailed summary documents that are over 60 pages long. Others use a one-pager, executive summary style. The style and structure of your summary will depend on your team and organization’s needs. Sure, you have the prototypes you created as artifacts, but those don’t tell the whole story of the week, and this is the opportunity to do so. We take photographs of our walls, whiteboards, and Post-its, and include them in our summary reports.

What Happens Next?

Capture and Document

Determine Next Steps

Continue the Practice

Capture and Document

Wrap-up documentation is helpful for the design sprint, whether you’re a consulting firm or an in-house product team. These summary artifacts are excellent ways to get new team members up to speed ...