The better AI agents get, the more prompting feels like managing work. You have to decide what you want done, explain what a good result looks like, and give the agent enough room to get there. That will become a basic business skill, including for people who have never managed an employee.
That sounds simple until you try to delegate a real assignment. It’s easy to ask for a better website or a useful research report. It’s harder to explain what would make either one useful to your business.
When an agent can research a subject, work across files, and produce a deliverable, a vague assignment can send it a long way in the wrong direction. More capability gives it more ways to act on your instructions. It also makes the decisions you leave out more consequential.
I think this is where a lot of the value in learning to use AI will move. Knowing how to explain the job, supply the right context, and recognize a good result will matter across whatever tools come next.
The hardest part is deciding what to ask for
Imagine asking an agent to improve a landing page. It could rewrite the headline, rearrange the sections, and make the page more visually polished. All of those changes might satisfy the instruction. None necessarily explains the offer more clearly to the intended customer.
Maybe visitors can’t tell who the product serves. Maybe the page asks them to buy before explaining the value. Those are different problems. If you haven’t decided which one matters, the agent has to make that choice for you or come back and ask. Neither a longer prompt nor a more polished design settles it.
In my own approach to AI work, I want to decide what the result is for before execution begins. A research assignment needs a question to answer. A website needs an offer the intended customer can understand. I can give the agent freedom over how it gets there once I’ve made the destination clear.
Managers run into this all the time: someone completes the assignment exactly as requested, and the result still doesn’t solve the problem. I’ve written about the same issue with AI pilots that harden existing workflows. Before making a process faster, someone needs to decide whether it deserves to survive.
A Stanford preprint published in August 2026 found that human-led collaboration dominated the Claude conversations researchers examined. People shaped the work through their prompts and follow-up exchanges. That fits how I think about delegation: setting the assignment is the beginning of your involvement.
A finished task needs a useful result
A polished document and a confident completion message can make a task feel finished. I still want to see what actually happened. Did the agent solve the problem, or did it produce something that looks like the deliverable I requested?
Anthropic makes a useful distinction in its guide to evaluating agents: the record of what an agent did is separate from the result it actually produced. I think that is a good starting point for anyone assigning AI work.
If you ask for a booking, check that the right booking exists. If you ask for a spreadsheet, check the calculations and assumptions. If you ask for research, open the sources and see whether they support the conclusions. The agent’s completion message tells you it’s ready for review.
Giving the agent that standard at the start makes the assignment easier to carry out. It can check its work and bring back specific problems. If a source contradicts the conclusion, I want to hear about it before I spend time reviewing the prose. If a spreadsheet depends on an assumption, I want that assumption visible.
The amount of checking should fit the job. I don’t want to spend ten minutes supervising a formatting change I can undo in seconds. A public commitment deserves more attention. Knowing where your attention matters is part of getting good at this.
Give the agent room to work
Good delegation also means deciding where the agent can act without coming back to you. Access to an email tool doesn’t settle whether it may send a message. The assignment should make clear when the work is preparation and when it includes taking action.
Clear boundaries save attention. An agent can investigate, prepare a result, and handle routine revisions while leaving consequential choices with the person responsible for them. That direction has to be available in the working environment, alongside the relevant business context. Lauren Hanford, VP of Product Operations at Sonar, makes this point in her essay on designing agent operating environments: we need to supply the context and direction the work depends on.
The Stanford researchers also found that friction was often productive: people clarified requests and corrected misunderstandings. I think we sometimes treat those exchanges as a failure of the tool when they are simply part of working through a problem. The useful question is whether the conversation moves the work forward.
That is why I don’t judge supervision by how many times someone approves an action. You can click through a dozen requests and still miss the decision that matters. I want routine work to move along and important choices to come back with enough context for me to make them.
A stream of activity updates doesn’t help much on its own. Tell me what needs a decision, why it matters, and what happens next.
This changes what it means to be good with AI
For a solo operator, this is a real change in the shape of the job. You may be used to keeping the reasons for a decision in your head because you’re also the person doing the work. Delegation makes those reasons useful to someone, or something, else. Getting them out of your head is part of making the business easier to run.
The gains should build over time. When an assignment goes wrong because a preference was missing, record that preference where the next assignment can use it. When the same question keeps returning, decide whether the agent lacks context or whether the decision really needs you. Repeated corrections are a chance to improve how the work is assigned.
I’d like AI education to spend more time on those situations. Give people an incomplete assignment and let them work out what’s missing. Show them a polished result with a weak conclusion. Reusable prompts can be helpful, but people need practice making the decisions those prompts depend on.
As agents carry more work through to completion, their users will spend more time setting direction and deciding what is good enough. Some will have teams. Others will run businesses on their own. Either way, the ability to turn an intention into a clear assignment will become part of how they compete. That’s why prompting is actually a management skill.