🚩Tactical Memo 089: Your Boss Doesn't Want Update

In partnership with

Welcome to Tactical Memo: Tactical advice for managers running teams, projects, and operations in the AI era. Read by 18,000+ leaders at Amazon, Deloitte, and Google. If someone forwarded this to you, join our free community here.

Speak naturally. Send without fixing.

Wispr Flow turns your voice into clean, professional text you can send the moment you stop talking. Not rough transcription you have to clean up. Actual polished text — ready for email, Slack, or any app.

Speak the way you think. Go on tangents. Change your mind mid-sentence. Flow strips the filler, fixes the grammar, and gives you text that reads like you spent five minutes writing it.

89% of messages sent with zero edits. Millions of professionals use Flow daily, including teams at OpenAI, Vercel, and Clay. Works on Mac, Windows, and iPhone.

Start flowing free

Quick announcements

I launched a YouTube channel. It's built for new managers: the people who got promoted and then got handed nothing. 👉 Can you subscribe here? I’d love to get some momentum going on it.

On Friday, August 21 at 12:00 PM EDT, I'm teaching a free 30-minute session that walks through the exact system I use to take a project from assignment to launched in 48 hours. 👉 Save your seat here.

The most detailed status report I ever wrote earned me a meeting I didn't want.

Early in my career, I sent my boss a weekly update that ran three pages. Every task listed, every blocker explained. I told myself I was being thorough.

Monday morning, I was in his office. He hadn't read past the first paragraph. He said the length alone told him something was wrong, because people who have things under control don't need three pages to prove it.

He was right, and it stung, because I knew exactly what those three pages were. They were a shield. I wasn't reporting. I was building a defense file so that when something slipped, I could point to page two and say I flagged it.

That's cowardice dressed up as diligence. A lot of you are doing it right now.

Here's the truth nobody tells you: your boss does not read your update to learn what you did. Your boss reads it to answer one question. Do I need to get involved? Every word you write either answers that question or hides from it.

Here is how I report up now.

1/ Answer the worry, not the question

Before I write a word, I figure out what my boss is actually losing sleep over this week. The renewal. The launch date. The hire that won't close. My first sentence hits that one thing head-on. Most people skip this step because facing the scary thing directly feels risky, so they write around it and hope. Hope is not a reporting strategy. Kill the worry in sentence one or everything after it gets read with suspicion.

2/ Open with a verdict

Every update I send starts with one of three words: on track, at risk, or off track. No warm-up. No context first. My boss told me it's the only part he reads on a busy day. When you make someone hunt for the bottom line, they assume you buried it on purpose, and most of the time they're right. If you can't state your verdict in three words, you don't have a status problem. You have a thinking problem.

3/ Keep it to one paragraph, sent the same day

My boss gets one paragraph from me every Friday at 4pm. Same length, same time, every single week. After a month of Fridays, my silence on a Tuesday means nothing is wrong. That's the asset. Long reports don't signal effort. They signal fear, and executives can smell it through the screen.

4/ Put bad news in the first line

When something breaks, it goes first, in plain words: "We missed the integration deadline." I learned this the hard way. I buried a slip in paragraph two once, and my boss found it anyway. He forgot the slip within a week. He never forgot where I put it. Burying bad news is lying with formatting. It costs you the benefit of the doubt on every report you send after, and you don't get that back.

5/ Pair every risk with what I'm doing about it

I never name a problem without naming my next move in the same breath. "The vendor is two weeks behind, so I moved testing up and I'm in their office Thursday." A risk with no plan attached is you handing your boss a job. Do that enough times and he'll conclude you can't carry your own project, and he'll be correct. Report the fire and show him you're already holding the hose.

6/ Make one ask, or say I have none

Each update ends with a specific ask ("I need ten minutes with legal before Wednesday") or the sentence "Nothing needed from you." That second sentence took me years to write, because it removes the escape hatch. Once you say nothing is needed, you own whatever happens next. Weak operators keep things vague so blame has somewhere to hide. Strong ones close the door on purpose.

7/ Write it so it can be forwarded

I assume my boss will forward my update to his boss without touching it. So I spell out the acronyms and cut any whining I wouldn't want read two levels up. Twice I've learned my paragraph went straight to a VP untouched, and both times my boss looked sharp for sending it. Making your boss look good upstairs is the quietest promotion strategy there is. Making him edit your work first is the quietest way to stall.

Insider Tip: Look at the operators who get left alone. Their projects aren't smoother than yours. Their bosses just stopped checking, because every report they ever sent answered the question before it was asked. That's earned. Nobody hands it to you.

Do This Now: This Friday, cut your update to one paragraph and open with a verdict. If that scares you, sit with why.

Free Library of Cheat Sheets👇

I put together a bundle of my top playbooks and cheat sheets for people who want to think sharper, lead better, and navigate the real career rules most people only learn the hard way → Grab it here for free.

Until next time,

Justin Bateh, PhD
Founder and Editor
Tactical Memo