Project Manager, Program Manager, Product Manager — Are any of these Producers?
the next phase of project leadership
In my first article (Project Manager or Producer), I attempted to find the differences between these two titles. Where I landed was somewhere between knowing what a Project Manager does (and doesn’t do) and realizing that the realm of a Producer is much more ambiguous and fluid role than most people expect.
Since then, the landscape has only continued to get fuzzier — for job seekers and hiring managers.
For job seekers, the questions range from, “Am I more like a Producer or Product Manager?” to “If I’ve been a Project Manager, could I be a Program Manager?”
For hiring managers, they may be considering a candidate pool where a bunch of Project Managers just applied to be Product Managers. Or perhaps they might have had a great interview with a Producer and but the job is for a Program Manager role.
How do we tell what part of these titles matter and what parts don’t? Before we answer that question, we have to understand that with the influence of Silicon Valley permeating through the global workforce, we are now entering the era of the Product Manager.
Product Managers seem to have become increasingly common as the growth of tech startups gurgle out of Silicon Valley. With every new product that is an app, comes with an app or is app-accessible, Product Managers are in demand. And let’s not forget the companies that don’t even make apps! Product Managers exist at online-only shops, hardware development companies and even investment companies.
So if they are proliferating and companies want them, who are they? More importantly to this article, what do they do? Are they Project Managers for products? Are they Producers for managing how a product is released? Do they handle all the different workstreams (design, engineering, etc.) for getting something made?
Let’s consider what we already know.
The Project Manager has the most concrete definition, the most tangible deliverables. Did these specific tasks come in on time and under budget? Yes. Did this project succeed? Presumably it did if it was on time and under budget. Are you doing your job? Also most likely yes if you’re focused on meeting deadlines and not overspending.
We’ve learned that a Producer’s role is more fluid. A person that can be more creatively driven to achieve the goals of a project, game, film, etc. This person may or may not encompass a Project Manager’s role. This depends on the size of the team and expectations of the organization on the Producer’s impact.
Now when we start to think about these other roles (Program Manager, Product Manager), it starts to become another exercise in word definition.
Program Manager — seems likely that this person would manage the program. Logically, the next question would be, “what defines the program?” Is a program a large project? Is it a bunch of projects? Do these projects have to relate to each other? What is the program?
In my experience, a program can be a collective of multiple projects, initiatives, campaigns, etc. The key here though is how each effort is integrated and/or aligned to achieve a greater impact for the organization. This doesn’t exactly equate to a Senior Project Manager who handles multiple projects. Instead (and this is assuming the context of a large company), the Program Manager strategically directs and supports a set of projects to a more cohesive whole.
Get stephanie perea’s stories in your inbox
Join Medium for free to get updates from this writer.
According to Wikipedia —
The project manager’s job is to ensure that their project succeeds. The program manager, on the other hand, may not care about individual projects, but is concerned with the aggregate result or end-state.
An example of this could be a person who is in charge of an organization’s Citizenship & Environmental efforts. There’s likely multiple projects going on at the same time — some for improving company-to-customer relationships and some for supporting the company’s commitment to being more environmentally responsible. As a Program Manager, that person would ensure that each of these projects efficiently and effectively play off each other to achieve the company’s goals in this area. Depending on the size of the company and the amount of support available, the Program Manager is likely to get in the weeds of the projects as well to ensure they are moving along in the right direction.
(If you, the reader, feel there’s a better example, please post one in the comments below!)
Then we think about Product Manager — seems like it should be someone who manages the Product. Right?
Again here’s Wikipedia:
The product manager investigates, selects, and drives the development of products for an organization, performing the activities of product management.
There’s also a more in-depth and interesting explanation of a Product Manager on the Aha! website. If you have a few more minutes, I suggest reading their articles.
(NOTE: Aha! is a Product Management tool and service “built for Product Managers by Product Managers”. My mention of this company is not an endorsement of or ad for their product.)
Ok — so a Product Manager cares about every aspect of a product. Cool, but, what the hell does that include? Could a Program be a Product? Is a Product part of a Program? How many projects are in a Program that create a Product? And how does a Producer fit into all of this??? (And why do these all start with the letter P???)
Even when we slow down to understand the differences, it’s easy to slip right back into a tornado of confusion. Despite one role being easier to define as the others, as soon as we think about it in relation to the rest, more questions arise. We immediately wonder about the right way to fit one role to the beginning and ending of another. We want to make the puzzle fit perfectly because it’s the simplest way to accept a set of roles and responsibilities. “This is my job. And that is yours.”
And perhaps, this notion is the fallacy.
In my career so far, “Producer” has been the most frequent job title, but I’d like to believe that I’ve also been a Project Manager, a Program Manager and Product Manager, despite not having had those titles (or the paychecks in some cases) yet.
In almost every job I’ve had, I’ve managed scope and schedule (project manager), coordinated multiple aspects across different workstreams and disciplines (program manager), and influenced creative or strategic direction on scope based on external and internal inputs (product manager). And of course, not to be forgotten, every job I’ve had included the soft skilled driven work of leveraging a team’s technical skills to get things done.
So what?
You might be thinking at this point, how does any of the above seem to help making any of this more clear? Definitions listed, example given, reference links provided, but somehow, it feels like we didn’t get anywhere.
Don’t be discouraged.
Job titles change along with market values. Your career continues to mature and grow. Who you are as a person and as a professional will keep changing. So I think the key is to realize that these job titles and roles are and will continue to be an evolution, and that your part in it, beyond titles, confining definitions, and bullet points, is to show your competency and capability to get things done with quality and integrity.








