🚩Tactical Memo 106: You’re Paid for Judgment, Not Answers
The answer takes 40 seconds now. The call still has to come from you.
Justin Bateh
October 25, 2026
Tactical Memo #107 | Navigating Modern Work · AI | 4 min read
Tactical Memo: a free newsletter on managing projects, people, and teams with AI. 3x a week, read by 18,000+ leaders at Amazon, Deloitte, and Google. Forwarded? Subscribe free.
Free masterclass How to Become a One-Person AI PMO. 60 minutes, live on Zoom, recording sent to everyone who registers. You'll see how AI agents run the repetitive parts of a project, with no code, in the tools you're already allowed to use. You'll leave with the setup that gets about 8 hours a week back on coordination, status reporting, meetings, and stakeholder comms, one project brain as your single source of truth, and a way to catch slips before your sponsor sees them. Attend live and you also get my RCITO prompting framework for useful AI output on the first try. Save your free seat |
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 asks what you'd do and you send back 5 options AI built in 40 seconds. The mistake: Producing the answers and leaving the call to the person who asked. The move: Send the decision first, with 1 line of reasoning, and keep the options behind it. |
The story
Your director messages you at 4pm. The vendor is slipping again. What would you do?
You open the chat window, paste in the context, and ask for options.
40 seconds later you have 5 options, each with pros and cons.
You clean it up, add a line at the top, and send it over.
She writes back 1 line. "Thanks. Which one?"
You sent her the answers. She was waiting on the call.
She could have asked the tool herself.
If you keep sending options to people who asked for a decision, you're in the same spot.
Early in your career, answers were the job. You found the number, you built the deck, you wrote the plan, and that was worth your salary.
Those answers now cost almost nothing to produce. (And everyone above you knows it.)
The higher you move, the less you're paid for answers and the more you're paid for judgment. Here's how to work with it.
The moves
1/ List the calls only you can make
Take 10 minutes and write down every decision on your plate that no tool and no junior person can own.
Who to escalate to. What to cut. Which risk to accept and which to refuse.
That list is your job now. Everything else on your plate is a task.
2/ Send the call, then the options
When someone asks what you think, lead with your decision and 1 line of reasoning.
The options go under it, if they go at all.
They came to you for the 1 thing the tool can't send.
Say this "My call is option 2, because it keeps the launch date and costs us 1 feature we can ship later. The other 4 are below if you want them." |
3/ Decide what gets ignored
Every week, name 1 thing you will NOT act on, and say so to the people who'd expect you to.
The alert that doesn't matter. The request that can wait a month. The risk that's smaller than it looks.
Anyone can add to the list. Deciding what stays off it is the senior move.
4/ Name what AI never owns
Write 3 lines for your team on what always stays with a person, and post them where the team works.
A clear line lets your team move fast on everything else without checking with you.
Checklist Anything with a person's name attached to it. Anything a client or sponsor reads without you in the room. Anything that spends money or moves a date. |
5/ Hand the answers to an agent
The status update. The meeting notes. The first draft of the plan.
Give them to an agent and keep the 10-minute review for yourself.
Those hours were paying for answers. Every hour you get back goes to a call only you can make.
6/ Make the call OUT LOUD
When you decide, say it in the room and put it in writing. "I'm choosing this," never "the team landed on this."
Judgment nobody sees doesn't count. The calls you own in public are the calls you get paid for.
Say this "I made the call to push the date. If it turns out wrong, that's on me, and I'll tell you what I'd do differently." |
7/ Send the call before anyone asks
When you see a slip coming, send your recommendation before the question arrives.
Options on request look like support.
A decision sent early looks like leadership.
Say this "Heads up. The integration is going to slip about 2 weeks. My recommendation is to cut the reporting module and hold the date. Say the word and I'll start." |
The outcome
| Most people | You |
|---|---|
| Paste the options the tool built | Send the decision, then the options |
| Treat every alert as a task | Name what gets ignored this week |
| Let the team guess what AI can touch | Draw the line in 3 sentences |
| Spend the week producing drafts | Spend the week on calls only you can make |
| Let the decision get credited to the team | Own the call out loud, right or wrong |
Proof. Korn Ferry surveyed 1,674 global talent leaders for its 2026 Talent Acquisition Trends report. 73% named critical thinking as their number 1 priority when evaluating a hire. AI-related skills came in 5th. Korn Ferry, 2025
This week
The answer is now the cheapest thing you produce.
The people who've learned this spend less of the week producing and more of it deciding, and they say their decisions where others can hear them.
Try it next time. When someone asks what you think, send the call first and the options second.
The call is the only part of your answer they can't get from the tool.
Reply
Which decision on your plate this week could only have come from you? Reply with the decision in 1 line. I read every one.
Until next time.
Justin Bateh, PhD
CEO @ AI Operators Lab
Founder & Editor, Tactical Memo