RESEARCH | Meet the users
Figure out what you need to research
- Similar cases
- Successful approaches and solutions
- People opinions and reactions
Google about everything you curious about the users and the case. The final goal is putting yourself in user’s shoes and understand their problems and what they need.
INTERVIEW + OBSERVATION
Talk to the real users or potential users, clarify your assumption and understand them more
The survey may be useful if need more quantitative research and large amount of users, or have to the interview remotely.
EMPATHISE | Be the users
Benefit of empathy map
- Remove bias from our designs and align the team on a single, shared understanding of the user
- Discover weaknesses in our research
- Uncover user needs that the user themselves may not even be aware of
- Understand what drives users’ behaviours
- Guide us towards meaningful innovation
The purpose of personas is to create reliable and realistic representations of your key audience segments for reference. These representations should be based on qualitative and some quantitative user research and web analytics (https://www.usability.gov/how-to-and-tools/methods/personas.html)
The goal is to form one of the most distinguish target group, who they are, what is there motivations and problems.
Write down a situation in which the user use the product. From that, how to design a product that meets those needs.
Without identifying the various characteristics of the user groups visiting your site you cannot hope to design an experience that includes the key elements that each type of user needs. Instead, you will end up creating a website that doesn’t perform well for anyone.
- User scenarios can be used in the ideation phase of a design project. This is where visualising how a user will use a product or service will help generate design ideas. A fundamental point to bear in mind is that user scenarios do not represent all possible users. Instead, they typically account for only the most common users or user motivations (The Interaction Design Foundation, 2018)
- Describe how and in which kind of situation the product or service would be used (put in context).
- Start a scenario with the triggering event and describe the sequence of actions and results with a right level of details.
- Scenario => requirements for the prototypes, what functions need to be built for the needs of users in the scenarios.
IDEATION | Concepting
FUTURICE IDEATION MAP
From the problem worth solving, list down the negative feelings when the problems are unsolved (left) , and the positive feelings when the problem solved (right). Based on the feelings, think about the solution for that.
SPRINT INDIVIDUAL IDEATION in 6–10 minutes
Create and accept as many ideas as possible, no critique, say yes, don’t be too critical to yourself.
Think about the color scheme, style guide and the visual look of the design.
PROTOTYPING | Make it real
Flowcharts are diagrams that show the steps in a process
Paper prototyping is sketching screenshots on paper as substitutes for digital representations. It is fast and perfect for early stage conceptualising. Even though in some case we do not need to do paper prototype, especially when we redesign from something existing already. However, it is still a intuitive and flexible way that every designer usually start with.
It’s fun to do the paper prototype before jumping to digital or final version. However, in some cases, we do not need to start every from scratch and the paper process is not needed to show to users.
Use tools as Sketch, Figma, Axure, Adobe XD, Balsamiq and so on for designing wireframes that make sense.
Using design software as Sketch, Photoshop or Illustrator to design the actual interface.
TESTING | See how it works
- Prototype should be real enough to get an authentic response in order to validate or invalidate a hypothesis.
- Think critically about what to build in prototype in order to get the feedback.
- Test goal is to find out if the solution works as planned or provides
TESTING IN PAPER PROTOTYPE
Plan the script
Roles: who will take care of prototype, who makes notes, who facilitate and talk to the users during the test
What to test (steps- results)
Beginning of the test
Introduction to users ( brief user privacy ethics, explain the scenario what is product for or in what situation, imagine you are now….)
Ask users think aloud so we can know what is they think right away at that moment
During the test
Take note how users act, do and how well they understand the task.
Give a clear instruction to user
TESTING IN DIGITAL PROTOTYPE
Invision is a good tool for mock up the prototype that allow users click and test the prototype without actual coding.
ITERATION | Get feedback and develop further
Develop the design based on real feedback from clients