When we first get in touch with a new client we try to get as much information as we can about desires, barriers, deadlines, preferencesPreliminary questions and meeting
- A few general questions about the target audience, competitors and existing design materials
- Short meeting where we go through the requirements of the hypothetical customer & creating the first user journeys.
- Set up interviews with users of the target group to validate personas and complete the customer & user journeys
- Research the competitors, get information about features, advantages and disadvantages
- Design mood boards for the product
- Schedule the project tasks in detail (weekly plan for at least 2 months and milestones for the rest of the project)
Prototyping & usability testing
We always show everything to the client the moment it’s ready, as it is the most important thing that they know about the UX design process steps.
We always start with sketching. It is the easiest way of visualizing our ideas. We usually force ourselves to create three different versions for solving a particular problem. It makes us think so we wont get lazy. We always show everything to the client. Always. Even the sketches, because it helps the client understand the evolution of the process and our way of thinking.
When we have a few good ideas and know how the main structure of the application will look like we start building a wireframe and the prototype. If were in a hurry and the product is a simpler one, sometimes we draw the wireframe or just use the sketches, take photos of them, and use one of the prototyping on paper apps such as Marvel or POP. Otherwise, most of the time we use Axure or Invision to create low-fidelity wireframes and prototypes in order to be efficient and as quick as possible.
- User testing
We work with 1 week design sprints. Testing in many iterations is a must-have when it comes to prototypes. We always validate our ideas based on tests with real users. During the UX design process its very important to understand that the product is for the users and not vice versa.
- Creating a screen flow
In case one of the stakeholders (client, developers, etc.) need one, we create a screen flow to show all the connections between the screens.
Detailed design & A/B testing
So on one side we have our mood boards that we showed to the client who gave feedback and hopefully now we have an idea about what style the application should have. On the other side we have a cool prototype which gives us most of the screens including arrangement, functionality, etc.
- Collecting best practices
We usually look for existing design examples (that can be an app from the store or a project on Dribble) and we collect so-called best practices. We usually use
- Look & Feel
Lets jump to the look and feel. We usually design 1 screen in different versions. the first isa light one, the second is pretty dark and the third is something colorful. Differences can be in the colors, shapes, fonts, icons, light-dark elements, etc. We always ask the client what elements they like from the different versions. If a second round is necessary, we design some more variations with the selected elements. You can read more on this topic .
- Detailed design
The next step of our UX design process is when we design all the pixel perfect screens in Photoshop or Sketch.
- Creating specification
We always create some sort of specification for the developers. A UI kit is always a must-have. We usually create animations for the interactions as they can be used for showing great things to the clients, but it’s a very helpful asset for the developers as well. If you have an idea how an animation should look like you shouldn’t write it down. You should share it visually, as it’s much easier and quicker to understand for everyone.
- A/B testing
We usually use A/B testing to decide which version of the app is better and to get a higher conversion rate.
We like it when the product goes in the right direction. We want to be sure that the application is implemented the way we designed it for a great user experience. There are two possibilities:
- If the development process is parallel with the design, its quite easy to follow whats being built as we communicate with the client/the developers on a daily basis.