The Design Process I flow through encompasses three core tenets:
To achieve a successful solution requires having appropriate understanding of the circumstances.
"Circumstances," here, being pretty much whatever is associated with the problem. Which could be a very large list. But, the more pertinent information one has, the more they can build upon when developing potential solutions.
This journey involves a lot of listening, note taking, sketching, and question asking, and hypothesis making.
A sample page of notes and initial ideas around a page component. These pages tend to be a running dialog with myself as I step through sketch iterations, making adjustments as new questions arise. I find the travel of thought to be beautiful.
The classic question, "What is Design?"
To me, Design can be summed up as, "Intentional decision making."
Taken one step further into the specific domain of UI/UX, it is the, "Intentional decision making guided by the information obtained from testing and observation relating to user interactions."
So the significance of this exercise is to analyze and refine ideas by the surrounding constraints (be they brand standards, test results, product limitations, etc.) to arrive at an optimum, valid solution.
Screens generated here are still relatively low-fidelity, but truer to scale and with mock data.
A screenshot of a portion of workspace. I tend to keep a page of scratch work where I step through ideas and workflows. They can become quite extensive as I track how one change can impact the rest of the flow or product.
Decisions are important, but without proper execution will fail to deliver.
This is where an idea becomes realized in the eye and we can get better grasp of how it will live when implemented. The closer it is to reality, the better people can respond. Accurate application of system styles and behaviors is required.
But craft is not limited to just the final visuals. Effort and attention should be applied to all parts of the process, especially those shared between teams and colleagues. Items such as adhering to naming conventions and clean work files are crucial for working collaboratively.
It's valuable to take the extra time and energy to make sure files are clean before handoff. Good naming and structure help immensely when working collaboratively. I tend to structure my layers similarly to what their HTML structure would be.
Every aspect of Design Thinking is synchronous.
None of these tenets live in isolation.
Sometimes this process is long and full of discoveries. Other times it is short and direct.
I believe one of my strengths is being able to quickly understand systems, and scenarios, to a high degree from which effective solutions can be designed, all while maintaining a high quality of craft throughout.
Design Thinking is a skill I am passionate about and practice in all aspects of my life, not just product design.
I hope the ideas presented here help give some insight into my approach. If interested, take a moment to explore some of the products I've been a part of, or get in touch if you have any additional questions!