This paper deeply discusses the design evolution of B-end products, starting from the design concept of "one stream", and proposes strategies to greatly improve the user experience while satisfying complex business logic. So, how do you balance complexity and ease of use to create a B-end product that is both efficient and friendly? Let's read this article and study it.
When designing system products, especially in the face of B-side complex logic product capabilities, the common and common way is to classify and classify various product functions in the form of one, second, or even more levels, and list and display them in turn on the front-end pages that users can view and operate.
When users find the list of functions that need to be operated and determine the sequence of each function that needs to be operated, there are several reasons for the existence of this product design pattern:
- In the default common sense, B-end products should pay more attention to complex business processes, and the focus of product design is to accurately and error-free design and develop complex business processes to achieve the normal execution of business processes.
- B-end product users have a high enough understanding of the business they are responsible for, and according to the principle of "it is not difficult for those who will know, and those who are difficult will not", it is not difficult for users to operate the functional modules of each product listed;
- The work stability of B-end product users is high and the requirements for product ease of use are not high;
- Due to the historical limitations of IT technology development and the limited investment in human resources, adhering to the principle of "giving priority to solving key user problems with limited capabilities", we will not invest too much in product functions within the scope of normal development of non-business processes.
The subjective slackness and the lack of objective stimulation conditions lead to the fact that the current B-end products do not need to pay attention to the wide dissemination and application of the product user experience design model.
With the continuous iterative update of IT technology, the implementation method is becoming more and more convenient. Returning to the users served by the product, users are living and emotional individuals, and they will also encounter many product systems that are extremely smooth to use in life and work, which greatly improves the user's product experience while solving the user's business pain points.
Users will compare, there will be imbalance in the hearts of users, new demands will arise in the hearts of users, and with the further development from the incremental market to the stock market, the stability of users in the post is also decreasing.
With the development of the times, all these factors have prompted us as product managers to re-understand and face B-end product users, respond to the pain points of B-end users, and provide B-end users with a product operation experience comparable to C-end products.
It is unavoidable that B-end products are more complex than C-end products, so how to provide B-end users with the user experience of C-end products while meeting the requirements for the smooth operation of B-end complex business logic?
Returning to the essence of product design, the product is to solve the pain points of users and serve the smooth and effective operation of the business. Although faced with such complex product logic and product functions, from the user's point of view, when dealing with specific business problems, users only focus on the product functions needed to solve the current business problems, and need to know what kind of logic should be followed to solve these product functions.
Then the product design concept of "one stream" is a very effective practical direction for product solutions.
The product design concept of "one stream" can realize the self-combination of required product functions based on the business scenarios faced by users, show users to users, and give users a reminder of what logical operations should be followed.
"One flow" has changed the original logic that users need to clarify the business problems they need to solve, and then decide which product function list they need and decide a reasonable order of operations, but now they only need users to clarify the business problems they need to solve, and the system product will "tell" users what product functions they need and in what order they should operate in what order. (Figure 1)
Figure 1 Comparison of the old and new design ideas of B-end products
The complex product logic of B-end products prompts that when designing product solutions according to the product design concept of "one stream", we should adhere to the direction of "simplifying front-end + complex back-end".
On the front-end page that users can view and operate, users are shown three parts: the flow track of information in the business process, the current status of the business, and the next executable action.
Leave the complex logic on the back end and leave it to the product and R&D. Taking the B-end sales order scenario as an example, a sales order will generate multiple delivery orders, and each delivery order will generate multiple acceptance orders. (Figure 2)
Figure 2 An example of a "One Stream" product design
Such a design can greatly improve the user product experience on the basis of realizing the smooth and orderly progress of the business, and truly achieve user-centric, user-centered and user-focused product design thinking focusing on solving user pain points.
This article was originally published by @Practice Knowing and Doing Unity on Everyone is a Product Manager. Reproduction without permission is prohibited.
Image from Unsplash, based on the CC0 license
The views in this article only represent the author's own, everyone is a product manager, and the platform only provides information storage space services.