Click on the blue word to follow my ↑, continue to get product design related content
The flow chart posted in the last chapter is very vague because it involves the company’s confidentiality. I have redrawn several diagrams using other products and businesses:
Business module and business association: this part mainly sorts out how many businesses the system needs to design, and what is the association between each business (what data to accept, what data to provide, and what data to produce).
Note: These are large modules that need to be refined during the design process.
Business decoupling is about simplifying complex processes.
Normal order management is: receiving platform users order, generate an order information. Process 1: Normal delivery, customer confirmation of arrival, end of order. Flow 2: No delivery, customer cancels order. Flow 3: Shipped, customer cancels order. Process 4: The customer confirms the arrival and applies for after-sales service. …
If you let the order module manage all this, then the order module will be very complicated, very logical. So we want the business to do as few complete things as possible.
Or order management, first define the business scope of the order module: to manage users’ orders and order status; Things to do: Manage order status; Received data: Receive the addition and modification information generated by other service modules for orders (in principle, the data cannot be deleted after being generated.) ; Output data: order details, order status;
And other functions: return and exchange, refund, let other business to deal with.
Back to the main body, I finished my last article on business and roles, so here’s how to design.
How to design (basic data, authority system, business, expansion) four, how to test
Three, how to design
Before we talk about design, let’s make a point. Product design is really difficult to avoid changes, on the one hand, customers need to change, on the other hand, they also need to consciously optimize. (My prototype has already been completely refurbished.) Even I write these articles to optimize, optimize design, optimize business, optimize way of thinking.
When it comes to design, there are mainly two: 1, how to design the prototype; 2. How to design business.
How to design a prototype
Background design structure:
Choose one according to your needs.
Components: Components are commonly referred to as templates. They include: form pages, buttons, input fields, radio, navigation, progress bars, and so on.
Component benefits, help you prototype quickly, improve efficiency.
Some companies have their own Axure components designed behind the scenes (my company has one). If your company doesn’t have one, but you want your prototype to look nice and neat, you can go to:
How the business is designed
Each family does different things, so I try to use a general way to express, take the user management and commodity management business of the e-commerce platform for example:
User management
1. A user has several roles. Assume that there is only one role and use that role to run the business process.
2. Then communicate with customers or imagine the scene (most customers just want to solve the problem in front of them). What are the role types of the platform?
3. Distinguish the business boundaries of each role.
4. Propose how to allow each role to operate on the platform within its jurisdiction.
This time will basically set a thing called “permission management”.
Common Rights Management: page, function, and data rights.
By granting different permissions to different accounts, the scope of services they can operate is limited.
Commodity management
First product management module you need to do:
1. Add, delete, change and check commodities;
2. The article of commodity management mainly focuses on the fields, such as commodity category, commodity postage scheme, participation preference, etc.
3. General categories are provided by the platform, or can be added by merchants themselves. So here we need to consider whether to add: category management module; The new category will become one of the category options when new products are added.
4. Postage scheme, as above.
So, how do you design your business? First of all, you should clearly understand what the current business module needs to do, generally draw a flow chart, and then constantly explore the boundary, and then consider whether new modules are needed to cooperate.
Next section: How to test.
One final piece of knowledge:
Background product design, we should try to reduce the degree of business coupling. Unless the data transfer type is defined, avoid data changes in service A and affect service data changes in service B.
Here’s an example:
The scheduling system, because it’s automatic, we set a lot of rules before we schedule. Such as:
1. Classes cannot be arranged on Monday morning.
2, the first and second section of the morning can not arrange PHYSICAL education;
…
After the system arranges courses, the courses will be arranged in the class schedule according to the restrictions and some rules.
After that, the school changed the rules so that classes could be scheduled on Monday mornings and not on Tuesday mornings. What about the classes already filmed? My answer is: leave it alone. Either rearrange the class or adjust the class one by one.
1. It seems that it is ok to move the class from Tuesday to Monday, but what if the class cannot be arranged on Monday or Tuesday? Move to where?
2. Set the positions that cannot be arranged directly as empty. If there is a misoperation, who will fill in the class? Users make their own decisions and let users modify them.
The principle here is that rules constrain the process, not the outcome.
Not exactly, just one of the basic rules I set for myself right now.
Product design related content, follow me ~
