Okay so this took me a while: products don’t just show up out of nowhere. Someone has to figure out what users actually need, what will move the business forward, and how to turn that into something real. That’s product management—not just tracking projects or running ads, but deciding what gets built and why.

If you’re picturing a product manager (PM) as the boss or the coder, that’s off. PMs own the product’s success, but they don’t write code or do the selling. They spend their days discovering user needs, setting direction, and working with teams to deliver. PMs align stakeholders and make tough calls, but don’t manage people directly.

Discovery is where it all starts. PMs dig into what users actually need—what annoys them, what they wish existed, what they’d really use. That means interviews, usage data, even rough prototypes. Skip this and you risk building something nobody cares about.

After discovery, it’s time for strategy. This is where PMs choose which problems to solve, for which users, and how. They balance what users want, what the business needs, and what’s actually possible. A real strategy means saying ‘no’ to most things, so the team can focus on what matters.

Execution is where strategy meets reality. PMs work with designers, engineers, and others to actually build and launch the product. They clarify what’s most important, answer questions, and clear roadblocks. It’s not just about speed—it’s about making sure the right thing ships.

Here’s the thing: the cycle doesn’t stop after launch. Discovery, strategy, and execution repeat as user needs and markets shift. PMs keep looping back, because what worked last month might flop today. Iteration isn’t failure—it’s how products get better.

PMs never work alone. Stakeholders might be engineers, designers, sales, support, leadership—even customers. Each brings their own priorities. PMs juggle these perspectives, aiming for alignment. That doesn’t mean everyone’s happy, but it does mean decisions are clear and informed.

Great products come from cross-functional teams—designers, engineers, QA, data folks, and more. PMs don’t ‘boss’ these people around; instead, they guide, clarify, and unblock. The magic happens when everyone shares context and trusts each other, not when they’re just checking boxes.

Here’s the reality: resources are always limited—time, people, money. PMs have to prioritize. Every call has tradeoffs: speed vs. quality, new features vs. stability, delight vs. business needs. Most days, PMs make decisions with incomplete info and lots of gray area.

Let’s clear this up: PMs aren’t project managers, manufacturers, or just marketers. They don’t write code or own every decision. Product management is about the full journey—discovering needs, shaping solutions, and iterating, not just running a checklist or campaign.

One hour, you’re interviewing users. Next, you’re prioritizing features. Then, you’re clarifying requirements with engineers. PMs jump between discovery, strategy, and execution—sometimes all in a single day. It’s a constant mix of context-switching, decision-making, and keeping the product moving forward.

Product management is a mindset: curiosity, clarity, and constant learning. It’s about discovering what matters, shaping a path, and rallying teams to deliver real value. Keep exploring: Teresa Torres’s ‘Continuous Discovery Habits’, Marty Cagan’s ‘Inspired’, or the ‘Product Management’ section on Mind the Product.