AI Workflows · Manager operating system · Updated June 2026
AI for Managers: The Weekly Operating System You Run With Claude
You do not need a new app. You need a routine. Here is the concrete weekly system a people manager runs with Claude for one on ones, status synthesis, decision memos, and prep, with a clear line you never cross around HR and privacy.
Key takeaways
- AI for managers is a cadence, not an app. The win comes from running the same five jobs every week, not from finding a clever new tool. Claude is the drafting and synthesis layer; you stay the manager.
- Synthesis and prep are where it pays. Turning meeting notes into a status update, prepping a one on one, and shaping a decision memo are high effort, low judgment tasks. That is exactly the work to hand over.
- The conversation and the verdict stay human. Claude can prep your one on one, but it does not run it. It can structure a performance note, but it does not decide what someone deserves. The judgment is the job.
- The privacy line is bright and simple. Do not paste identifiable employee data, health information, compensation tied to a name, or anything from a live HR matter into a general AI tool. Strip the names, or keep it out.
The manager's real problem
If you manage people, your week is not short of work. It is short of time to think. You finish a day of meetings with a notebook full of fragments, three decisions half made, two one on ones tomorrow you have not prepped, a status update due to your own boss, and a performance note you keep meaning to write. None of it is hard. All of it is slow. By the time you have wrestled your notes into a coherent update, the day is gone and the actual managing, the conversations and the calls, gets squeezed.
The question most managers ask is the wrong one. They ask whether AI is coming for the job. We answer that directly in will AI replace managers, and the short version is no, the role shifts toward judgment. The more useful question is narrower. Of the dozen recurring tasks in your week, which ones are slow assembly work that a strong drafting partner can take off your plate, so you spend your hours on the part only you can do? That is what an operating system answers. It is a fixed routine that routes the assembly work to Claude and keeps the judgment work with you.
The point is not to manage with AI. It is to spend less of your week assembling words and more of it on the conversations and calls that actually move your team.
Hand to Claude, or keep human: the decision table
Before the routine, the routing. The whole system rests on one habit: knowing which manager tasks are safe and smart to hand to a drafting partner, and which must stay with you. This table is that split for the work a people manager does every week. Read it as a boundary, not a feature list.
| Task | Hand to Claude (with anonymized inputs) | Keep human |
|---|---|---|
| Status synthesis | Compress your own rough notes and updates into a clean weekly status read for your boss or team, organized by theme, progress, and risk. | Deciding what to escalate, what to downplay, and what a slipping date actually means for the people involved. |
| One on one prep | Turn your notes on a report's recent work into a short agenda: wins to name, two questions to ask, one topic to raise. No personal data, just the work. | Running the conversation, listening, reading the room, and responding to what the person actually says. |
| Decision memos | Structure a tangle of options into a tight memo: recommendation up top, the strongest arguments, the real risks, what you would need to believe. | Making the call, owning the tradeoff, and standing behind the recommendation when it is questioned. |
| Performance documentation | Tighten and structure a note you have already written about work output and behaviors you observed, using neutral, specific, factual language. | The judgment about the person, the rating, the consequences, and anything drawn from a live or sensitive HR matter. |
| Meeting prep | Build an agenda, draft talking points, and pre write the questions for a planning meeting or project review from your own context. | Facilitating, handling disagreement live, and the real time choices about where to push and where to let go. |
| TLY rule of thumb | Hand over the assembly: turning your raw material into clean structure and prose. The input is your notes, never a person's record. | Keep the judgment and the conversation. If a real person is affected by the output, you decide and you deliver it. |
Notice the pattern. Claude does assembly; you do judgment. In every row the AI works on material you already have, your notes, your context, your draft, and produces structure or prose. The moment a task turns on a verdict about a specific human or pulls from their private record, it crosses back to you. Keep that line clean and the rest of the system is just speed. If you want the deeper logic of what to route and what to keep, our siblings on delegate then automate, never the other way and tasks to delegate to AI cover the principle this table puts into practice.
The weekly operating system, step by step
Here is the routine. It is built to run in well under an hour across a normal week, slotted into the gaps you already have. Each step is a fixed job with a fixed prompt shape, so it becomes a habit you do not have to reinvent. Use your own AI policy and keep identifiable employee data out of every step.
- Monday: synthesize last week into a status read. Paste your own rough notes, updates, and bullet fragments from the prior week. Ask Claude to organize them into a short status update grouped by progress, blockers, and risks, in plain language. Example prompt: "Here are my unstructured notes from last week. Turn them into a tight weekly status update for my director: three to five themes, what moved, what is blocked, and the one risk worth flagging. Keep it factual and skip the filler." You then edit it for what to escalate. That is the judgment part.
- Before each one on one: prep a sharp agenda. Pull your notes on what that report has been working on. Ask for a short agenda built from the work, not the person. Example prompt: "Based on these notes about a team member's recent project work, give me a one on one agenda: two specific wins worth naming, two open questions to ask about the work, and one development topic to raise. No assumptions about the person, just the work in front of me." The prep is AI. The conversation is entirely yours.
- Midweek: turn a hard call into a decision memo. When you face a real decision, dump everything you know into Claude and ask for structure. Example prompt: "I am deciding whether to move a project deadline. Here is the context and the tradeoffs I see. Draft a one page decision memo: clear recommendation up top, the three strongest arguments, the two biggest risks, and what would have to be true for this to work." You make the call; Claude just makes your thinking legible.
- As needed: structure a performance note you already wrote. Write the substance yourself, in your own words, describing observed work and behaviors with no identifiable detail you would not want leaving your systems. Then ask Claude to tighten it. Example prompt: "Here is a draft note about observed work output and behaviors, with names removed. Make it more specific, neutral, and factual, and flag any language that sounds like an assumption rather than an observation." The judgment, the rating, and the real record stay with you and your HR process.
- Before any meeting you run: build the prep. Give Claude the goal and the attendees' roles, not their personal details, and ask for an agenda and talking points. Example prompt: "I am running a 30 minute project review with four stakeholders. Goal is to align on scope for the next phase. Draft an agenda, three talking points, and the two questions I should ask to surface disagreement early." You walk in prepared; you still read the room live.
- Friday: a five minute verification pass. Reread anything Claude touched that will leave your hands. Check every fact, date, and name. Confirm nothing identifiable about a person slipped into a tool it should not have. This step is short, it is non negotiable, and it is the part that keeps the whole system safe.
Paste-ready: your weekly manager operating system
Pin this where you plan your week. Run it top to bottom and the cadence becomes a habit you stop having to remember.
- Monday, 15 min: Paste last week's rough notes into Claude. Ask for a status read grouped by progress, blockers, and one risk to flag. Edit for what to escalate.
- Before each one on one, 5 min: Paste your notes on that report's work (no personal data). Ask for two wins to name, two questions to ask, one development topic. Run the conversation yourself.
- Midweek, 10 min: Dump the context and tradeoffs of one real decision. Ask for a one page memo with a recommendation, the strongest arguments, the real risks. You make the call.
- As notes arise, 5 min: Write the substance of a performance note yourself with names removed, then ask Claude to make it specific, neutral, and factual.
- Before any meeting you run, 5 min: Give the goal and roles only. Ask for an agenda, talking points, and two questions to surface disagreement early.
- Friday, 5 min: Reread anything that will leave your hands. Check every fact, date, and name. Confirm nothing identifiable went into a tool it should not have.
Paste-ready prompt: Monday status synthesis
"Here are my unstructured notes from last week. Turn them into a tight weekly status update for my director: three to five themes, what moved, what is blocked, and the one risk worth flagging. Keep it factual, plain, and short, and skip the filler. Do not invent anything that is not in my notes. Notes follow."
What AI does not replace, and the lines you do not cross
This system makes you faster at the writing around management. It does not make you a manager. Hold these lines.
What stays human, always
The one on one itself. The feedback delivered to a person's face. The decision about someone's rating, promotion, pay, or future. The read of a room in a tense meeting. A drafting partner can prepare you for every one of these, but it cannot do any of them. The relationship and the judgment are the job, and they are not delegable.
The HR and privacy line
Do not paste identifiable employee data into a general purpose AI tool. That means no names tied to performance verdicts, no health or medical information, no compensation linked to a person, no protected characteristics, and nothing from a live disciplinary, grievance, or legal matter. Strip identifying detail before anything goes in, or keep it out entirely. Anything touching a formal HR process goes through your HR team and your approved systems, not a chat window. When in doubt, it stays out.
The one rule that prevents most problems
Before you paste, ask: would a specific person be harmed if this left our systems, and does it name them? If yes, anonymize it or do not use AI for it. Follow your own company's AI and data policy over anything on this page. That single check handles almost every risk in this system.
How we built this
This operating system comes from the work senior managers actually do in a week, not a theory of management. We started from the recurring manager tasks that are high in assembly effort and low in personal judgment, the ones that eat time without needing the manager's unique read, and we drew a hard boundary around anything that touches a real person's record or a live HR matter. The prompts are written in the shape we teach: give the role, the goal, and the standard, then keep the verdict with the human. We do not publish invented productivity numbers or fake manager testimonials, because the brand just launched and honesty is the whole point. We date this guide and refresh it as the tools and the privacy norms evolve. Confirm any data handling claim against your own company's AI policy before you rely on it.
What this means for your week
You do not need to become an AI expert to manage better. You need a routine that takes the slow assembly work off your plate so your hours go to the part of the job that is actually yours. Run the six steps. Synthesize on Monday, prep before each one on one, shape your hard call midweek, tighten your notes when you write them, prep before you facilitate, and verify on Friday. Keep the conversations, the verdicts, and the private records firmly in human hands.
That routine, run consistently, is the real skill. It is not about prompts or tools. It is about knowing where your judgment is the value and routing everything else. That is exactly what the AI for Managers course is built to install, the routing, the prompts, and the guardrails, as one repeatable weekly system.
Part of TLY's AI Workflows → operating systems for senior professionals.
Frequently asked questions
What is the best way to use AI as a manager?
Treat it as a weekly operating system, not a single tool. Use Claude to synthesize your notes into a status update, prep sharper one on ones, shape decision memos, and draft routine writing. Keep the conversations, the judgment about specific people, and anything involving private employee data firmly human. The value is the cadence you run every week, not any one clever prompt.
Can AI prepare my one on ones and performance reviews?
It can prepare them, not conduct or decide them. Claude can turn your notes about a report's work into a one on one agenda, and it can tighten a performance note you have already written. But the conversation, the rating, and the consequences stay with you, and you should keep identifiable personal data out of any general AI tool. Run anything formal through your HR process and approved systems.
Is it safe to put employee information into Claude?
Not identifiable employee information. Do not paste names tied to performance verdicts, health or medical details, compensation linked to a person, protected characteristics, or anything from a live HR matter. Strip the identifying detail first, or keep the task out of AI entirely. Always follow your own company's AI and data policy, and when in doubt, leave it out.
How much time does the weekly manager system actually save?
We do not publish an invented number, because the honest answer depends on your role and how much writing your week involves. What we can say is that the system targets the slow assembly tasks, status synthesis, prep, and routine drafting, that managers consistently report as time sinks. The aim is to move those from a slow grind to a fast first draft you edit, so your hours shift to the conversations and decisions only you can make.
Will using AI make me a worse manager?
Only if you hand over the wrong work. The risk is letting a tool make judgments about people or run conversations, which it cannot do well and should not do at all. Used correctly, it removes the assembly work that was crowding out your actual managing, so you have more time for the relationships and decisions that make you good at the job. The system on this page is built around exactly that boundary.
Build the system, not just the intention
Most managers know AI could help and never build the habit, so it stays a vague intention instead of a routine. The managers who get hours back are the ones who run the same small system every week until it is automatic. We teach the cadence, the prompts, and the guardrails as one repeatable operating system for people who manage people.
Take AI for Managers: the weekly operating system for people managers Join The Leverage Club for $49 and get the manager prompts, agendas, and decision memo templates Not sure where to start? Take the 2-minute course finderSources: TLY hands on use of Claude on manager drafting and synthesis tasks, including status updates, one on one prep, decision memos, and meeting prep (June 2026); general principles of people management and data privacy as applied to AI assisted work. This guide does not publish benchmarked figures or named case studies. Confirm any data handling claim against your own company's AI and HR policy before you rely on it.