Whoever accepts a request on the spot either has no strategy, or has one but doesn't yet trust it enough to defend a "no."
In leadership roles (senior PM, head of product, tech lead), the instinct is to respond quickly to requests. It feels collaborative, avoids friction, shows willingness. It is exactly the opposite signal. Someone who says yes fast typically either doesn't have a full picture of what is already prioritized, or has that picture but hasn't built the vocabulary to defend priorities out loud. In both cases, the person is confusing availability with delivered value.
The opposite posture is to accumulate "thoughtful nos." This doesn't mean refusing: it means pausing, adding context, and responding with the current hierarchy of priorities. In practice, it turns into phrases like:
- "That makes sense. Where would this fit compared to X and Y, which are already on the list?"
- "For this to go in now, what comes out? I can help you decide."
- "Is this a tactical or a strategic request? The answer changes how I handle it."
The image is not mine: it came from a senior Engineering Manager I worked with at Unico, in a 1:1. "I wouldn't want you to become a corner-store peanut vendor PM, someone who never has the whole strategy in hand." Accepting any request because everything seems important is exactly that: losing sight of the whole strategy. A senior product leader stands out for what they choose to leave off the list, not for what goes on it.
This principle came from direct feedback I received in a 1:1, from the same Engineering Manager: "don't say yes right away, collect thoughtful nos." I have carried it with me ever since, and today it is one of the first things I pass on to people I mentor in the transition to product leadership.