All writing
2 min read

Working With the Product Manager Who Wants You to "Make It Pop"

You will not out-argue the PM who wants you to "make it pop." How to work with the difficult one, minus the sabotage fantasies.

Somewhere in your company there is a product manager whose entire feedback vocabulary is "can you make it pop" and "let's circle back." You will not out-argue this person. I've watched people try. It's like teaching a cat to fetch - technically possible, but mostly it just stares at you.

So let's talk about actually working with the difficult PM, because "difficult PM" is not a rare bug. It's a standard feature of the job.

First, separate the two cases, because the fix is different. Is this person difficult with everyone, or just with you? Ask around, quietly. If it's everyone, relax - it's not personal, it's just weather. If it's only you, that's worth a calm, direct conversation now, before it becomes a story you tell bitterly for years.

A few things that genuinely help:

Put it in writing, minus the attitude. After every fuzzy verbal request, send the boring confirmation. "Confirming: I'll take X, due Tuesday, scope is Y. Shout if that's wrong." Nobody can call a confirmation email passive aggression. It just happens to make a vague request impossible to deny three weeks later. Funny how that works.

Make him choose. "Happy to do the seventeenth revision. That, or the thing you greenlit on Monday. Not both by Friday, so which one?" You're not refusing. You're handing back the tradeoff he keeps pretending isn't there.

The loaded "interesting." When a request makes no sense: "Interesting. Help me understand the user impact." Said flat, it does most of the work. Either they explain and you learn something, or they hear themselves out loud and quietly retreat. Both are fine outcomes.

Appeal to what they actually want. Most difficult PMs aren't villains, they're anxious about shipping and looking good. "To design the right thing I need to be in the strategy meeting - how do we make that happen?" lands better than a fairness argument. Frame it as their win, not your right.

What this is not

This is not a sabotage guide. I know the fantasy: "accidentally" lose his files, book the review during his lunch, start an office pool on when he cracks. Don't. It's beneath you, it's an excellent way to become the person who quietly gets managed out, and the best revenge has always been the same boring thing - do excellent work, document it, and let the contrast speak for itself.

You can't fix the PM. You can control how clearly you communicate, how well you document, and how calmly you escalate when it genuinely matters. Most of the fighting between design, engineering, and product comes down to this: design wants it pretty, you want it shippable, the PM wants to look good in the demo. Say that out loud, with a straight face, and half the drama evaporates. The other half you save for the group chat.