When we are making a Saas product, we understand the product goals, how do we confirm the scope of the project? This article starts from the design scenario of a warehouse product, and explains how to do this link in the middle, hoping to help you.
The scope layer, located in the second layer of the five-layer model of product design, is mainly tasked with defining the functional requirements and content elements of the product. In other words, after determining the overall strategic direction of the product, the scope layer is to address the question "What do we need to offer?" ". This includes a list of features that the product should have, the content elements of the product, the user needs that must be met, and so on.
Next, let's continue to analyze the design and application of the scope layer based on the previous example.
Let's say we're designing an internal enterprise software management for an enterprise. After understanding the product goals and splitting the project, how do you confirm the scope level of the project?
1. Collection of business scenarios
The first step is to communicate with the target user group and gather their needs and feedback.
Here's a small example of a needs survey:
You decide to do a field survey and follow the warehouse keeper to observe his day's work
And then you talk to the custodian.
The warehouse keeper said: "Today's work is very smooth, there is no problem with the quality of the materials received by the production, and there is no return; The quantity of purchased materials is not small, and the quality is also qualified; When it was shipped, the finished product was not knocked out. ”
You hurry up and ask questions, and record everything the storekeeper says, and the day is over.
The next morning, you make a list of user scenarios, get ready to go to dinner, pass by the warehouse, and suddenly find that the production materials have been shipped out.
You hurry up and ask; "What's the situation?"
The warehouse clerk said, "If you want this batch of materials, you need to transfer them to other warehouses."
You say, "Ah, you haven't said this before."
The storekeeper said, "You didn't ask."
After reflection, you decide to start with the following dimensions:
- Understand the job description of the regular warehouse clerk and the planning and cognition of the management personnel for this position
- Refer to the workflow existing in the design of competing products, work backwards to deduce the application scenarios, and confirm with the warehouse keeper to think about which scenarios are available, which scenarios are not, and why
- Sort out the docking people involved in the work of the warehouse keeper, and understand the work scene of the warehouse keeper from the side of the contact person
After re-investigation, the work scene of the warehouse keeper was reorganized:
2. List of functions and information
After completing the demand research and collecting the user business scenarios, you need to think about the system solution, where the system should intervene, how to cooperate with the overall process after adding the system, and what are the corresponding functions?
Scenario examples:
After receiving the excel of the delivery notice, the warehouse keeper downloads and prints the delivery notice, goes to the warehouse to find the corresponding materials, counts and puts them in the delivery area, and the delivery staff signs to confirm the delivery.
Draft Proposal:
The system sends out a prompt to remind the warehouse keeper to distribute the goods, the warehouse keeper can view the corresponding delivery notice on the system, which writes the warehouse and location where the material is located, the warehouse keeper takes the delivery notice and sets off to find the corresponding material, and places it in the corresponding delivery area, and the PDA scans the material QR code out of the warehouse.
Basic business function points:
- Shipment message notifications
- View the shipping note
- Download the shipping note
- The PDA scans the code and sends it out of the warehouse
What business information is required for each function? The current shipping note is as follows:
Think about what information do you actually need today?
On this basis, we can think about the information that other businesses may need at the system level, such as document number, document receipt time, outbound time, etc.
In this way, a list of corresponding functions and information sheets are organized.
III. Concluding remarks
This article only makes a basic explanation, it will be much more complicated in the actual warehouse product design, warehouse business is the foundation of many businesses, involving many user groups, such as planners to know the inventory in transit, available inventory, sales to support locked inventory, pre-sale inventory and so on. Therefore, the product structure is a very important thing to think about, and we will talk about this at the structural level.
Looking back on the product objectives, in the research process, we should not only look at what the business personnel are doing, but also think about the rationality of the overall process, whether there is any business missing at present, and communicate with the managers to understand their management philosophy and whether to make adjustments to the current process.
This article was originally published by @一心 on Everyone is a Product Manager and is not allowed to be reproduced without permission
The title image is from Unsplash and is licensed under CC0
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.