Redesign a monitoring solution for electronic communication- UX Design Sprint (Part 2)
Updated: Dec 29, 2018
Google Design Sprint (2 Days)
After that, we used two full working days to run the Google Design Sprint to create new information architecture. Addition we tried to find find the common ideas.
1. List Print Questions:
To be making sure each team member understands about insight the project, we put questions relate to discussing the product vision, goal and outcome from the client and team members as well.
1. What is our target user? — Compliance, Officers, Technicals, Legals
2. What do we offer? — Large employee base, get more revenue, understand value and offerings
3. How could this fail? — 3rd party changes APIs, too high maintenance, misunderstand about what is being built
4. What is the next 5 year goal? — Planning the services like Slack and Instagram
5. Why do they want our websites archived? — The cheapest
After discussing, we chose three core things as the target that we need them in this MVP (Minimize visible project), it included:
Having an area somewhere on the website to track all the metric data.
Changing the experience and user’s behavior to review the message list and action on that.
Improving the advanced search behavior.
2. Stakeholder Interview
We had an opportunity to hear their troubles when they run on the website to draw ideas need to resolve.
3. Mind Map
Based on the information that we collected, we brought all the first ideas in mind on the paper. On the mind map, we do n’t need about a gorgeous or unique map, anything for arrows and basic shapes are enough.
3. Sorting Card
Sort Card or How Might We method is an essential method, to take the insight and come up with positive solving the challenge. We avoid using words as personal in this step.
“How” guides team members to believe the answer is out there.
“Might” lets team members know their HMW statement might or might not work, and either possibility is okay
“We” reminds team members that the Design Sprint is about teamwork and building on each others’ ideas
- Google Design Sprint Book
During review, we gathered ideas and capture all day from begin like How might we notes, sprint questions, mind map flow to figure out and think some more the new ideas from stakeholder. Try hard to think about the solutions as personal
6. Sketch Crazy 8s
Crazy 8s is the paper with the eight pies. In one minute per each pie, we have a quick sketch on any elements we want to present. Why the time is so rush? The human will be forcing their brain to push new creativity when the time to squeeze you into a specific limit. I did some sprint designs I felt the productive core of Crazy 8s was very high to catch an idea.
7. Solution Sketches:
Whilst we had enough the information, mind map ideas and sketches around, then we based on that and made the personal storyboard that we want to represent. We also picked for each yourself one or two main ideas to give the concentrate on that solutions. Moreover, two or three peoples can work the same segment together to make the comparison and various options to support the different ideas.
Focus on solving all metric data on the dashboardFocus on the main menu navigationFocus on how to view the message list and detailsFocus how to work well on advanced search and filter
At the end of the day, we did all sketch solutions, so many ideas on how might we note with a lot of solutions ready to go ahead. For sure, we tried hard and satisfied with that.
8. Vote on Solutions Sketches
Day 2, we continued with Google Design Sprint and caught up anything on the first day, looked around at sketch solutions have been stuck on the wall. We had small dot stickers in hand and can vote for any components that this is an awesome idea need to turn up.
9. Speed Critique
After voting, we have looked on which components had the vote and discussed around that component with an answer like:
Why do I like this part?
What the value we can bring it into the design?
What is the hidden thing inside that we can to follow and grow up?
The discussion will end up when the owner of that component (had voted) to say out loud about why bring it into the design? What the next when to continue keeping with that. The owner will be the final guy for any discussing on each voted component
10. Super Vote
We had five sketch solutions with a lot of ideas for the redesign, also heard from stakeholder as well. Now, we had three super votes per person, and it’s important to choose the best idea that we want to follow it.
11. Choose 2 prototypes to go ahead
Finally, we collected all the storyboard had most of the super vote to go ahead with the wireframe prototype. We had two storyboards that conflicted on each other. Then, we worked on two different prototypes and each prototype presents on reflected flow.