TL;DR — Alex Hormozi says the most valuable skill in business is getting other people to do things for you. He’s right, but the phrase is easy to misread. It isn’t about control. It’s about getting capable people to take ownership of outcomes with you. A boss pushes the chain from behind and has to keep pushing. A leader takes the front, gives people a real why, and pulls. This is how I’ve tried to build M10DIGITAL — and where I’ve gotten it wrong along the way.

I’m a problem solver.

But you can’t solve big problems alone. At some point the work outgrows one person, and the whole game changes.

Alex Hormozi once gave a blunt answer to the question of which single skill matters most in business: the ability to get other people to do things for you. His logic is simple. If you have that one skill, you can bring in people who have every other skill you don’t.

At first that sounds like a fancy word for delegation. It isn’t.

Delegation is just the visible part — one person hands work to another. The real skill sits underneath it: creating the conditions where capable people want to point their energy at the same goal you’re chasing.

Anyone with authority can hand out an instruction. A manager assigns a task. An owner signs a paycheck. A client hires a contractor. None of that buys you enthusiasm, creativity, loyalty, or even good work.

Compliance is cheap. Commitment isn’t.

That’s the whole difference between a boss and a leader. A boss leans on position: do this because I’m in charge. A leader earns something deeper: do this because the outcome matters, because you can see how your piece fits, and because you trust the people running at it with you.

So the real job isn’t getting people to do things for me.

It’s getting people to own outcomes with me.

Pushing the Chain vs. Pulling It

There’s an analogy I first heard tied to John Wooden, though the more common version belongs to Dwight D. Eisenhower.

Lay a chain on a table and try to move it by pushing from the back.

The links bunch up. Some go left, some go right, some barely move. You can push harder, but more force mostly makes more of a mess.

Now walk to the front and pull.

The links line up. They follow. Same direction, no fighting.

A boss pushes the chain. The instructions, the deadlines, the reminders, the corrections — all of it travels from behind. It creates motion, sure. But it only lasts as long as you keep pushing. Stop, and the movement stops with you.

A leader pulls the chain. You move first. You set the direction. You explain why it matters, and you give people something worth following. Purpose sets the direction. Trust holds the links together. Clarity takes out the slack.

That doesn’t mean a leader never gives an order. Sometimes you have to. Deadlines get set. Disagreements get settled. Weak performance gets addressed. But pressure can’t be the operating system.

If people only move when the founder pushes, the founder hasn’t built a company.

He’s built a pile of dependencies.

The question was never are people moving. It’s what’s making them move.

We work this way on purpose. We stay close to the business instead of standing around it — because when you’re close enough, you can see where growth is actually getting stuck, and you can pull from the front instead of shoving from the back.

Attraction Comes Before Delegation

Here’s the part people skip.

Delegation only starts after someone has agreed to get in the arena with you. Before you can hand anyone responsibility, you have to attract someone capable of carrying it.

That’s brutally hard early on.

A big company can offer a known name, a steady paycheck, a defined role, and a fairly safe future. A young company offers the opposite — an unfinished product, a half-built org, shifting roles, thin resources, and a real chance of failure.

Talented people have options. They aren’t sitting around waiting for you to tell them what to do. They have to be convinced that this problem, this company, this person is worth a slice of their one finite working life.

So entrepreneurial leadership starts with the ability to make an opportunity feel real.

In Silicon Valley, Keenan Feldspar can get anyone fired up about his ideas. He’s a joke on the show, but the underlying skill is real. Some people can describe a possibility so clearly that you start to picture yourself inside it. Steve Jobs was the extreme version — he could make hard goals feel inevitable and talk brilliant people into work they’d have called impossible the day before.

But excitement isn’t leadership.

Charisma gets people in the room. It can’t keep them there. Eventually the vision has to be backed by real judgment, real plans, real work, and a relationship people can actually trust.

Charisma opens the door. A strong why is the reason someone stays.

If you’re the kind of builder, operator, or creative who wants to be close to that work, that’s the exact person we’re trying to attract.

The Company-Level Why

If you want people to do meaningful work, your first job is to explain why the company exists at all.

A company-level why answers plain questions:

• Who are we here to help?
• What problem are we committed to solving?
• What change are we trying to make?
• Why is this worth our time?
• What standards decide how we do it?

This isn’t a grand mission statement. A why doesn’t have to promise we’ll change humanity. Inflated language usually breeds eye-rolls, not belief. A modest, believable purpose beats a dramatic promise nobody buys.

Fixing an annoying process. Serving a customer everyone else ignores. Doing unusually good work. Setting a higher bar in an industry that settled for mediocre. Any of those is enough. What matters is that the purpose is specific enough to shape decisions and honest enough to survive contact with reality.

A good why works like a compass. It helps people decide what to chase, what to walk away from, and what the work is even supposed to accomplish. It lets someone make a reasonable call when I’m not in the room.

Without a shared why, every decision has to travel back to the top. The founder becomes the brain, and everyone else becomes a pair of hands.

With a strong one, judgment starts to spread. Ours is simple: we believe in the dreams of passionate entrepreneurs, and we make the hustle count. That single line has settled more decisions for us than any process doc ever has.

The Task-Level Why

A company can have a great mission and still hand off work badly.

The company-level why explains why the organization exists. The task-level why explains why a specific piece of work needs to exist. You need both.

Any time we ask someone to do something, the assignment should answer five questions:

1. Who owns it? One person moves it forward. Collaboration can be shared. Ownership can’t be fuzzy.
2. What has to get done? Define the outcome, not just the activity. What’s different when it’s finished? What does “good” look like?
3. How should it be approached? Spell out the process, standards, resources, constraints, and non-negotiables. How much you prescribe depends on the risk and the person’s experience.
4. When is it due? A real deadline, plus any milestones or dependencies that matter.
5. Why does it need doing? The purpose, the stakes, the impact on the patient or client, the link to the bigger goal.

The why comes last on the list, but it gives meaning to everything above it.

Without it, a person knows what motion is expected but not what the motion is for. When things change — and they always change — they can’t adapt, because they don’t know which part of the instruction was essential and which was just the suggested route.

Say someone on our team is told to send a clinic a performance report every Friday. That covers the what and the when. It says nothing about the why.

If the point is to reassure the clinic that progress is happening, the report should lead with momentum and clear proof of results.

If the point is to catch underperformance early, it should surface the deviations and the open questions.

If the point is to help the owner make a budget call, it should focus on return, tradeoffs, and the recommended next move.

Same task. Three completely different reports — decided entirely by the why.

When people understand the why, they can tell whether the task is even the right way to get the result. They might find a better one. They might notice the ground shifted. They might stop the team from efficiently finishing something that stopped mattering last week.

That’s not disobedience.

That’s ownership.

Delegation Transfers a Result

One of the mistakes I’ve made growing M10DIGITAL is confusing handing off activities with handing off ownership.

Work would leave my calendar and land on someone else’s, so it looked like delegation. But that person still needed me for every real judgment call. I’d moved the labor and kept the responsibility, the context, and the decision-making.

That’s not real delegation. That builds a team of hands waiting for instructions — not a team of minds that can actually move the business.

Real delegation transfers a result, not a to-do list.

The leader defines the outcome, explains why it matters, sets the guardrails, hands over the resources, and makes clear how success gets measured. Then the person actually gets room to decide how to get there.

So that “how” in the five-part list has to be handled with care. Sometimes the method genuinely can’t move — legal requirements, financial controls, brand standards, client commitments, a proven procedure. Follow those exactly.

But when the method isn’t essential, prescribing every step quietly kills the ownership you were trying to build. In those cases, “how” should sound like guardrails, not commands:

• Here are the standards we won’t compromise.
• Here are the resources you’ve got.
• Here are the risks to avoid.
• Here’s what we’ve already tried.
• Here are the calls you can make without asking me.

The outcome belongs to the person. The guardrails belong to the company. The road between them should hold as much freedom as the situation can responsibly allow.

And freedom has to come with accountability. Autonomy without accountability drifts. Accountability without autonomy is just control with extra steps. Healthy delegation is both at once:

You own this result. You know why it matters. You’ve got room to use your judgment — and you’re accountable for how it turns out.

Why Makes Autonomy Possible

Explaining the why can feel like a waste of time up front. I already know the context. Passing it along seems slower than just saying “do this.”

In the short run, that’s true.

But that’s the wrong comparison. The real trade isn’t explain it once vs. do it once. It’s explain the reason now vs. answer a running stream of questions later.

When people only get instructions, every change in circumstances becomes another decision that lands back on me. When they understand the purpose, they handle most of those themselves.

A strong why isn’t inspirational decoration. It’s operational infrastructure.

It sharpens prioritization, because people know which outcomes matter most. It lifts quality, because they know what the work is supposed to accomplish. It builds adaptability, because they can change the method without abandoning the goal. It fuels motivation, because the work is tied to something beyond ticking a box.

Eisenhower understood this with stakes far higher than any business. In Crusade in Europe, he wrote that an American soldier needed more than an order — he needed to understand why. People deserved a basic grasp of the cause and the consequences of what they were being asked to do. He went as far as to say belief in the cause mattered as much to success as the discipline that comes from command. (Crusade in Europe)

It scales down to a company of any size. People perform differently when they understand the cause behind the command.

The stronger the why, the less force it takes to keep the chain moving.

Trust Turns Persuasion Into Action

Purpose starts the movement. Trust is what keeps it going.

People trust leaders whose words and actions line up. Ask for sacrifice while you shield yourself from every inconvenience — they notice. Praise initiative and then punish every failed experiment — they notice. Call people owners while hoarding information and every real decision — they notice.

Trust builds through repeated evidence. You tell the truth when the truth is uncomfortable. You admit what you don’t know without dropping the responsibility. You give credit freely, address weak performance directly, keep your promises, and make decisions that actually match the principles you announced.

Competence is part of trust, too. Good intentions don’t cover for bad judgment forever. People follow someone who understands the business, thinks clearly, learns fast, and stays calm enough to tell an emergency apart from an inconvenience.

That doesn’t mean being the best salesperson, marketer, operator, or designer in the building. Building something real means hiring people who are better than you at plenty of things. We say it out loud: M10DIGITAL is still growing too. We don’t claim to have every answer.

But the founder does have to be good enough at judgment to spot excellence, ask sharp questions, name the destination, and decide which experts to trust.

Humility isn’t the absence of conviction. It’s holding a strong view without pretending you’ve got every answer.

Influence Without Manipulation

“Getting people to do stuff” has a knife’s edge in it. It can describe leadership. It can also describe manipulation.

Manipulation hides what’s really being traded. It leans on fear, insecurity, loyalty, ambition, or missing information. It treats the other person’s free choice as an obstacle to get around.

Leadership does the opposite. It lets people see what they’re joining, what’s expected, what they might gain, what they might lose, and why the work matters. It respects their right to make an informed call.

Both get action. Only one builds trust that lasts.

An ethical leader doesn’t quit persuading — persuasion is the whole job. Customers have to be persuaded to try something unfamiliar. Investors have to be persuaded to risk money. Employees have to be persuaded to trade a safer path for an uncertain one.

The line is whether the persuasion respects the other person’s choice, and whether the why you promised matches the reality they live.

Manipulation is organizational debt. It can buy a season of hard effort, but eventually people find the gap between the promise and the truth. The best ones leave first, because they have the most options. The ones who stay get guarded, political, or checked out.

You can extract more than you give and still build something big. But you’ll have built a machine that runs on pressure. The moment the pressure drops, it starts to break.

The Skill Behind All the Other Skills

Getting people to do meaningful work pulls in a whole cluster of abilities: communication, recruiting, judgment, empathy, negotiation, teaching, storytelling, conflict resolution, org design, and self-control.

That’s what makes Hormozi’s line deeper than it first sounds. It isn’t a shortcut around the other skills. It’s the coordinating skill that forces all of them to grow up together.

You can’t attract excellent people without becoming someone worth joining. You can’t direct them without thinking clearly. You can’t keep them without earning trust. You can’t multiply them without learning to delegate. You can’t build leaders without giving up some control. And you can’t get good judgment from people while hiding the reasons behind your own.

The real test is what happens when the founder isn’t there.

If everything stops, you’ve collected helpers. You haven’t built a company.

If people keep making good calls, keep recruiting strong people, keep serving customers, keep moving the mission — then leadership got built into the company.

The founder’s greatest achievement was never proving how much he can personally get done.

It’s building a group of capable people who know where they’re going, believe the destination is worth it, know exactly which results they own, and have the authority to move.

The boss stands behind the chain and pushes.

The leader gives people a why, takes hold of the front, and pulls.

Frequently Asked Questions