I reduce the risk of failure by delivering product design
driven by facts

This meeting is a weekly call or meeting when the designer and the decider from the team will plan the goal for this week and will discuss all needed things to achieve the goal.

The research phase of a project serves many purposes. It is meant to help you understand the market space, the users, their needs and their goals. You can look at it as the stepping stone towards defining the requirements for the product you are about to design.

Research is known to be an essential step across the entire life cycle of a product, not only in the beginning. It will most likely happen every time a new feature is developed, or in order to improve existing ones. It can be done in order to improve conversion rates or reduce friction for users.

The very crucial thing is to start Recruitment as quickly as possible. We need to gather all respondents in our base and schedule a call with them to understand their points of view.

This move allows us to feel comfortable at the beginning of the process. Some initial respondents are in the base, we can smoothly
go on with the project.

The goal is to deliver the first ideas and drafts in the first week. It’ll probably be some low-fidelity solutions, but it’s quite important to collide with each other our imagination about the project and present this to the client and to the end-users.

This meeting is a weekly call or meeting when the designer and the decider from the team will plan the goal for this week and will discuss all needed things to achieve the goal.

On the other hand, the designer will make a presentation about progress in the project and will give to consider some doubts and problems that appeared during the first week.

All projects are done from the scratch, so we need to adjust the proper strategy to your product. There are a lot of factors we need to pay attention to.

We have to say honestly at this stage what activities we need to do and why. For example, user-testing is not included in your expectations and we need to throw this out from the roadmap.

To complete the project the designer has to work deeper in some days and go with some creative, but business-oriented ideas.

Prototype testing is all about getting real people to interact with a website, app, or other product you’ve built and observe their behavior and reactions to it.

Whether you start small by watching session recordings or go all out and rent a lab with eye-tracking equipment, prototype testing is a necessary step to make sure you build an effective, efficient, and enjoyable experience for your users.

This meeting is a weekly call or meeting when the designer and the decider from the team will plan the goal for this week and will discuss all needed things to achieve the goal.

On the other hand, the designer will make a presentation about progress in the project and will give to consider some doubts and problems which appeared during the first week.

As you know well, this is the best way to transfer the knowledge from the team to the designer, but also to make it inversely.

If we have some new, attention needed problems we need to organize the next workshop with the team to fix all issues and push our product forward.

To complete the project the designer has to work deeper in some days and go with some creative, but business-oriented ideas.

Prototype testing is all about getting real people to interact with a website, app, or other product you’ve built and observe their behavior and reactions to it.

Whether you start small by watching session recordings or go all out and rent a lab with eye-tracking equipment, prototype testing is
a necessary step to make sure you build an effective, efficient, and enjoyable experience for your users.

Usually, I use Sketch, Figma and Zeplin, Avocode to hand over my assets. It’s easy to use by developers and really straightforward solutions saving time and money.

Recently, I’ve been using only the Figma software which is a phenomenal tool to cooperate with developers and to create a basic style guide for the project.

All that user-testing should be described in detail to create a general overview for the testing phase.

All crucial conclusions are listed in an affordable version for every member of the team. It’s a solid basis to proceed with the next testing sessions.

To make a general user-testing phase we need to provide a well-working prototype that will be a substitute for the real product.

It allows us to make the very precise UX Research phase without guessing the functionality.

After a really tough design process, we expect to have something more than only a design thing. I am on the same page, so I discovered that we can easily plan for developing the product based on my recommendations.

I’ll gather all insights from the market, place all trends in the report and recommend the best ways to reach the sky.