Study record of product requirement document (iii)

We have structured the idea through the mind map, then we need to carry out the feasibility of the program deduction, verify that the product function is feasible, estimate how much manpower and material resources, so we need to through the prototype design to carry out the relevant requirements of the demonstration. Writing PRD documentation from the outset makes it difficult to evaluate the product in all its aspects, and it is not possible to know the feasibility of the solution, and it is not possible to consider the product visually and carefully.

Prototyping is to help us to think more carefully, and to do the assessment of the needs, but also to the brain of the idea of the output, through the prototype design, we can do product preaching. Compared to the previous abstract text description, the prototype is more clear about the needs of the product, and the design and technical staff or the boss can also be more intuitive to understand the product intent.

Prototype design is to frame the structure of the requirements, so the prototype is also known as wireframe, the specific performance of a variety of methods, related to a number of ancillary software, such as: Axure RP, Balsamiq Mockups, Uidesigner and so on.

When it comes to prototyping this step, it's not just about the idea, we need to have a deeper understanding of the elements on each page and the attributes of those elements. For example, the button element, we need to consider the function of this button, and this function to bring back to the backend and front-end feedback. For example, this button is registered Member button, after the user operation, the first step is to verify that the user input information is legitimate, illegal to give the front-end feedback; legal and back-end communication Verify that the same information is already present, there is a front-end feedback, does not exist then go to the next step, registration success , the feedback after the successful registration is the jump page, or the popup layer prompts the user to complete the information, these are need more detailed consideration. Of course, these finer thoughts are left in the writing of the requirements document, and what we need to do at this point is to show these elements through prototypes.

There are three types of prototype design: hand-painted prototypes, grey model prototypes, interactive prototypes

1. Hand-Painted prototypes

Because prototypes are also known as wireframes, hand-drawn is the simplest and most straightforward method, and the quickest way to express product contours (e.g.).

Hand-painted prototypes are highly efficient at the initial stage of validating ideas, are also easy to discuss and refactor, and are suitable for rapid prototyping when agile is developed.

2, gray mold prototype

The prototype is made of graphic design software, my most commonly used software is Photoshop and fireworks, relatively hand-painted prototypes, gray mold clearer and cleaner, but also for preaching, but need to familiarize the product personnel with the use of graphic design software (such as).

Gray mold prototype is often used in the design of mobile internet products, because of the complexity of the interactive requirements of mobile products, prototyping software is difficult to express the demand efficiently, so the design of mobile internet products is usually the gray model prototype plus interactive documents combined into PRD documents. (After a few days I will talk about the mobile Internet product design)

3. Interactive prototypes

The interactive prototype is a prototype that is done using prototyping software, which is the axure RP, and usually the interaction prototype is designed earlier than the PRD document, and is the final step in the product manager's idea deduction. The prototype, produced by interactive prototyping software such as Axure PR, is almost identical in function requirements to the performance of interactive requirements and formal products, so sometimes interactive prototypes are also called product demos.

Usually the interaction prototype is the product manager and the interaction designer to discuss the determination, and then by the interaction designer, but the vast majority of companies do not have the role of interaction designers, so this kind of work is ultimately responsible for the product manager. (Many companies give visual designers the title of an interactive designer, but the essence of visual design)

About Axure PR Production interaction prototype I do not introduce more here, there are many such tutorials on the network, my personal advice is to learn axure PR, casually understand the structure of the site template, this can help you more structured use axure PR. (Recommended a prototype I painted before, the site has been closed, the prototype was also relatively simple design, there are a lot of missing pages, for reference only to see.) ）

The above three methods are not a gradual process, but are three ways of prototyping, depending on your product requirements and team requirements.

Product managers design prototypes to help them to think more carefully about the feasibility of the program, but also to explain to others, so that the audience can clearly and intuitively understand the product, but also to ensure that the product in the implementation process, according to the product manager initially conceived the needs and expectations of the completion. Therefore, the Product Manager prototype is not very high requirements, as long as the other side can understand understand, the use of hand-painted prototype is the most efficient method.

Study record of product requirement document (iii)