職涯 - 談談Project manager的角色與責任

Open in ChatGPT Open in Claude

歡迎收聽「Mark 的技術雜談」，我是人工智慧主持人璦廷。專案經理這個角色總是充滿魅力，甚至被許多工程師視為職涯目標，但你真的了解它的核心價值嗎？讓我們來看看專案經理都在做些什麼。他們雖然不直接帶人，卻需要處理複雜的跨部門溝通。一個優秀的專案經理不僅要過濾需求、明確傳達目標，更要在品質、時間與資源之間找到最佳平衡點。這個重點值得注意：專案經理絕對不是只負責傳話的代理經理。在實際的專案場景中，最困難的往往不是缺乏點子，而是如何落地執行。好的專案經理會關心執行團隊的難處，主動協調資源，而不是把計畫丟過去就坐等結果。總結來說，這份工作的深度決定了市場價值。做得淺可能只是高級助理；做得深，就像是掌控全局的導演，能讓所有資源在對的時間精準到位。節目最後，留給大家一個思考方向：在你目前的團隊中，專案經理是扮演著傳聲筒，還是真正引導大家走向成功的靈魂人物呢？

Podcast ConversationAI dialogue version of this article · Mandarin audio

Introduction

During 1-on-1 career discussions, I've found that many junior developers are interested in the Project Manager role, or they see it as one of the ultimate career paths for an engineer.

Additionally, there's the Product Manager—also often called a PM, but with a different job nature. They're sometimes referred to as DMs, responsible for understanding customer needs and planning product development. Some companies even have Program Managers, who handle product marketing, positioning, and promotion. However, these roles are outside the scope of this article.

Most Project Managers manage projects, not people. It's a professional role, not a managerial one. Some might be happy to hear they don't have to manage people, but it involves communicating and coordinating with many project stakeholders. This is no easy task. For complex projects that span across departments and organizations to run smoothly, the Project Manager's role is crucial.

Key Responsibilities of a Project Manager

1. Filtering and Confirming Requirements

Understand why the user proposed this requirement. => Start by clarifying the reasons with the requester.
Clarify if the requirement is reasonable (technically/schedule-wise). => Discuss the requirement's feasibility with the relevant personnel.
Analyze and consolidate requirements, then write requirement documents and confirmation letters.

2. Clearly Communicating the Description and Purpose of Each Requirement

Ensure all team members have a clear understanding of the goals.

3. Cross-Departmental Communication and Coordination

Manage resources and expectations among different departments.
Prioritize tasks to make the most effective use of limited resources (finding a balance between quality, time, and scope).
Set priorities. Because resources are limited, clearly inform the team which features are the most urgent and which are secondary.

4. Project and Resource Planning and Progress Tracking

Plan and schedule upcoming projects.
Coordinate the resources needed for the project.
Monitor project progress and identify potential bottlenecks.

5. Ensuring the Outcome Meets User Expectations

Ultimately, the Project Manager's goal is to ensure the project's outcome meets the expectations and needs of the stakeholders.

A Project Manager is Not a Proxy Manager

Someone once asked me, "Silicon Valley doesn't lack ideas; it lacks people who can execute. Most ideas die in execution. So what makes me different from others?"

I think what sets me apart is this: I've been here for a year and a half, and I'm the one responsible for the execution team. I think through how to actually implement things. Looking back at my past projects, none seem to have failed in execution. When I propose something, it's usually something my team will do, and I also consider how other departments can collaborate.

The real problem isn't a lack of people who can execute. It's that no one cares about the people who are actually doing the execution. They just forward plans and ideas to the implementers without considering their difficulties or what they might be lacking, and then just sit back and wait for the results.

Therefore, for a complex project to be completed successfully, a Project Manager can play a very important role.

Conclusion

A Project Manager not only needs to be skilled at coordination and communication but also needs to understand the knowledge, background, and jargon of various professional fields. They must understand what each stakeholder cares about and what each role's responsibilities are within the project. A technical background isn't strictly necessary, but it's a bonus and can make leading projects easier. However, people with technical backgrounds are often not the best communicators. The most crucial thing is to be interested in this type of work and have a passion for planning and dealing with people. Otherwise, this job can be painful.

The role of a Project Manager has a lot of depth, and this depth greatly affects their market value. A shallow PM might act like a switchboard operator or a senior assistant. But a deep PM, who can plan, strategize, and arrange everything perfectly, is like a director: they know who needs to enter the scene and when, they arrange the necessary resources, and when the time comes, the actors perform according to the script.

Ultimately, you have to have a passion for any job. Without passion, you won't last long.