Shulou(Shulou.com)06/03 Report--

This article introduces the relevant knowledge of "how to quickly grasp the design ideas and methods of B-side projects". In the operation of actual cases, many people will encounter such a dilemma. Next, let the editor lead you to learn how to deal with these situations! I hope you can read it carefully and be able to achieve something!

Preface

The business purpose of the B-end product is clear, and the business logic and scenario are relatively complex, so there are higher requirements for the designer. To understand the B-end business more clearly, here are some ideas when I switch to the B-end product design:

Change one's role orientation

In view of the fact that I have been doing C-side business before, I am also faced with the design contrast between the two sides. B-C side has different business attributes, product positioning, user groups, visual presentation, and business logic / process. This will be a process of knowledge transfer.

Need to change their entire design ideas and role positioning, from the previous passive requirements to do drawings, only to implement the output of the design draft, to passive to active. We also know that the cooperation between design and products is to achieve and complement each other. In the face of the more complex business scenarios and logic on the B side that we are not familiar with before, try our best to intervene in advance, think ahead, and think about the whole link to actively put forward some ideas about the product when docking with the product demand. you can also help yourself sort out the needs, understand what the fundamental problems are, and what uses and goals are the core behind the requirements. Also find ways to collect feedback from users and business parties, or take the initiative to conduct competitive product research and user research, which not only allows us to understand users' needs and business scenarios more clearly, but also makes it easier to dig out demand breakthroughs, find better solutions and more valuable driving points, and empower the business. No longer just a tool person who passively accepts, but also requires himself to be a "project-driven designer", try his best to participate in the whole link, and look for value points that can be excavated and contributed in each link.

Systematically learn business-related knowledge

After changing my position, because the B-side project I am responsible for is a business that I have not come into contact with before, many business scenarios cannot be treated with the empathy of designing C-end products, and there are higher business threshold and business depth. First of all, I carefully and systematically learn some relevant knowledge involved in the business, which can help me understand the business details of the design work in my hands. Communicate the product requirements with the industry and research team in many aspects, and clarify the business logic of each step. If you don't understand, you can ask and learn more. In the process of product review requirements, you must thoroughly understand the business logic and then consider how to design and implement it. To ask why the business process is like this, the jump of each page, the purpose of each function and what is the business meaning, and so on, several more versions of the style to explore the best solution.

Analysis and insight into product business scenarios

Before the design work is carried out, we first need to analyze what is the background of the product, what to do, and what services to provide to users. Investigate and analyze the status of its competitive products? What is the stage of development now (generally, there are very few competitive products on the b side), whether it is online search or book search to learn about some information in the industry, you can also find some indirect competitive products to draw inspiration. What is the target user group of the product (user profile)? What permissions do users with different roles have? And analyze what important processes exist in the business, what is the intention and value of the design behind it, and which pain points to solve for users or business. After a preliminary business analysis, a general analysis of the use scenario, in the requirements analysis stage, to have some basic understanding of the product itself and the industry itself.

Design execution & Landing Strategy

The logic of B-end products is more complex, and the requirements of interaction and experience should be more cautious. Therefore, the design needs to be more restrained and rational. Although the overall requirement of visual interaction of B-end products is not as high as that of C-end, it is necessary to show each function point clearly and clearly. And let the user know the intention of using each function button or page. Avoid the confusion of function stacking relationship.

At the beginning of product design, we need to comprehensively consider, grasp the general direction of product design and business development, synchronously build a general design framework for the page, a unified visual design language, a general specification of components, and quickly reuse efficiency-enhancing design. that is, more energy can be devoted to combing the product logic and the visual performance of the interaction mode and function. Also should always maintain communication with the industry and research team, from the technical and design level comprehensive consideration, which visual presentation is more reasonable, which is more efficient and more stable, the supporting scene is more comprehensive … Ensure the feasibility of the current product plan. Comprehensively create the consistency of the product experience and achieve an orderly and unified operation experience, in short, the core focus: the interface is clear and easy to understand, the user's operation threshold is low, can quickly use the product, efficient and focused to complete the task.

Review the results and summarize the experience regularly

After the project is online, timely review and summary is also particularly important, which is what I want to focus on next. I can summarize and analyze the successes and deficiencies I have done through review and thinking. summarize those helpful and reusable experiences to precipitate their own methodology. Review is an effective way for designers to improve themselves, and it can also empower the team to improve the efficiency of the team and enhance their value.

This is the end of the content of "how to quickly grasp the design ideas and methods of the B-end project". Thank you for your reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.