Everything anyone produces inherently comes from their own personal experiences. As a designer, I pull deeply from the places I have travelled, the lessons I have learned, and the people I have met.
When approaching a design problem, I intentionally pause and acknowledge the assumptions or biases I bring to the the situation. Especially when working as a group, I have found it to be extremely beneficial for all members to feel able to be open and honest about their unique perspectives.
A design is not design without discovery and growth in throughout the process of developing an idea. Deeply understanding the people or places that will be affected by the design or product is essential.
I prefer to learn about a problem by researching precedents, interviewing stakeholders, and visiting key locations related the the project. The goal is to delve into their world and identify ways to improve the overall experience
After experiencing a problem, it is important to reflect on the information gathered and theorize ways to meet the needs of the client. Ideation allows me to look at a situation from all angles in order to create actionable connections.
At this point, I create diagrams, sketches, or charts to visualize and synthesize the data collected in the research phase. Attention to detail and in-depth discussion is paramount to be sure that all facets of a problem are addressed appropriately.
Once I have identified possible solutions; they must be built, tested, and analyzed. Prototyping is such an exciting and critical step. It is the point where I learn if the interpretations of my research were made with empathy, or if I can gain insights to iterate or improve my assumptions.
Trial and error is a beautiful thing. Failing, learning, and trying again only brings about wisdom for the next design problem.
Rarely, a project is ever truly “finished,” even if it has been introduced into the real world. The design will most likely require updates or refinements to further adapt to our ever-changing environment.
Additionally, it is important to be able to verbalize the purpose of a design easily to anyone—especially if the person trying to interpret the solution does not have a design background. It is unfair to expect everyone to speak the jargon of our industry.
A successful design solution should be able to be expressed and presented in simple terms.
