When Justin Kaster and I first started talking, he was in the midst of working on the next iteration of his business ideas and wanted help defining what his team could do next. I ran a 3-day Design Sprint with Justin’s team to design, test, and get feedback on new concepts that could help him evaluate the best next direction for his business.

The magic of the Design Sprint is its ability to neutralize politics. When I work with teams, I have frank conversations about politics and team dynamics going into the Sprint. The agenda I design takes into consideration the realities of those dynamics. I use methods to draw out ideas from everyone in the room and facilitate sharing and dialog so that politics aren’t what matters and great ideas can shine through.

These methods used are both a means to solve the challenges at hand and as practice so that educators walk away with tools they can use to continuously improve and refine on their own. First: we identify our “to solve” and refine by putting the human beings we aim to help at the center of our problem solving. Then: we come up with new ideas rapidly. Last: we define solutions that will be tested and tried after our work together.

Language is a tool people use every day but words can fail us. Drawing feels uncomfortable and intimidating to many of us. But even the worst (and I’d argue that there is no bad drawing — the only bad drawings are the ones that aren’t drawn.) Drawing communicates volumes compared to a sentence.

From low-fi, hand-drawn sketches to wireframes or clickable demos, we recommend prototyping with both your stakeholders as well as target users. Sometimes our prototypes are solely for the internal team to vet out interaction patterns. We often focus on an MVP (Minimum Viable Product) release. However, MVP is not an excuse to suck.