## Key Takeaways

- **An AI employee without a manager drifts.** Routines pile up, rules contradict each other, and when something looks wrong, nobody feels responsible for looking.
- **The right manager is the person closest to the work, not the most technical person.** Managing an AI employee is a judgment job about output and priorities, not a systems administration job.
- **The job is smaller than people fear:** roughly fifteen minutes a week of reviewing what ran, what changed, and what should be retired.
- **Whoever signs up should also plan their own replacement.** Manager changes are when AI setups quietly die, so succession belongs in the role from day one.
- **"Everyone manages it" means nobody does.** Shared usage is healthy; shared accountability for the setup is an accountability gap with a friendly name.

![Comparison of four candidates for managing the AI employee, with the ops lead as best default](/images/blog/who-should-manage-your-ai-employee/owner-candidates.webp)

## The question nobody asks until week six

The first weeks with an AI employee tend to run on enthusiasm. Someone connects the tools, a few teammates set up reports, small wins get posted in the channel. Around week six the enthusiasm meets its first real test: a report looks stale, a routine posts something odd, or two automations disagree, and the question surfaces for the first time. Who actually owns this thing?

If the answer takes more than three seconds, the honest answer is nobody. That is worth fixing this week, because an unmanaged AI employee does not fail loudly. It degrades: quiet stale routines, unreviewed output, and a slow slide into "I am not sure we can trust it", which is usually a management gap rather than a tool problem.

## What managing an AI employee actually involves

The word "manage" scares people into thinking this is a big job. Here is the whole role:

- Keep an eye on the workload: know which routines run, retire the ones nobody reads.
- Own the rules: shared definitions, standing instructions, and who gets to change them.
- Review the review-worthy: spot-check important output, especially anything client-facing.
- Handle corrections: when output is wrong, make sure the fix gets saved, not just patched.
- Review access twice a year: which tools are connected and whether each is still needed.
- Plan succession: a documented setup that survives your own departure.

That list fits inside fifteen minutes a week for most teams, plus occasional bursts when something new gets set up. What it requires is judgment about the work itself: is this report right, is this routine worth its slot, should this task run without review yet. Which points directly at who should hold the role.

## The candidates, honestly compared

| Candidate | Why it seems right | The catch | Verdict |
| --- | --- | --- | --- |
| IT / most technical person | "It's software" | Cannot judge whether the pipeline report is correct, only whether it ran | Wrong default, useful ally |
| The founder / CEO | Cares most about output | Becomes the bottleneck, then goes quiet for two weeks and everything stalls | Fine at 5 people, fails at 20 |
| Ops or team lead closest to the work | Can judge quality, sees daily usage | Needs a mandate, or their calls get overridden | Best default |
| "Everyone" | Feels collaborative | Accountability diffuses to zero | Not a real answer |

The pattern behind the table: an AI employee produces work, and work is judged by whoever understands it best. An ops lead can look at the Monday revenue summary and know within seconds whether it smells right. That instinct is the core qualification, and it is why the manager question has the same answer as "who would manage a junior human hire doing these tasks".

IT still matters. Connection issues, workspace-level permissions, and vendor questions are real and occasionally technical. The working split that holds up: the ops-side manager owns what the AI employee does, IT supports how it stays connected. The day-to-day craft of the role, feedback, standards, and delegation, is the same skill covered in [how to manage an AI coworker](https://viktor.com/blog/how-to-manage-an-ai-coworker).

![A new-hire onboarding card prepared by an AI employee](/images/blog/who-should-manage-your-ai-employee/in-practice.webp)

## The fifteen-minute weekly routine

Ask the AI employee to prepare its own management review, then read it. That is most of the job.

```prompt
Every Friday at 15:00, post my weekly review in this thread:
1. Every recurring task that ran this week, with a one-line status.
2. Anything that failed, was corrected, or produced unusually
   different numbers than last week.
3. Any new rules or instructions saved this week, and by whom.
4. Routines nobody has reacted to or mentioned in 30 days,
   as retirement candidates.
```

Reading that takes five minutes. Acting on it takes ten: retire one stale routine, resolve one rule conflict, spot-check one important output. Weeks with nothing to act on happen often, and that is the system working.

Two habits make the routine stick. First, do the review in a channel rather than a DM, so the team sees that someone is watching and where decisions get made. Second, when you correct something, close the loop in writing: the difference between a managed and unmanaged AI employee is whether corrections get saved as rules or evaporate in threads.

## The part managers skip: your own replacement

Manager changes are the single most common way a working AI setup dies. The person who ran it leaves or changes roles, the routines keep running for a while on borrowed time, then a connection expires or a rule needs changing and nobody knows how any of it works.

Succession takes one hour up front:

1. Keep the setup in shared channels, so nothing critical lives in your DMs.
2. Have the AI employee maintain a living "how this workspace runs" doc: every routine, its owner, its rules.
3. Name a deputy who has actually done the Friday review at least twice.

The full playbook, including what to do when the departure already happened, is in [what happens when your AI employee's manager leaves](https://viktor.com/blog/what-happens-when-your-ai-employees-manager-leaves). The short version: a setup documented in shared spaces transfers in a week; a setup in one person's head does not transfer at all.

## When to revisit the choice

The right owner at five people is often the wrong owner at twenty-five. Revisit the role when usage spreads to a second team, because a sales-side manager should not arbitrate rules for the finance team's reports. The natural evolution is one manager per team's slice of the work, with the original owner keeping workspace-wide concerns like access reviews and conventions.

The first weeks under a new or newly formal manager are also the right time to tighten fundamentals: what runs with review, what runs without, and what gets checked. If you are early in the rollout, [the first seven days guide](https://viktor.com/blog/first-7-days-with-ai-coworker) and the [human-in-the-loop setup](https://viktor.com/blog/how-to-keep-a-human-in-the-loop-with-your-ai-employee) are the two companions to this post.

## Frequently Asked Questions

### Who should be responsible for an AI employee in a small company?

The person closest to the work it produces, typically an ops lead or team lead. They can judge output quality at a glance, which is the core of the job. IT supports connections and permissions but should not be the default owner.

### Does managing an AI employee require technical skills?

No. The weekly work is reading a self-generated review, retiring stale routines, resolving rule conflicts, and spot-checking output. Judgment about the work matters far more than technical depth; genuinely technical issues can be escalated to IT.

### How much time does it take to manage an AI employee?

About fifteen minutes a week in steady state: five reading the AI employee's own weekly review, ten acting on it. Expect short bursts of extra time when new routines get set up or when a team joins.

### Can an AI employee manage itself?

It can do the reporting half: listing what ran, flagging failures, surfacing stale routines. The deciding half, what to retire, which rule wins, what deserves review, needs a human with context. Self-reporting plus human judgment is the working combination.

### What happens if nobody manages the AI employee?

Nothing dramatic at first, which is the trap. Routines accumulate, definitions drift between reports, corrections stop being saved, and within a quarter the team quietly stops trusting output that nobody was checking. The gap almost always shows up as "the AI is unreliable".

### Should the founder manage the AI employee?

At five people, often yes, because the founder is closest to everything. Past ten or fifteen people the founder becomes a bottleneck: rule changes queue behind their calendar. Hand the role to the lead whose team uses it most, and keep the founder as an escalation point.

---

**Viktor is an AI employee that lives in Slack, connects to 3,200+ integrations, and does real work for your team.** [Add Viktor to your workspace -- free to start →](https://viktor.com/?utm_source=blog&utm_medium=cta&utm_campaign=who-should-manage-your-ai-employee)