Where there are people, there are editors of rivers and lakes

Editor’s note: This article is from WeChat public account “Kevin changes the world” Kevingbsjddd) , author: Kevin bit change the world.

During the special period of the epidemic, several product managers who wanted to leave were still looking at opportunities. Even though it may be difficult at this stage, I still want to break away from the “haunting” workplace battle relationship.

Where there are people, there are rivers and lakes.

The product manager meets the

▲ Workplaces are like rivers and lakes

No matter what type of business, there will be workplace arguments that fight for personal interests. The outbreak of chaos occurred when personnel were inefficient and confused about their work.

Everyone likes to be a factual team at work. Every minute and every second is meaningful and valuable. It’s not because you worry about offending people or you care about human rights, you can even postpone the task or even give up the task.

But the company is growing faster and faster, and there are bound to be problems in personnel and business expansion. As a result, the business is not standardized, there are many people, and the work is unclear.

Here I list two types of product managers’ work-related phenomena at work.

Demand priority is not always ranked

Requirements represent the input of development, design, and operations personnel. When the product manager’s project is not favored by the company or the weight is reduced, the investment in project resources will be suspended.

Many product managers, as members of the project, naturally do not know what happened at the project strategy level? As a result, the project suddenly runs out of resources or needs are postponed

The product manager meets the

▲ Product demand priority

In fact, this is the beginning of the battlefield story in the workplace. Because the project is reduced, the weight of the project is increased ….

New leaders, new resources and new forces will strive to increase the priority of the project. The old methods and leaders behind it will inevitably become the object of project extension.

80% of the time, the story behind different product departments of the same project team

An Internet product is divided into front-end and back-end. I have written about front-end and back-end sharing before.

▲ Front and back

But the client and the platform are actually irreconcilable. Both parties hope that the other party can reduce their workload. For example, the needs of the user side are that the platform side provides sufficient support capabilities, but the platform side wants to be able to control the needs of the user side, and iterate and develop products in strict accordance with the capabilities of the platform side.

The product manager meets the

▲ The focus of each platform and client

For example, the advertisement configuration on the APP, the initial stage of the product will let the background of the APP be configured. However, as the product iterates, the configuration of advertisements needs to be on multiple ports such as APP and H5. It is more reasonable to port the advertising platform to the platform.

But the platform may think that the advertisement configuration is not required by other APP product lines, and hope that the APP will complete the advertisement system by itself.

Over time, the demand side will become a question of spear and shield. Too many user-side requirements make the platform unable to standardize and become the back-end of a certain product line user-side. The platform wants to build a way to support multiple client needs

Product manager meets the

▲ Platform-side iterative rest assured

Thus, for the same product line, the competition for demand priorities and the right to speak is particularly important. Generally speaking, if the product line has a general product owner, it will be arranged. However, if the platform and user end are two different product lines at the beginning.

So both parties inevitably want to reduce their work and tasks as much as possible. In the end, a boss or higher management is still needed.

20% strategic considerations

The product manager is still a job.

We can choose the environment and projects we work in. The company’s internal adjustments are still options for work.

The user experience design element mentioned that product managers should stand at the outermost level in requirements design: strategic considerations.

Product manager meets the

▲ Strategic consideration of product design

If you want to gain more voice and shorten the time of trouble in the workplace, research the company’s new project startup funds, resource investment, and mainstream business relationships with the company. At the strategic level, team projects that will be eliminated in the future will be avoided.

Because some projects are doing dying struggles, while others are doing big shows.

So choosing the latter will obviously be conducive to career advancement.

At the same time, in the workplace, product managers are proficient in project management, documentation, and prototypes. So communication becomes a very important job.

Including business communication, requirements communication, task communication, figuring out what to do, what leaders want to do, and how teams can do it are the main communication tasks for a product manager.

So the failure of the strategic layer selection will inevitably face the situation where the entire department is dropped in the workplace.

When there are people, there are rivers and lakes

The above two workplace battle arrays, one is point and the other is face.

Point: Upstream and downstream in the product line

Area: the choice of company’s strategic layer

The two perspectives are the upstream and downstream work of product managers and the horizontal transfer of departments.

Product manager meets the

Upstream and downstream of the product, one side must be the limitation of demand, and the other is the direction of demand support. For example, the customer service business department needs the product department, and the product department wants to limit the needs of the business department; between the product departments, it is supported by one party and restricted by one party;

The product manager meets the

There are independent innovation projects between product lines andThe business needs to develop 2 or 3 product lines.

The last thing to say is that since you can’t escape the battle in the workplace, at least you know the classification of this problem. It is best to follow up this classification to do your job and solve it according to the actual situation.