Title
Final accountability. It stays with the leader, and pretending otherwise is how people end up carrying weight they were never given authority to carry.
The operating system
Four frameworks and the mechanism between them. Built across twenty years inside schools, humanitarian assistance at USAID, and founder-led companies where honest feedback was the only kind on offer.
Start here
An organization is a drivetrain. Something generates the power, something chooses the gear, something decides the direction, and something transfers the force to the wheels. When an organization runs badly, people usually blame the parts. It is almost always the connections between them.
A clutch is the only component in a car engineered to slip. Everything else is built to grip. It exists so that two things spinning at completely different speeds can meet without shattering each other. Engine at four thousand rpm, gearbox not turning at all: take away the part in between and you do not get movement, you get metal filings.
That part is emotional intelligence. Not a soft skill, a mechanical necessity, and the reason the book is called CLUTCH rather than something about vision.
The architecture
Each one does a specific job. Together they are a complete leadership operating system, and each fails in a way the others predict.
I
The engine
Six cylinders that generate capacity. When one stops firing the whole thing runs rough long before anyone names why.
CREATE in fullII
The gearbox
Six leadership stances, and when each one is the right gear. The gearbox does not choose your destination.
VOICES in fullIII
The navigation system
Six decision modes. The question is not what to decide, it is how to decide who decides.
The 6C Compass in fullIV
The handoff system
Eight steps for transferring ownership so it stays transferred, rather than coming back with interest.
DELEGATE in fullThe engine
Six cylinders. An organization generates capacity the way an engine generates torque, and when one cylinder stops firing the whole thing runs rough long before anyone names why.
An engine down one cylinder still runs. It just runs rough, burns more, and gets slower in a way nobody can quite point at. Most teams diagnose the symptom. The engine light tells you which cylinder.
Ask yourself
Name the last thing that took three times longer than it should have. Which of the six was it?
If you cannot answer that in ten seconds, that is the answer.
The gearbox
Six leadership presences, shifted by context. You do not have a leadership style. You have one gear you never shift out of, and your team has built its habits around it.
A gearbox does not choose where you are going. It decides how much of the engine’s power actually reaches the road right now. The worry leaders raise first is whether changing presence will confuse people. It does the opposite. Teams do not need you consistent. They need you legible.
Ask yourself
What gear were you in for your last three hard conversations?
Same gear all three times is a gearbox stuck in third. It will get you along a motorway and nowhere up a hill.
The navigation system
Who decides, how, and when. Six modes, named out loud, so nobody has to reverse-engineer decision rights from your tone.
Satnav does not drive the car. It tells you which turn belongs to you, before the junction rather than in it. Command is not domineering, it is simply expensive, and most organizations spend it like it is free.
Ask yourself
Map your last ten decisions. How many were actually yours to make?
If the answer is seven, you do not have a trust problem. You have an architecture problem.
The handoff system
Eight steps for transferring real ownership, so a handoff develops someone instead of dumping a task on them.
You can hand someone the keys and still keep a foot on the pedal. That is most delegation. Define the container, not the contents: the why, the what and the by-when. The how belongs to them.
Ask yourself
Think of the last thing you handed over. How many times has it come back to you since?
Once is a handoff finding its feet. Three times was never delegation. It was a loan.
The distinction most delegation dies on
Final accountability. It stays with the leader, and pretending otherwise is how people end up carrying weight they were never given authority to carry.
Operational ownership. It transfers, completely, and the boundary gets said out loud rather than assumed.
Most delegation fails because these two get conflated. The leader believes they handed over the work. The team believes they were handed a test. DELEGATE separates them and makes the line explicit, which is the difference between delegation that sticks and delegation that comes back with interest.
Three ways in
The whole system, on paper
CLUTCH is the operating system in full: all four frameworks, emotional intelligence as the mechanism between them, and a diagnostic for every part. Or buy the one framework that matches what is currently breaking, as a standalone ebook at $3.99.
Essays, weekly
Long enough to actually argue something. One idea worked through properly, with the coaching questions I would ask in the room, what to try on Monday, and the occasional account of getting it wrong in public.
LinkedIn newsletter, short
One framework, one move, read in ninety seconds on a phone between meetings. It is where people disagree with me in the comments and the argument gets better for it.
Or skip ahead
Six cylinders, thirty questions, ten minutes, and no email wall on the questions. The bottleneck is rarely where you think it is, which is why guessing costs more than asking.