Before drawing the prototype, all need to do what else?

In the eyes of many partners, product managers may be drawing prototypes, writing documents, and then going around tearing up the world and drawing cakes. But in reality, these only account for a very small part of our work. Drawing prototypes and writing documents belong to the final output stage of product design, so before this, we need to do what work? Today, I'll take the recent project "Facility Management - Warehouse Management" as an example, which I temporarily helped my colleague to do, so I also started from zero. For such a project, how do I start?

First, learn and understand the whole life of the equipment business is how? At the same time to know the warehouse management is in what part?

By reading and communicating with colleagues to understand that equipment management will involve the following business:

equipment procurement stage - equipment acceptance stage - equipment into the warehouse - equipment out of the warehouse - (maintenance program, inspection, quality control management) - Equipment loss reporting?

Then each stage inside the storage of many business details, so from big to small, and constantly deep into the business details, you can from the whole to the details, from macro to micro control.

Second, understand the purpose of the demand and the scope of the demand

In the first step we have understood the entire business process of the equipment, the next step is to analyze the function we want to do:

Treasury management needs purpose: to achieve the physical and financial accounts in line with the physical and classified ledger in line with the same time to meet the needs of reporting to the superiors.

The scope of warehouse management requirements: including equipment in, equipment out of the warehouse, equipment inventory, equipment transfer, equipment loss, etc., but also need to generate a variety of reports, in order to report to the superiors.

Third, understand the function of the target user and its user goals.

Target users: purchasing teachers, warehouse teachers, equipment section head, section staff and other personnel to participate in collaboration at the same time.

User goals

Purchasing teacher: can realize the development of medical equipment procurement plan and goods acceptance.

Warehouse teacher: after the acceptance, can complete the medical equipment warehousing and out of the warehouse, and at the same time can generate warehousing and out of the warehouse report data.

The person in charge of the equipment section: for the hospital's overall equipment income and expenditure macro-control. The real realization of saving resources, improve the level of information management of the hospital.

The department: the realization of the equipment request to buy, claim, report loss and other needs.

Fourth, to understand the function of the collaborative process between the various user roles is how, respectively, responsible for what?

Because it involves multiple roles involved, surely the division of responsibilities, what each person needs to do, are to match the actual business scenarios, otherwise the system is designed, it is difficult to match their actual work.

This link will produce the "offline business process map". This includes what roles are responsible for each link, and what does each role need to do? On the one hand, this flow chart is to help you clearly understand the actual business, on the other hand, it is for the later development students to understand the business process.

Fifth, user verification

The above four steps, are we in the office to think and ask, but you do not know whether the actual is really so? You will find a lot of doubts and problems, so you need to organize the problem, go to the hospital to run, the actual verification of these issues and business. I then went to the teachers of the First People's Hospital in Hangzhou to conduct surveys and interviews.

Six, come back to confirm the business process, the user collaboration process.

After confirming the good, come back you need to once again organize the business process as well as clear business-related details. Here will be the output of the "business process map", "user role collaboration flow chart".

VII. Clarify the impact of the existing business on the system? What is the data flow of the business?

The company's equipment management platform has been iterated to version 3.4.0 by now, so you need to consider what is the impact of the inbound/outbound business in the system? How does the data flow go? Output the Data Flow Diagram.

Eight, the product architecture diagram and user operation use cases

Related business you have understood, next you need to clarify the scope of the inbound and outbound function and architecture. At the same time, you need to draw the user in the scope of these functions, which functions can be operated. Here I will output "product architecture diagram", "user operation use case".

Nine, page architecture and page fields

In the eighth step, you have completed the product architecture diagram, then in this step, you also need to sort out the page architecture, and then each page of the required fields to organize. Here I will output the Page Architecture Diagram and the Field Lookup Table.

When you get to this point, you can start to draw prototypes, but of course, you will still have a lot of problems in the process of drawing prototypes, and you need to keep polishing and refining your details.

and

I'm Yu Xiaozhi.

I'm a product manager and entrepreneur, and I've been called the "best storyteller of the post-90s".

and

I'm Yu Xiaozhi.