Promote a Bot to director and let it build and run its own t

How this helps you

Your attention goes to one weekly report per area while the work underneath keeps running.

✦ Try it

I'm promoting you to director of [area]. Build three new Bots that report to you: one to [job 1], one to [job 2], and one to [job 3]. They report directly to you, never to me. Ask each for proof of work and source links. Send me only what I need to know once a week on [day] morning, unless something is extremely urgent.

Fill in: [area] is the domain it now owns. [job 1] to [job 3] are narrow, repeatable jobs (for example: check competitor prices daily). [day] is when you want the summary.

What they did

In xAI's Enterprise Teams webinar, field engineer Santi Garza shows a model the team uses internally. A Bot that already watches competitor fares is told: 'I'm promoting you to director of competitor intelligence. Build three new Bots that report to you', one for competitor prices on similar flights, one for competitors' social accounts and what lands with their customers, and one for their websites and promotion emails. Its title changes and three Bots appear. He then tells it the three report to it, never to him, and to surface only what he needs once a week on Monday morning unless something is extremely urgent. His advice from management reading: talk to between one and seven direct reports, and ask Bots for proof of work and source links so the director can check them.

Who it's for: People running five or more Bots, and teams that want one owner per area instead of a crowded sidebar.

Before you start

A Bot that has already done the job by hand for a while and knows the context.
A clear area it can own (competitors, support, hiring).
Room in your plan's usage for three more Bots on schedules.

How to try it

Pick the Bot with the most context on one area. Ask it to summarise its current job first.
Promote it with a title, and name the three sub-jobs you want (prompt below).
Check the new Bots in the sidebar and read each one's description.
Set the reporting line: they report to the director, never to you; the director sends you one weekly summary unless something is urgent.
Ask for proof of work and source links on every report, and spot-check the first Monday summary yourself.

What to expect

The Bot thanks you, its title updates, and three Bots appear in the sidebar with their own descriptions. The following Monday, one summary with links instead of three separate streams of messages.

Common mistakes

Promoting a new Bot. Promotion works because the director already has the context; build that first.
Giving yourself ten direct reports. Keep one to seven Bots talking to you and let directors handle the rest.
Accepting summaries without evidence. Ask for links and proof so the director can catch a weak worker.

Related tips

A manager Bot that never does the work itself: Give a lead Bot one job: break work down, hand it to worker Bots, and check results against the goal. Big projects then run as a chain you only talk to at the top.
Pick a main Bot so it can see and delegate across your team: A main Bot gets wider visibility into your other Bots, messages you first, and hands work out.
How to trust your Bot's work more: Put most of your effort at the top: code structure, then lint/tests/CI, then prose rules, then human review.