Unlocking Real Leverage with AI Delegation
Starting to delegate to AI feels awkward. It is a lot like hiring your first contractor: you know there is leverage on the other side, but the first steps are messy and uncertain. The myth of the perfect plan holds many people back, but the reality is you just need to begin.
The payoff is real, but the start is always a little rough.
Here is how I do it.
Why AI Delegation Feels Awkward
The first time I tried delegating to an AI agent, it felt exactly like onboarding a new team member. I was not sure what to hand over or how to check the work. The results were messy and there was a lot of copy/pasting. It took a lot longer than doing it myself.
Delegation is always awkward at the start, whether you are working with people or machines. The learning curve is part of the process, and the discomfort is a sign you are moving forward.
Here are five principles for getting started:
Start Small
Begin with a simple, concrete task. Even if it feels trivial, this gives you a clear baseline. The first attempt will be clumsy - that is normal. Each iteration helps you refine your instructions and identify potential issues.
Expect to Iterate
The journey to effective AI delegation is not linear. Each round improves your ability to specify requirements and spot problems. Do not expect perfection on the first try. Instead, focus on learning from each attempt.
Use Human Delegation Frameworks
Apply the same frameworks you use for human delegation. The VSEM framework helps separate vision, strategy, and execution. A GTD approach breaks work into manageable chunks. I wrote more about how to apply these delegation frameworks in AI coding in this post.
Treat it Like Hiring Contractors
Approach AI delegation like hiring contractors: experiment quickly and move on if something is not working. Do not get stuck trying to make a suboptimal approach work. The goal is to find what works for you.
Embrace the Mess
The path to effective AI delegation is not smooth. It is fiddly and sometimes frustrating. But every experiment brings you closer to real leverage. The mess is part of the process - embrace it and keep moving forward.
How to Delegate a Workflow
Start with a Fixed Task
Begin with something entirely fixed, without AI, to get used to the tools you have available.
For example, I use n8n to automate a Kit tag addition that creates a Google Calendar entry for my webinars. It was fiddly to create, but it helped me learn how the workflow tool worked.
If you are more technical, try using n8n. If you are not, Zapier is a great place to start. There are plenty more tools out there if you need more options.
Look for Decision Points
Once you are comfortable with the tools, look for decision points in your workflow where you would not normally give the job to a computer. Try and find a really simple decision that you make all the time.
If you are not sure what an AI might be able to do, ask an AI agent to brainstorm where an agent could help within your workflow. This kind of meta-thinking about strategy is a really important skill to develop in the age of AI.
Automate One Thing
Pick a small decision to automate. Set up the automation in your chosen tool. Add an AI agent to handle the decision point. Test, iterate, and refine.
Each experiment will teach you something new about the tool and what AI can do, slowly increasing your leverage over time.
If something doesn’t work, revisit when a new model comes out. Those who will be at the forefront of this will be the ones who are willing to go back and push the boundaries again, and experiment and learn. The tech is moving so fast that what didn’t work three months ago might just work now, unlocking big productivity gains.
An Example
Here is an example. Imagine you receive inbound emails asking for advice. You probably already automate parts of this process, using rules, by marking particular emails as important based on who they are from. Try first to move this process to a workflow tool. (Note: this could get expensive if you get a lot of email, so perhaps do the first pass of filtering via your existing email rules, such as emails not directly addressed to you.)
Once that’s done, how do you process the rest? Normally, you might read each one and decide: should you reply personally, refer the person to a resource, or have AI draft a first response?
This is a perfect decision point to automate. Set up a workflow where AI reviews the email and drafts a reply for you to approve, or marks the email as important for your attention. You can start by automating the triage step, then gradually hand over more of the process as you gain confidence.
The Payoff and Next Steps
Delegating is always awkward. It could be the job is done only 80% as well as if you did it. But if we learn to delegate and let go of our perfectionism, real leverage opens us for us. The beauty of the AI age is that this leverage is beginning to be available to all, not just high performing leaders. We need to learn the skills they use to delegate to realise the same benefits.
The awkwardness is a sign you are learning and making progress. Every experiment brings you closer to the kind of leverage that transforms your workflow. You do not need a perfect system; you just need to start. Share your experiences, keep experimenting, and watch as the payoff grows.
More articles
The Huge List of AI Tools: What's Actually Worth Using in May 2025?
There are way too many AI tools out there now. Every week brings another dozen “revolutionary” AI products promising to transform how you work. It’s overwhelming trying to figure out what’s actually useful versus what’s just hype.
So I’ve put together this major comparison of all the major AI tools as of May 2025. No fluff, no marketing speak - just a straightforward look at what each tool actually does and who it’s best for. Whether you’re looking for coding help, content creation, or just want to chat with an AI, this should help you cut through the noise and find what you need.
Read moreHow I Make Complex AI Changes
Most technical leaders know the pain. You get partway into an ambitious AI project, then hit a wall. You are not sure how to start, or you get so far and then stall out, lost in the noise of options and half-finished experiments.
Recently I tackled this head on. I did this live, in front of an audience. I used a framework that finally made the difference.
The challenge: could I take a complex change, break it down, and actually finish it, live on stream? My answer: yes, with the right approach. Here is exactly how I did it.
Read moreBuilding AI Cheatsheet Generator Live: Lessons from a Four-Hour Stream
I built an entire AI-powered app live, in front of an audience, in just four hours. Did I finish it? Not quite. Did I learn a huge amount? Absolutely. Here is what happened, what I learned, and why I will do it again.
The challenge was simple: could I build and launch a working AI cheatsheet generator, live on stream, using AI first coding and Kaijo1 as my main tool?
Answer: almost! By the end of the session, the app could create editable AI cheatsheets, but it was not yet deployed. A few minutes of post-stream fixes later, it was live for everyone to try. (Next time, I will check deployment on every commit!)
Try the app here: aicheatsheetgenerator.com
AI: The New Dawn of Software Craft
AI is not the death knell for the software crafting movement. With the right architectural constraints, it might just be the catalyst for its rebirth.
The idea that AI could enable a new era of software quality and pride in craft is not as far-fetched as it sounds. I have seen the debate shift from fear of replacement to excitement about new possibilities. The industry is at a crossroads, and the choices we make now will define the next generation of software.
But there is a real danger: most AI coding assistants today do not embody the best practices of our craft. They generate code at speed, but almost never write tests unless explicitly told to. This is not a minor oversight. It is a fundamental flaw that risks undermining the very quality and maintainability we seek. If we do not demand better, we risk letting AI amplify our worst habits rather than our best.
This is the moment to ask whether AI will force us to rediscover what software crafting1 truly means in the AI age.
-
I use the term “software craft” to refer to the software craftsmanship movement that emerged from the Agile Manifesto and was formalised in the Software Craftsmanship Manifesto of 2009. The movement emphasises well-crafted software, steady value delivery, professional community, and productive partnerships. I prefer the terms “crafting” and “craft” to avoid gender assumptions. ↩
Why Graph RAG is the Future
Standard RAG is like reading a book one sentence at a time, out of order. We need something new.
When you read a book, you do not jump randomly between paragraphs, hoping to piece together the story. Yet that is exactly what traditional Retrieval-Augmented Generation (RAG) systems do with your data. This approach is fundamentally broken if you care about real understanding.
Most RAG systems take your documents and chop them into tiny, isolated chunks. Each chunk lives in its own bubble. When you ask a question, the system retrieves a handful of these fragments and expects the AI to make sense of them. The result is a disconnected, context-poor answer that often misses the bigger picture.
This is like trying to understand a novel by reading a few random sentences from different chapters. You might get a sense of the topic, but you will never grasp the full story or the relationships between ideas.
Real understanding requires more than just finding relevant information. It demands context and the ability to see how pieces of knowledge relate to each other. This is where standard RAG falls short. It treats knowledge as a stack of random pages, not as a coherent whole.
Time for a totally new approach.
Read more