“Everything is designed. Few things are designed well.”- Brian Reed.

I believe in simplicity and efficiency when designing products. Always remember, that you design for people and not for the latest device or feature. You need to fulfill user needs in a friendly and easy way. To do so you must understand their concerns, fears, and goals.

To design things well, you must have a design process that you believe will work well for people that will use your product.

A design process is an essential part of creating good and efficient products. It helps to build a good relationship between user and product. Here is my design process that I use when creating a design.


Before jumping into the design I always make sure to ask relevant questions in order to discover the key information that will drive design strategy and will help me to understand the problem I’m going to solve.

“When the why gets stronger, the how gets easier.” — Jim Rohn

I’m starting with Stakeholders Interview asking them relevant questions about the product I’m going to design and what is the must-have and nice- to- have features this product should involve in their opinion.

After that, I’m turning into Competitive Audit​ and see what competitors have on their plate, what their strengths and weaknesses and how the product I’m going to design can take advantage.

The next step in my design process is User Research​. It’s very important to understand for who you are creating the product. What are the user motivations, behaviors, and needs? Once you understood for whom you are designing the product, it will be much easier to provide a better experience.

Market Research is not less important. Before you jump into a design you must understand if the product you designing relevant to the specific market so you can make the right commercial decisions.

Stakeholders Interview​ | Competitive Audit​ | User Research​ | Market Research


Design solves a problem. In order to provide a solution, I first need to understand the problem. Going through brainstorm and trying different approaches I provide a pixel-perfect design at the end.

First thing first I creating a Mood board and collecting designs I think can bring me some inspiration both for and UI.

After that, I start creating Wireframes for the product and creating user flow for different scenarios including some edge cases that might pop up.
This is an incredibly important step since it will be a skeleton for the whole product. Once you will define the whole user journey of the product you will dramatically reduce mistakes and undefined use-cases.

Once I have wireframes, I can jump into Design. For complex projects, I will start with the Design System to keep things consistent.

A design system unites product teams around a common visual language. It reduces design debt, accelerates the design process, and builds bridges between teams working in concert to bring products to life. Source

Here is a great book with tons of useful information.

When a design is ready I Prototype all screens, make all interactions connected usually using Invision. And when necessary adding a Motion Design to navigate the user to desired interaction. This step helps me to imitate the real product.

The prototyped version then tested with the focused user group. The User Testing step is critical when creating a good product. The users provide you early feedback before the product is developed. This helps you to tweak the product and see the missed or confusing parts of the design.

Mood board | Wireframes | Design | Prototype | Motion design | User testing



Working with developers in a way that works for both designers and developers is an essential part when it comes to creating good products.

Making sure to provide all relevant information to developers that will bring the design to actual working product. Proper design deliverables are an essential part of the full product cycle. I’m responsible for checking UI discrepancies.

Design review | QA tests

Evaluation & Optimization​

Inform design decisions along the way.​

After the product is launched it’s important to measure all relevant data. No matter how well-researched your UX decisions may be, it’s impossible to predict all possible use cases.​

You will need to collect the data that will help you to study how users interact with an actual product, and what are their pain points that you could improve and phase two of the product.

When possible to collect User Behavior Feedback always do it. You will learn a lot from this feedback. It’s an eye-opening experience.

The last step is collecting UX KPIs.

Key Performance Indicators, also known as KPI, are quantifiable measurements that help an organization define and track the progress toward its goals. Source

You can read more about 5 UX KPIs You Need To Track in this article.​

Collecting data | User behavior feedback | UX KPIs (Key Performance Indicators)​

Thanks for reading!
Hope this was helpful.

Source link


Please enter your comment!
Please enter your name here