How to simplify our product?

How to simplify our product?

Possible answers (6)

. We should structure the product's possible actions into workflows—for example, a purchase workflow, a profile update workflow, etc. Once we have outlined and grouped the processes, the next step is to simplify the steps in each process. The rule of simplification is always the same: product components are always much more complex to the users than we think. Thus, anything we consider as “not easy” should be simplified.
. If the problem is in the number of objects, we should come up with new methods of categorizing them according to Miller's law. Having too many objects is always bad even if we think that users are used to it.
. Another thing that complicates the product could be a component that is falling out of the product’s context. Also, we should avoid objects unusual in their type and shape as it is often causing an information noise (, ).
. Sometimes, to simplify product concepts, it can be useful to use pictures, small animations (.gif), etc. The simplest example is replacing one instruction of 70 words with a 4-second long .gif animation explaining the same.
. The absence of complaints does not mean that the product is ideally adapted to users' needs. We need to determine which product components are being ignored by users and decide what to do with them.
. We can replace some of the visible functionality by converting it into "system hints." This will help to significantly "lighten" the interface. The idea is to show the user some buttons/actions only when needed and hide them the rest of the time.

Related questions

How useful you found this?
Not useful
1
2
3
4
5
6
7
8
9
10
Not useful
Very useful
Thank you for your contribution!
previous bias
next bias
keepsimple logo
picLog In
My ProfileSettingsLog Out

UX CORE GUIDE

arrow downHow to use

UXCG is a free tool that helps teams detect cognitive bias-related UX problems across all product stages, whether you're prototyping, testing, or improving a live product

How to use UXCG

  1. Choose your product stage below;
  2. Find your question (either manually or through search);
  3. Read possible answers.

Each answer explains how cognitive biases relate to your specific situation. Since you understand your context best, you can apply the insights directly. While the tool doesn't provide ready solutions due to each case's uniqueness, it reveals new perspectives backed by cognitive science.

Label description
Questions related to in-house team members cooperation (product, development teams and others).
Questions related to product development stage (from concept to first public release).
Questions related to sales, marketing funnels, prospects and leads communication, and overall product packaging.
Questions related to user interaction with actual product and its features.
Questions related to product analytical data analysis.
search icon
Select your product stage
#10.

Why do users complain about the quality of our support?

#30.

What common mistakes do we make when dealing with product analytics?

#41.

What should we do if our colleagues’ stubbornness is hurting teamwork?

#43.

What to consider when planning product releases?

#45.

What to do if our team members do not share their opinion?

#50.

How to deal with an incompetent colleague/manager?

#59.

What should we consider when referencing political, social, or economic events in our messages?

#61.

What should we do if our team wastes too much time on minor details?

Be Kind. Do Good.