Navigating the Design Process

Introduction

Design is an essential aspect of any successful product or service. It’s the process of creating something that is not only aesthetically pleasing but also functional and user-friendly. However, the design process can be complex and challenging to navigate. This article will provide a comprehensive guide on how to navigate the design process, from initial research to final delivery.

What I’ve learned about the process

As a designer, I’ve learned that the design process is not just about creating something beautiful. It’s about solving problems. Aesthetics and animations are all secondary to creating solutions that meet the needs of the users. Nothing matters if nobody uses your software so make sure your focus is on the problem and not outside noise. This requires an iterative process, and it requires leaning into the iterations to acquire a deep understanding of the problem, the users, and the business requirements.

What you’re getting into

Before you start navigating the design process, it’s important to understand what you’re getting into. Design is a collaborative effort, and you will be working with a team of individuals with different skill sets and backgrounds. Don’t think you are going to disappear into Figma and come back with a beautiful design. It’s essential to communicate clearly and effectively with all of your team members to ensure that everyone is on the same page. That is especially true for the product trio. The product trio consists of a designer, product manager/business analyst, and tech lead. Each member of the trio brings an understanding of the user, business, and technical requirements. A successful project adheres to all three types of requirements so it’s essential to work closely as a trio to meet the demands of all three requirements.

From a design standpoint

As a designer, you are the gatherer of information. You are responsible for understanding the problem, the users, and the business requirements passed to you by your product manager and through research. Making an elegant app is the payoff but never forget that discovery is the backbone of the product and all of its features. Take all discovery phases seriously and conduct thorough research to ensure that you have a deep understanding of the problem and the users. That is how an elegant solution comes to life.

Initial Research

The initial research phase is essential for understanding the problem and the users. This phase includes conducting tests, interviews, and gathering business requirements. Additionally, you should create an epic, which is a high-level overview of the problem and the solution.

Sketches

Once you have a deep understanding of the problem and the users, it’s time to start sketching. Rough sketches can be done with pencil and paper or using an app like Concepts. It’s essential to focus on core concepts while sketching. There is no need for perfection since the motive is to lay down the highest level of architecture. This first foundation of the app is critical, and multiple rounds will be necessary. Take the app in a few different directions to broaden the possibilities and don’t be afraid to throw out the bad ideas. Heavily involve the tech lead and product manager in this phase and remember to focus on the highest levels of architecture. Don’t forget to user-test your assumptions.

Wireframes

Wireframes define the architecture at one level deeper than sketches. They include no color and no fluff with a focus on the hierarchy of copy, CTAs, navigation, and other elements. Figma is an excellent tool for creating wireframes and allows for easy prototyping for user testing. The tech lead should review the wireframes for feasibility, and the product manager should ensure they meet the business requirements before moving forward.

High Fis

Once the wireframes have been tested and approved, it’s time to create high-fidelity designs. These designs should be pixel-perfect and built off of the tested wireframes architecture. This is where your color pallet, UI components, spacing, animations, and other details are incorporated. Multiple rounds will definitely be necessary but life will be much easier after strong sketching and wireframing phases., As always, it’s essential to involve the tech lead and product manager in this phase but at this point, there should be no surprises. Don’t forget to prototype and test these designs with users.

Cards and Refinement

Once the high-fidelity designs have been tested and approved, it’s time to meet with the delivery lead to ensure that the product is ready for delivery. This includes refining the designs with the entire technical team, creating JIRA cards, and ensuring the product or feature is clearly broken down and effectively communicated. Meeting with the technical team can be short and at the top of a refinement session. One of the perks of keeping your tech lead involved during the whole process is that they can help explain the new feature in more technical terms and aid with any questions. The entire trio has signed off on the feature at this point so they will be allies in your cause.

Conclusion

The design process is a complex and iterative journey that requires a strong team and effective communication. As a designer, you are responsible for gathering information, taking discovery seriously, and bringing the product to life through sketches, wireframes, high-fidelity designs, and refinement. The product trio of the designer, product manager/BA, and tech lead work closely together to ensure that the design meets business requirements, technical feasibility, and user needs. By focusing on the highest level of architecture and prioritizing user testing, you can create a successful product that meets the needs of both the business and its users. With dedication, focus, and a passion for design, you can also navigate the design process and create impactful products that make a difference in people's lives.