The Subtle Shift: Janna Bastow on Distinguishing Product Management from Project Management

In a recent LinkedIn post, Janna Bastow explores a common inflection point for professionals in product-focused roles: the moment they realize their responsibilities lean more towards project management than true product management. Bastow uses her own early-career experiences and insights from ProdPad customers to highlight the subtle, often unnoticed, shift from strategic discovery to relentless delivery.

The Allure of Delivery Over Discovery

Bastow begins by recounting a personal realization: “I realized I wasn’t a product manager. I was a project manager.” This moment of clarity, she suggests, is more common than acknowledged. She elaborates on how, in early-career stages, the pressure to “deliver” can overshadow the essential work of understanding user problems and market needs. This often manifests as discovery phases being traded away for immediate output, sales teams making commitments that the product team must then fulfill, and strategy becoming an afterthought.

“Discovery kept getting traded away for delivery. Sales sold. Teams scrambled. Strategy was something discussed after the fact.”

According to Bastow, this environment can feel productive on the surface, characterized by busyness and apparent success. However, she points out that in hindsight, the pattern reveals a lack of dedicated time for problem exploration and an inability to decline requests that don’t align with strategic goals. This leads to a growing backlog of commitments driven by external pressures rather than internal product strategy.

The Impact of Constant Delivery Pressure

Bastow highlights that this dynamic is particularly prevalent in B2B environments, where “customization is framed as responsiveness.” While acknowledging that such a phase might be necessary for survival or initial traction, she warns of the dangers when it becomes the permanent state of operation.

“But if it never ends, it reshapes your role and your skills without asking your permission.”

In Bastow’s view, a prolonged focus on delivery without a corresponding emphasis on learning and problem validation can fundamentally alter the nature of a product role. The skills developed become those of a project manager—coordinating tasks, managing timelines, and ensuring output—rather than a product manager, who should be focused on identifying and solving the right problems for the right users.

Identifying and Addressing the Shift

The core challenge, as Bastow articulates, is not necessarily spotting this shift but rather deciding on a course of action once it’s recognized. “The hard part isn’t spotting it early. It’s deciding what to do once you’ve named it,” she writes. This implies a need for deliberate strategic choices to reclaim the product management function, which may involve setting clearer boundaries, prioritizing ruthlessly, and re-establishing the importance of user research and problem definition within the organization.

The Central Question

Bastow concludes by posing a reflective question to her audience: “When did you first realize you were optimizing for delivery instead of learning?” This prompts a broader conversation about the common pitfalls in product development and the importance of maintaining a healthy balance between execution and strategic exploration. Her insights underscore the critical need for product leaders to be vigilant about the true nature of their work and to actively shape their roles around genuine product discovery and problem-solving, rather than succumbing to the pressures of constant delivery.