​UX/UI Design

Define the problem: Before we can move into any design, we need to understand why we’re doing it. This can only be done by clearly understanding the problem we’re trying to solve.

Clearly define our users: We need to know for whom we’re solving the problem. The contextual things they might face in their day-to-day life can help us understand how to best make our product work for them. And although we discover these things in research, we need to clearly define them before we start building.

Ideate: We utilize design practices like story mapping and sitemaps as the lowest fidelity versions of the product we’re building. These help us understand the complexity of the product and hash out important questions before we get into things like page layout and UI.

Define the core feature set that will best solve the problem at hand: Once we understand the core functionality, we use user stories to hone in on what matters and cut the fluff distracting from the core experience.

Low-fidelity wireframes: Once we understand the direction of the product and the general hierarchy, we start ideating what these actual pages look like. In this stage, we’re both trying to understand things like layout and what content goes where. However, this stage is also the next filter for complexity. Here, we can start to get a better understanding of all the content and subpages that will need to exist.

High-fidelity wireframes/design system: At this stage, we put together all of the pieces in their full fidelity and complexity. We build out systems that make changes and hand them off to developers who can build out pages that can be utilized in usability tests.