4.8 Yes, But…

There’s a version of most PMMs, especially early in their careers, that says yes to everything, finishes everything, and never lets anything drop. It feels like building a reputation as someone who delivers. It’s actually building a reputation as someone who’s tired.

What Gets Missed

PMM sits at the connective tissue between Product, Sales, and Marketing. Everyone needs something from us, and being needed feels good — so we say yes, and yes again. What’s invisible in the moment is the math: every yes is a unit of capacity, and capacity is finite. Say yes to five things with bandwidth for three, and you don’t find extra hours — you spread thinner. Quality drops. Delivery slips. Work that should be great becomes good, then okay, then not.

Two lines worth remembering, from a manager who said them plainly: “You’re better to deliver 3 things awesome than 5 things average.” And: “The business responds to pain, not pleasure.” By saying yes to everything, there’s no visible evidence of a capacity gap — no dropped balls, no missed deadlines that can’t be explained away. Which means no business case for more resources, and no urgency to add capacity. Saying yes to everything tells the organization “I got this.” You don’t got this.

The Power of the Z Axis

Most prioritization conversations think in two dimensions: the what and the why. There’s a third axis that gets forgotten: the when.

“Yes, but when?” is not a negotiation tactic — it’s a clarifying question that forces a real conversation about trade-offs. It says: I hear you, I want to do this, and I need you to help me understand where it lives relative to everything else I’m holding. The full version sounds like: “Yes, I can take that on. To do it well, I’d need to push the launch brief back a week, or drop the battlecard refresh to next cycle. Which one would you rather trade?” Now the stakeholder is in the conversation, not just handing off a task to be silently degraded.

What This Does

Saying “yes, but…” doesn’t make you look weaker — leaders do it every day, and they notice when a team member does it too. It signals you understand what quality takes, that you’re managing a function and not just a to-do list. And when you’re honest about trade-offs, you create the visibility the business needs to understand your actual capacity — which is how you build a case for real resources, not just absorb more load quietly.

This isn’t an argument for reflexively saying no by default — that just makes you a bottleneck instead of a partner. The goal is to be helpful in a way that’s sustainable and high quality, and “yes, but” is what starts that conversation honestly.

Full post: Yes, but … →