🚩Tactical Memo 110: AI Took the Visible Half of Your Job
The reporting runs itself now. So does your absence from the room.
Justin Bateh
November 01, 2026
Tactical Memo #110 | Navigating Modern Work · Career | 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.
Enrollment closes tonight Become an AI-Powered Project Manager. Tonight is the deadline to enroll in the November cohort, and it is the final cohort of 2026. The price goes up in 2027, so this is the last group at the current rate. 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. You'll get the 5-part prompt structure that gets executive-ready output on the first try, the 4 agents that take status updates, meeting notes, planning, and stakeholder comms off your plate, and the scope workflow that logs every new ask the day it arrives and prices it against the date. Enroll before tonight's deadline 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 November cohort |
In brief The situation: The work you automated first was the work leadership actually saw you do. The mistake: Most people take the hours back and say nothing about it. The move: Put your judgment on top of the output and spend the hours visibly. |
The story
The status report that used to take 90 minutes now takes 6.
The meeting notes summarize themselves, and the steering deck rebuilds off last week's version.
You got your Friday afternoons back.
Then the quarter closes and nobody mentions any of it.
The thing that put your name in front of leadership every single week is now a task that runs in 6 minutes.
The tools took the most repetitive part of the job first. That was also the most watched part of the job.
If your calendar got lighter this year and your standing in the room did not get bigger, that is the trade you made without ever agreeing to it.
The first part of your job AI takes is usually the part that was making you visible. Here's how to work with it.
The moves
1/ Audit what used to carry your name
List what you produced 12 months ago that leadership actually opened and read.
Mark the ones a tool now writes for you.
You cannot rebuild visibility you have not noticed losing.
Checklist The artifacts leadership read with your name on them. Which of those a tool now produces. What you spend those hours on now, and who has seen it. |
2/ Put a judgment line on top of every automated artifact
The update still goes out. Add 1 line above it that only you could have written.
What you decided, what you are watching, and what you want from the reader.
The output stopped being proof of anything. The call sitting on top of it is the proof.
Do this "My recommendation is to hold the launch date and cut the migration. The vendor slipped 2 weeks and integration testing has not started." |
3/ Say what the tool did and what you checked
Name the automation plainly, then name the part you verified yourself.
People find out either way, and finding out later costs you more than telling them now.
Hiding the tool makes your contribution look smaller, because the only part left to see is the draft.
Say this "The draft is agent-generated. I verified the vendor dates and both numbers in the risk table myself." |
4/ Spend the reclaimed hours where people can see you
The time came back. If it all goes into more work nobody watches, your standing drops while your output holds steady.
Put a few of those hours into the conversations where the decisions get made.
Hours you win back only count as a gain if somebody watches you spend them.
5/ Take the work the tool cannot take
Go find the messy, cross-team, politically loaded problem everybody has been walking past.
That part is still yours.
A model will NEVER own a decision that 3 directors disagree about.
Work that needs a human judgment call is work your name stays attached to.
6/ Hand your setup to the team
Write down how you built it and run 1 session walking the team through it.
You lose nothing by giving it away, because the setup was never the scarce part.
Automating your own job happens quietly. Automating the team's job happens with your name on it.
7/ Say the time savings as a business number
Count what actually came back and say it ONCE, in the room where budgets and headcount get discussed.
Say where the time went, not only that you saved it.
Hours saved stay invisible until somebody turns them into 1 sentence a leader can repeat.
Say this "Reporting takes 4 hours a month now instead of 20. I moved that time onto vendor risk, which is where the schedule actually moves." |
The outcome
| Most people | You |
|---|---|
| Automate the visible work and say nothing | Name the tool and name what you checked |
| Send the clean artifact and stop there | Put your own call on top of it |
| Pour the saved hours into more unseen work | Spend some of them where decisions get made |
| Keep the setup to themselves | Hand the setup to the whole team |
| Hope the time savings get noticed | Say the number once, in business terms |
Proof. Microsoft's Work Trend Index found that 87% of employees said they were productive while 85% of leaders said the shift to hybrid work had made it hard to feel confident that people were, a gap Microsoft tied to managers losing the cues they used to read work by. Microsoft, 2022
This week
Nothing about your work got worse this year. A part of it just stopped being watched.
And you were the last to notice.
The people handling this well are not using fewer tools. They moved what leadership sees from the artifact to the decision, and they said so out loud while they were doing it.
Try it on the next update that writes itself. Add the line only you could write, and sign it.
An automated job is not a safe job. It is a quiet one.
Reply
What is the 1 thing you automated this year that people used to thank you for? Reply with the task. I read every one.
Until next time.
Justin Bateh, PhD
CEO @ AI Operators Lab
Founder & Editor, Tactical Memo