What to delegate to an AI operator and what to keep
The useful question is not whether AI can do the work. It is which parts of the work you would be glad never to touch again, and which parts you should never give up.
· Work · 4 min read
Handing work to an AI operator goes badly in two ways. Some people give it nothing, because they do not trust it, and they miss the benefit. Others give it everything, and find out later that some decisions should never have left their desk.
A better approach is to sort the work by what it needs, not by what the tool can technically do.
Good work to delegate
- First drafts of emails, posts, landing pages and customer stories.
- Follow-ups that are clear in shape, such as a webinar follow-up to the people who registered.
- Reworking one piece into other forms.
- The preparation before a decision, such as gathering the facts and laying out the options.
- Repeat jobs where last time’s brief is a good starting point.
Work to keep
- The yes. Anything that goes out in the company’s name should be approved by a person.
- Strategy and priorities: what is worth doing this quarter, and what is not.
- Sensitive relationships, such as a key customer, a complaint or a negotiation.
- Claims about your product or your customers. Someone who knows the facts should check them.
A way to hand over a job
Give the operator a short brief, the way you would for a new colleague. Say what the job is, who it is for and what good looks like. Then read the first result carefully, and say what to change. The first round teaches both of you what you mean.
How Levric does it
On the Work board, Chief and your team work on the same jobs. Chief takes the jobs you hand it and drafts them. When a job needs a person, it moves to Needs you, and nothing goes out until you approve it. When you approve a job, Chief moves straight on to the next one.
That keeps the split simple. Chief does the preparation, and you keep the decisions.
See it in the app: the Work tour