Phase 3: putting the selected solution on paper
Last updated
Last updated
The previous phase left us with a set of Concepts, each carefully crafted by a participant. Each represents an opinionated hypothetical solution for solving the challenges at hand. Ideally we create prototypes and test each of these Concepts, but as that would take a bit too much effort, we instead align on 1 'winning' Concept that we then collectively work out further. This phase is all about deciding on a solution to test and work out all details needed to build the prototype.
Humans have limited short-term memory and limited energy for decision-making, which is why an unstructured debate is not the right form for selecting a 'winning' Concept. Instead we'll follow a structured approach that Jake, inventor of the Design Sprint, refers to as "unnatural but efficient". All Concepts of the previous phase are hung onto the wall and everyone inspects them in silence. Afterwards, a 'winner' is selected through dot-voting.
Exercise Concept Voting - Reread your notes from the Note Taking exercise and inspect all the Concepts on the wall. - Take as many red dots as you like and stick them on all parts of all concepts that you like or you think is a good way to answer the Sprint Questions.
The above exercise is performed to create a heat-map that helps making the real decisions later. It's about registering interest and not about making commitments, so dont be frugal with your dots. Below we see an example of dot-votes on our Concept. In our case, the team saw value in the price recommendation as well as the graph that visualizes progress towards your earning goals. Also, showing how much the Host still needs in total this year even got two dots.
The Facilitator now presents all Concepts with a focus on where the dots are. Tell the name of the Concept, the general idea and the parts with a lot of heat. It is recommended to appoint one Volunteer that writes down 1 – 3 sentences on rectangular post-its for each presentation that the Facilitator gives in the next task, which are added above each Concept. After explanation of a Concept, anyone who voted on this concept for a different reasons can speak up as to prevent misinterpretation.
Exercise Synchronized Voting and Decision (15 mins) After all presentations, all take a good look at the concepts and dots. - Decide in your head which concept you think should be prototyped and tested. - Take a rectangular post-it. Write down the concept title and reasons for your decision. - Everyone takes a green dot and writes their initials on it. - Then, at the same time, everyone sticks the dot on the feature or Concept they selected. Everyone presents their decision to the group and the Decider. - Finally, the Decider selects one of the Concepts as the main Solution and optionally also parts of other Concepts that are really interesting.
As you can see it is finally up to the Decider to pick. What is great about the structure of the above exercise is that the Decider can also optionally take parts of other Concepts. Even though we are selecting a 'winner' we wouldnt want to throw away good ideas or elements. For our leading example we assume that the Decider picked our Concept and did not take with it any other parts.
Exercise User Test Flow Everyone takes the square post-its. Look back at the ‘winning’ concept. Write 6 story steps that you think are a good way to guide a user through the solution. Tip: start your sentences with verbs.
For our Concept we came up with the flow below in which a Host selects to set the price of its room and indicates to Airbnb that this should become its primary source of income. The platform looks into the Host's bank transaction data (through PSD2 or other Open Banking solutions) and extrapolate earnings of a room based on the number of days the Host wants to rent out its room. The artificial intelligence compares the expected income with the bank account expenses to come up with a suitable price that allows the Host to sustain itself.
Such User Test Flow is created by each participant individually, after which we put all flows underneath eachother to prepare (you guessed it) for dot-voting a winner. In our example below it is Person 2 whose User Test Flow is selected by the Decider.
Exercise User Test Flow Voting - Put up the purple post-its as shown below. - Participants stand up in turns and read out their post-its and stick them on the grid. - Every participant votes on the row they think is clearest using a red dot. The Decider makes the final decision using the green dot.
Now that we decided on a concept and detailed the steps further, we should ensure to not leave any open questions for the prototypers. The Storyboard details the proposed solution to the platform experience of the most constrained role and gives us a means to test and validate the role's participation in the platform. It is recommended here to appoint a Volunteer that draws the story board so that the Facilitator can focus on facilitating.
Exercise Storyboarding (60 mins) Arrange a big whiteboard and draw 8 cells on it. - [10 mins] Take the 6 post-its from the winning User Test flow. Stick the post-its in 6 of the cells (see below). - [10 mins] Jointly look at all the Concepts and find drawings you can re-use and stick into the cells. The focus should be on reusing the winning Concept, but feel free to borrow from other Concepts that better represent it. - [40 mins] Complete the cells by drawing around the Concept parts and add all details. Advice: start with the first, then the last, then the rest.
First we take our post-its from the User Test Flow and put them in the cells where we plan to draw them out. Of course there is always room to shift a bit so dont spend to much time.
After working collectively for the past hour we arrived at the Storyboard below. As you can see, it is really as detailed as web application screens would be including all buttons. We also added the mouse pointer to indicate what part of the screen is clicked to jump to the next screen.
The Storyboard tells the tale of a Host that wants to set the price of its rental house in such a way as to provide a primary source of income. Airbnb requests insight in the Host's transaction data to estimate the expenses that should be covered by the rental income. After asking for additional information, the Host is presented with a recommended price. Creating a prototype of this Storyboard enables us to test various hypotheses, such as whether a Host gives Airbnb access to its transaction.
