Product & Project Managers: The Voice and the Engine

Why confusing project managers with product managers costs organizations dearly

Organizations frequently blur the distinction between product management and project management, and that is to their detriment. These roles sound similar, occupy adjacent organizational spaces, and collaborate intensively. Yet conflating them guarantees mediocrity in both functions.

The confusion persists because both positions involve coordinating people, managing timelines, and translating requirements into deliverables. Yet their core constituencies differ fundamentally. Product managers serve as "the voice of the customer"—though excellent product managers recognize customers exist within ecosystems requiring multiple stakeholders. Mark Vogelgesang, former guest on the CX Pod who held various project management roles in GSA before moving to product management at Salesforce, spent the majority of his time conducting conversations. These discussions occurred on two tracks: with peers exploring ideas and potential initiatives, and with leadership negotiating prioritization and resource allocation. His job centered on ensuring requirements remained current as environments shifted, functioning essentially as continuous customer research.

Four principles govern great project management: 

1. Know what you need not do. Project managers who attempt every task themselves become bottlenecks.

2. Understand what others require to succeed. This extends beyond immediate deliverables to encompass annual rhythms, competing deadlines, and workload pressures.

3. Assemble well-rounded teams providing specialized knowledge for diverse situations.

4. Maintain a living plan.

This last point merits emphasis. For example, Ishmael Interactive’s Aaron Meyers allocated a substantial time at the start of the year to intensive planning for the Website Evaluation Project, a massive, annual review of GSA’s digital footprint that he stood up and managed. Then, once launched, he devoted 10-20% of ongoing effort to continuous adjustments. The alternative—neglecting a plan for weeks before revisiting—produces chaotic corrections rather than manageable evolution. As Aaron observed, no plan survives first engagement, but plans updated continuously survive engagement better than those left static.

The practical implications extend beyond semantic clarity. Organizations that fail to distinguish these roles either duplicate efforts wastefully or create gaps nobody fills. Product managers absorbed in team coordination neglect stakeholder research; project managers distracted by external priorities lose track of team needs. The Website Evaluation Project, and, indeed all of the Enterprise Digital Experience work, succeeded despite the pessimism of senior leadership because the product or program manager, Ana Monroe, and the project managers, Mark first and then Aaron, occupied distinct roles with complementary focuses—one maintaining external alignment, the other internal efficiency.

For professionals considering transitions between these functions, Aaron suggests bypassing templates and specialized training, which are frequently unrealistic. The transferable skill is human insight: genuinely knowing team members' specific strengths, maintaining regular conversations, and tracking how capabilities shift over time. Those interested in keeping small groups cohesive gravitate toward project management; those fascinated by how products fit within organizational ecosystems tend toward product management.

The distinction matters because organizational success requires both voices heard clearly. One speaks for customers and context; the other ensures the machinery actually runs. Confusing them means neither speaks effectively.

What we’re into this week

Scott:
It’s so rare that we hear about all the stuff that has to happen before a great thing gets made, like your Website Evaluation Project, Aaron. We mostly only hear about the end product. But I managed to find a little version of what you all did this week in this fun, albeit pretty niche, story about how great products come from great teams, check out this deep dive into Leica, the camera company, and learn about the product and design decisions that made them what they are today.

Aaron:

Oh that is cool! I like a Leica…But, as might be obvious, I’m more into learning-by-doing, I want everyone on this team to play Immaculate Grid, a social game about baseball, really makes me think about game data in a relational way.

Ana:

Omg I LOVE baseball. I’m looking forward to when the kids can sit through a whole game. Our conversation on the CX Pod, however, of course made me revisit this article, Determining the true value of a website: A GSA case study, which Aaron and I co-wrote when we were closing in for the win on the Enterprise Digital Experience project, which include the website evals. 

Aaron:

Oh that was a good article! Glad you brought that one up. And yes, very pertinent to the topic of the CX Pod this week, 🤗

Credits

Host: Ana Monroe
Guest: Aaron Meyers
Producer: Ana Monroe
Words: A. Adams
Artwork: Workers on Girders of Auditorium, New Paris Opera c. 1867 Hyacinthe César Delmaet and Louis-Émile Durandelle. Via the National Gallery.
Why this artwork? People coming together to achieve a project is a common human experience. One that, in our opinion, is under celebrated. This beautiful photo wonderfully illustrates how people achieve goals, together.