←
AI for Managers
Aware · M10 · lesson 10 of 26 · queued
Preview — browse every lesson free. Enroll to mark lessons complete, open partner links and save your progress. Login & enroll →
📖
in this lesson

Tasks AI Should Not Do

12 min

Priya Nandakumar leads a twelve-person product analytics team. She had just finished a great month using AI to speed up her routine work, summarizing reports, drafting status updates, cleaning up meeting notes, when she caught herself about to do something that made her stop cold. It was 9 p.m., she had a stack of peer feedback for an underperforming analyst named Devon, and she typed half a prompt: "Using this feedback, draft Devon's performance review." Her cursor hovered over the send button. Then she deleted it. Something in her gut said this was different from summarizing a report, and she was right. That instinct, knowing which tasks AI should never touch, is the most expensive skill a manager can lack. This lesson turns that instinct into a clear set of rules.

Why This Matters

It is tempting to reason: "If AI can do X, I should have it do X." That logic is a trap. Using AI on the wrong task does not just produce a weak draft. It can damage a relationship beyond repair, create legal exposure, leak confidential data, or quietly destroy your credibility with your team. And the accountability lands on you every time, because you are responsible for whatever you send, decide, or communicate, even when AI helped.

The reassuring part is that the line is learnable. There are four categories where AI should never be the decision-maker, plus a handful of tasks that blur the line and demand extra care. Learn those, and you can move fast everywhere else with a clear conscience.

Some judgment should not be automated. Your relationships, your values, and your accountability are not bottlenecks to optimize away. They are the job.

The Four Categories Where AI Should Not Decide

Category 1: High-stakes decisions with real consequences. These affect people's livelihoods, careers, or legal standing: who to hire or promote, who to let go, performance ratings that drive pay, compensation, role assignments. They require judgment rather than analysis, the consequences are often irreversible, and the context, the relationships, the history, the politics, is exactly what AI cannot see. Use AI to organize information or lay out options. Make the call yourself, with full knowledge, and loop in HR or legal where compliance matters. The wrong move is "have AI evaluate these two candidates and recommend who to hire." The right move is "help me think through the tradeoffs between these two strong candidates," then you decide based on fit, culture, and team dynamics the AI knows nothing about.

Category 2: Anything with legal or compliance implications. Contractor-versus-employee classification, accommodation decisions, discrimination questions, intellectual property, anything that could later become evidence. AI is not a lawyer, and a confident wrong answer here creates real liability that is yours. Use AI to understand a concept ("explain what reasonable accommodation generally means") and then take the actual decision to HR or legal. Never let AI tell you what to do on a compliance question.

Category 3: Sensitive HR or interpersonal communication. Difficult behavioral feedback, communicating a termination or a reassignment, conflict resolution, anything involving harassment or someone's personal circumstances. Here tone and timing matter more than content, and a cold AI-drafted message can break trust permanently. Use AI to prepare your thinking, "how should I structure this conversation, what does this person need to hear," then deliver it yourself, in your own voice. Drafting "the message telling Sarah she is moving teams" and sending it as-is is the wrong move. Thinking through what Sarah needs from you, then talking to her in person, is the right one.

Category 4: Decisions requiring ethical judgment. Whether to disclose a mistake to customers, how to balance team welfare against business pressure, allocating scarce resources fairly, whether to challenge a questionable decision from above. Ethics requires values, and AI has none. It can lay out stakeholder impacts; it cannot make a moral choice. Use it to explore implications, then make the call yourself. "Should we disclose this quality issue?" is not a data question. The right framing is "AI can size the scope and impacts, but the decision to disclose is mine, and we disclose because integrity matters more than cost."

The Tasks That Blur the Line

The dangerous tasks are not the obvious ones. They are the ones where AI looks genuinely helpful but hides a trap.

  • Performance evaluations. AI can summarize feedback and even draft narrative, which is exactly why it is tempting. But evaluations carry legal consequences, expectations are deeply contextual to the role and the organization, tone can quietly signal bias, and a negative review affects pay and career. Use AI to find themes across feedback sources, then write the evaluation yourself, shaped by your knowledge of the person, and have HR review for fairness.
  • Hiring decisions. AI can screen and score candidates, but it reproduces the biases in its training data, misses growth potential and team fit, and creates discrimination risk if it screens out protected classes. Use it to organize candidate information and standardize your interview questions. Make the actual decision with full knowledge and diverse perspectives. If you are reaching for AI to "be objective" in hiring, stop. Informed human judgment is fairer than seemingly objective automation.
  • Analysis of sensitive data. Employee, engagement, or team data is confidential, and many AI systems store or log what you paste in. Check your organization's policy before using any external tool, prefer private or on-premise tools, anonymize and aggregate first, and never put identifying information in a prompt. If you are analyzing identifiable employee data in a public AI tool, that is a hard stop.

A simple red flag ties these together: if using AI starts to feel like it is replacing your judgment rather than informing it, that is your signal to put the tool down.

A Worked Example: Devon's Review and a RACI Check

Back to Priya at 9 p.m. Rather than trust her gut alone, she ran the decision through a RACI map, the simple framework that asks who is Responsible, Accountable, Consulted, and Informed for a piece of work. It made the boundary obvious.

She listed the tasks involved in Devon's review and mapped each one:

  • Gathering and summarizing the raw feedback from five peers and two stakeholders: AI is a fine helper here. Responsible for the first-pass summary, Priya accountable. Low risk, because she will verify every theme against the source comments.
  • Identifying the themes and judging which ones actually matter for Devon's role: Priya is Responsible and Accountable. AI does not know that Devon's core job is data accuracy, so a polished summary could bury the one issue that matters under three that do not.
  • Writing the evaluation and its tone: Priya, Responsible and Accountable, with HR Consulted for fairness. If Devon contests a single sentence, she has to own and explain it, which means she has to have written it.
  • Delivering it in the one-on-one: Priya alone. No AI anywhere near this step.

The map showed that exactly one of four tasks belonged to AI, and it was the lowest-stakes one. Priya put a rough cost on the alternative to make the point to herself. Devon's rating fed a merit cycle worth about $6,000 in raise and bonus, and a sloppy or biased review carried real risk of a grievance that could cost far more in time and trust. Letting AI draft the whole thing to save perhaps 40 minutes was a terrible trade against a $6,000-plus decision she would have to defend line by line. So she used AI only to cluster the feedback into themes, spent the saved 40 minutes thinking hard about Devon's actual growth path, and wrote the review herself. When Devon later pushed back on one point in the meeting, Priya could explain exactly why she had written it, because she had.

Common Ways Managers Get This Wrong

Delegating judgment under the banner of "automation." "I will let AI decide so it is objective" is the most seductive mistake. AI is not more objective; it reproduces bias and carries no accountability. You do. Own the decision.

Using AI to avoid a hard conversation. "I will have AI write it so it sounds professional" usually means you are dodging a talk that needs to happen with you clearly present. Use AI to rehearse your thinking, not to outsource the courage.

Treating AI as fairer than you. It is biased differently than a human, not less. Your informed, thoughtful judgment, especially with diverse input, is often the fairer instrument.

Breaching confidentiality by habit. Pasting employee data into a public tool to "just analyze it quickly" can violate confidentiality and feed future models. Check policy, use private tools, anonymize first.

Five Questions Before Anything Sensitive

When a task feels even slightly weighty, run these five checks. A "yes" on any of them means slow down and add a human layer.

  • Is this a judgment call? If yes, it is human work, not AI work.
  • Are there real consequences? If yes, add review layers before acting.
  • Could this become public or legal? If yes, be very careful and involve HR or legal.
  • Is sensitive information involved? If yes, check policy and use private tools only.
  • Would I be comfortable explaining this later? If no, do not do it.

Note that deciding the larger organizational policy on AI use, what tools are approved, what data may ever touch them, is a leader-level call. Your job at the team level is to operate cleanly inside those guardrails and to flag when they are missing.

Human Judgment Is the Advantage, Not the Bottleneck

It is easy to read a lesson like this as a list of restrictions. It is the opposite. The work that AI cannot do, the judgment, the difficult conversations, the ethical calls, the relationships, is precisely the work that makes you valuable and hard to replace. Choosing not to use AI on something is often the right, honest choice. "This is too sensitive to delegate to a tool" is a sign of good leadership, not a failure to keep up.

A month after the Devon review, Priya noticed her team trusted her feedback more, not less, even though they all knew she used AI heavily for routine work. The reason was simple: they could tell which parts were hers. She had kept the human parts human, and that line was visible.

Responsible Use: Accountability and Confidentiality

Two responsibilities sit underneath everything in this lesson, and they are worth naming on their own because they do not disappear just because you used the tool sensibly.

The first is accountability. Whatever you send, decide, or communicate is yours, even when AI did the drafting. If Devon had taken his review to HR, "the tool wrote that sentence" would not have been a defense, and Priya knew it. Treat that as a feature rather than a burden. Accountability is what keeps you reading an output carefully instead of skimming it, and it is the reason the highest-stakes work stays in your hands in the first place.

The second is confidentiality. Not every piece of information belongs in an AI tool, and the boundary is easy to cross without noticing. Employee records, individual performance detail, compensation data, financial figures that are not public, and strategic plans belong in systems your organization controls or in your own head, not in a service whose data handling you cannot see. The five questions above give you the trigger. The discipline is actually stopping when the answer says stop, including at 9 p.m. when stopping is the inconvenient option.

There is a third point that the section on human judgment already makes, so connect it here rather than repeating it: choosing not to use AI on something is itself a responsible use of AI. Being straight with your team about that choice, saying plainly that a piece of work was too sensitive to hand to a tool, builds more trust than quietly using one and hoping nobody asks.

Practice and Reflection

These work far better written down than answered in your head. Give them twenty minutes with your inbox closed.

  • Name your red lines. Write down the three tasks in your role that should never be delegated to AI, and next to each one write why. If you cannot articulate the why, the line will not hold at the moment you are tired and behind.
  • Examine the temptation. Which task in your week would be genuinely tempting to hand over even though you should not? Be honest about what makes it tempting, usually volume or dread, then name exactly what would be lost.
  • Run a legal check. Are there parts of your role with legal or compliance implications where you should talk to HR or legal before using AI at all? Put that conversation on the calendar rather than filing it as a someday item.
  • Audit your confidential data. List the categories of information you handle that are confidential, and decide now where each may and may not go. Deciding in advance is what protects you when the decision arrives mid-task.
  • Test decision ownership. Take a decision you made in the past month. Could you have delegated it to AI? Should you have? Work it through against the four categories and see where it lands.
  • Consider the trust effect. If your team knew exactly how much of your decision-making involved AI, what would change in how they see you? Priya's answer was that visibility helped her, because the human parts were visibly hers. Would yours hold up the same way?

Key Takeaways

  • High-stakes decisions stay yours. Hiring, firing, evaluations, and compensation require judgment, carry irreversible consequences, and depend on context AI cannot see.
  • Legal and compliance matters need professional review. AI is not a lawyer. Use it to understand concepts, take the actual decision to HR or legal.
  • Sensitive communication needs your voice. Use AI to prepare your thinking, then deliver difficult messages yourself, in person.
  • Ethical judgment is human work. AI can lay out options and impacts; only you can decide what is right.
  • Confidentiality is your responsibility. Never put identifiable employee data into a public AI tool. Check policy, use private tools, anonymize first.
  • Map the task before you delegate it. A quick RACI check shows which sub-tasks AI can safely take and which must stay with you, usually the highest-stakes ones.
  • Human judgment is your competitive advantage. The work AI cannot do is exactly the work that makes you essential. Protect it on purpose.