The PM Job Is Mostly Alignment, Not Backlog Grooming

You are about to hire or promote a product manager. In your head, the job is clear: own the roadmap, groom the backlog, ship features. Then the person lands, and half their week goes to conversations, not tickets. You wonder if they are working. They are. The messy truth is that the PM job is mostly alignment and communication, and if you do not set that expectation up front, you will judge good work by the wrong yardstick and burn out the person doing it.

The backlog is the smallest part of the job

A PM who lives in the ticket queue looks busy and delivers little. The work that moves a product is getting people to agree on what matters and why, then keeping them agreed as things change. Productboard makes the case that a PM's real responsibilities are alignment and communication, not the feature list. The feature list is the output. Alignment is how you get a list worth building.

This matters for how you read your PM's calendar. Time in meetings and user calls is not time away from the work. It often is the work. If you want a quick gut check, watch Prasant Lokinendi walk through a real PM day, from standups to user calls to roadmap work. The tickets are the last stop, not the whole trip.

Managing a product means managing people you cannot boss

Here is the part that trips up new PMs and the leaders who hire them. A PM has responsibility without authority. They own the outcome but cannot order anyone to build anything. Alex Ewerlöf, writing from years as a programmer, puts it plainly: the product is made by people, and a PM's main job is to motivate and encourage the people doing the actual work.

That changes what "good" looks like. A PM who tells engineers what to build is doing it wrong. A PM who tells them why, so they can find a better how, is doing it right. Ewerlöf's list of ways to fail is really a list of alignment failures: no vision, no "why," no time with customers, no willingness to say no. Every one is about communication, not process.

Are they doing PM work, or just project work?

A lot of people with PM in their title are running projects, not products. They track tasks, chase deadlines, and report status. Useful, but not the same job. Mithil Srivastav draws the line: project work moves tickets across a board, PM work drives outcomes. If your "PM" spends the week updating a plan nobody argues with, you have project coverage, not product coverage.

The test is simple. Ask what decision your PM owns this quarter and what tradeoff they made to own it. If the answer is a schedule, you have a project manager. If the answer is a bet, with things they said no to, you have a product manager. Know which one you are hiring for before you write the job post.

Set the honest picture before day one

The daily reality is unglamorous and full of gray. Jason Shen has written about the parts nobody warns you about: the ambiguity, the politics, the stretches with no clear right answer. If you hire someone who expects clean roadmaps and gets fog instead, they will feel like they are failing when they are actually doing the job.

So say it out loud. Shelly Kalish's breakdown of everyday PM work is a good conversation starter for a new hire, because it names the invisible tasks that never make the highlight reel. And if your best candidate comes from an odd path, do not flinch. Jori Bell fell into PM by accident and found the old skills carried over. Judgment and communication transfer. A tidy resume does not guarantee either.

The deep cut

The thing easy to miss is that you, the leader, are the one who sets the wrong expectation. When you frame the role as backlog owner, you train your PM to measure their worth in tickets closed and reward the wrong behavior. Then you wonder why alignment is thin and engineers do not know why they are building. The fix starts before the hire. Write the role around outcomes and decisions, tell the person the day will be messy and full of conversations, and stop treating meetings and user calls as time stolen from "real" work. Set the honest picture, and you get a PM who spends time where it counts instead of one hiding in a queue to look productive.

Three questions for your team

• Are we doing product management or project management right now? Name the outcome our PM owns this quarter and the tradeoff they made to own it. If there is no tradeoff, we have a gap to fix.
• Where is our PM's time actually going, and does the split match the job? If the calendar is all backlog and no customer or team alignment, we set the wrong expectation and need to reset the role.
• Before the next PM hire or promotion, have we told them the honest picture, ambiguity, politics, and all? If not, we are setting someone up to feel like they are failing at the real job.