Recently rested relatively early, feel the evening to write a log, a write on a few hours, more impact on the rest of the time, so stopped writing a few days, today suddenly remembered some things to write ...
Self-evaluation of work norms, I've been commenting. 3.5,3.5 is a more awkward score, more formalistic, more subjective, more human, the more will give more than their own ability of the objective score, I should have given 4 points (the highest is 5), but think or forget, on the one hand because it is really always in the groping norms, how to standardize; On the one hand, because there is no clear working standard, I Also do not know what is the most normative; on the other hand, some so-called normative process, because still in the experimental stage, basically to use strictly to implement the experimental stage of the norms, communication costs and learning costs are also very large.
For the Internet product planning, the end to show you, is a planning document, about this planning document, I was a long time, summed up some of the documents, to solve some of the problems:
Who are you looking for?
Some of the planning documents, I really do not understand, there are two reasons: 1. I didn't write it myself, 2. It's not for me to read.
In thinking about who to see this problem, in fact, should be constantly thinking about their own in the company or planning the role of the project, to WHO to see? Of course it is for you and others outside of you, as well as yourself to do other project planning personnel, technology developers, art designers, testers, marketers, market research, bosses, bosses, and possibly other people on hand, because of this, this document that wrote your own name may have a lot of impact on you, Different people read the document, as long as you do not consider for each other, there will be many problems to find you, later there will be a great deal of communication costs.
As the author of the document, you must constantly for these people to continue to do transposition thinking, and constantly with them to do the feasibility of communication, especially technology, art design, which is related to the project whether the smooth conduct of the problem.
What do you do before you write a document?
In fact, before writing a document, basically brainstorming, discussion and thinking, the key is, brainstorming, and did not identify who to do the planning and writing documents, also did not confirm the task fell on who, if you are the master planning, but also the project leader, this is fine, if not, and do not have the necessary minutes of the meeting, the final written document, Some of the details that might have been discussed before may have been forgotten, so it is necessary to do some scattered records before writing the document, and to collect some questions.
Of course, if the most normative approach and time allowed, there should be market research and data analysis, but I always think, do not need all the operations through formal market research and data analysis, a group of qualified product planners themselves should be long-term follow-up products, and deep in the use of products, become a user's son, And may become the user opinion leader, as long as it is so, before writing a document, actually already mastered a lot of implementation and user feedback, but no written instructions, but these empirical research results and implementation, must be later collated and written expression.
What does the beginning say?
Project name? Implementation scenarios? Project introduction? I think it is: give a clear definition of what will be done-the definition of the project.
It is best to solve the problem of project name and project noun definition, and write it down through writing, which is to solve the problem of what to do, only understand what to do, give a clear definition to what will be done, this definition must discuss the unanimous adoption, and then concrete to the concrete implementation model.
The definition of project name and project noun is--can be copied and spread to others, when others ask what kind of project, the responsible person always answer, so it is convenient to remember, easy to spread, and express clear and concise good understanding.
What do we do next?
The project definition is resolved, then the project requirements and plans are identified, and the next step is to list all the requirement points related to the definition strictly by definition, and make some necessary analysis to list the solution outline.
Of course, if the project is relatively large, the demand point will be completed step-by-step, the corresponding solution will be given step-by-step, however, I always believe that the initial project planning, from the definition of the law, the need to divide the finer the better, and then use scientific methods to find the most important, for complex projects, and then give a phased solution, to solve the most important, The core, which is the structure, which is the higher priority problem.
If these problems are not solved, it is easy to ask later: When will this function be done? If you don't have a plan, you can't answer it. If people are always consulting your plans and solutions, this is not a good thing, this is definitely your project to do, prepare when to do, these issues are not considered, and do not have a good communication with others, especially the whole day to focus on your products boss.
Next, Demand confirmation
The so-called demand confirmation, is to confirm the project definition, project requirements, solutions, product line planning issues, confirm the correct, and then proceed to the next step, so as to avoid the later to do the implementation of a number of problems, such as priorities, what to do, how to do these issues. Do need to confirm, the product responsible personnel have a lot of requirements, how to make the project equivalent of personnel, non-project team to the project staff understand your product aspects and ideas?
Oral expression is important, to use a simple and clear ppt, the most concise and clear verbal description, the so-called product personnel persuasive, in the need to identify the most easy performance. In addition, you can intentionally and without intention to convey your product concept, so that your product design more convincing, so that you can reduce the harassment of many consulting molecules.
Of course usually experienced designers, in the previous two steps without plaintext, the model has been made, I do not deny this practice, because the people who can complete the model, when the model, the mind already has a preliminary product requirements model, and understand the project design of the starting point, there are models or product concept map, Can help to think, verbally after discussion and confirmation of the requirements, to make the core product model, so that more specific model testing can get more discussion and feedback, reduce the possibility of rework, reduce the time to write documents need to repeat and communication costs.
However, the documentation for the final solution will need to be restarted from the "Project definition" "Project requirements and plans" and continue to be adjusted on the model to make the model more complete and feasible.
Let's write here today ...
In fact, there are many details of the above mentioned, but the reliable product planning, basically do not see me these words, these problems are the novice on the road slowly groping out, in addition, this log to express is not what the document writing process and norms, I even own documents also in the absence of a standardized environment to explore and improve slowly ...
