Research process to understand fully understand the user. It's all about finding out what the user knows, thinks, and feels in order to be able to solve their problems. Includes analytic research, user interviews, domain research.
That information gets condensed, sorted, and carefully considered in order to inform the next steps.
Once I have a good understanding of the users, my brain is overflowing with ideas and my fingers are itching to start drawing them out.
This allows me to explore early concepts - from visual solutions to architecting the flow of information. Getting rudimentary ideas out quickly for consideration and setting up a blueprint for a polished solution is the goal.
Ideas move foward from sketches to the screen during this step. Iteration happens most frequently here as collaboration happens with visual designers and developers help shape the refined solution.
A fully fleshed out solution includes the overall look and feel of the system. The architecture and consistent behaviors of the elements within the system is also a part of this step in the process.
We'll never know if our ideas work until we put them in front of users. This step of the process can happen any time after we start sketching and include solutions at varying levels of refinement. User feedback helps drive the direction of the design iterations.
Our ideas are only as good as our effectiveness in communicating them. Articulating the design and the design system is critical to insuring accurate implementation for development.
Documentation can include annotated wireframes, high-fidelity screens, site maps, content mapping, or Zeplin projects depending on the development team.