In eight weeks you redesign one workflow from your own role, and you measure what it changed.
"Overall, I found it genuinely useful."
Ashik, Operations Manager, on the delegation brief he brought me. Full context further down.
AI now drafts, analyses, summarises, and prepares work. The manager who simply reviews more output gets buried. The manager who designs how human and AI work move together becomes the one who leads.
Gartner reports that 74 percent of managers feel unequipped to lead change, and that manager development has been the top HR priority for three years running. The skill is in demand. The supply is almost empty. That gap is your window.
Right now, being able to orchestrate human and AI work makes you rare. In three years it will be expected. The managers who build the capability first will hold the advantage when everyone else is scrambling to catch up.
Today, when AI-supported work is unclear or incomplete, it lands on the manager to fix. More review. More correction. More clarification. The output is faster, but you carry more.
After this system, you set the standards before work begins. You define what AI handles, what you decide, what gets reviewed. You orchestrate. You are no longer the bottleneck. You are the architect of how the work moves. That is a different kind of manager, and a far more valuable one.
Catching errors. Rewriting drafts. Clarifying prompts. Competing for the same roles as everyone else, with the same skills as everyone else. Replaceable.
Sets standards. Defines what AI does and what humans decide. Leads instead of catches. Holds a capability most managers do not have yet. In demand. Hard to replace.
This is the same system organisations bring me in to install across their teams. Here, you build it for yourself, applied to your own work, in a cohort of managers doing the same.
You map how work moves through your role today, and where it keeps coming back to you. You leave week one knowing exactly where your drag sits.
What it is worth: you can name the one place work keeps coming back to you. Most managers carry that cost for years without ever naming it. This is also the week you decide whether to continue, and you owe nothing further if you stop.
Each week builds one capability from the list above and applies it to your own team and workflow, in order. Capability one in week two, and so on through capability six in week seven. You practice each on real work, with the cohort and with me.
What it is worth: every artifact is built on work you already owe someone. None of this is homework on top of the job. The hours you put in are hours you were going to spend on that work anyway, spent differently.
You bring the eight weeks together into one redesigned workflow you have actually built, plus the measurement habits to keep improving it. You finish with proof of capability, not a certificate that means nothing.
What it is worth: the cost is recovered the first time your redesign prevents rework on a real project. After that it keeps paying, because the workflow stays redesigned and you keep the method.
One thing I ask in return. In week eight we write down what your redesign actually changed, as a number. Rework avoided. Hours returned. A decision that stopped being made twice. You keep it for your own case, for a review or a promotion conversation. With your permission, and with nothing in it that identifies you or your employer, I use it for mine. You are in the first ten, so your result is what this system gets judged on.
A certificate records that you turned up and passed something on a given day. It is a record of an event. It was never evidence that you can do the work, and that is as true of the well-known names as it is of mine.
Work you have actually done is a different kind of evidence. You finish this system holding artifacts you built, on your own real workflows:
This is what you bring to a promotion conversation, a performance review, or your next interview. It is harder to argue with than any badge. It shows, in your own work, that you can do what most managers still cannot.
So I am not going to show you results from a programme that has not run. What I can show you is the part of the work that is already running. Managers bring me one real task they are about to hand to AI, and I set the boundary inside it: what AI may do, what it must not, what a human decides, and when it has to stop. That is capability two and capability three of the seven, delivered on a live task.
Two managers have taken it that far. Here is what they said, in their own words.
"They are what transformed it from a task description into a practical governance document."
"Overall, I found it genuinely useful."
Ashik, Operations Manager
"The four-bucket logic (decline needing all four negatives, escalation needing just one signal) is a smart, deliberate call. I have learned something from that."
Andrew, operational excellence and transformation
He is reacting to that one design decision, on his own task. He has not seen this cohort run, and he is not endorsing it.
The guardrails in both cases are my work, not theirs. They are reacting to the judgment that went into their task. That judgment is what the eight weeks teaches you to make yourself, on your own workflows, without me in the room.
This is a founding-cohort price. It is set so a committed manager can fund it personally, and so it is an easy approval if your organisation pays. After the founding cohort, the price rises.
Many managers have their development funded by their employer. If you want to ask, the case is simple, and I give you the words for it:
"For AED 2,300 I will build the capability to lead our team's human and AI work as a designed system, and bring back a redesigned workflow we can use. The cost is recovered the first time it prevents rework on a real project."
You see exactly how this system works in the first week. If it is not for you, tell me before week two and you owe nothing beyond the first week. No forms, no friction.
Some managers need to know this shift exists. Some need to have used it once, on something real. Some need to be able to redesign how their work runs. Only the third one needs eight weeks.
It is not the right fit if:
It is built for you if:
Tell me your role and the one piece of work that keeps coming back to you. One line is enough. No form, no application.
If it is not right for you I will say so, and I will say why. If it is, I hold you a place in the ten.
Once the ten are set, week one begins. You start mapping your own work from day one.
Message me on LinkedIn, or write to me directly. I read every message myself.
Message me on LinkedIn Or email me