In the impression of most Internet people, B-side designers drag and Number List drop components for splicing, just like building blocks. It leads to saying that the B-side UI designer is in a passive position in the project process. If you want to get out of this predicament, you must first understand how to describe the core value of the B-side business?
This article mainly explains the different commercial value/user differences of the product itself/delivery method from three perspectives.
1. 3 confusions about the product itself
Three questions that are often discussed at work:
What is the product itself?
What is the difference in the commercial value of different types of B-end products?
And how to layer and manage users on the product side?
So how can we as designers understand these issues? Then we will explain them step by step.
1. How to describe a B-end product - what is the product itself?
In projects, we often encounter such scenarios:
Copy from this site
It's a fake demand
The boss says……
Competitors do the same...
This module wants to highlight...
other etc.
The root cause of this type of scenario is that the product or the designer does not know the positioning of the product, which often leads to not knowing how to make decisions. So what are we going to do with this scenario?