Ideas are cheap.
That isn’t an insult to ideas. Ideas matter. But most businesses are not suffering from a shortage of them.
Owners have ideas. Managers have ideas. Employees have ideas. Consultants certainly have ideas. Put six reasonably intelligent people in a room for an afternoon and you can probably leave with a whiteboard full of them.
The harder part is knowing which ideas are actually good.
Then implementing them.
Then seeing what happens when the idea collides with customers, employees, schedules, software, budgets, existing processes, physical constraints and all the other irritating details that were conveniently absent from the whiteboard.
That last part is where a lot of management thinking breaks down.
We tend to treat thinking and implementation as two separate jobs. Someone comes up with the idea. Someone else does the work.
But implementation is part of thinking.
TL;DR
Leaders should delegate work. They should build management layers, systems and processes that reduce how much routine work depends on them.
But delegation becomes dangerous when the people making decisions stop seeing what happens after those decisions are implemented. The work can move down the organization. The information created by that work has to come back up.
The goal isn’t to keep the owner’s hands on everything. It is to keep the owner’s head connected to reality.
Ideas Are Cheap. Judgment Isn’t.
A good idea can be extremely valuable. But the idea itself is only the beginning.
You still need to know whether it is a good idea or merely an idea that sounds good in a meeting.
You need to understand what it will cost, who it will affect, how difficult it will be to implement, what could go wrong, what could go wrong if you do nothing, and whether the organization is actually capable of executing it.
That requires judgment.
And judgment gets better when it has evidence to work with.
An idea sitting in someone’s head hasn’t encountered very much evidence yet. It hasn’t frustrated a customer. It hasn’t confused an employee. It hasn’t run into a software limitation. It hasn’t added three unexpected steps to a process. It hasn’t saved two hours a week. It hasn’t broken anything. It hasn’t worked surprisingly well.
It is still mostly a hypothesis.
Implementation Is Part of Thinking
We often imagine the process like this:
Think. Decide. Implement.
Thinking happens first. Then a decision is made. Then everyone else gets busy executing it.
I think a better model is:
Think. Do. Observe. Learn. Think better.
Implementation creates information that did not exist when the idea was conceptual.
Suppose you create a new approval process because mistakes are slipping through. On paper, adding another approval makes perfect sense. The new control gets implemented and the error rate drops.
Success.
Except quotes now take two days longer to reach customers. Salespeople start finding ways around the approval process because they are losing deals. The approver becomes a bottleneck. Small decisions that used to take five minutes now sit in a queue.
Was the original idea wrong?
Not necessarily.
Maybe the company genuinely needed better control. But implementation exposed information that wasn’t available when the process was designed.
The next version can now be better. Maybe only certain quotes require approval. Maybe there should be thresholds. Maybe the underlying problem wasn’t approval at all, but unclear pricing authority.
You could not learn all of that from the original strategy meeting.
You had to put the idea into contact with reality.
When Ideas Only Travel Down
This is where hierarchy can become dangerous.
Hierarchy itself isn’t the problem. Businesses need roles, authority, management and delegation. Someone has to be able to make a decision without assembling the entire company for a town hall meeting.
The problem is one-way hierarchy.
A leader has an idea. It goes to a manager. The manager gives direction to an employee. The employee implements it.
And that is where the information stops.
The employee discovers that the process doesn’t quite work. The customer reacts differently than expected. A workaround becomes necessary. A seemingly minor rule creates a major delay.
But none of that makes its way back to the person who made the original decision.
So the leader moves on to the next idea while still believing the previous one worked exactly as intended.
Do that long enough and seniority can start insulating people from the consequences of their own decisions.
That is a dangerous place for a business to end up.
Authority can move downward. Reality has to be able to move upward.
The Hands Know Things the Head Cannot See From a Meeting Room
The people doing the work encounter information that simply isn’t visible from a strategy session.
That doesn’t mean the frontline employee is always right. It doesn’t mean management should abandon broader strategy every time someone dislikes a new process.
It means different positions inside a business can see different parts of reality.
The person doing the work may understand a physical constraint that management overlooked. The salesperson may see customer resistance before it appears in a report. The project manager may discover that two individually reasonable procedures conflict with one another. The bookkeeper may notice that a supposedly efficient process creates a mess three weeks later.
That information is valuable.
The hands don’t merely carry out the head’s ideas. They generate information the head needs in order to think well.
This Is Not an Argument Against Delegation
There is an obvious trap here.
An owner reads something like this and concludes that they need to stay involved in everything because nobody understands the business like they do.
Please don’t.
That is how the owner becomes the bottleneck for the entire company.
The objective of Infinite Leverage is almost the opposite. The owner should become progressively less necessary to routine execution. People, managers, standards, systems, technology, controls and written company knowledge should allow more of the business to operate without requiring the owner’s direct involvement.
But there is a difference between delegating work and disconnecting yourself from the information created by the work.
You can stop preparing every proposal without becoming ignorant of why proposals are being lost.
You can stop managing every project without becoming unaware of where projects regularly break down.
You can stop talking to every customer without becoming disconnected from what customers are actually experiencing.
You can stop personally following every process without having no idea whether the process works.
Leverage should create distance from routine work. It should not create insulation from reality.
There Is Such a Thing as Being Too Close
The opposite problem exists too.
If you spend every hour doing the work, you may understand today’s operational details extremely well while having almost no time to think about where the company is going.
You can miss patterns across departments. You can ignore capital allocation, risk, hiring, market changes, strategy and the design of the business itself because today’s problems consume all available attention.
That isn’t good leadership either.
Too close to the hands and you can lose perspective.
Too far from the hands and you can lose reality.
The goal is not maximum proximity. It is maintaining the feedback loop.
Design the Return Path
As a company grows, this feedback loop becomes less automatic.
When there are four people in the business, the owner probably hears about every problem whether they want to or not. At forty people, information starts moving through layers. At four hundred, an executive could make decisions affecting hundreds of employees without ever speaking to most of the people living with the consequences.
At that point, staying connected to reality has to become intentional.
A few questions are worth asking:
- When we introduce a new process, who is responsible for telling us what happened after it was implemented?
- Can employees challenge a standard that clearly does not work, and is there somewhere for that feedback to go?
- When someone discovers a better way to perform recurring work, does that knowledge improve the system or stay in that person’s head?
- Do we measure whether a decision produced the desired result, or merely whether everyone complied with it?
- How does customer friction make its way back to the people designing policies and systems?
- When management makes an assumption, when do we go back and check whether reality agreed?
This doesn’t require executives hovering over people’s shoulders.
It requires a return path.
The business needs a way for what employees learn, what customers experience and what implementation reveals to feed back into standards, systems and future decisions.
Creators Stay Close Enough to Be Corrected
There is a useful distinction between having ideas and creating.
A creative person can imagine something that doesn’t exist.
A creator has to deal with what happens when they try to make it exist.
Reality starts arguing back.
The budget isn’t enough. The software won’t do what you expected. Customers don’t care about the feature you thought they would love. Employees interpret the instruction differently than you imagined. Something you assumed would be difficult turns out to be easy. Something that looked trivial becomes the entire project.
That doesn’t mean reality should limit ambition.
Quite the opposite.
Understanding the constraints tells you what actually has to change if you want to accomplish something ambitious.
There is a big difference between challenging a constraint because you understand it and ignoring a constraint because you never bothered to learn about it.
Keep the Head and the Hands Close Together
The higher you move in an organization, the easier it becomes to spend your time with abstractions.
Dashboards. Strategies. Reports. Plans. Policies. Budgets. Organizational charts.
Those things are useful because leaders need to see the larger system.
But every abstraction is a compressed representation of something happening in the real world.
A customer is waiting. An employee is making a judgment call. A manager is working around a broken process. A salesperson is hearing the same objection for the tenth time. A piece of equipment is sitting idle. Someone has figured out a better way to do something and nobody else knows about it yet.
The further the head gets from the hands, the easier it becomes to manage the representation while losing touch with the thing being represented.
So delegate.
Build management layers. Build systems. Document knowledge. Automate repetitive work. Create controls. Get yourself out of work that does not require you.
But make sure the learning comes back.
The goal is not to keep your hands on every task.
The goal is to make sure your thinking can still be corrected by reality.