An introduction on design thinking, process guide

An introduction on design thinking, process guide

1. Empathize

   • Observe what people do and how they interact with their environment gives clues about what they think and feel. And what they need.
   • Engaging with people directly reveals a tremendous amount about they way they think and the values they hold.
   • Observe - Engage - Watch and listen.
   • When you move from empathy work to drawing conclusiones from that work, you need to process all the things you heard and saw in order to understand the big picture and grasp the takeaways of it al.

2. Define

   • Bringing clarity and focus to the design space.
   • It results in your point of view, the explicit expression of the problem you are striving to address.
   • Synthesis of your empathy work that gives you the advantage that.no one has: discoveries that you can leverage to tackle the design challenge; that is, insight.
   • A good point of view is one that:
     • Provides focus and frames the problem.
     • Inspires the team
     • Informs criteria for evaluating competing ideas
     • Captures the hearts and minds of people you meet.

3. Ideate

   • Mode of the design process in which you concentrate on idea generation.
   • Mentally it represents a process of going wide in terms of concepts and outcomes. Ideation provides both the fuel and also the source material for building prototypes and getting innovative solutions into the hands of your users.
   • Combining your conscious and unconscious mind, and rational thoughts with imagination.
     • Building. Prototyping

4. Test

   • when you solicit feedback, about the prototypes you have created, from your users and have another opportunity to gain empathy for the people you are designing for.
   • To refine prototypes and solutions. Testing informs the next iterations of prototypes. Sometimes this means going back to the drawing board.
   • To learn more about your user. Testing is another opportunity to build empathy through observation and engagement—it often yields unexpected insights.
   • To refine your POV. Sometimes testing reveals that not only did you not get the solution right, but also that you failed to frame the problem correctly.
   • Show don't tell.
     • Create experiences.
       • Ask users to compare

5. Prototype

   • is the iterative generation of artifacts intended to answer questions that get you closer to your final solution.
   • To ideate and problem-solve. Build to think.
   • To fail quickly and cheaply. Committing as few resources as possible to each idea means less time and money invested up front.
   • To communicate. If a picture is worth a thousand words, a prototype is worth a thousand pictures.
   • To manage the solution-building process. Identifying a variable also encourages you to break a large problem down into smaller, testable chunks.
   • Start building. Even if you aren’t sure what you’re doing, the act of picking up some materials (post-its, tape, and found objects are a good way to start!) will be enough to get you going.
   • Prototype and Test are modes that you consider in tandem more than you transition between.