Hala 🤩 !
Here is the Part 3 of this serious which I’ll talk about Design Sprint Foundation – The Udacity nano Degree. You can View the Previous Part:
Through this article we gonna talk about the Day No.2 – Activities, what we gonna do and deliverables in details, so let’s begin.
Day 2 Is Almost About Voting On The Concepts, Deciding Which Direction To Go In, And Creating A Storyboard To Work On The Day3.
- Heat Map Voting.
- Presentation Of The Concept.
- Decider Voting.
- Story Boarding.
1-Heat Map Voting
Each Team Member Has Voting Dot Sheet, He Will Remember The Goal And Questions Of The Sprint, Silently Walking From Concept To Concept, He Will Start Post Dots On The Concept He Like, May It Will Be A Part Of An Concept, May Be It’s One Concept, Whatever, It’s About How Your Member Feels About The Concepts. More on Google Design Sprint Kit Also, It might help if you check Decision Matrix by Google.
Okay, Now The Moderator Gonna Go Through Concepts, Concept By Concept, And Start Presenting What He See & Can Understand, He Also Focus On The Areas Which Takes Lot Of Voting Dots – So He Will Go Deeper Into Details, No One Should Speak For The Entire Time, Till He Ask The Question At The End Of Each Concept :
Is There Is An Area Voted On Which I Miss Communicated? And It’s Not About An Artist Reveals Himself, Simply Someone Can Say “Oh, I Voted On This Step Because Of Bla Bla Bla”. The Artist Will Still Be Unknown.
Now Each Member Will Have A Voting Dots, Another Color With His Short Name Written On It, For Example, “MY” For Mohamed Yahia! – They Have 10 Min, To Decide On Which Concept Or Part They Want To Represent As The Solution, They Should Have Also Post-it, To Write On It Why They Decide Like That, And Then – All Of Members On The Same Time After The Time Is Up – They Will Post Their Dots On The Concept Or Part Of Concept They Choose.
What’s After !?
Members Will Represent “Why” They Choose This Concept Or Part Of Concept To The Moderator, After That, It’s Time For Decider To Make A Decision!
If Team Member Has A Question, He Shouldn’t Ask, He Can Only Write His Question On Postit And Leave It Somewhere Close To The Part He Wanna Ask About.
The Decider Will Take Only Two Votes Dots With Stars On It, He Can Only Use Two Dots. He Can Choose A Full Concept, Two Parts From Two Different Concepts, Or A Whole Concept With Specific Part From Another Concept.
Talk With The Team !?
Decider Can Choose To Talk With The Team About Decision He Gonna Take Or Go On Directly Without And Discussion.
Note, There Is A Tricky Point Here, Team Can Decide To Go With Only One Way “ Applying One Concept Or Combined Concept” – Or They Can Go With Two Competing Concepts At The Same Time. Anyway, Let’s Move On The Next Stage!
It’s All About Story Board, The Story Board Will Show How The Design Will Looks Like Screen By Screen Run Through, So The Designer Will Not Lose Any Time In The Day 3 To Deliver The Prototype. It’s The Only Reason To Get Hi-Fidelity Prototype In Only One Day, It Contains Two Main Exercises :
- User Test Flow Map: Deciding What The Steps Will User Walk Through.
- The Story Board Itself: Detailed Step By Step Walk Through In Details For How The Screen Will Look Like.
User Test Flow:
Write 6 steps that show how you imagine a user would test out the Project. Use 1 sticky note per step. Based on the chosen Concept and review the Map. You have 8 minutes for this exercise. Use your timer!
Reference Steps for Design Sprint team
- Each member takes 8 minutes to write 6 individual steps on 6 sticky notes.
- Each puts their steps on the wall in horizontal stripes
- decider reads through timelines
- decider chooses which timeline to work with might not be perfect so can add/adjust from
Write 6 steps that show how you imagine a user would test out the Project. Use 1 sticky note per step. Reference the chosen Concept and review the Map. You have 8 minutes for this exercise. Use your timer!
The Moderator really comes into play during this exercise of the Design Sprint. As this exercise is longer and involves open dialog, it is possible for the team to divulge into unproductive ideas & tangents that are not useful for the Storyboard creation process. It is imperative for Moderators at this step to keep everyone on task and focused on the goal of creating a very detailed Storyboard.
The Artist is responsible for turning the ideas/thoughts presented by the group into designs and sketches within each cell of the Storyboard. This person does not need to be skilled at drawing. The basic skills they need to have is the ability to draw boxes and the ability to write legibly enough for the team to read the words within each cell. The larger you can create the Storyboard, the easier it will be for the Artist to successfully create drawings in each cell that are actionable. If your drawing space is too small, your Storyboard will lack the details that the team will need when beginning to Prototype on Day 3.
Key Parts to Remember:
This is all about combining the Concept of the User Test Flow to create a cohesive Storyboard of the user testing experience through the product.
- Draw 8-10 empty cells
- Add User Test Flow steps sticky notes to the cells where they make sense.
- Do a quick outline of what each cell might look like you can cut up pieces of the Concept and paste them directly onto the Storyboard with tape.
- Going through each cell step-by-step to detail each part of the cell:
Tips for a Successful Storyboarding process:
- Don’t create anything new!
- Use parts of Concepts directly in the Storyboard by cutting up and taping pieces where they might be useful.
- Make sure all discussion stays focused on the goal.
- Use specific words rather than fake words so that no word choices have to happen when creating the Prototype
That was the end of The second day, and now we are ready to go through the Day3 – which I’m going to talk about it in next few days ISA.
Again, Remember, The Design Sprint Kit site by Google – is here for help also. and keep in your mind, That it’s not the pure way of implementing Design Sprint, but – it’s the way used by AJ&Smart – and it’s very moderated that’s why it’s really useful and productive!
Scenarios describe the stories and context behind why a specific user or user group comes to your site. They note the goals and questions to be achieved and sometimes define the possibilities of how the user(s) can achieve them on the site. A ...
Testing of prototypes, products, or interfaces by users of a system in design development This gauges human expectations against a designed artifact, determining whether something is useful, usable, and desirable. Testing should collect per...
It is a form of qualitative research consisting of interviews in which a group of people are asked about their perceptions, opinions, beliefs, and attitudes towards a product, service, concept, advertisement, idea, or packaging. Gauging opinions...
Web analytics is the measurement, collection, analysis and reporting of web data for purposes of understanding and optimizing web usage. What we care about - as designers: This process provides a gateway for your organization to become invest...
Content analysis is a research method for studying documents and communication artifacts, which might be texts of various formats, pictures, audio or video. Social scientists use content analysis to examine patterns in communication in a replicable a...
Experience sampling is a way to find out more about an experience while the event is actually happening. Participants stop what they are doing and take time to note their experiences over a period of days, weeks, or even years — which can result in...