Understand the strengths of project management designers in team collaboration

At the annual meeting invited to participate in the project management Round table, in fact, I only in a very short time the project management function, also did not aspire to engage in project management goals. However, from the work history and experience, I have a certain understanding of project management, and have been deeply aware that the designers understand the project management in the team will have a better advantage.

Read the summary of several participants, I write this blog is mainly to do a reflection, not the point of view. Smile's manuscript before the hair also showed me the next, time is too tight, not careful scrutiny, in this by the impression to add some content.

How do I define failure?

Any project should first define what is the key objective? Which is the bottom line that can be controlled, is it important to finish on time? Or is it important to pursue quality? The same goal, in different projects, it has a different priority. For example, to do a project to catch a conference, fixed time August 21 must come out. Then this time period is the key goal, because if you come out after August 21, there is no sense, certainly calculate the project failed.

At the same time, we reached a consensus, the Internet product design Agile iterative process, the vast majority of successful products are in the process of continuous improvement mature. If the key objectives of the project are much more, it is likely that one is not well controlled and fails. For example, we often meet the boss in a short period of time to make a good product expectations, there are time, quality two key goals.

The composition of the team?

has been listening to Mr. Zeng sharing QQ Mailbox team experience, in fact, is the Google model of small team collaboration, which I think is the most efficient way of working. The so-called small team, that is, from the various professional technical groups, select the project interested colleagues to form the project team. and can be evaluated according to the deliverables, m and p two lines.

The idea of a product manager, product designer, and product engineer is similar to the three roles I've summed up in the Internet product design operations reference. In addition to the business, excellent product managers should master a certain number of user research, data analysis skills, and the ability of excellent designers must also be compound.

1. The less people the better, three types of roles fully supported: Product managers, product designers, product engineers;
2. Emphasize comprehensive ability, do not advocate the meticulous division of functional position;

What is the difference between a product manager and a project manager?

As we talk to a node, we suddenly find that the definition of the Product manager and the project manager is different. English is called PM, actually one is product manager, one is Project manager. Most of the peers may think that there is no difference between them, the actual situation is so, very confusing.

I agree with Mr. Zeng. "Product managers are mainly to communicate with users, project requirements, and the project manager is responsible for the progress of research and development, and ensure the implementation of products on line." "They are absolutely wrong, just go back to the" target "problem, the project manager is responsible for the progress, the product manager is responsible for the quality. A person at the same time control progress and quality, easy to fall into the game of death cycle, on the contrary, can promote and contain each other.

As for their relationship, my point of view is "There are n projects under one product." In theory, the project is responsible for the product, and the product and project are two parallel systems, even if the level is wrong, they should not constitute a reporting relationship.

How to promote communication?

Fully agree with Sheng "project manager is not a mouthpiece" point of view, I think the manager should be more understanding of business model and professional technology, accumulate their own unique knowledge system. Although we claim to be professional and technical personnel, if we do not know more about the company's core product business model, sooner or later will be marginalized.

This example is given on several occasions "when you come up with a plan, you may not make any comments; When you come up with a demo, everyone's opinion is crackling." "Because others are different from your goals, it also makes sense that we should do it right away, rather than think about it."

All communication we recommend face-to-face, meetings to discuss results, and emails are used to publicize the results. Meetings and emails are just forms of communication, and excessive forms can be bogged down in formalism.

How to avoid internal friction?

Some people say that the tragedy of Chinese internet companies lies in "internal friction". There is no unified strategic attempt from top to bottom, each have their own calculations, which not only consume resources, but also expend energy. Everyone is assuming that their job is the most important, or important.

When talking about the sense of responsibility, Mozi said, "Before people say", I added the phrase "do not say afterwards." Such problems can easily arise when functional positions overlap. Of course, the most serious Chinese characteristics are not too many participants, precisely too many policymakers.