For EOS Implementers

Recognition

What to listen for

You hear the whole business in a quarterly, and again in every L10 after. A few things worth listening for:

“We carried it over. Again.”
“We moved it to Dave, and it stopped moving for him too.”
“It’s not that she can’t. It’s that nobody else can.”
“Sales, delivery and billing all need Sarah this week, and she’s already at 120%.”
“Can’t we just get an AI to take some of this off Sarah’s plate?”

You know the two people issues: right person in the wrong seat, and wrong person in the right seat. Those lines are what I call the third people problem: the right person, in the right seat, simply overloaded.

The People Analyzer was right and GWC held. There’s no better seat to move them to, and the rock still waits on them. It’s a design problem, not a people problem.

Two questions that sort it

Not every overloaded person is this. To tell, think about the person everything runs through and ask two questions.

Would someone just as good be any less buried?

If they’d cope, it was the person or the fit, and that has a people fix. If they’d be buried by month two, the problem is the work.

Has more help ever made the pile smaller?

A hire, a new tool, AI? If it all got absorbed and the same people are still buried, the problem is the work, and that’s what I fix.

What I do about it

If the work is the problem

There’s something I can do about that, and it isn’t a tool your client bolts on.

Your toolkit has moves for this, and they’re the right ones. Back to the Accountability Chart, then Delegate and Elevate. Often that’s enough.

When it isn’t, it’s because the work inside the seat keeps its shape. The easy parts come off the plate, and the reason the work runs through that person stays.

That reason is a call only they know how to make, more volume than one seat was ever built for, or every part of the business landing on them at once.

Nobody designed that work. It grew up around the person doing it, which is why it can’t move to anyone else.

It’s also why hiring a second one doesn’t help. The Accountability Chart designed the seat, and nobody designed the work inside it, so the new hire walks into the same pile.

That kind of work doesn’t come off a shelf. It’s a build, designed around that one piece of work in that one business.

See one working

Try it on a client you have in mind

That isn’t a claim you should take on faith, so here’s one running.

Tarvi handles the day-to-day operations inside Admentus, my own business, in a system I designed and own. It is the small version of what I just described, grounded in how this business actually works, so when you describe a client it is reasoning against something rather than improvising.

Tarvi is also one agent. What gets built for a client is several, each with a defined role inside work that was designed first, with people checking where checking matters.

Try it yourself. Describe the situation you’re looking at in your own words. There’s no form and nothing to sign up for.

The order matters more than the tooling does. Here’s the clearest example I know.

Detroit, 1906

The vision was right

Henry Ford never had an advisor like you. You’re the one part of this I’m making up. The rest happened.

It’s 1906, and your client has the vision on one page. Build a car for ordinary people instead of the wealthy, and get the price low enough that they can actually buy one. It isn’t a vague vision, and he didn’t arrive at it comfortably. He fought his own financial backer over it, and in 1906 he bought the backer out.

The vision is right, and this year it’s working. The Model N sells for $500 and becomes the best-selling car in America.

Then you sit down for the quarterly, and he drops an issue on the list: orders are coming in faster than the shop can fill them. The rock writes itself. Double output this year.

The quarter it stops working

You both reach for what you know

Before you decide anything you go look at the shop, because that’s the job. Cars are built one at a time at fixed stands. The parts are getting closer to identical but aren’t there yet, so a fitter still files and adjusts each one until it seats, and every man has his own way of making them meet. The shop turns out a few dozen cars a day.

So you do what your discipline does, and it’s the right call almost every time you make it. Re-scope the rock and put a clear owner back on it, or move it to next quarter so production has room to catch up. Ford does what an owner does, and hires more men.

Watch what the hiring actually buys him. Every man he takes on learns the job from the men already there, so the work stays exactly the shape it was, with more hands on it. He’s bought more of the same ceiling at a higher payroll.

You’re the only person in that building who can see the whole thing at once. The men on the floor see their own bench, and Ford sees demand he can’t fill. What you see is a vision that’s right and a rock that still won’t move.

You’re the one who says out loud what’s wrong: every car in that shop is still fitted by hand, one at a time, by men who each do it their own way. That read is correct, and it’s also where the work leaves your category.

The right order

The car had to change first

While the shop kept hiring, Ford’s engineers spent the next two years making the parts identical, so nothing would need fitting. The Model T arrived in 1908, the first Ford built entirely from interchangeable parts and designed from the start to be manufactured instead of fitted by feel. A part went in because it was made to go in, not because a skilled man made it go in.

Only then did the moving line work, and it didn’t arrive until 1913, five years after the car it was built for. The method came second because it had to. Run a moving line on hand-fitted parts and all you get is chaos moving faster.

What the best of those men knew moved out of their hands and into the fixtures, the gauges and the dies. The skill went into designing the work instead of doing each piece by hand.

Neither of you could have drawn that up in the room in 1906. It took Ford years and a different car to get there, and the line came later still.

Design the system

The work your client’s rock keeps waiting on gets designed as a system: the calls it depends on, how much one seat can hold, and who else needs that seat at the same time.

They own it

The person it used to run through owns that system, and the work stops funneling through them.

Then it scales

A new hire can step into a system that was designed, and AI agents can run the repeatable part of it, so that seat stops being the ceiling and the rock closes.

Design first, method second. Most firms try it in the other order.

Where I come in

You already did the hard part

Ford’s story only goes this far. He had years. Your client has this year’s V/TO and a rock that’s been carried since spring.

You got the vision out of the leadership team’s heads and onto one page, and you built the meeting pulse that keeps it alive after the offsite. Most firms never get that far.

You’ll know the client I mean. The V/TO is right, the team is healthy, and the scorecard is green everywhere except the one measurable that matters.

What’s left sits underneath the rock. The work behind it runs through one person, because it grew up around them instead of being designed. Setting the rock is what makes it real. It doesn’t make the work itself movable.

You can see it from where you sit. Neither of you can fix it in the room, because the fix has to be built.

The method

What I actually do

I take one business system, the one that rock actually runs through, and map how it works today under real load. Then I redesign that work into a system owned by the person it runs through, and I build the AI-operated part that runs the repeatable work inside it. It’s the level below your 20%: the how.

This fits firms roughly $3M to $50M in revenue, profitable, with a real operation already running and one clear place it’s constrained. One system per engagement, not the whole company at once.

It’s the wrong call for a business still finding its footing, for a team that can’t agree on who decides, or for an owner who won’t look past the tool they’ve already picked. And if what we find is a quick fix rather than a redesign, I say so, and that’s where it ends.

See the full method

For you

What referring gets you

There’s no fee and no kickback here. Nothing changes hands, so there’s nothing about the introduction that could look wrong to your client later if it ever came up.

What you get is an answer for the issue that keeps coming back to the list, the one you can name but can’t build your way out of. Telling a client honestly that the next move is architectural, and knowing who does that work, is worth more to the relationship than guessing at it.

I’m glad to go the other direction too. When mapping a client’s system turns up a people or seat problem, or an owner with no operating system yet, I send that client to you. And if you just want somebody to sanity-check a client situation before you decide it’s even worth an introduction, call me for that.

Next steps

When you’re ready to introduce us

However you make the introduction, it goes the same way from there, and I follow up once without chasing. Here’s what your client hears from me:

A conversation first. Twenty minutes to see whether there’s a real fit. If there is, we spend ninety minutes mapping how the work actually runs, on a shared whiteboard, and sketching where agents fit and where your people stay. There’s no charge for either, and you keep the map.

If it’s worth doing, I send a proposal for the first piece: one part of the system, built and running in a few weeks. Each piece stands on its own.

Send them the short version

One page written for the owner. Reading it commits them to nothing.

See the one-pager

Send them the link

One link, and they book the first call themselves. Nothing waits on you.

See the mapping session