Product design is less about screens and more about decisions. In this lesson we follow one feature from a support ticket to release and look at every point where a designer changed the outcome.
You will map the double diamond onto that story and see why teams loop back to research more often than diagrams suggest.
What you will learn
- Map the double diamond onto a real feature
- Name the roles a designer works with daily
- Write your first problem statement
Exercise
Apply the method to your current project, post your result in the cohort channel and bring one question to the next critique session.