Digital product minimum

What

This UX minimum named “Holy 6“ are plays that are necessary for the basic quality of each minimum product. For good user experience, it is necessary that designer 1. understand the problem, 2. solve the problem by design and 3. test it to see if the design works. This UX minimum is a package of methods that helps fulfill the essence of UX design which is essential to take as one.

Why

  1. To understand the problem
  2. Solve the problem by design
  3. Test it to see if the design works

The UX Minimum

For good user experience, it is necessary that designer 1. understand the problem, 2. solve the problem by design and 3. test it to see if the design works. This UX minimum is a package of methods that helps fulfill the essence of UX design which is essential to take as one. It consists of these necessary steps: Research → Prototype → Testing

????Research → User stories → IA & flow → Prototype → Testing → Presentation

Recommendation: When each step is done, we recommend going through it with a stakeholder and seeing if it is all. After approval, we should not go back to the previous step. This protects us from changing the assignment at a later stage.

1. Research (1-3 days)

It doesn't matter what all is behind this step. designer focuses on good user experience and is responsible for it. Therefore, he should get to know the user, and design for him within the prioritization of time, feasibility, vastness, and our clients' business model. In practice, this research is just a list of notes or for example flows from competitors, “moodboards”…

Why:

  • To understant the problems from the user prespective. It does not mean 100% adapt to the user. In practice, it is a compromise between business, technology, user; price, time, scope.

Sources:

  • Business assignment
  • Bussines questions
  • Requirements
  • Bussines data
  • Statistics (analytic tool)
  • Competitors
  • Technologies
  • Engineers plays
  • Finding out technical limits and opportunities via research meetings
  • User
  • Proto-personas
  • User-personas
  • Qualitative deep interview
  • User Journeys
  • User flow & qpestions
  • Quantitative questionary
  • Pre-testing
  • Product users research
  • User journeys
  • Design
  • Brand assets

2. User stories (1-3 Days)

PM assets, business assignments, technical limits and opportunities, user needs are translated into user stories. This step is playful mainly for the designer to have an idea of what will be on each page. However, for better clarity, it is good to group individual user stories into groups together. It doesn't matter which tool you choose for noting user stories, the sheet must be clear and easy to share. This list can be single-purpose, but after agreement with PM it offers other work options (user stories roadmap, planning).

Why:

  • For the designer to know what they will draw on the page, and vice versa, what should not be on the page.
  • See the context of individual user stories for better work that will come later.

3. User flow (1-4 days)

Then we translate user stories into user flow. Each user story must be implemented into energy flow and connect into one flow with starting point and ending point, because later, it can be difficult. We will create a kinda wireframe without a layout. In the end, we find out the energy flowing through the flow, how many pages and modals there will be, and we see what is happening on the backend, and we can prepare for it.

Why:

  • See how energy flows from the landing page through the chain of actions and reactions to fulfill the key action.
  • See the flow of energy from the user's perspective and the flow of backend energy and see it as a one energy flow.
Untitled

4. Prototyping (2-8 days)

When the energy flow is ready, it is known how many pages will be used and which components, the energy flow will be translated into a layout. Pencil and paper, digital tool (Figma, Balsaniq, Axure) can be used for this. The goal is to get to a real design much as possible. The UI is part of UX!

Why:

  • Make a prototype as soon as possible and test it to see if it works.
Untitled

5. Qualitative testing of usability (1 day)

Write a scenario Based on defined questions we prepared short scenario, that led testes thru homescreen to detail of film, settings and searching. Create a prototype that covers user stories or main features. Prototype sould be close as possible to final design with UI. Find testers find 5 participants. Do user testing and repeat, until all negatives turn into positives. And note all opportunities and ideas for further evolution.

Why:

  • To verify the designer's hypothesis
  • Find all the negatives and turn them into positives
Untitled

6. Presentation (1 day)

In addition to the final designs, we should prepare a presentation that will support the designs with proof from the last testing that the design works. We should also present our process to show what has been done and show the context.

Why:

  • Thanks to the test results, we will facilitate the sale of our designs, show the essence of UX design, and the designer will have a clear conscience.

Asset:

  • Template
Untitled

Next steps

  • Finish visual design
  • MVP definition of designs with front end. Specify what will be developed.
  • More testing and improving