Assassins who expect the product manager

【Introduction】:

From the interactive designer to product manager unwittingly two years, although the role has not completely transformed, but the attitude and methods of doing things have undergone a significant change. The biggest change in mentality is: owner mentality (ownership), goal-driven, there is no excuse. The product manager must be a proactive person. He is not a human resource. He does not have any authority, but he also has to co-ordinate various resources so that various roles can meet their goals and meet their goals together. During the encounter difficulties and setbacks are also many, one of the difficulties lies in the grasp of technology.

I am responsible for the data products, maybe a project, I will at the same time with java development, data warehouse development, front-end development and app client development, they are asked for, or want to abuse them. Then it's surrounded by various terms - architecture, clustering, java, jquery, hbase, caching, modules, js, calling server, interface, cdn, database, mysql, jar, broker, memory, distributed, semantic, data mining , Hive, Hadoop, Reverse Proxy, Streaming Computing, Offline Computing, Instant Query, PHP, Variables, Parameters, Join, Stream Join, Instance ... Too Much.

One day I stood in front of our department's bookshelves, determined to learn some technical knowledge, but also found that technology involved in all aspects, can not start.

So I met the development asked: Hey, what do you think I should learn technical knowledge?

Their answer is very different -

Some say: You do not have to add anything, just consider the business level, and describe your needs clearly, leaving the rest to the development.

Some say: Well, as a product manager who deals with technology every day, you should learn technical knowledge, such as ... and then hear a lot of nouns ...

Normally, we often hear the siege division evaluate the product manager. If the product manager is only responsible for the specific needs, the siege masters are also very active, very advanced and very creative. They just do not give them Opportunity and time to think, is it? That PD's and program ape should have what is different? Or in addition to "think", siege division of the product manager what are you looking forward to?

So, I'll give you a simple survey of siege masters to find out how they look at product managers, what do they think are good product managers? What kind of product manager gave them a headache? What do they think the product manager's professionalism is mainly reflected in? What technologies do they think product managers need to supplement?

The questionnaire was sent only to the siege division, invited dozens of siege division I have had contact with, architects, development engineers, test engineers, data development engineers ... ... levels, but look similar, especially Recommended articles, each word Aberdeen, read the reading, thought-provoking. If you share, fortunate to help other product managers make the same progress, would not Kuaizai. In fact, finishing the article's biggest purpose is: self-encouragement, give yourself a mirror, often photos.

Question 1: What kind of product manager will let you recognize or even admire?

In addition to the other options, there are three development students, they were added three points:

1. Have control over the future market and forecast

2. Good at planning and finishing

3. Independent, calm

[Comments]: GG in the development of it seems, the product manager is responsible for the things that are right, want to understand, communicate clearly. The rest of the work is to develop things. Yesterday also heard a big product manager talked about what I quite agree, he said, marketing department and product manager is the most expensive, the market is to get the budget smashing effect, and a non-reliable product manager, would like to do not fly Demand, toss a group of people (design, development, testing, operation and maintenance ah, ah operation, the market ah ...) work overtime, released on the line and found that is not the case, so you develop the students pay All water. Development students also expect the product manager "think" ability to excel - Anyway, we live in life, you have to figure out ah ... .... In addition, it is useless to come up with ideas and ideas, and good product managers have to be able to smooth out their ideas so that people of all colors understand what you are thinking, whether it is rhetoric or not The story is good, drawing is also good, in short, you have to let developers GG know how to encode, interactive designers know how to design, visual designers to know what style to go in ... ...

To be able to do both, product managers do not have to constantly broaden their horizons, keep trying, constantly enrich their knowledge and ability in all aspects? So if you do not have very good ideas and ideas, amateur and non-part-time people may remind yourself that you can not rest on their laurels and you have to try their best to find out about foreign designs, websites, latest trends and data. Products and solutions that were attacked by the siege divorcees ... because the siege divisions often cling to front-line forums and websites ...

Question 2: What kind of product manager will make you depressed and even refused to cooperate?

【Comments】 As you can see, siege division students do not like the product manager does not have long-term planning, always mention some short-term needs. This kind of thing is no technical content right? As a product manager, small short-term needs can not be overlooked because the overall product experience is an interlocking one. It does not solve some rigid short-term needs and how to talk about the long-term healthy development of the product. However, when the demand for program ape to mention, if you frequently mention a demand, and then follow the progress, then mention one. Each other's needs, so that we can not see the association, classification, can not know how to solve these needs and product long-term development goals? Then programmers will think you've lost the value of being a product manager or just a functional product manager.

Siege masters hope you bring a clear sense of purpose and direction, you need to draw a blueprint for products, such as 2014, our product development goal is what direction, around this direction, what we have to do to give up Which? In this direction, we have to do what major projects, these large projects, will be divided into a number of small-scale projects, and which small needs are to achieve the goal in that direction. Although these long-term plans, like picture-puffs, can not be used as PRDs (product feature requirement documents) that can be developed and started, it is important.

Also, do not think that siege masters have no sense of belonging to the product - are they just immersed in the pleasure of writing code? you are wrong. A small demand for you, for them, may be tens of thousands of lines of code to work overtime, there may be tangled in each line of code, some codes may be hungry, staring bleary sleepy eye knock out. Half done, you say, for a variety of reasons, do not do it. Or released, you do not give to promote well, let the user to use, later busy forget the other products. Regardless of custody students, and sometimes even the program ape can not wait to maintain it as an external interface.

Of course, siegemasters want the product manager's delivery needs to be thoughtful. This is just as cliché as a "wolf" story. Today you delivered a demand that has been confirmed. Tomorrow suddenly caught a loophole, and soon to replace the program, and then determine the day after tomorrow find yourself a bit wrong, only to find development to change needs, over time, the siege division of your "is determined" is not sensitive. You can argue several times before the formal delivery, multiple reviews, but make sure your documentation at this time is 0.N version rather than the final version. And be sure to finally submit a demand confirmation document that will not change again. If once the programmer begins to design and begins coding, you suddenly find that there is a problem with the logic that omits a requirement or a requirement, and you are waiting to be stuck with an unreadable label.

Of course, depending on your mutual trust with you and your partner, you can tell him to have a good look at the document or find out if you have any questions during the coding process. Because of the form, the product managers who work overtime and turn around every project will inevitably get confused.

The siege division will also despise the boss every day when the shield as a product manager, if you tell him that the boss needs to be done, then you have to "good product manager" and a step further. To professionals, pure enforcement and supervisor roles are the least technical. . So sometimes the product manager is a sandwich biscuits, the boss called you a black house, tell you what to do, argued useless, the heart does not agree, follow-up must do, but also personality split for their own special supportive identity needs. . Of course, adhere to their own principles dare to boss and product manager is there, we call him "idol."

Question 3: Do you think the professionalism of the product manager is mainly reflected in? (Up to 3 items)

【Comments】 Before a group in Wangwang, a group of students chatting idea (hereinafter PD for the product manager in English abbreviation), A classmate said: You have this idea, directly to find a few development and design together ah. B classmate said: no resources ah. A classmate said: PD or not? B classmate said: PD are not missing any one, a lot of grasping, so much PD why? Before I did not switch product manager, I also thought that the product manager is a non-professional work, a lot of his work is spent on communication, coordination, grasp the progress, he looks like everything will be a little bit, but nothing will be too proficient For the one who wants a little "professional achievements", the choice of product manager is not really a good job. After all, being a good product manager takes too many chances. The product needs to be able to shine, the product to be influential ... what about a professional product manager? Where do product managers improve their professionalism?

In the next five options, "can think" - business sense, vision and long-term planning, once again take advantage of. Followed by the idea that you want to be imaginative, you can think carefully, do not take the siege masters to the ditch, to express clearly and eliminate the misunderstanding of the various roles. As for the other aspects, although very important, the team with fine division of labor can also allow more people to work together.

Most of the siege division of this problem is not a natural choice: all above. Come on, boy.

PS: One of the other answers supplemented is a senior technical expert in the data world whose answer is: In the future data world, you have to understand the data. Know how to use the data, will look at the data, can really make the product manager can think more, can add more ...

Question 4: What is the biggest obstacle you currently have with your product manager? (Up to 3 items)

This problem, Heidi missteps, the problem options are not designed, the result that most people choose the other. Let's take a look at the supplementary answers to the rest of you:

No obstacles. It's okay now. There may be errors in the delivery of information. No current cooperation is not bad. Long time no see product manager. . Lack of communication, can not express their ideas well for development in order to agree with the views of engineers can not seriously think no idea, just to accomplish a task, nothing big obstacle. Demand is not clear The idea of ​​the product can not be sustained No I do not have a product manager, I am a technical product manager Now the product manager is good, nothing big problem ah

【Comments】 Several of them are barrier-free is our counterpart siege division, Heidi stole that if the vote becomes anonymous vote, several students will not change the answer, ha ha. .

Combining with other options, we can find that fighting for the assassin's recognition of the needs and their clear communication and reducing the omission and misunderstanding of information are the keys to the smooth progress of the project.

For the identity of the need to distinguish whether the siege division is not agree with the demand or do not agree with the solution.

We usually say that the demand actually refers to the product manager to deliver the functional requirements of the document carried by the content, for the siege division is the demand, but in fact is to meet the needs of a user or company to provide the final solution. Sometimes, siege masters do not agree with the demand is not not agree with the user or company's "need", but the solution has many questions.

Product Manager directly omit the mining needs of the user needs, analysis of the company's needs, the direct delivery of solutions, even if the solution will explain the project background, the project objectives, but may still cause an understanding of the fault, the siege can not be true from the heart Agree with why to do so. As a product manager to keep in mind: program ape is our comrades, partners, is a great realization, definitely not to the product manager to work, and absolutely not a machine, not a system - just enter the command can be run. In the early stages of demand, try to understand and participate in the program as far as possible (he does not have time to participate is his thing), so that they can work with you to understand the background of demand, to understand the needs of stakeholders, to meet this demand from the heart .

However, at the level of identifying needs, the solution is not one that the product manager came up with, and if the siegemaster is involved earlier, he can contribute advice and be accepted for the solution, you are less likely to have to communicate the cost of the solution .

Question 5: Do you think product manager is the development of the background is important? (Single choice)

【Comments】 Most of the siege division that score, such as:

Depends on the type of product manager is the system product manager or business product manager. Note: The system product manager partial functional product manager, mainly according to product vision, goals and operational needs to design products to support, and business product manager is planning a business, such as logistics warehouse, this business You may need to design a product or design an event. Depends on the project is responsible for what projects, pure technology projects or the best development background. But "a little bit is actually a good thing, but it is not good if you have more

Students who choose not to be important still think that the most important thing for product managers is their ideas.

And think more important classmate, basically think to know a little development, can help the product manager to judge feasibility. "If the product manager with the development background, the first time to determine the extent of landing needs, will not become a complete utopian," "the best development background, but not important, can learn more about point development knowledge, know What needs can not be done. "

One student added: It does not matter at all. "Attitude first, efforts second." Do not understand the technical product manager, to remember that you have a group of skilled cattle, humbly ask them a lot, and exchange a lot, the siege division are simple, kind, naive, simple and helpful.

Question 6: As a siegemaster, do you think product managers should know something better to work with you? (Up to 3 items)

【Comments】 immeasurable vast expanse of technology, product manager how to add technical knowledge to be able to input-output ratio than the highest ~ take a look at the recommendations of the siege division it.

Web site infrastructure knowledge of the highest number of votes (in line with expectations ah), the site infrastructure knowledge enables product managers and other non-technical role to quickly understand how a website is built up, understand the basic concept of the site technology architecture - siege division also recommended "large Web site technology architecture: the core principles and case studies, "the book, for such people as we can simply be a technical dictionary of terms Yeah.

In addition, the main job of a product manager is to do requirements analysis, then describe requirements, and UML is a language that helps product managers communicate better with development. Use case method is an effective description of the user's needs