Table of Contents
Your manager walks past your desk for the fifth time today. She hovers. She checks. She corrects the font size on your presentation. She reminds you about the deadline you already circled in red on your calendar. This is managing. And according to Henri Fayol, the man who essentially invented modern management theory back in 1916, this might be exactly the wrong thing to focus on.
Here’s the strange part. Fayol never said stop managing. He identified five functions that every manager must perform: planning, organizing, commanding, coordinating, and controlling. Organizing was just one piece of the puzzle. But when you look at what most managers actually do with their time versus what Fayol meant by organizing, you start to see why the distinction matters more than you’d think.
The Architecture of Work
Think about the difference between a building inspector and an architect. The inspector walks around checking if walls are straight, if wires are properly insulated, if the stairs meet code. The architect designs the structure so the walls want to be straight, so the wiring system makes sense, so the stairs feel natural to climb.
Fayol’s concept of organizing is closer to architecture than inspection. According to his framework, organizing means establishing the structure of the enterprise. It means creating roles, defining relationships, allocating resources, and building the framework within which work happens. When you organize well, you design a system. When you merely manage, you spend your days fixing what a poor system produces.
The distinction sounds academic until you realize how much time most managers spend being building inspectors when they should be architects.
What Organizing Actually Means According to Henri Fayol
Fayol broke organizing down into specific elements. He talked about unity of command, which means each person reports to one boss, not five. He emphasized clear chains of communication so people know how information flows. He insisted on unity of direction so everyone understands where the organization is headed. He demanded that authority matches responsibility.
These aren’t abstract principles. They’re structural decisions that either get made intentionally or happen by accident. And when they happen by accident, you end up managing instead of leading.
Consider a restaurant kitchen during dinner service. A well organized kitchen has stations. The grill person handles the grill. The sauté cook handles sauté. Each person has their tools within reach, their ingredients prepped, their tasks clear. The head chef doesn’t stand over each cook correcting their technique mid service. The system works because it was organized to work.
A poorly organized kitchen is chaos. People collide. Tools go missing. The chef runs around putting out fires, literally and metaphorically. The chef manages constantly because the organizing never happened.
The Counterintuitive Truth About Control
Here’s where things get interesting. Most people think management equals control. You manage people, which means you control what they do. Fayol did list controlling as one of the five functions. But he meant something different than what modern managers often practice.
To Fayol, controlling meant monitoring whether work followed the plan and taking corrective action when it didn’t. It was a feedback mechanism, not a surveillance system. The difference is enormous.
When you organize properly, you need less controlling. The structure does the work. Roles are clear, so you don’t need to constantly tell people what to do. Communication channels are established, so information flows without you playing telephone operator. Resources are allocated logically, so you’re not always scrambling to fix shortages.
The paradox is that managers who want more control should spend more time organizing and less time trying to control. It’s like trying to control the temperature in your house by running around with a space heater instead of just installing insulation. One approach treats symptoms. The other addresses structure.
What We Lost When We Forgot to Organize
Somewhere between 1916 and now, organizing became the boring part of management. The tedious work of designing systems, clarifying roles, and establishing processes feels less important than the dramatic work of making decisions, solving crises, and commanding teams.
Business schools teach strategy and leadership. They teach decision making under pressure. They teach how to inspire teams and navigate office politics. The structural work of organizing gets compressed into a single class on organizational design that everyone forgets the moment they graduate.
So we end up with managers who are great at making decisions but terrible at building systems where good decisions happen naturally. We get leaders who can inspire but can’t create structures that sustain momentum when inspiration fades. We produce executives who can handle crises without noticing they could have organized to prevent most crises in the first place.
This connects to something interesting happening in other fields. Software engineers realized this decades ago. They figured out that well organized code needs less debugging. Well designed systems need less maintenance. You can either spend your time managing bugs or organizing code architecture. The best programmers do the second thing.
The same principle appears in urban planning. You can manage traffic with more police directing cars, or you can organize roads, signals, and public transit so traffic manages itself. One approach requires constant intervention. The other builds intervention into the structure.
The Five Subcategories Nobody Talks About
Fayol broke organizing into five subcategories that management books skip because they seem obvious. Obvious and practiced are different.
First, specialization. Let people use their actual skills. This seems simple until you make your best designer handle customer service because “everyone needs to understand the customer.”
Second, unity of command. One manager per person. This seems obvious until you’re in a matrix organization reporting to your functional boss, project boss, and regional boss simultaneously.
Third, clear communication chains. This seems straightforward until you’re in your seventh Slack channel trying to figure out which one is for actual decisions.
Fourth, unity of direction. Everyone knows the strategic objectives. This seems basic until half your team thinks the goal is growth while the other half thinks it’s profitability.
Fifth, authority matches responsibility. If you’re accountable for outcomes, you need authority over decisions. This seems logical until you’re responsible for a project with no authority over budget, timeline, or team.
These are all structural. When they’re missing, managers compensate for structural problems with constant personal intervention.
The Gardening Metaphor
Think about gardening. A novice gardener manages plants. They water when plants look dry. They move plants when they’re not thriving. They constantly intervene because they’re reacting to problems.
An experienced gardener organizes a garden. They consider sun patterns before planting. They group plants with similar water needs. They amend soil to match what they’re growing. They create a system where plants mostly take care of themselves, and intervention is minimal and strategic.
Both gardeners care about their plants. But one built a system that works. The other is perpetually managing chaos.
This is what Fayol understood about organizations. You can manage people all day long. Or you can organize work so people know what to do, have what they need, and understand how their piece fits into the whole. The second approach is harder to set up. But once it’s established, it requires less daily firefighting.
When Managing Makes Sense
To be fair, managing isn’t always wrong. Sometimes you need tight control. Sometimes you need constant oversight. Sometimes the work is so novel or so high stakes that you can’t just set up a system and walk away.
Fayol knew this. That’s why he included commanding and controlling alongside organizing. The five functions work together. You need all of them. But the ratio matters.
If you spend 80 percent of your time commanding and controlling and 5 percent organizing, you’ve built a house of cards. It only stands because you’re holding it up. The moment you step away, it collapses. Or worse, you become the bottleneck. Nothing moves without you. You’re indispensable, which sounds good until you realize it means you can never stop managing long enough to think about whether you organized things properly in the first place.
Organizing connects directly to planning, another of Fayol’s five functions. Planning is figuring out where you’re going. Organizing is building the vehicle to get there. You can’t organize without knowing the plan. And your plan won’t work if you can’t organize resources to execute it.
But here’s what’s interesting. Most organizations treat planning as the important work and organizing as the implementation detail. They spend months on strategic planning. They bring in consultants. They create frameworks and roadmaps and vision statements. Then they hand it off to middle managers and say “make it happen” without reorganizing anything to support the new direction.
It’s like planning a road trip from New York to Los Angeles but refusing to organize your route, supplies, or schedule. You know where you want to go. You just haven’t structured anything to get there. Then you’re surprised when you end up lost in Kansas with an empty gas tank.
What This Means for You
If you manage people, ask yourself: Are you managing or organizing? When problems arise, do you solve them personally or change the structure so they stop arising?
When someone doesn’t know what to do, do you tell them or clarify the role? When communication breaks down, do you relay messages or establish reliable channels? When work falls through cracks, do you catch it or reorganize responsibilities?
Every time you solve a problem personally instead of structurally, you’re managing. You’re creating dependency. You’re building a system that needs constant intervention. If that’s your default mode, you’re working too hard and accomplishing too little.
Fayol ran a mining company his entire career. He dealt with real people and real problems. What he discovered was that managers who succeeded weren’t the ones who managed hardest. They were the ones who organized best.
Modern management books condensed Fayol’s five functions into four: planning, organizing, leading, and controlling. They merged commanding and coordinating into leading. That sounds minor, but it shifted focus from structural design to personal influence.
Leading emphasizes inspiration and motivation. Those matter, but they’re not the same as organizing. You can be charismatic with terrible structure. The inspiration fades when people hit system failures. Companies hire inspiring leaders who fail because motivation can’t fix bad organization. It’s like running a marathon in concrete shoes.
Why This Still Matters
Fayol’s work was published in 1916. You might ask why anyone should care about century old management advice. The world has changed. We have technology he couldn’t imagine.
But the fundamental insight holds. Work happens through structure as much as effort. You can work harder or organize better. Most managers default to working harder. They manage more intensely, control more tightly, command more clearly. All of that burns energy without building capacity.
Organizing builds capacity. It creates systems that work when you’re not watching. It establishes structures that guide behavior without constant instruction.
This matters more now, not less. Remote work means you can’t manage by walking around. Global teams mean you can’t coordinate through hallway conversations. You need structure that works even when you’re not there to hold it together.
The Question to Ask
Here’s the test. Imagine you disappeared for a month. Not because something bad happened. You just took a long vacation without cell service. What falls apart? What keeps working?
If everything falls apart, you haven’t organized. You’ve been managing. You’re the system. Remove yourself and there’s no system left.
If most things keep working, you’ve organized well. The structure carries the work. People know what to do because roles are clear. Resources are accessible because allocation is logical. Communication happens because channels exist. Decisions get made because authority and responsibility align.
This doesn’t mean you’re not valuable. It means you’ve built something that doesn’t depend entirely on your personal intervention every minute of every day. You’ve created capacity beyond yourself. That’s not weakness. That’s the whole point of organizing.
Fayol understood something most modern managers miss. Management isn’t about making yourself indispensable. It’s about building organizations that work. The better you organize, the less you need to manage. And paradoxically, the less you need to manage, the more value you actually create.
So maybe the title of this article is wrong. You shouldn’t stop managing entirely. Fayol never suggested that. But you should probably stop managing so much and start organizing more. Because managing is what you do when organizing fails. And if you’re managing all the time, that tells you something about how well you’ve organized.
The question isn’t whether to manage or organize. The question is which one builds the foundation for everything else. Fayol gave us the answer over a hundred years ago.
Most managers just haven’t organized their thinking enough to notice.
