It is often blocked by R & D and operation? You need to master the 8 steps before realizing the requirements

The product manager and I often complain about it , The need to work hard , What we get is not recognized by the team and the demander . When communicating with R & D , Almost speaking on your knees , After the launch, the demander came to roast , It is also expected that there are still some gaps .

First describe a scene , See if there is your shadow inside ：

1. You receive a request , Immediately think about how to solve this problem , When I think about it, I begin to draw prototypes , Soon draw a prototype and show it to the leaders , The leader pointed out a series of problems directly .
2. After several rounds of revision , Finally, it enters the requirements review stage , At the requirements review meeting , Scheme developed 、 Operational challenges , Open it directly at the review meeting , A requirements review meeting , To carry out 1-2 Hours , Finally, a second review will be conducted .
3. After the launch , The business side responded that , In fact, this and what they want , There are still some gaps . You feel so tired , Not understood .

If something similar happens to you , Follow the steps below , Will greatly reduce the occurrence of such scenes .

01 Demand analysis

When we receive a demand , Don't immediately think about how to achieve , First ask the demand side a few questions ：

• This needs to be solved
• After that , What value can it bring to you
• If you don't deal with , What's the impact of that ?

After asking these questions , You generally know the context of this demand , And the priority of the requirements , If the demand side can not even answer these questions , That demand can be rejected .

for instance ： The operation students said that our login system does not meet the current needs , I hope the system can support wechat login . According to the above 3 A question , Let's communicate with the demander , The demand side says ：

“ In the next quarter, we will focus on the transformation of wechat fan purchase , But now the account system only supports “ Email login ” and “ Phone number ” Sign in , After several rounds of operation test , It is found that the purchase conversion of unregistered fans is very low , To a large extent, it is stuck in the registration process , Unwilling to fill in the mobile phone number , Afraid of receiving harassing text messages . Support wechat login , It will greatly increase the paid conversion effect of fans .”

Understand the usage scenarios of the demand side “ Under the wechat system scenario, fans can log in quickly ”, Not doing it will affect the transformation , It is something that must be done . Next, let's move on to the second link 「 Hand drawn wireframes 」

02 Hand drawn wireframes

The purpose of this task is to sort out the functional modules of this requirement , And the association between modules , The product can be graffiti on paper . What to do at this time :

1. Is to take the hand drawing , Go to the R & D director , Discuss the feasibility of the scheme , Avoid stepping on a pit that doesn't understand technology .
2. At the same time, let the R & D students participate , Know what the product will do next , What problem to solve .

for instance ： Take your hand-painted map of the login process , Tell the R & D students what problems to solve , After the R & D students read it , The demand is not a big problem , But you have to think about , Registered users , How to associate accounts after logging in with wechat .

After communicating with R & D students , You have added one more “ New and old user associations ” Wireframe .

Next into 「 Product structure 」 Finishing stage .

03 Arrangement of structural drawings

Organize the hand drawn drawings , Let's further sort out the product structure . The output of this stage , Is the definition of the module , Or what problems this module solves .

for instance ： The above example supports wechat login , The functional modules involved are ：

• new 「 The user login 」, Support wechat account login to register .
• 「 New and old user associations 」, solve 「 Old users 」 Log in with wechat account , Bind or unbind the original account ;
• involves 「 Change Password 」 Module optimization ： Pay attention to users who only have wechat login , It is impossible to change the password ;
• In the original account system , There is a security vulnerability in the mobile phone authentication code login mode , increase 「 Current limit for mobile phone number registration 」.

Completed the structure diagram , Start the process sorting between modules .

04 flow chart

Purpose to define roles , Logic rules in the core function module 、 Branching conditions and final results . It also prevents us from missing scenes . There are two things you can do at this time ：

1. Take the flow chart , Look for you leader Let's talk about , See if there is any problem with the process ; If the business is complex , You can communicate with the employer , See if there is any requirement omission ;
2. Communicate with R & D students in advance , Let the R & D students also understand the process of the whole module .

for instance ：

05 Detailed structure drawing

Each functional module , To refine to fields , Avoid missing information , The front and rear data shall be consistent .

for instance ： Or the wechat login scenario mentioned above , The user logs in via wechat for the first time , To get the user's userid、 Phone number , If the mobile number does not exist , Then you need to generate the user name (username). List all the key fields , Re sort out the product ideas .

06 Prototype interaction design

above 5 After that step , That product 80% Your thinking has been completed . According to the team habit , Determine the level of detail of the interaction , If high fidelity prototype is required , Then make the interaction more perfect , Mark where there is interaction , There are logical places to mark the rules . How to draw interactive prototypes is not discussed here , If necessary , You can leave a message to communicate .

Complete the prototype interaction design , Here you are leader look down , Organize a small-scale demand side review , See if the problem on the demand side has been solved .

Tool recommendation ：Axure、 Ink knife .

07 The requirements document

After communicating with the employer , Start writing requirements documents . About requirements documentation , Some teams ask to write doc file , Some just need to be marked at the prototype .

I prefer to write doc file , Because the requirements document is a re inspection and sorting of product output . The first reader of the requirements document is the product manager , Then there is research and development 、 Test and other partners .

There are several key points to note in the document :

1. The first is to write documents according to modules , Be clear about the background and definition of each module ,
2. When there is more demand ( exceed 3 individual ) when , To mark the priority (P0、P1、P2), Ensure that core functions are prioritized .
3. Be careful not to make nouns , Keep the same content consistent .

Complete the above , You can enter the requirements review stage .

08 Requirements review

Now let's get to know each other again 「 Requirements review meeting 」, It's not a PK Workload meetings , But with R & D 、 Test and other team partners' information synchronization , Announce the beginning of the project , More work should be done before the review meeting .

Requirements review is also a process ：

1. Requirements document in advance 1 Days to send to the small partners in the team , Let us know the demand in advance .
2. At the formal requirements review meeting , First, let's talk about synchronization with everyone , This demand , Why do we need to do this , What problems have been solved ; A higher-level one can talk about this demand , What value can it bring to the business or team .
3. First, let's talk about the structure diagram and flow chart , These two explanations are over , The team partners basically understand what the focus of this demand is , Then I will focus on logical judgment .
4. Last , Have a time schedule , Then the team partner fills in , Ensure the rhythm of teamwork , If there is deadline, Small team partners will arrange their time more reasonably .

Last ： Requirements review is just a propaganda , The key points are offline . I hope the above can bring you some help .