Please enable JavaScript.

Coggle requires JavaScript to display documents.

The Design Sprint 2.0 - Coggle Diagram

- - - - Morning: Vote on the solutions
        Ah, Tuesday morning. A leisurely stroll around the gallery of concept sketches, coffee cup in hand, taking it all in. We spend the whole morning deciding what to prototype, starting with the Heat Map, where people place multiple votes on inspiring parts of sketches so that clusters can form. These clusters are then highlighted in the solution presentations, where the moderator walks the room through each individual sketch, followed by the straw poll (where everybody puts one vote on the one solution they want to push forward). The morning is rounded off with the Decider’s vote, where they pick one or two concepts that they want to prototype.
      - Afternoon: Create the storyboard
        We added a new exercise here that makes the storyboarding process at least 27 times easier (give or take). It’s called User Test Flow and it’s a form of Note & Vote exercise. Everyone designs the barebones of their own storyboard and then we vote on the one or two that we end up prototyping. Even though it’s an extra step, it speeds up the storyboarding process by a million miles and eliminates the “designing by committee” aspect of it. Here’s a video that explains it in detail (and there’s a Medium post on it, too).
        So by the end of Tuesday, all of the decision-making is done, and your experts can retire and pick up their day jobs again. You’ve got a clear direction and can move on to prototyping and testing what they asked you to.
        We can’t stress enough what a massive win this is. It’s a low-commitment version of the old Sprint concept, but the output is just as polished (if not more) and it has won many reluctant clients over.
    - - Morning: Define the challenge
        We mix things up a bit by starting with the expert interviews and “How Might We” questions. While that’s not what the book recommends, we found that this order helps us dive deep into the problem and ask better questions, with a better understanding of the situation.
      - Related: When a design sprint isn’t the answer.
        Armed with this knowledge, we then move on to defining the long-term goal and capturing the Sprint questions. Doing it this way, the progression feels more natural, and what we learned in the interviews often feeds into the sprint goal.
        We spend 45 minutes (tops) creating a passable map, which is easy enough by this point. In the book it takes half a day, but when it’s all built up like this you can do it in 45 minutes. You do NOT need longer to create a map that’s good enough. The Decider then chooses a target area on the map—and voilà! That’s Monday done in half a day. Time for lunch and a BIG coffee…
      - Afternoon: Produce solutions
        Now that you know everything worth knowing about the problem, it’s time to think about potential solutions. We basically do the entire day of Tuesday on Monday afternoon (while suitably caffeinated, of course)
        We start with the Lightning Demos (which would take place on Tuesday morning) and spend less time looking up inspiring solutions than the book suggests. #Timehack!
        Once we’ve captured the standout ideas from the Lightning Demos, we move straight on to the four-part sketches, which we condensed, again, to keep the momentum going. There’s still plenty of time to comfortably design up the solutions and stick them on the wall for the next morning.
      - That’s Monday done
        all your knowledge pooled, your target set, your concept sketches done. Phew, now it’s time to go home and sleep. Tomorrow’s a big day.