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

 

Michal Michanczyk, a Product Designer
with over 13 years of experience.

I believe that the time
has passed for solutions
that are based on assumptions and intuition.

It’s time for the fact to speak. Facts that I will find out for you from the interviews with your real users.

I believe that working on goals, not on predetermined specifications, is the only right way. You do not need therefore prepare boring briefs. We will start our work with my original workshops.

image of Michanczyk person

No long-term contracts. No tricking you into services which you don’t need. Inquiring, workshops approach. Working on goals, not spects. Treating your product as my own. Becoming your partner.

Supposing is good

Finding out is better

Briefing

To make a decision that we can cooperate we need to meet each other and your product. We can make a briefing face to face, but also on a call.

We don’t need to have a brief or specification, but we can also go on without this. I will gather all requirements during our call and workshops.

Strategy

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.

Initial interviews

To get to know your goals, expectations and business market as well we need to make an interview with the expert from your team.

After that, I have a general overview of the product and we can move forward with the next steps.

Kick-off Workshops call

This is the best way to transfer the knowledge from the team to the designer. I’m taking a part as a moderator/facilitator and also support with advice to decide which way we want to proceed.

Mostly this is the most important part of the process because both sides can easily agree on what we want to achieve and define the real problem to solve.

Planning meeting

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.

Discovery & Research

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.

Starting Respondents Recruitment

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.

First drafts

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.

Demo & Planning meeting

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.

Establishing main look & feel

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.

Hard UX / UI job

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

First Prototype Testing session

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.

Demo & Planning meeting

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.

UX Workshops to solve new problems

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.

Hard UX / UI job

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

First Prototype Testing session

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.

Tidy Components & Assets

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.

Report from User-Testing

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.

Clickable Prototype

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.

Strategy for developing your product

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.

The real value of our cooperation isn’t
in UX or Design. It’s in insights you’ll get
to develop your product and grow. That’s an outstanding value.

Product Expert Analysis

If you have an existing product I will make an audit to diagnose what is incorrect and prepare a comprehensive analysis to present on our next meeting.

Real Business Value

UX and Design is worth nothing when it’s not nested in reality. I will prepare the grow strategy and solve a real users’ problems to provide the value they expected.

Clickable prototype tested with users

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

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

Useful assets for developers

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

Backlog for developers

It’s a crucial thing to smoothly involve developers to the process without any hindrance. Atomic stories gathered in the backlog is a standard in agile-oriented environment.

We can use Jira or other solution for that.

Top-notch design

I always care about world-class design
and really pleasant experience while using a product. I like to conduct a pixel perfect approach and I am focused on the great quality of the design even in some edge cases.

case study image

We improve the quality of your life

case study image

Scandinavian Hub for IT employees

case study image

Send packages and receive incomes immediately