Read time: 7 minutes

Welcome to Tactical Memo, my memos on helping leaders and teams execute and operate smarter in the AI era. Each issue delivers a field-tested framework for a real leadership and management problem.

👉 Why Read This Edition: You will learn how to push back on your boss or a senior leader without damaging the relationship, and why the people who never say no are usually the first ones to get passed over.

Upcoming Free Webinars

Become the Project Manager Everyone Wants to Work With
Monday, April 20th at 11:00 AM EST
30 Minutes
Live on Zoom, Register here

The 4 Phase AI Framework Every Project Manager Needs
Friday, April 24th at 11:00 AM EST
30 Minutes
Live on Zoom, Register here

THE PROBLEM

Here is an unpopular opinion. The person on your team who says yes to everything your boss asks is not a team player. They are a liability. And deep down, your boss knows it.

Your VP walks into your office on a Tuesday. She needs a new report by Friday. You already have a launch on Friday. A steering committee on Thursday. A client escalation that has been sitting in your inbox for three days. You open your mouth to explain the load, and out comes, "Sure, no problem, I will get it done."

You walk back to your desk and immediately resent her for it. You resent yourself more. You know you are going to be up until 1am on Thursday eating the cost of a decision you made in four seconds.

Most people handle this situation in one of three ways, and all three are pathetic.

The first type says yes to everything and silently drowns. They think agreeability is a career strategy. It is not. It is a slow way to become the person everyone dumps work on and nobody takes seriously for the next level. The promotion does not go to the person who said yes the most times. It goes to the person whose judgment the boss trusts. You cannot demonstrate judgment if you have never said no.

The second type says no, but does it badly. They get defensive. They list their current projects like a grocery receipt. They explain why they cannot. They sound like they are making excuses, and everyone in the room feels it. The boss walks away thinking, "I need someone who can handle pressure." That person just lost credibility without realizing it.

The third type plays political games. They say yes in the meeting and then quietly deprioritize the work, hoping the boss forgets. They move slowly, send vague updates, and pretend they are making progress. This is the worst of the three. It is cowardice dressed up as compliance. And every senior leader I have ever worked with figures it out within two cycles.

All three share the same root problem. They treat "no" as a rejection of the person asking. It is not. A good no is a business decision. And senior leaders, the real ones, respect a well-reasoned no far more than a hollow yes.

THE FRAMEWORK

THE STRATEGIC NO FRAMEWORK
(download a free copy of this framework here)

I spent years running recovery teams and consulting engagements where I reported to CEOs, COOs, and partners who had no patience for excuses and no tolerance for incompetence. The ones I worked best with were the ones I learned to push back on. Here is the framework I built.

Part 1: Agree with the goal before you disagree with the request

Here is what most people get wrong. They hear the ask and immediately start defending their calendar. That is a losing move. You are signaling that your workload matters more than the thing your boss just said was important.

Start somewhere different. Start with the outcome she is trying to get to. "I want to make sure we hit the board deadline on the Q3 report. Let me tell you what I am seeing on my side so we can figure out the best path." Now you are not opposing her. You are aligned with her goal and problem-solving out loud.

This is not a trick. It is the truth. Your boss does not actually care about the report. She cares about what the report unlocks. The board meeting. The budget approval. The CEO's question from last week. When you name the real outcome, you move the conversation from "do the task" to "solve the problem." And solving the problem might not require the task at all.

Here is what you do not do. You do not lead with "I am really busy." You do not list your projects. You do not say "I do not think this is a good use of my time." Every one of those signals that you think your time is more valuable than hers. Whether or not that is true, it is a conversation you will lose every time.

I ran a recovery team a few years back where the CEO wanted a weekly deep-dive deck on a failing initiative. I did not want to build it. Not because I was lazy. Because building it meant pulling two engineers off the actual recovery work. I did not tell him no. I asked him what decision the deck was helping him make. He said he wanted visibility into whether we were on track. I offered him a 15-minute standing call instead. He took it. The deck never got built. The recovery shipped on time.

Part 2: Show the tradeoff in her currency, not yours

Senior leaders do not think in tasks. They think in priorities and tradeoffs. If you cannot speak that language, you are going to lose every negotiation.

When you need to push back, you need to show, very specifically, what gets dropped, delayed, or degraded if this new thing jumps the line. Not in vague terms. In her terms. The launch that she presented to the CEO last month. The client she named in the all-hands. The deadline that the board is expecting.

Say it like this. "I can absolutely take this on. If I do, the March launch slips by two weeks and I will need to tell the sales team they are demoing old features at the conference. Do you want me to make that tradeoff, or is there another option we should look at?"

Now she has to make the call. Not you. That is the entire point. You are not saying no. You are handing the decision back to the person who actually has the authority and the context to make it. Peter Drucker wrote about this decades ago. The job of a leader is to make priorities clear. When priorities conflict, somebody has to decide. If you decide unilaterally by saying no, you are overstepping. If you decide unilaterally by saying yes and then silently missing the other deadline, you are being dishonest. The right answer is to surface the tradeoff and let the right person choose.

Here is what you do not do. You do not say "I will try." You do not say "I will see what I can do." Those phrases are career poison. They sound agreeable and they buy you forty-eight hours of peace, but they guarantee a worse conversation later when the work does not ship. Be precise. Name the cost. Let her pick.

Part 3: Offer a better option if you have one

This is the part that separates the people who get promoted from the people who stay stuck. Do not show up with a problem. Show up with a path.

If you genuinely cannot take on what she is asking, do not end the conversation there. Give her a real alternative. A different person who has the bandwidth. A different timeline that actually works. A smaller version of the ask that gets her 80% of what she needs for 20% of the effort. A question that reframes the problem entirely.

Your boss is not hiring a task executor. She is looking for someone who can think. Every time you turn a "no" into a "here is how we get this done better," you deposit trust into the relationship. Over time, those deposits compound. The people who get the stretch assignments and the corner office are not the ones who said yes the most. They are the ones whose judgment their boss learned to rely on.

Here is what you do not do. You do not offer a fake alternative just to look helpful. If the alternative is worse than the original ask, do not suggest it. Senior leaders see through that immediately. Only offer it if you would bet your reputation on it, because that is what you are doing.

Part 4: Say the actual word

After all of that, there are still moments where you have to say no. Clean. Direct. Without hedging.

Most people cannot do this. They soften it until it disappears. "I am not sure if this is the best use of our team right now, but I could maybe look at it if things shift, although I do have a lot going on, so let me circle back." That is not a no. That is a five-sentence apology for having an opinion.

Say it like an adult. "I do not think we should do this, and here is why." Then explain. Briefly. Without apologizing. Without hedging. Without the word "just."

Your boss is not going to fall apart. She is a senior leader. She negotiates with other senior leaders all day long. The worst thing you can do is handle her like she is fragile. Treating her like an adult who can hear a direct opinion is not disrespectful. It is the highest form of respect you can offer.

THE REAL TEST

Here is the question that tells you whether you did this right.

Did your boss walk out of that conversation with more trust in your judgment, or less?

If she walked away thinking, "That person actually thinks about tradeoffs and tells me the truth," you won. Even if the answer was no. Even if she pushed back. Even if she overruled you.

If she walked away thinking, "That person is difficult and makes everything harder," you did it wrong. Not because you said no. Because you said it in a way that was about you, not about the work.

The best leaders I have worked with under pressure all had the same quality. They made me better at my job because they told me the truth. When they pushed back, it sharpened my thinking. When they agreed, I knew it was real. I never had to wonder whether they actually believed in what we were doing. That kind of trust is worth more than a hundred eager yeses.

This week, pick one request on your plate that you know, deep down, you should have pushed back on. The meeting you did not need to attend. The report nobody reads. The favor that will cost you six hours you do not have. Go back to the person who asked. Tell them what you are seeing. Offer them a better path or ask them to make the tradeoff. Fifteen minutes, that is it.

Watch what happens. The relationship will not break. It will get stronger. Because you just treated them like the decision-maker they are, and you just showed them that you are the kind of person whose word actually means something.

That is how you say no without burning the bridge. You do not burn the bridge. You build it.

If this helped you, send it to someone who could use it this week.

Until next time,
Justin

P.S. Here are my upcoming workshops and courses:

Build Your Execution Sense: The Edge AI Can’t Automate: 1 Day Workshop. When AI gives everyone the same tools, execution sense is what's left.

Run Your Week On Autopilot with Claude Cowork: 1 Day Workshop. Your work is everywhere. We will show you how to pull it all together.

AI-Powered Project Management: 4 weeks, live cohort. Build the skills to apply AI to your real projects, starting week one.

Project Management That Actually Works: 4 weeks, live cohort. Build the project management skills that actually drive outcomes.

✍️ From the Desk of Justin Bateh, PhD
Simple tactics. Real results. No fluff.