Please enable JavaScript.

Coggle requires JavaScript to display documents.

Design Thinking In Depth - Coggle Diagram

- - - - STEP 1:
        
        Observing is listening with your eyes. Practise how to listen with your eyes to find out what people value and care about.
        
        Who: What types of people do you want to observe?
        
        Where to go online: Where can you observe your target audience online? Are they on social media?
        
        Where to go offline: Where can you observe your target audience in the real world?
        
        What things to watch for: What are you curious to discover?
    - - STEP 2:
        
        ENGAGE
        
        We may call this technique ‘interviewing’ but it should really be more like a casual conversation.
        
        BUILD RAPPORT
        
        •Body language (mirror their style)
        
        •The tone of your voice (non judgemental tone, neutral curiosity)
        
        •Facial expression (express sincere interest)
        
        LISTEN MORE, TALK LESS
        
        Prepare some questions you would like to ask, but expect to let the conversation to deviate from the questions. Do not include your own judgement into the conversation.
        
        ASK WHY
        
        Elicit stories from the target users, and always ask “Why?” to uncover deeper meaning.
        
        ASK OPEN-ENDED QUESTIONS
        
        Interviews are more fruitful as a conversation rather than as a survey. Examples of open-ended questions: How, When, Tell me about, Why, Show me. Ask for specific examples. Do not ask leading questions.
        
        DON’T RUSH
        
        When people feel judged or rushed, they close up. Let the conversation flow naturally, instead of being in a hurry to finish asking your list of questions.
    - - STEP 3:
        
        CHANGE YOUR PERSPECTIVE
        
        If the target user is a toddler, try to see the world from his height.
        
        LIMIT YOURSELF
        
        To understand the experience of target users who have eyesight problem, consider applying Vaseline on spectacles.
        
        ENGAGE IN AN ANALOGOUS EXPERIENCE
        
        To understand the perspective of target users who have an injury, consider waxing some hair to have some “injury” to care for instead of real wounds.
        
        DO IT YOURSELF
        
        Experience it as if you are the target user. Note: choose this option only in a non-dangerous situation.
- - - - is critical to the design process because it results in the POV: the explicit expression of the problem you are striving to address. The POV defines the right challenge to address, based on your new understanding of the target user and the problem space.
      - HOW TO DEFINE:
        
        A good POV is one that:
        
        Provides focus and frames the problem
        
        •
        
        Informs criteria for evaluating competing ideas
        
        •
        
        Provide a clear common direction so that your team to make decisions independently in parallel
        
        •
        
        Specific, not broad. Crafting a narrowly focused problem statement tends to yield solutions that are greater quantity and higher quality when you are generating ideas
        
        •
        
        Inspires your team
- - - - ideation is about pushing for a widest possible range of ideas from which you can select, not simply finding a single, best solution. The determination of the best solution will be discovered later, through user testing and feedback.
        
        HOW to ideate?
        
        Technique 2: Sketch-storming
        
        Technique 3: Body-storming
        
        Technique 4: Mind-mapping
        
        Technique 5: Prototyping
        
        Technique 1: Brainstorming
- - - - To fail quickly and cheaply. Committing as few resources as possible to each idea means less time and money invested up front.
      - •
      - To manage the solution-building process. Identifying a variable also encourages you to break a large problem down into smaller, testable chunks.
      - •
      - To test possibilities. Staying low-res allows you to pursue many different ideas without committing to a direction too early on.
      - •
      - To start a conversation. Your interactions with users are often ten times richer when centered around a conversation piece. A prototype is an opportunity to have another, directed conversation with a user.
      - •
      - To communicate. If a picture is worth a thousand words, a prototype is worth a thousand pictures.
      - •
      - To ideate and problem-solve. Build to think.
    - - Start building. Even if you aren’t sure what you’re doing, the act of picking up some materials will be enough to keep you going.
      - •
      - Don’t spend too long on one prototype. Let go before you find yourself being too emotionally attached to any one prototype.
      - •
      - Identify a variable. Identify what’s being tested with each prototype. A prototype should answer a particular question when tested.
      - •
      - Build with the user in mind. What do you hope to test with the user? What sorts of behaviour do you expect? Asking these questions may help focus your prototyping and help you receive meaningful feedback in the testing stage.
- - - - HOW TEST
        
        Show, don’t tell. Put your prototype in the tester’s hands, or put your tester within an experience. Don’t explain everything yet. Give the minimal context so they understand what to do. Don’t explain your thinking or reasoning for your prototype. Let your tester interpret the prototype.
        
        •
        
        Have them talk through their experiences. For example, when appropriate, ask “tell me what you are thinking when you are doing this.”
        
        •
        
        Actively observe. Watch how they use (and misuse!) what you have given them, how they handle and interact with it. Don’t immediately “correct” what your tester is doing.
        
        •
        
        Follow up with questions. Listen to what they say about it and the questions they have. “Show me why this would (not) work for you.” “Can you tell me more about how this made you feel?” “Why?” “What do you think this button does?”
        
        Testing reveals if our prototype meets the user needs, and allows us to refine our point of view or reframe the problem.
        
        Through testing, we can observe how to user reacts to the prototype, and learn more and empathise with the user.
        
        To make iterations and refine the prototype