Engineering often defaults to a 'project mindset,' focusing on churning out features and measuring velocity. True alignment with product requires a 'product mindset,' which prioritizes understanding the customer and tracking the value being delivered, not just the output.

Walmart reframed planning around desired outcomes, not feature lists. This gave engineering teams the flexibility to innovate on solutions, increasing engagement and productivity, despite initial resistance from leadership accustomed to feature-based roadmaps.

The old product leadership model was a "rat race" of adding features and specs. The new model prioritizes deep user understanding and data to solve the core problem, even if it results in fewer features on the box.

A true product-led culture doesn't mean the product team dictates decisions. Instead, its primary function is to surface and clearly frame cross-functional tensions and trade-offs, enabling the entire organization to make cohesive, system-wide decisions.

The question "do we need product management?" often arises from a fundamental misunderstanding of the role. When organizations use product managers like a hammer to cut a branch (ship features) instead of hammering a nail (solve the right customer problem), they are misusing the tool and will inevitably question its value.

Product leaders often try to implement agile best practices within their team, but fail because the surrounding organization still operates on a project-based model. The rest of the company treats the product team like a feature factory, handing over requests and demanding deadlines, creating immense internal friction.

Product leaders should reframe roadmaps from a list of features to a series of barriers they are removing for customers. This shifts focus to high-leverage outcomes like reducing complexity, enabling zero-handholding onboarding, and accelerating time-to-value.

To get product management buy-in for technical initiatives like refactoring or scaling, engineering leadership is responsible for translating the work into clear business or customer value. Instead of just stating the technical need, explain how it enables faster feature development or access to a larger customer base.

When introducing product management into a legacy organization, a critical mindset shift is required: moving from a project-centric view to a product-centric one. Success isn't the launch; it's the beginning. The focus must be on long-term product health and measurable outcomes, not just on-time delivery of outputs.