Management is a judgment job, so use AI in the right layer
Managers do two different kinds of work. There is preparation work: gathering facts, finding the open question, creating an agenda, drafting a summary, comparing options, and remembering the follow-up. Then there is judgment work: listening, interpreting context, deciding what is fair, setting expectations, and taking responsibility for the outcome.
ChatGPT is strongest in the preparation layer when the manager supplies the context and reviews the output. It can turn scattered notes into a conversation plan or show that a decision memo has a recommendation but no evidence. It cannot know whether a teammate is having a difficult week, whether a short reply reflects stress or brevity, or whether two employees were held to the same standard.
I use a simple rule: ask the model to organize what I know and reveal what I do not know. I do not ask it to infer a person’s character, diagnose a motive, or decide a consequence. That distinction protects the employee and improves the manager’s thinking.
My manager workflow by task
| Task | Useful AI role | Manager remains responsible for |
|---|---|---|
| 1:1 preparation | Agenda, themes, questions, and action list. | Relationship context, listening, priorities, and commitments. |
| Coaching | Behavior-focused wording and question practice. | Fair interpretation, empathy, boundaries, and follow-through. |
| Team update | Clear draft with owners and known uncertainty. | Accuracy, confidentiality, timing, and final voice. |
| Decision memo | Options, evidence, assumptions, and tradeoffs. | Decision authority, risk appetite, and approval. |
| Performance review | Organization and neutral draft language. | Evidence, rating, consistency, HR process, and decision. |
1:1s: prepare a better conversation, not a longer agenda
A 1:1 can become a status meeting if the manager arrives with a list of tasks and no space for the employee’s perspective. I use ChatGPT before the meeting to turn factual notes into a short agenda: wins, blockers, decisions needed, development questions, and follow-up. I ask it to suggest questions, not conclusions.
Good input might include the employee’s stated goal, a project milestone, an unresolved dependency, and the last agreed action. Bad input is a stream of labels such as “not engaged” or “seems difficult.” Labels compress interpretation into a fact and make it harder to have a fair conversation.
Before opening ChatGPT, I remove details that are not needed for the agenda. I do not need a medical detail to ask about a workload blocker. I do not need a protected characteristic to prepare a development question. Data minimization improves both privacy and the quality of the conversation because it forces me to focus on the work.
After the 1:1, I can use an approved workflow to turn confirmed actions into a checklist. I keep the employee’s own goals and words distinguishable from my interpretation. If the employee asks for a change in role, support, accommodation, or workload, the manager follows the organization’s actual process rather than letting a generated paragraph become the record.
Coaching: describe behavior, impact, and next step
The most useful coaching draft begins with an observable event. What happened? When? What was the impact? What standard or goal was relevant? What would better look like next time? That gives the employee something they can respond to. It is very different from asking AI to explain why someone is careless, defensive, or unmotivated.
I ask ChatGPT to separate fact, interpretation, and question. If a project update arrived two days late, that is an observation. “The person does not care about deadlines” is an interpretation. “What made the update difficult to send on time?” is a question. Keeping those apart helps me enter the conversation curious without pretending the impact did not occur.
The manager should check for equal standards. Would I describe the same behavior in the same way for another person? Am I relying on a single anecdote? Does the employee have the authority, access, training, and time needed to meet the expectation? An AI output cannot answer those questions unless I provide the evidence, and even then I own the judgment.
For harassment, discrimination, retaliation, accommodation, leave, discipline, or termination, I involve HR or the designated owner. ChatGPT can help me rehearse respectful wording, but it should not give the organization a legal conclusion or create a record that bypasses the required process.
Team updates: clarity beats managerial theater
Managers often have to explain a change before every detail is known. ChatGPT can help draft a calm update that distinguishes what changed, why it matters, what the team should do now, what is still unknown, and when the next update will come. That is more honest than asking it to make uncertainty sound confident.
I give it confirmed facts and a specific audience. A message for a small project team is not the same as an announcement to the whole company. I ask it to remove private employee context, preserve the decision’s actual scope, and list owners rather than vague “we” language.
Before sending, I check whether the update creates a promise. “We are evaluating the timeline” is not “the launch will happen Friday.” “We will share more next week” is a commitment I should be ready to keep. A manager must own the difference between a draft and an announcement.
I also read the message aloud. If it sounds like a press release, a generic motivational speech, or a voice nobody on the team recognizes, I rewrite it. The goal is clearer communication, not a synthetic managerial persona.
Decision memos: ask for options, not an oracle
Managers can lose hours turning a messy discussion into a decision memo. ChatGPT is helpful when I provide the raw facts and ask it to create a decision frame: the decision to make, options, evidence, assumptions, tradeoffs, risks, reversibility, approver, and open questions.
I do not ask “What should we do?” as the only prompt. That invites a polished recommendation with invisible assumptions. I ask what information would change the recommendation and which risks are hard to reverse. I ask for the strongest argument against each option. Those prompts make the manager think rather than merely accept.
A decision memo should say who has authority and who needs to be consulted. It should not disguise disagreement as consensus. If two stakeholders want different outcomes, the memo can state that clearly and identify the decision required. AI can make the conflict easier to see; it cannot resolve the organization’s priorities.
Once the decision is made, use AI to draft the follow-up with the exact scope, owner, date, and reason. Then check that the communication does not reveal private deliberations or create a commitment beyond what was approved.
Performance reviews are not a safe place to outsource judgment
Performance-review work contains personal information and can affect pay, promotion, opportunity, and employment. I use AI only for narrow support: organizing documented examples, checking whether a draft names observable behavior, identifying missing evidence, and suggesting questions for the manager to answer.
I do not ask it to infer a rating from a person’s writing style, compare employees using incomplete notes, predict potential, diagnose attitude, or recommend a consequence. A model can reproduce a manager’s inconsistent standards while making the result look objective.
The EEOC has warned that AI and other software used in employment decisions can create disability discrimination risks. A manager’s policy should define when HR review, accommodation processes, validation, documentation, or a specialist is required. ChatGPT is not the approval process.
Privacy: choose the account before the prompt
The same words typed into different ChatGPT account types can sit under different data controls, sharing behavior, retention, and administrator settings. OpenAI documents that ChatGPT Business data is excluded from model training by default and that each user’s chats are not automatically visible to other members. That is useful context for a manager, but it does not automatically approve a workflow.
Before using employee or client context, I check the organization’s policy, the exact account and plan, connected apps, who can share a chat or project, retention, and whether the output will be stored in a system of record. I use the minimum information needed. A business workspace is not permission to paste every document a manager can access.
For a low-risk personal task, ChatGPT’s Data Controls and Temporary Chat documentation describe separate controls for training, history, memory, and deletion. Those settings are not interchangeable, and a Temporary Chat with an external action can send data to a third party subject to that recipient’s policy. Managers should understand the workflow end to end before using it.
My practical rule is simple: if I would not put the information in an ordinary shared document with the intended audience, I do not put it into an unapproved chat. For sensitive management work, I redact names and details or use the approved business workflow with the right reviewer.
Six prompts I would keep
1. Prepare a 1:1 without mind-reading
Use these factual notes to prepare a 30-minute 1:1. Separate observed work, open questions, the employee’s stated goals, blockers, decisions needed, and follow-up. Suggest curious questions. Do not infer motivation, attitude, personality, health, or intent. Flag any statement that needs evidence before I use it.
2. Turn observations into useful feedback
Convert these documented observations into feedback using situation, behavior, impact, and next step. Keep the description specific and neutral. Do not label the person, speculate about intent, add an event that is not in the notes, or recommend an employment consequence. Give me two questions to check my interpretation.
3. Draft a team update
Draft a concise team update from these confirmed facts. Include what changed, why it matters, what is still unknown, next actions, owners, and when the next update will happen. Do not reveal private employee information, imply a decision that is not final, or use a confident tone to hide uncertainty.
4. Build a decision memo
Create a decision memo with context, decision to make, options, evidence, assumptions, tradeoffs, risks, reversibility, recommendation, approver, and open questions. Keep facts separate from assumptions. Do not choose for me; show what information would change the recommendation.
5. Prepare a difficult conversation
Create a conversation plan from these confirmed facts. Include an opening, observable examples, questions, desired outcome, listening points, boundaries, and follow-up. Use respectful language. Do not make a legal conclusion or recommend discipline. Mark topics that require HR or specialist review before the conversation.
6. Review a manager draft
Audit this draft for accuracy, unnecessary personal information, unsupported judgments, unequal standards, accidental promises, confidentiality, tone, and whether it answers the real audience’s question. Return MUST FIX, REVIEW WITH HR, and READY TO EDIT. Do not rewrite until the issues are listed.
A manager’s review pass before sharing
I use a short review pass because most failures happen at the boundary between a draft and a real audience. First, I check facts against the source. Then I check audience and confidentiality. Then I check fairness and tone. Finally, I check what the message commits the team to doing.
| Check | Question |
|---|---|
| Evidence | Can I point to the note, document, or decision supporting this sentence? |
| People | Did the draft infer intent, personality, health, or protected information? |
| Audience | Does every person receiving this need every detail? |
| Commitment | Does the message promise a date, resource, decision, or outcome I have not approved? |
| Voice | Would I say this directly and respectfully to the people involved? |
A seven-day manager pilot
Day one: choose three low-risk tasks: one 1:1 agenda, one internal update, and one decision-memo outline. Record how long each normally takes and what makes it difficult.
Days two and three: use the prompts with redacted, factual notes. Keep the source next to the output. Count the edits needed and list any unsupported inference or missing context.
Day four: ask a peer manager to review one draft for fairness, confidentiality, tone, and accidental commitments. A second reader often sees a problem the author has normalized.
Day five: move one approved action into the team’s actual task or documentation system. The point is to test whether the workflow finishes, not only whether the prose looks good.
Days six and seven: decide which tasks should become repeatable prompts, which need a different tool or approved workspace, and which should not use AI. Keep the process narrow until the review standard is easy to follow.
My recommendation
Use ChatGPT as a manager’s preparation desk: bring messy notes, ask for structure, expose assumptions, rehearse questions, and draft in your own voice. Keep the employee’s perspective and the manager’s accountability in the room.
The highest-value workflows are often ordinary: a better 1:1, a calmer update, a decision memo that shows its assumptions, and a follow-up list that has owners. Those tasks are valuable because they improve consistency without pretending that people are spreadsheets.
When the work affects employment, privacy, health, legal rights, safety, or a customer relationship, narrow the AI role and add the appropriate human review. Faster text is not a management outcome. Better judgment, clearer expectations, and more trustworthy follow-through are.