March 27, 2020

Day 3 - Choose the right path

It’s awesome to have a lot of ideas. It’s a great feeling. But I’ve got bad news: you can’t build and test everything. And even if you could, it wouldn’t be very useful, because you’d have too much information to sift through. So you’ve got tough decisions to make: which solutions will you pursue and which will you put on ice?


This day is all about the distilling of all the possibilities that were discussed over the past two days and start prototyping on a single solution. In this solo activity, I have got the advantage of being the facilitator and the decision-maker. However, if you are doing this activity in a team, it’s up to the facilitator to choose the decision-maker to have the final say on what solution to implement.

Search for Conflict

In a group setting, the chances of conflict will be more. This is essential and can be a gold mine for the best approach to implement a solution. While doing the crazy eight, I also came up with my list of conflict:

  • Routes can be as complex as starting the trip on a 4 cross junction or a roundabout or right in the middle of tiny crisscross pocket roads or need to take a detour to start the trip in the right direction.
  • How can the new directional navigation track the current position of the vehicle?
  • The context switching of navigation can be confusing sometimes, how can we make sure the transition doesn’t confuse the driver.
  • How do you decide the essential information that the user needs to locate himself or help him find nearby localities while on the trip?


It’s good to review all the assumptions that have been collected throughout the sprint. Decide on a plan to test and validate these assumptions by performing a user study. Since I’m the target user, I am keeping assumptions that I think is relevant for this study:

  • I will be okay if the app delays the switch to a directional navigation system, once the vehicle has picked up momentum or at a min, speed is at 20km/hr. However, the reverse behavior will not kick in when the speed goes down the triggering speed.
  • I will be okay by showing the current vehicle movement by a combination of an indicator showing the proximity of the destination or next route change and animating the road that indicates the movement of the vehicle like as in the games.

Final Storyboard

In this step, I want to show how the user will step through the prototype. This is done by drawing a comic book storytelling method – like frame by frame - that tells a story of a single action in the critical path. Design details and layouts are not important at this stage.

Key take away from Day 3 sprint

Your search for your mental visuals ends up on this day's sprint. The confusions and assumptions are still high, but that cannot halt the progress. Iteration and user testing is the way forward.

Day 4, 5 - A new way to Navigate

More Articles