The Art of the Strategic Yes and No

One of our favourite podcasts, HBR IdeaCast from Harvard Business Review, ran an episode in 2020 that we keep thinking about. Host Alison Beard sat down with Bruce Tulgan, founder and CEO of RainmakerThinking and author of The Art of Being Indispensable at Work, to talk about a problem every busy professional knows well: too many requests, and too little knowledge on how to respond to them.

Why we say yes too often

Tulgan opens with a diagnosis on why we say yes so often and with so much ease. Most people in the workplace want to be the indispensable go-to person, and that desire gets stronger during uncertain times, when jobs feel less secure and proving value feels urgent. People say yes because they fear disappointing others, even when they know they cannot realistically take on everything being asked of them.

What happens then? Overcommitment. Tulgan describes the pattern: you juggle too much, you work constantly, you start disappointing people anyway, delays and mistakes creep in, and relationships suffer. Eventually you develop what he calls a "siege mentality". At that point you start saying no, but for the wrong reasons. You are no longer evaluating the quality of the request or the person making it; you are simply reacting to feeling overwhelmed.

What makes a yes a 'bad yes'

A bad yes, in Tulgan's framing, happens when someone agrees to a request they genuinely cannot deliver on, whether because of missing skill, missing authority, or missing capacity, but says yes anyway because in the moment they want to please. The issue is that yes carries weight. Yes takes time and energy. Yes raises expectations. If you fail to deliver, or you deliver the wrong thing, that becomes what you are known for.

The intake memo habit

Before deciding anything, Tulgan recommends tuning into the request itself. Pay attention to the ask. Take notes. Ask clarifying questions: what exactly is needed, when is it needed, how is it needed, why is it needed. This is what he calls the intake memo habit, and it does two things at once. It shows the person making the request that you are giving it proper attention, and it helps you understand whether the request is as small as it first appears, or much bigger.

This does not mean turning every minor favour into a formal process. Tulgan's own example is a request for a paper clip: even there, a quick clarifying question (a big one or a small one?) prevents a mismatch later. The habit scales up or down depending on the size of the ask, but the instinct to clarify before committing stays constant.

The no gates framework

Once a request has been properly understood, Tulgan applies a simple three-question filter before deciding how to respond. He borrows the language of "gate review" from complex project management, where projects move through stage gates before proceeding, and adapts it into what he calls the no gates. The three questions are:

1. Can you do this? This is the capacity and skill question. Do you have the ability, the knowledge, and the available time to actually deliver on what is being asked?
2. Are you allowed to do this? This is the authority question. Is this decision yours to make, or does it sit with someone else in the organisation, whether that is your manager, a client, or a governance process?
3. Should you do this? This is the priority and strategic fit question, and it is probably the most difficult self-evaluation. Even if you can do it, and you are allowed to do it, does it deserve your time more than the other things competing for it?

Running a request through these three gates gives far more clarity than reacting in the moment. A request that fails the first gate needs a different kind of yes (delegate it, or flag it as a stretch opportunity).

A request that fails the second gate is straightforward to redirect, because the decision genuinely sits elsewhere.

A request that passes the first two gates but fails the third is the hardest one, because it usually means saying no to something you could technically do, simply because something else matters more right now.

How to communicate the decision

Tulgan is candid that no amount of careful phrasing makes a no pleasant to hear. What makes a no land well is everything around it. Reputation does a lot of the work here: if you have a track record of sound decisions, people trust your no even when they are disappointed by it. In the moment, explaining the reason behind the no (you cannot do it, you are not allowed to do it, or it should not take priority right now) makes it read as a business decision rather than a personal rejection.

Tulgan also points out that the right answer is often not a flat no at all. "Not yet", "yes, in two weeks", or "no, not framed this way, but reframe it and the answer might be yes" are all legitimate outcomes of running a request through the no gates.

Making a yes count

A yes deserves the same discipline as a no. Tulgan describes the strongest yes as one given in your area of specialty: something you already know how to do well, fast, and with confidence, where you know exactly how to deliver and how long it will take. The next best yes is an honest stretch opportunity, where you are transparent that this is not yet your specialty but you would like it to become one.

What matters most, in Tulgan's view, is execution rather than perception. Saying yes at the wrong time, to the wrong request, undermines your career far more than a well-reasoned no ever could, because it puts you in a position where you either fail to deliver or deliver something of limited value. Every good yes is a chance to attach tangible, valuable results to your name.

Power dynamics and the vertical anchor

Tulgan acknowledges that not every yes or no is entirely within your control. He introduces the idea of a "vertical anchor": no matter how flat or collaborative a workplace tries to be, someone is ultimately in charge, and recognising that is liberating rather than limiting. The practical advice is to maintain an ongoing dialogue with whoever you report to, so they understand your priorities and your strengths. That does not mean you only work within your area of passion; sometimes the answer from above is simply that something needs to get done regardless. Once you know what is not up to you, everything else becomes your call to make.

Redefining influence

The most distinctive point in the conversation is Tulgan's challenge to a piece of conventional wisdom: that if you lack authority, you should use influence instead. He argues this often gets twisted into influence peddling, badgering, bargaining, withholding support, or going over someone's head to get what you need. Every time you try to use influence this way, Tulgan argues, you lose it.

Real influence, by contrast, comes from being someone others trust, want to work with, and want to see succeed. The people who consistently appear on every "go-to person" list are not focused on extracting what they need from others; they are focused on what they can bring to the table. They are willing to be seen as difficult in the moment, because their underlying commitment is to service, not to being liked.

A closing thought from the episode

Tulgan's parting advice, given to listeners navigating the pressures of 2020: know exactly how many hours you have in a week, account for sleep, family, and basic needs, and then offer your time in specific, allocated blocks rather than vague claims of being "too busy". Saying "I have four hours on Thursday I can give this" signals far more discipline and respect for the other person's request than a generic decline ever could.

We find this conversation valuable because it reframes yes and no as business decisions rather than personality traits. We try to apply the same discipline at Xcelerate when we evaluate which client requests, internal projects, and opportunities deserve our time.