How Leaders Build Their AI Agents
Last week, I did something completely different—I took a two-day break from AI to explore dinosaur skeletons.
Yes, quite the opposite of AI.
Stepping back gave me a valuable reminder: AI is a fantastic collaborator, but human creativity requires moments of disconnection and reflection.

So when I read Angela Yang’s “Need to attend a meeting, order groceries or book a flight? There's an 'AI agent' for that”, I reflected on a fundamental truth.
Too often, leaders rush into AI without taking a step back to see the bigger picture.
Because as we’re nearing the end of our Implementation Program, a four-week trajectory where Lead with AI graduates turn theory into action, some themes emerge.
Learning from those, here are five steps to elevate how you think about building your AI agents.
Five Steps to Successfully Build AI Agents
1. Don’t Start with AI—Start with the Problem
In a previous edition, "Successful AI Implementations Start Specific," I already shared about choosing the right AI tasks.
Most AI failures happen because people jump straight into execution without truly understanding the problem they’re solving.
The best AI applications focus on tasks that meet my G.E.D. + R. Framework:✅ General – Could a great generalist do the job?✅ Error-Friendly – Is there room for mistakes – since AI will make them?✅ Digital – Is the work online? AI can’t cook yet.+✅ Recurring – Apply AI where you spend the most time.
Added to that, consider Joy. A recent joiner, Jael Chng, was surprised to hear me mention this. But it makes sense: a task could be perfectly G.E.D.+R., but if you enjoy doing it - why apply AI to it?
If AI isn’t saving time, reducing costs, or improving efficiency, it’s not the right tool for the job.
2. Write Out Your AI Process Before Touching Any Tools
I see this mistake all the time: Someone gets excited about AI, starts setting up a new tool, and then gets stuck.
Instead, write down your task and the ideal outcome of your AI implementation.
Then, map out the entire AI workflow:
- What triggers the AI? (e.g., an email, a document upload)
- What input does it need? (e.g., a customer request)
- What does AI process? (e.g., summarizing or classifying data)
- What happens to the output? (e.g., saved to a CRM, emailed to a user)
We did this on a Figjam board and had a lot of fun.

Once you’ve written out the flow of your “Minimum Loveable Product” (MLP), ask ChatGPT to roast you.
Is what you’ve conceived actually the best way to reach your objectives?