The fields of project management and product management are commonly — and erroneously — used interchangeably. Its practitioners even tend to use the same acronym: PM.
The only people who know the difference between project managers and product managers are product managers…or project managers…I can’t remember
— I Am Devloper (@iamdevloper) April 9, 2021
Even people in the software development industry are sometimes confused about the distinction between product management vs. project management, and this leads to many misunderstandings.
Imagine you’re asked to recruit a new team member and the hiring manager says something like, “Yeah, product or project manager.” Believe it or not, that really happens.
Let’s unpack how the two roles differ.
Table of contents
- Product vs. project
- What is a product manager?
- What is a project manager?
- Product manager vs. project manager: Key differences
- Is a project manager just a junior product manager?
- A dangerous trend: Project managers in disguise
Product vs. project
Before we tackle the differences between a product manager and a project manager, let’s understand what products and projects actually are.
A product is the vehicle of value. It can be software, hardware or even an intangible service.
The purpose of products is to drive business results by delivering value to users. Because business objectives and users evolve over time, a product is never complete; it exists as long as the need exists.
A project is an execution tool. In other words, it’s a way of achieving goals.
Projects aim to achieve a specific goal (scope) within set constraints (e.g., budget, time). You can think about scrum sprints as short projects.
When we manage a product, we manage a long-lived, ever-evolving vehicle of value. Managing projects is all about achieving specific, constrained goals.
With the difference explained, let’s examine what, exactly, product and project managers do.
What is a product manager?
The exact role of a product manager is heavily context-dependent and differs dramatically depending on the environment. A product manager working at an early-stage startup will have a completely different job description than a corporate product manager working on an established product.
The product manager’s role
If we had to distill all the responsibilities of a product manager into a single tagline, it would be along the lines of, “Doing whatever it takes to ensure product success.”
Product managers contribute to success by focusing on three main areas:
- Strategy — establishing and understanding product direction and goals
- Discovery — uncovering opportunities to realize the strategy and understanding what to build next
- Execution — ensuring that our speed of learning and delivery is high and the way we build is effective
Strategy
A product manager’s strategic activities typically include:
- Establishing long-term product vision
- Setting quarterly/yearly objectives and key results (OKRs)
- Maintaining and improving the business model
- Preparing business cases
- Managing a high-level business roadmap
- Performing competitive research
- Monitoring relevant trends
- Discovering and establishing positioning in the market
- Building consensus among stakeholders around vision
Discovery
The product manager’s responsibilities around discovery include:
- Conducting user research
- Doing market analysis
- Understanding and optimizing user and customer journeys
- Spotting and prioritizing opportunities
- Discovering and prioritizing assumptions
- Planning experiments to verify assumptions
Execution
At the execution stage, the product manager is responsible for:
- Removing the team’s impediments
- Establishing and improving delivery processes
- Day-to-day decision-making and prioritization
- Splitting ambiguous goals into more manageable targets
- Decomposing big features into developable chunks of work
- Coordinating dependencies and working with stakeholders
- Managing the development roadmap and budget
The distribution of effort among execution, discovery, and strategy depend on the context, role, and seniority of the manager. A junior-level PM on a corporate assignment might focus more on execution and discovery, for example, whereas a senior product manager at a startup would likely spend most of their time doing strategic work.
Measure of success
“Do we achieve desired business outcomes simultaneously generating value for our users?”
Key skills of a product manager
To be successful in the role, product managers should have the following skills:
- User research
- Strategic thinking
- System thinking
- Technology and design
- Leadership
- Stakeholder management
- Research and analysis
- Strategic thinking
- Communication
What is a project manager?
Whereas product managers have a breadth of responsibilities, project managers are more focused and specialized. PjMs don’t contribute as much to strategy and discovery areas; the execution is their bread and butter.
Project managers have the skills and time to go really deep into execution and improve efficiency. For example, a product manager doesn’t have time to monitor and improve granular metrics such as time-to-first review. That’s why we have project managers.
The project manager’s role
Great project managers can bring order and organization to even the messiest and most complex of undertakings.
Compared to product managers, project managers play a much smaller role in the strategy and discovery phases of product development but are integral to the execution.
Some activities of a project manager include the following.
Strategy
- Rallying key stakeholders around vision
Discovery
- Coordinating discovery activities and ensuring they are aligned with delivery activities
- Helping with documenting key learnings
Execution
- Managing budget
- Co-creating and striving to deliver on deadlines
- Monitoring and improving delivery pace metrics
- Removing the team’s impediments
- Establishing and improving delivery processes
- Balancing between adequate communication and not distracting the team
- Ensuring the development team has whatever they need to work efficiently
- Decomposing big features into developable chunks of work
- Coordinating dependencies and working with stakeholders
- Resolving conflicts within the team
- Working with engineering leads to manage technical debt
- Negotiating with stakeholders (including product managers) around scope vs. budget vs. timeline
Although project management is focused on going deep into the execution area, project managers also contribute to strategy and discovery work. Their contribution there, however, is usually limited compared to product managers.
Measure of success
“Are we delivering the desired scope within the planned time and budget?”
Key skills of a project manager
To be successful, project managers should be proficient in:
- Agile frameworks
- Conflict resolution
- Process optimization
- Technical fluency
- Negotiation
- Budgeting
- Timeline management
- Stakeholder management
- Team leadership
- Communication
- Risk management
Product manager vs. project manager: Key differences
The table below describes the key differences between the product manager and project manager roles:
Is a project manager just a junior product manager?
It’s a common misconception that you become a project manager first and, once you are experienced and skilled enough, you can be “promoted” to product manager.
While it’s true that many project managers eventually become product managers, it’s more of a career pivot than another step on the ladder. High pressure and a low sense of product ownership can quickly burn out project managers.
But product and project management are separate career paths. A skilled project manager with years of experience can easily manage a dozen of complex, interdependent projects with unrealistic budgets and timelines — all while managing the most difficult stakeholders. A generalist product manager would probably sweat at the mere thought of doing so.
It’s true that project managers share only on a fraction of product managers’ overall responsibility. But in return, they are true specialists in execution.The more complex the endeavor, the more pressing the need for such a specialist.
Product managers are generalists that often contribute to execution, but they deliver the highest value when they work on establishing product direction. Project managers deliver the most value when they focus on tiny execution details. At a certain scale, you need both.
A dangerous trend: Project managers in disguise
Product management is hot. In recent years, the interest in the role skyrocketed.
This presents a big problem: Suddenly everyone wants to become a product manager. The title is fancier, the salary is often higher, and the overall job description is often more interesting than that of project manager. Who doesn’t want to be the next Steve Jobs?
As a result, companies struggling to hire a project manager have adopted an ingenious tactic: they simply changed the title from project to product manager! What’s worse, it seems to be working.
Given how hard it is to get into product management, the chance to get the title on your CV is tempting, even if the actual job description expects 100 percent execution and nothing more.
This trend blurs the boundaries between the roles even further. The last time I checked job boards, there were actually more offers for these project managers in disguise than for actual product managers.
In the long run, this trend will blur the boundaries between these roles even further. At some point, we will probably stop calling people project managers altogether. A new era of execution-focused product managers seems to be around the corner.
The post Product manager vs. project manager: What’s the difference? appeared first on LogRocket Blog.
from LogRocket Blog https://ift.tt/8FxRWdv
Gain $200 in a week
via Read more
