Product Intern's first experience

Every year there will be a considerable number of interns into Tencent internship, and sit next to my lovely mm is. Internship can make university study and company work smooth docking. And the same cute Tencent product intern small wood students found: In the work of passion, but also self-control, there is clarification, but also self excavation. I think all the students who are going to work will be able to take a look, especially those who are ready to enter Tencent:

When I was not in the field of products, the product manager in my heart as a creative designer, the mind has a sense of unrestrained thinking, there is boundless imagination, can do as much as possible to do a lot of new and interesting fun tools. But in the actual work and learning process I found that a product, or a function, or even a very small icon, is not a product manager casually patted the head can be thought out. Divergent thinking is of course conducive to differentiation, but the differences between the different will be useful products. And good products are often based on a large number of research, data clarification, demand clarification and so on a series of complex processes, and then finally designed.

If you want to make a good product, or want to be a good product manager, then in the process of product design and implementation, you must pay attention to the following basic sources:

(i) Clear objectives

Clear goals, this is a product must remember the most fundamental principle. In fact, whatever it is, it is a very important principle.

First of all, want to know why to do this product (function), the starting point is what, the purpose is what, expect to make what effect;

Secondly, to determine the target is concrete, is achievable, and ultimately can be measured;

Finally, we should define the time goal and determine the expected completion deadline.

If you do not know the target, it will be like a headless fly-like disorderly flight, even if only the design of a very small function, it is possible to kill each other, or even completely vain kung fu. If the above three points are clear, then can be in the heart of a detailed planning, the next work can be messy.

(ii) Attention to data

Research is a product planning in the important preparatory work, research other similar products, research market and user needs, and so on, often after the product planning and product design of the compass. The research is divided into two kinds, one is qualitative, the other is quantitative.

We are often accustomed to the qualitative elucidation and description, by virtue of their own feelings and experiences, think 1234 and so on.

Feeling is very important, but the individual's thoughts and feelings tend to be biased, and may be due to some habits or other factors into some kind of misunderstanding. So quantitative research and elucidation is very necessary. Non-theory is in the early stage of product plotting, or after the product on-line, data statistics are very important.

We all know that the user browsing the web, is usually F-type, but I counted a page, but it is the right side of a very narrow and very small area of the click Rate is much higher than the area of twice times the right side of the list, the right clicks at least twice times the left. The area with high clicks in the right-hand module only accounts for 1/2 of the module's own area. If it's not back-end data feedback, I might never have imagined that a small module on the right side of the page clicked more than the other modules around it.

Therefore, please the Product Manager must pay attention to the data, no matter in any work link.

(iii) reasonable control of time

Time is a very important factor. "Fast" is the law of Internet survival. But good products need time to grind. So it is very important to control the time and the relationship between speed and quality.

How to plan, make the whole team operate efficiently in a limited time, how to allocate the valuable time and spend it in the most worthwhile place. These are important capabilities that are required as product managers.

First, the product manager needs to allocate time reasonably to UI design, requirements design, development implementation, functional testing, quality evaluation, and so on, and to determine the start and end of each work time, as well as the time between the input and output of the work.

Second, always communicate with the person responsible for each task or interface to track the progress of the work and ensure that it is completed on time.

Third, always check whether the current work is the right target, meet the needs, and the expected consistency. If you disagree, you need to find out immediately, so as not to waste the time and energy of giants.

In addition to mastering this large point in time, but also to control the small point of time. The product manager's big department time is to communicate with people, often meeting. Therefore, when presiding over the meeting, the rhythm of the control meeting to ensure that the problem in the shortest possible time to resolve, but also one of the basic quality of product managers.

Before the meeting, the first thing to do preparation, in advance will be the topic of the meeting, to discuss the content as far as possible a day in advance to the participants, so that the Giants all know ahead of time. In the meeting, the problem will be the same as the Masters, as soon as possible, identify and then deal with contentious issues, discuss them one at a time, and try to solve more problems within a limited period, if the individual issues are more controversial, you can put them in the final discussion, or put them under discussion for further discussions, and do not open more than 1 hours of meetings. If some of the problems are not related to all the participants, but also suggested that after the final meeting, with the relevant students 0 ding discussion, so as not to waste other students time.

In short, whether it is their own time or someone else's time, product managers should be very clear and reasonable placement and use.

(iv) efficient and accurate communication

Communication ability is the basic ability that the product manager needs.

Documents, forms and PPT, emails, online chat tools and de law, as well as interviews, meetings, etc., are all necessary weapons for product managers. There are many ways to communicate, but the goal of communication is consistent-----------to facilitate the rapid transfer and synchronization of information in the team, and to ensure the symmetry of information (understanding without ambiguity).

First of all, we must learn to summarize. To the document, PPT, mail, online chat a kind of text flow communication, must learn to write a summary. The summary must be concise, so that the recipient of the information can be swept a glance to understand the situation, and then to the need to learn more details. Lest let others read a half-day also do not understand you to say what, waste a lot of time, finally still confused. Interview, meeting time is also the same, but only text flow into the speech, the first summary of the talk, so that the masters of the mind have a spectrum, follow-up to listen to the details of the description is also easy to understand.

Second, be coherent and logical.

Writing documents, writing emails is the daily work of product managers, requirements documents, meeting minutes, evaluation plans, and so on, these seemingly trivial, in fact, the whole product design, development, testing, evaluation and other aspects of the important basis of work. Clarity and logic are necessary factors for document and message readability. If there is no logic, chronological the same casually narrative, confusion may be a period of time they can not understand, not to mention others. The process of speaking and communicating, with clear, logical, and strong language organization, makes it easier for others to understand their point of view and easier to convince others.

To give a simple example, a description of the requirements of a function, if according to the objectives (overall requirements), structural framework, functional description, data sources, content requirements, interactive design and visual design, statistical requirements, such as the order of the description, so that the appropriate staff only need to see their relevant departments can. Otherwise, it will greatly increase the cost of reading the requirements document for the students who work in each link.

Finally, ensure consistency, no ambiguity

Documents, forms, PPT, and Mail are the carriers of information to ensure that it is readable and understandable without ambiguity, to save the time spent on reading by developing and testing students, reducing the cost of communicating again, and avoiding the extra overhead of rework due to misunderstanding. There are no two identical leaves in the world, so it is normal to understand the differences. But timely communication, to ensure that the consistency of both sides is very necessary. Therefore, whether in the discussion in the Conference, or in the written communication, we must always confirm the understanding of consensus, there is no ambiguity.

(v) Focus on every detail

The design of the product is just an overview, think about it roughly like that. Product managers must focus on every detail: determine that all results triggered by each operation are considered, avoid omission, and confirm the final design and implementation of each detail; no tool can be ignored or skipped, even if the spacing between rows and lines of the page, Word and word spacing should be confirmed. It may be these small places that ultimately determine the success or failure of your product. Sink destroyed in the nest, do not because of small negligence and all their efforts destroyed.

These are the most basic and important principles of being a product manager, and I hope to help my classmates in the field of product.