This is my process.
From corporate websites to dating apps, every project requires a unique approach. However, my process is always the same. This is how I deliver a thoughtful, well-executed, and thoroughly tested solution every time (as explained by GIFs from some of my favorite movies).
1. Define the goal.
If I don’t know why I am designing, then I can’t be expected to know what I am designing. To do this, I usually implement the “Get-Who-To-By” briefing template. This is arguably the most important step in my process. Once I have this information, I am set up for success.
2. Know your audience
I like to construct a point of view based on the needs and insights of my users. What are their pain-points? What are their priorities? What value can we provide them? If I can empathize with them, I can solve their problems. This is a great time to develop user personas.
3. Do the research
It helps to be an (armchair) expert when it comes to your client’s industry. When in doubt, Google is your friend, but I always like go straight to the source. Clients love answering questions about their industry. This is also a great time to look at competitors and familiarize yourself with any emerging trends.
4. Collaboration is key.
I start my rough ideas with pen and paper. Next comes inspiration gathering, whiteboarding, and mockups. Real-time feedback and collaboration within the team is essential during this time. This is usually the longest step in my process and involves people across multiple business units collaborating together to find a unique design solution.
5. Put it out there.
Next, my work gets put in front of stakeholders, clients, and users for feedback. Sometimes this throws me back to step four. If I need to defend my choices, I always do so with strong data points if possible. However, if someone doesn’t like the color green because of a traumatic childhood event, there’s not much you can do. That’s actually a true story, by the way.
6. Follow through.
Whether it’s creating a comprehensive style-guide the entire company can use, collaborating with developers at an outside agency, or being available over the weekend before a product launch, I do everything I can to make sure my team is supported after the design is finalized.
7. Lessons learned.
Taking the time to look back on what went wrong, what went right, and any important lessons learned along the way is extremely important to me. Whether it’s a new skill I picked up, a new software I learned to use, or a new connection I made at the company, every project allows me the chance to grow as a designer.
“If you recognized (and enjoyed) the movies above, we might have more in common than just design!”