This article non-original, only for personal learning.
demand analysis
Do needs analysis, do not always use "I think ..." "I feel ..." this type of statement needs to be done to explain why this demand, this type of explanation is feeble, there is time to do interviews with users, may Tencent reference 10/100/1000 law (10 monthly user surveys, focus 100 users blog, gather feedback 1000 user experience), only a global understanding of user needs, in order to make human use of the product.
When demand analysis at the meeting, with the rise of brainstorming, the demand increase, full of dozens of vivid and colorful, this is normal, this time as a product manager, do not announce the end of the meeting, direct identify needs, it is very foolish.
I always insist on one point: people not only increase demand for the product manager, will reduce demand for talent is regarded as a product manager.
I've been through a product review meeting after several demands, after I performed prioritize needs, the latter a temporary increase in demand, and unlimited lives to work overtime, to make the final product is neither fish nor fowl, have a variety of functions, no primary or secondary divided, confused.
In general, the demand analysis, personally think that the correct approach is: added a lot of demand in meeting the needs analysis, conduct record, and then back to the positioning of the product above, from the top to think, do not appear and you do a travel APP, plus a social function, various concerns private letters, that's superfluous.
According to product positioning thinking, the most important function of the selection out, and participants were carefully and confirm, including the boss's opinion, asking if the project manager can achieve and so on, the demand will mainly be determined then, after the meeting organize, email confirmation for feedback.
The main function of the selection out of the development, improve the efficiency of the development cycle, rapid on-line product, users can quickly trial and error, through user feedback to make better product experience.
After determining demand, after the design and development process, not an idea appears, temporary increase demand, so the impact of some of the initial product planning and development schedule, in my personal experience, plus the late chaos needs are often of little significance.
Prototyping
After identifying needs, general product manager working on prototyping, and now most of the product managers need to understand the interaction, so you have to know, but also professional.
1, a prototype based on information architecture, depending on the product, I suggest using relatively simple prototype map to show.
Figure prototype impossible by a one-time, you need to be reviewed and a variety of changes, making high-fidelity prototype figures relate to those hoplinks time-consuming, it needs to change, you need to spend a lot of time, give clear remarks like, Improve efficiency.
A variety of colors and shapes buttons appear on the prototype map, UI designer after the design ideas will greatly interfere with, would interfere with thinking, professional people to do professional things.
2, in the process of FIG prototyping, it is recommended to draw a clear operational flowchart, there is a clear idea reference is made to FIG prototype, each function requires a detailed flowchart drawn out of the respective order confirmation process go pass, which is essential.
There is often a product manager in determining demand, will fall directly draw a prototype map, to finally finish the development, we found that the most simple login registration process are a dead end, it really is laughable.
Remember that each function draw the corresponding flowchart.
3, in the process of painting the prototype figure for the functional description determined to make use of positive words, do not use the term vague uncertain.
Functional Description points can be listed on the points list, straightforward, do not use large blocks of text, easy to understand design and development.
For example, this is the message interface for counter-example: the user interface can leave a message in the message, delete the message, tap the screen to refresh.
Programmers will see the collapse, whether logged in to leave a message that the word limit, how many initial display, an administrator can delete messages or delete users, is the drop-down refresh refresh or otherwise?
Fairly standard practice:
Initial display message 26 and message Click below to see more about the pages button.
Visitors can not leave a message, Login User comments can be conducted.
Message word limit of 50 plus words.
Guest Book, you can delete, delete other users without permission.
These are just a simple example, functional description clear enough to improve the efficiency of design and development, reduce communication costs.
4, a small detail, played a lot of products, some products are still made,
Is "login", not "landing"
Is "login", not "landing"
Is "login", not "landing"
The important thing to say three times.
Requirements Document
Requirements document is the product manager of the daily work, maybe we did not do a good job for the job, focusing on details.
To determine the name of a requirements document specification, later proceed accordingly, easy to document finishing.
Requirements document, beginning with the need to give the product definition, a product description to what the user, based on what the scene, the use of this product do.
About requirements document terms and definitions, we need to give a specific explanation of proper nouns.
Demand article basic information architecture diagram and product use case diagram, should be put up, easy to read to understand the whole idea of the profile of the product, a better understanding of the requirements document.
Planning version of the product, we are determined to fill, it is uncertain to be written communication.
For specific functions, function definitions are given first, and then give a detailed flow chart, preconditions, function rules, clearly defined post-process uses words were said not to use the expression product manager program itself is not particularly aware of such as: regular expressions and other words to describe the rules, such a description uncertain right or wrong, the programmer see this content is more exclusive, professional people to do professional things, trust them for their son.
Product manager for the user to fill in information, comments, messages and other content field descriptions give a specific rule, which is an essential quality of the product manager, such as a general rule, the state issued 140 words microblogging, QQ personalized signature 50 words and other mainstream social networking, with specific reference to understand the product to give a reasonable explanation field rules.
other
1, the last one in the product design process, do not deliberately pursue innovation, to break some of the existing product interaction logic.
For example, change passwords, email and other content have been binding on the menu settings inside, so many years of training the users of this product, do not free to break the habit, break the effect will be counterproductive.
2, every time, and design and development to communicate, first want to say good question, why do so, find the appropriate product data and sample supports, to explain your approach in order to persuade them not to leave him seriously because the program opinions refused to your needs, you will immediately tear force, which is an act of the most pointless.
In fact, I have met programmers are unreasonable, provided you have enough reason to convince him.
At last
I grew up listening to a lot of truths, but still had a bad this life.
People still agree with this statement, so I prefer to swap pit, in the product design process, only fall off after the pit to make their own impressive, actually in trouble until after solving, product design in order to have more experience, ability to be promoted.
Another very important thing is to summarize, you finish line on a product, a product iteration, in a product after reading the book, you do not go through the experience, and seen to have read, shed for the process of summarize the contents of the pit and carried out by mindjet software such records, very necessary, let you experience rapid absorption of knowledge, ability as they quickly improved.
