Key Takeaways
- A shared AI employee fails in four predictable ways: conflicting instructions, duplicate automations, work trapped in DMs, and rules nobody owns. All four are preventable with a handful of conventions.
- Channels beat DMs for anything the team relies on. Work done in a channel is visible, searchable, and survives the person who requested it. Work done in a DM is invisible to everyone else.
- Every recurring routine needs exactly one named owner. Not a committee. One person who can change it, pause it, and answer for what it produces.
- Conflicting instructions are a people problem wearing an AI costume. When two teammates give opposite rules, the AI employee did not break; the team never agreed on the rule.
- Write the shared conventions down once. A ten-line "how we work with our AI employee" note prevents most of the mess before it starts.
The Tuesday two people asked for the same report
An ops lead asks the AI employee for a weekly inventory summary, Mondays at 9. Three weeks later a teammate, who never saw that thread, sets up almost the same summary for Tuesdays, with a slightly different definition of "low stock". Now two reports disagree every week, and a third teammate has told the AI employee in a DM to always exclude the Berlin warehouse, which applies to one report and not the other.
Nobody did anything wrong. Each request was sensible on its own. This is simply what happens when a team of eight shares one AI employee the same way they would each use a private chatbot. A shared AI employee is closer to a shared teammate, and teammates need working agreements.
The four failure modes
1. Conflicting instructions
One person says "always round to whole numbers", another says "two decimals, always". The AI employee gets both, in different threads, weeks apart. Whichever rule was saved for the specific task wins, and the other person concludes the AI is ignoring them.
The fix is ownership, covered below, plus one habit: state rules in the channel where the work happens, so a disagreement surfaces as a visible conversation between humans instead of as silent flip-flopping output.
2. Duplicate automations
Recurring tasks are the biggest win of an AI employee and the easiest thing to duplicate, because recurring work set up by one person runs quietly in the background where nobody else sees it. Two near-identical weekly reports with different filters is the classic case.
Before setting up anything recurring, ask the AI employee what it already runs:
List every recurring task you currently run for this team: name,
schedule, channel it posts to, and who set it up. I want to check
for overlap before adding a weekly inventory summary.Thirty seconds of checking beats months of two reports that almost agree.
3. Work trapped in DMs
DMs are fine for personal drafts and questions. They are the wrong place for anything the team depends on, for one structural reason: nobody else can see it, search it, or take it over. The person who set up a critical routine in their DMs becomes a single point of failure. What happens when that person leaves is its own topic, covered in what happens when your AI employee's manager leaves.
The rule of thumb: if a second person would ever care about the output, it belongs in a channel. Deciding where your AI employee works, which channels it joins and which it does not, is part of the same setup conversation.
4. Rules nobody owns
"Whose definition of active customer are we using?" If the answer is a shrug, the AI employee is running on whichever definition was said most recently. Shared vocabulary needs to be agreed once and saved once.
The operating rules that fix it
| Rule | What it prevents |
| Team-relevant work happens in channels, not DMs | Invisible work, single points of failure |
| Every recurring routine has one named owner | Flip-flopping instructions, orphaned automations |
| Check existing routines before adding new ones | Duplicates |
| Shared definitions get saved as standing rules, in writing | Vocabulary drift between reports |
| Changes to a routine are announced in its channel | Silent surprises for everyone downstream |
The owner role is lighter than it sounds. Owning the weekly pipeline report means: you can change its rules, you get asked when someone disagrees with its output, and you pause or retire it when it stops earning its slot. Five minutes a week, most weeks zero.
A useful convention for the definitions row: keep one pinned message or short doc per channel titled "standing rules", and tell the AI employee those rules apply to all work in that channel. An AI employee with persistent memory will hold them across every task, and new teammates can read the same ten lines the AI works from.
Personal assistant habits vs shared employee habits
Most people arrive with habits formed on personal chatbots, where every conversation is private and nothing persists between users. Those habits are precisely what breaks a shared setup.
| Personal chatbot habit | Shared AI employee habit |
| Everything in a private chat | Team work in team channels |
| Rules stated whenever, wherever | Rules saved once, in the channel that uses them |
| Set up automations freely | Check for overlap, then set up with a named owner |
| Nobody else affected by your instructions | Your instructions may change a report six people read |
| Abandon experiments silently | Retire routines out loud |
The shift is small in practice and mostly amounts to doing in public what you used to do in private. Teams that make it get compounding returns: every saved rule, every documented routine, every visible thread becomes shared infrastructure instead of one person's private setup. That compounding is the argument for rolling the AI employee out to the whole team deliberately instead of letting adoption happen one private DM at a time.
A ten-line conventions note to steal
Post this in the channel where your AI employee does most of its work, adapt the specifics, and pin it:
- Team-relevant requests go in channels. DMs are for personal drafts only.
- Before creating a recurring task, ask the AI employee what already runs.
- Every recurring task has one owner, named in the task itself.
- Only the owner changes a routine's rules; everyone else proposes in-thread.
- Shared definitions (active customer, pipeline, low stock) live in the pinned standing rules.
- Rule changes get announced in the channel, one line is enough.
- Reports nobody read in a month get retired, out loud.
- Disagreements about output go to the owner, not into new contradictory instructions.
- New teammates read this note and the standing rules on day one.
- The AI employee is told this note applies to all work in this channel.
Frequently Asked Questions
How many people can share one AI employee?
There is no practical cap on people; the constraint is conventions. A team of thirty with named owners and channel discipline has fewer problems than a team of five giving contradictory instructions in private DMs.
What happens when two people give an AI employee conflicting instructions?
The most recently saved rule for that specific task typically wins, which means output silently flips and the overridden person loses trust in the tool. Prevent it by giving each routine one owner and stating rules in the channel where the work happens.
Should employees use the AI employee in DMs at all?
Yes, for personal work: drafting, research, questions. The line is dependency. The moment a second person relies on the output, move it to a channel so it is visible and transferable.
How do we stop duplicate automations?
Make "ask what already runs" a habit before anything recurring is created, and give every routine a named owner. An AI employee can list its own recurring tasks on request, which makes the check a thirty-second step.
Who should own a shared routine?
The person closest to the work it produces, not the most technical person in the room. The owner's job is to answer for the output and be the single door for rule changes, which requires domain knowledge more than technical skill.
How do we onboard a new teammate to a shared AI employee?
Have them read the pinned conventions note and the standing rules for their channels, then make their first request in a channel rather than a DM. Ten minutes of reading replaces weeks of accidentally relearning the team's agreements.
