The 5 Steps to Lean AI: Kill First, Automate Last
A lean thinking map for solo workers who want to orchestrate AI agents without automating their chaos.
The trouble with automating too early is that you scale the mess.
I’m a founder, intrapreneur, and former CIO rethinking governance for the one-person business, navigating sole accountability in the age of intelligent machines—informed by plenty of scar tissue. All posts are free, always. Paying supporters keep it that way (and get a full-color PDF of my book Human Robot Agent plus other monthly extras as a thank-you)—for just one café latte per month.
Most people want to make a meaningful difference through their work—whether it’s designing intuitive apps, offering an online course, or baking artisanal banana bread. And whatever the goal, it always begins with ideas. Lots of them. Usually, way too many.
And in the age of AI, it is very easy to add yet another automation to implement one of those ideas. Maybe even too easy. So what if you have twenty AI agents doing work for you while you sleep? If you don’t have the headspace to review all the outcomes—congratulations!—You’ve implemented agentic productivity theater.
I’ve spent countless hours building automations for things I thought were important: customer orders, invoicing, and reports, only to watch the business models they supported crash and burn. The ROI was a solid zero. I could have saved myself months of frustration by asking one question first: Do we even need this workflow at all?
The answer, embarrassingly often, was no.
The Solo Worker’s Trap
Here’s what makes this especially painful for solopreneurs and one-person businesses. When you’re the single wringable neck—the only person accountable for everything—automation feels like oxygen. You’re drowning in tasks, so you grab the nearest AI agent and throw it at the problem. I get it. I’ve done it. And I’ve regretted it many times.
The trouble with automating too early is that you scale the mess. You don’t get efficiency. You get faster chaos and cognitive overload. Elon Musk admitted as much about his own Tesla factories: he tried to automate many steps before questioning whether those steps should exist at all.
So before you hand your processes over to Claude Cowork, OpenClaw, or a shiny new n8n scenario, let me share a map I’ve been refining for years. Five orientations, not prescriptions. Five questions to ask before you launch a single automation prompt.
1. Clarify and Eliminate
Start with the question Musk keeps hammering: what’s the point? Tie every idea to someone who really needs it. Not “the legal department”—point at a specific human who can explain why this request exists and what it means for them.
I once spent weeks building an onboarding workflow for a new business idea that collapsed less than two months later. Nobody needed it. Nobody cared. I just thought it was a good idea, until it wasn’t. The process shouldn’t have existed in the first place. The best requirement is the one you kill before it wastes your time.
2. Simplify and Accelerate
Whatever survives the kill list gets stripped down. Steve Jobs understood this with the iPod and iPhone—every button and widget faced ruthless scrutiny. Does this need to exist? If yes, make it so intuitive that people barely have to think.
Having fewer steps means fewer errors, faster results, and less of your evening spent debugging workflows. This is where solo workers and lone AI orchestrators tend to overcomplicate things, by the way. We add options because we can, not because we should.
Having no human team to push back makes it dangerously easy to build yourself an automated monstrosity with more bells and whistles than common sense. Human teammates have the decency to ask “why?” or at least roll their eyes. AI agents don’t. They happily execute whatever pointless task you give them.
3. Amplify and Elevate
After eliminating and simplifying, you might feel the urge to add something. Good—but Hick’s Law says decision time grows with the number of choices. So only add options when they don’t complicate things, when they don’t add friction to other people’s experiences.
For example, when I publish a blog post, I share it on LinkedIn, X, Threads, and Substack Notes. That amplifies my reach without complicating the experience for anyone. It makes it easier for people to find me, not harder. The addition is orthogonal—it extends what’s possible without interfering with what already works.
The question to ask: does an additional feature idea create new possibilities without forcing people to deal with more options?
4. Codify and Automate
Now you can think about automation. This is where your specialized AI agents, workflow scenarios, and algorithmic managers earn their keep. But only after you’ve eliminated and simplified.
I once automated pan-European invoicing for a business that never even achieved product-market fit. What was the point? All my automations got switched off. Automation is the reward for doing everything else right.
The prerequisite for automation, of course, is codification. If you can’t describe a process clearly enough for a machine to follow it, you’re not ready to automate it. No codification, no scalability. And for Solo Chiefs running a “cockroach business”—one built to survive any environmental change—premature automation is one of the most effective ways to waste your time.
5. Specify and Delegate
After you’ve automated what can and should be automated, you’re left with tasks that require judgment. The question becomes: whose judgment? Could you hand this to a personal assistant, a business partner, or a sophisticated AI agent orchestrator?
Here’s what you should never delegate: work that wastes time (eliminate it), work that’s too complicated (simplify it first), or work that a basic algorithm or simple agent can handle (automate it). Delegation is for what remains after you’ve been through the other four steps.
I know the operational loneliness of carrying the full picture. The temptation is to delegate everything that feels heavy. But passing down convoluted processes to humans or advanced AI agents is foolishness, not leadership.
The Order Matters More Than the Steps
To create these Five Steps to Lean, I borrowed from Lean Thinking, from Musk’s five-step algorithm, from the ESSA Framework, and from the “four steps to freedom“ that productivity bloggers keep reinventing ad nauseum. I added the amplification step in the middle because I wanted to balance efficiency with effectiveness. Claude and ChatGPT agreed.
👉🏻 Note: I count simple, specialized AI agents among simple workflow automations (step 4). I count complex AI orchestration (whether performed by humans or AI) as delegated management (step 5). The difference matters. 👈🏻
The real insight for leaders in 2026: AI agents make the wrong order more expensive, not less. When automation was manual and slow, premature optimization wasted your time. Now that AI agents execute at lightning speed, premature automation wastes your time and your money and creates problems at scale.
The map is simple. Eliminate. Simplify. Amplify. Automate. Delegate. In that order.
Jurgen, Solo Chief
P.S. This post was first published on Leadership in Change.
I'm So Tired of All the Attention-Grabbing Bullshit
Going online is like walking onto a bazaar where everyone is poking you, luring you, and yelling at you.
Is the Age of AI a Golden Era for Neurodivergent Workers?
For the neurodiverse mind, AI is not a prosthesis. It’s an interface adapter.












Hi Jurgen! I happened to find this article just after reading about 22 AI-era tricky questions, and it kinda clicked with some questions I've thought of but left me with some more.
While this one roadmap is def a must for Solo Chiefs, it also seems to guide (as for me) greater businesses about Sustainability (1) and AI-David (2) (and Middle Management (3), a bit) points.
1. Kill/Simplify: accounting for climate (and financial, which is usually a higher priority to capitalistic entities) cost of implementing AI might help decide whether a task should be automated or left to humans. Like... why develop a power-hungry single-task machine only to follow the trend, or, more often, why add AI layer where common computers work just fine with a dash of cognitive human load? It might sound old-fashioned, but do we as humanity need a hundred of corporate TikTok editing AI tools instead of using that energy for developing reliable healthcare instruments?
2. Same goes for hierarchical established companies vs 3 humans in AI trenchcoat. If, of that 200 (000) employees entity, only three of them do decide how the work's done and what the brand brings for the table, they'd better rule the robots. Here the answer seems clear to me (thanks to your yet another brilliant article about PVMVP): the companies could use the diversity and personal approaches of their plenty workers to improve compared to smaller-capacity organizations or solopreneurs. Make the most of their humans, so to say jokingly. Meanwhile, for now it's small groups and individuals who make the most change for diversity and inclusion, as it seems to me (and as all my respect goes to them, I suppose corps could do better as well).
3. Which brings us here: from what I can grasp, the main value of managers in AI-era might no longer be executing tasks, but rather developing, testing and monitoring this 5-step process for various business implementations. While they not necessarily all have to requalify as AI prompting experts, their experience and agility seem to become of greater importance for discriminating essential from "bells&whistling", simplifying while accessing value, and overall adding common human sense to AI literal techno-brains. Source: my two jobs where managers are so busy cherry-picking individual tasks that I'm desperately in need (and somehow becoming, in my junior position) of someone to actually manage whole processes, settle guidelines and defining priorities. AI can handle the checklists, but it can't decide what and why we're actually doing.
Kinda sorry for the longread, and I do suppose some of those thoughts are actually common knowledge. Still, I'd love to discuss this point of view of mine or maybe learn what to read from you or others on this topic. Thanks a lot for the delicacies for though!