🚩Tactical Memo 111: How To Push Back When Your Boss Won’t Listen
She isn’t ignoring your numbers. She’s defending a sentence she already said in front of people.
Justin Bateh
November 03, 2026
Tactical Memo #111 | Navigating Modern Work · Management | 5 min read
Tactical Memo: a new issue every Tuesday, Thursday, and Sunday on career growth, AI at work, and modern management, read by 18,000+ leaders at Amazon, Deloitte, and Google. Forwarded? Subscribe free.
Free live lesson, Nov 11 How to Become a One-Person AI PMO. Wednesday, November 11, 11:00 AM EST. 90 minutes, live on Zoom, recording sent to everyone who registers. You'll see how agents run the repetitive parts of your projects with no code in the tools you're already allowed to use, how to get back about 8 hours a week from status reporting and follow-ups, how to keep one source of truth in a single project brain, and how to catch slips before your sponsor sees them. Live attendees also get my RCITO prompting framework, which is not in the recording. Register free |
Subscribers only, until 4pm EST today How to Handle Every Hard Conversation at Work. $27 for readers of this newsletter, today only. The price goes back up at 4pm EST. The conversation you've been rehearsing in your head for 3 weeks, handled. Scripts and structures for pushing back, delivering bad news, saying no to your boss, and resetting an expectation you never agreed to. Get it for $27 |
Enroll in the next live cohort AI-Powered Project Management. Stop rebuilding status updates, meeting notes, and plans from scratch every week. In 4 weeks you install my AI Project Operating System on your real projects, so the reporting runs on its own and your week goes to the decisions only you can make. Enroll today and the waiting room opens immediately. You get the prep materials and a head start on your setup now, so you walk into day 1 already running instead of getting oriented. Enroll in the next live cohort |
In brief The situation: Your boss decides fast, says it in front of people, and then nothing you bring moves her. The mistake: You come back with better evidence and argue the answer she already gave. The move: Stop refusing. Price the yes and hand the choice back to her. |
The story
She commits to the date in the meeting. The 15th.
You know it's 6 weeks of work and she's just promised 3.
So you build the case overnight. Vendor lead times, the test window, the 2 people already committed elsewhere. 1 page, sourced, impossible to argue with.
She reads it for 4 seconds and tells you the team will need to move faster.
She had already said it OUT LOUD.
She wasn't rejecting your evidence. She was protecting a commitment she made in front of her own boss, and your page asked her to take it back.
Your numbers were right. They were also 1 day late.
Once your boss has said her answer out loud, new facts stop sounding like information and start sounding like a correction. Here's how to work with it.
The moves
1/ Get there before she commits in public
Raise it while she's still forming a view, not after she's announced one.
A rough 2-line message the morning before the meeting beats a perfect 1-pager the morning after.
Before she commits, you're helping her decide. After, you're asking her to back down in front of people.
Say this "Before tomorrow's call, one thing worth knowing. The vendor came back at 6 weeks, not 3. Want me to bring options into the room or handle it after?" |
2/ Replace the refusal with a price
NEVER answer with a flat no. Answer with yes and what the yes costs.
The sentence is always the same shape. Yes, we can do that. Here is what moves.
A no starts a debate about you. A price starts a decision about the work.
Say this "Yes, we can hit the 15th. That moves the data migration to December and pulls 2 people off the reporting build. Do you want it that way?" |
3/ Convert your numbers into her units
She ignores your numbers because they measure your work. Story points, utilization, test coverage, open tickets.
Restate the same figure in what she is held accountable for. A date, a dollar, a headcount, a customer who notices.
Numbers in your units sound like an excuse. The same numbers in her units sound like risk to her.
Same data. Different owner.
4/ Hand her 2 options and a recommendation
1 option reads like a demand. 3 reads like you couldn't decide.
2 options, each with its cost, and a line saying which one you'd pick and why.
People defend the position they chose, so let her choose the one you wanted.
5/ When she's already jumped, attach a condition instead of a rebuttal
You will not reverse her in the room. Stop trying.
Agree with the direction and attach 1 check that fires before the damage does.
She keeps her decision. You keep a tripwire.
Say this "I'm with you on the 15th. One check. If the vendor hasn't confirmed by Friday, we both need to know that day, not at the end of the month." |
6/ Put the tradeoff in writing within the hour
Send a short recap of what was decided and what it costs. No argument in it anywhere.
Send it to her, not to the room.
Nobody remembers a tradeoff they heard once. People remember the one they read.
Do this "Confirming where we landed. We're holding the 15th. To do that, migration moves to December and Priya comes off reporting this month. Shout if I have that wrong." |
7/ Make her name the cut
Don't tell her the work doesn't fit. Ask her what comes out to make room.
When she names what gets dropped, the work shrinks and you never refused anything.
Ask this "What should come off my plate to make room for this?" "If both can't land this month, which one do you want first?" "What would you want me to protect if the date slips anyway?" |
8/ Spend your credibility on decisions, not on her delivery
She misreads the room sometimes. You will be right about that often, and being right about it buys you nothing.
Let the tone go. Push only where a wrong call costs money or time you can't get back.
You get a small number of pushes per quarter, and every one you spend on style is one you don't have for a date.
That fight is free to lose.
9/ Build the record so the next one is cheaper
Keep a running note of what you flagged, what she decided, and what happened.
Bring it back ONCE, with no victory lap in it. "Last quarter we held the date and testing got cut. We paid for that in February."
1 accurate prediction, repeated quietly, buys more room than 10 good arguments.
The outcome
| Most people | You |
|---|---|
| Bring the numbers after the call is made | Flag the risk before she commits in public |
| Say no and then defend it | Say yes and name what it costs |
| Argue in the team's units | Argue in the date, dollar, or customer she owns |
| Hand her 1 answer to approve | Hand her 2 options and a recommendation |
| Leave the tradeoff in the meeting | Put the tradeoff in writing the same hour |
Proof. James Detert at the University of Virginia has surveyed workers since 2018 on whether they push back to a boss or other senior person, and finds they do it about 1 time in 3. The rate barely improves for ordinary operational problems, the everyday slipping date and overloaded team. Most disagreement with a boss never gets said at all. University of Virginia, 2022
This week
You are not going to win this one by being more right.
The people who influence a boss like this aren't the ones with better evidence. They just get there earlier, and they price everything.
Try it next time she announces a date you know is wrong. Don't argue it. Send 2 options and what each one costs, and let her pick.
The only no she will ever accept is the one she makes herself.
Reply
What's the one call your boss made this year that you saw coming and couldn't stop? Reply with the decision. I read every one.
Until next time.
Justin Bateh, PhD
CEO @ AI Operators Lab
Founder & Editor, Tactical Memo