Build to prototype, not to polish

We stopped spending so many cycles on design explorations of static mocks or walkthroughs and said, 'How quickly can we get into prototyping the path in real software, even if it's messy and you throw it away,' at least for something like Slack. You got to live and touch and smell the software.

Storyboard some solution visually with a Sharpie and not a pencil, not Figma initially, not high or low fidelity. What is the unconstrained perfect solution to this burning problem?

The goal of the design sprint is not to sort of come up with these are the features we should build. The design sprint is to generate a lot of illustrative concepts that bring the strategy to life because a picture is worth a thousand words.