Now Hiring: Humans Who Can Boss Around Bots

Written by James Sanders

Over the first few weeks of this series, we’ve covered two big ideas: what seats only humans should fill, and what tasks AI should take off those humans’ plates. The next step is to make sure your roles and job descriptions actually reflect that reality.

Most small and mid‑sized businesses still write job descriptions as if AI doesn’t exist. You see long lists like “must draft reports, prepare emails, compile data, take notes, and maintain records.” Then you hire a smart person, give them AI tools on the side, and hope they figure out how to use them. That’s backwards. In 2026, the job itself should assume AI support for routine work, and focus your people on judgment, relationships, and results.

A useful way to rethink roles is to shift from “jobs” to workflows. Instead of asking, “What does this role do?”, ask, “Which workflows is this role responsible for, and which steps in those workflows truly require a human?” For example, an operations coordinator might own three workflows: project setup, weekly reporting, and client communication. Within each, some steps are clearly human (setting priorities, handling exceptions, talking to clients), while others are perfect candidates for AI (drafting emails, summarizing meetings, building basic reports).

Once you see it that way, you can rewrite job descriptions to make the division of labor explicit. The human owns outcomes: accurate information, satisfied customers, on‑time projects, clean hand‑offs. AI is named as a tool the role is expected to use to handle repetitive tasks efficiently. You’re no longer hiring someone to “do data entry and send updates”; you’re hiring someone to manage a workflow where AI generates the first draft, and the human reviews, corrects, and makes the judgment calls.

This shift also changes how you hire and develop people. You start looking for candidates who are comfortable working with tools, not threatened by them. Curiosity, process thinking, and the ability to spot when the software is wrong become just as important as traditional skills. You’re building roles around “human‑plus‑AI” from day one, instead of bolting technology onto a legacy job description and hoping culture catches up.

Next week, we’ll look at the human side of this equation: how to keep your culture healthy, your policies clear, and your legal guardrails in place when AI is officially “on the team.”