The 4 Functions of Management: Planning, Organizing, Leading, Controlling
Turn this article into takeaways for your work.
Each assistant summarizes the article only for you and suggests best practices for your work.
The four functions of management are planning, organizing, leading, and controlling, often shortened to POLC. Planning sets the goals and the route. Organizing arranges people and resources around that route. Leading motivates people to follow it. Controlling measures results and corrects course. Together they describe what managers actually do all day.
Most management textbooks open with this list, and for good reason. It gives a vague job title a clear shape. If you've ever wondered whether a bad quarter came from a weak plan, a muddled structure, a disengaged team, or no one checking the numbers, POLC gives you four places to look.
Where the four functions came from
The model isn't a single invention. It's a simplification of older work, and knowing the lineage helps you avoid overstating it.
The root is Henri Fayol, a French mining executive. His monograph Administration Industrielle et Générale first appeared in 1916, and it described the managerial process as five elements: forecasting and planning, organizing, commanding, coordinating, and controlling. An English translation reached Britain in 1929, and a later translation by Constance Storrs, titled General and Industrial Management, appeared in 1949. If you want his wider ideas on authority and unity of command, our page on Fayol's administrative management covers them.
The four-function version is what later textbook authors made of that list. Fayol's "commanding" tends to show up as "leading" in modern books, and coordination gets folded into organizing. For instance, OpenStax's free textbook Introduction to Business lists "coordinate work activities" under organizing. The same publisher's Principles of Management, released in 2019 under a Creative Commons license, takes what its preface calls a traditional approach built around leading, planning, organizing, and controlling.
So the honest summary is this: POLC is a textbook convention descended from Fayol, not a quote from him, and not a finding from a controlled study.
Key Facts
Key Facts
- Henri Fayol's Administration Industrielle et Générale first appeared in 1916 and listed five elements: planning, organizing, commanding, coordinating, controlling (EBSCO Research Starters).
- The modern POLC list is a later textbook simplification. OpenStax's Principles of Management (2019) is organized around leading, planning, organizing, and controlling.
- OpenStax says the four functions are highly interdependent, and managers often perform several at once.
- Luther Gulick's POSDCORB (Planning, Organizing, Staffing, Directing, Coordinating, Reporting, Budgeting) comes from his essay "Notes on the Theory of Organization," written in 1937 during his time on the Brownlow Committee.
- Controlling is a loop, not a final step: reviewing results feeds back into the next round of planning.
The four functions, one by one
Planning: decide where you're going
Planning means setting objectives and working out how to reach them. OpenStax breaks it into setting objectives and stating the mission, examining alternatives, determining the resources needed, and creating strategies to reach the objectives.
In practice, a plan answers four plain questions. What outcome do we want? By when? What will it take? And what would make us change course?
Common failure: plans written as wishes. "Grow the pipeline" isn't a plan. "Add 40 qualified opportunities by the end of Q2 by running two outbound sequences and one webinar" is.
Organizing: put people and resources behind the plan
Organizing turns a plan into a working structure. OpenStax lists designing jobs and specifying tasks, creating the organizational structure, staffing positions, coordinating work activities, setting policies and procedures, and allocating resources.
This is where most "who owns this?" confusion gets resolved or created. A clear ownership map is the output of good organizing, and a tool like a RACI matrix is one way to record it.
Common failure: reorganizing to fix a planning problem. Moving boxes on an org chart won't help if nobody knows what the goal is.
Leading: get people moving and keep them moving
Leading is the human function. OpenStax describes it as leading and motivating employees toward goals, communicating with staff, resolving conflicts, and managing change.
Here management and leadership overlap, and people argue about where one ends. We unpack that debate in leadership vs. management. For this model, treat leading as one of four managerial duties, not the whole of leadership.
Common failure: assuming a good plan and a good structure will motivate people on their own. They won't. Someone has to explain why the work matters and clear the obstacles.
Controlling: check results and correct
Controlling closes the loop. OpenStax describes it as measuring performance, comparing it to standards, and taking corrective action to improve it. It adds that reviewing results feeds the next round of planning, so the cycle starts over.
Common failure: treating control as policing. Good control is mostly about early signals. A weekly look at three leading indicators beats a quarterly autopsy.
How the functions fit together
POLC is often drawn as a circle or a staircase, which suggests a tidy sequence. Real work is messier. According to OpenStax, the functions are highly interdependent, and managers frequently do several at once. A manager adjusting a plan mid-month, reassigning a task, and encouraging a discouraged analyst is doing planning, organizing, and leading in the same hour.
A useful mental model: planning and controlling are the two ends of a feedback loop, and organizing and leading are how the work gets done between them.
POLC compared with Fayol, POSDCORB and other models
Several frameworks describe the manager's job. They answer slightly different questions.
| Framework | Originator and date | Elements | Best used for |
|---|---|---|---|
| POLC | Textbook simplification of Fayol | Planning, organizing, leading, controlling | Teaching the basics; diagnosing which part of management is weak |
| Fayol's five elements | Henri Fayol, 1916 | Planning, organizing, commanding, coordinating, controlling | Understanding the historical root; thinking about authority and coordination |
| POSDCORB | Luther Gulick, 1937 | Planning, Organizing, Staffing, Directing, Coordinating, Reporting, Budgeting | Public-sector and executive administration where staffing and budgets are explicit duties |
| Scientific management | Frederick Taylor | Scientific study of tasks and standard methods | Optimizing repeatable task work |
| High Output Management | Andy Grove | Output-focused management with indicators | Judging a manager by the output of the team |
POSDCORB deserves a closer look. The acronym lists seven functions: Planning, Organizing, Staffing, Directing, Coordinating, Reporting, and Budgeting, as one account of his work puts it. Compare it with POLC and you'll see POSDCORB is more granular. It pulls staffing, reporting, and budgeting out as separate items. POLC has no separate slot for them: staffing sits inside organizing, as OpenStax's list shows, and reporting and budgeting are usually treated as part of planning and controlling.
Neither is "right." POLC is easier to remember and teach. POSDCORB is easier to audit, because each letter maps to a concrete duty.
How to apply the four functions: a step-by-step routine
You can run POLC as a monthly or quarterly routine for a team. Here's one practical version.
Step 1: Write the goal and the finish line
State one to three objectives, each with a number and a date. If you can't tell whether you hit it, it isn't ready.
Step 2: List the work and the resources
Break each objective into workstreams. For each, note the people, budget, tools, and approvals you'll need. This is the planning half of the job.
Step 3: Assign owners and decision rights
Name one owner per workstream. Decide who approves, who contributes, and who needs to be informed. Remove any task that has no owner.
Step 4: Set the leading rhythm
Decide how you'll keep people energized and unblocked. That might be a weekly check-in, a monthly one-on-one for each direct report, and a standing slot where people can raise obstacles.
Step 5: Choose the control signals
Pick two or three measures that tell you early whether the plan is working. Set a threshold that triggers action, such as "if weekly qualified leads fall below 8 for two weeks, we review the campaign."
Step 6: Review and feed forward
At the end of the cycle, compare results to the plan. Write down what to change, then use it to plan the next cycle. That's the loop OpenStax describes: results feeding back into planning.
Template: POLC planning sheet
Copy this table into a doc or spreadsheet and fill one row per objective.
| Objective | Planning: target and date | Organizing: owner and resources | Leading: how we'll support people | Controlling: signal, threshold, review date |
|---|---|---|---|---|
| Example: Reduce onboarding time for new customers | Cut from 21 days to 14 days by end of Q3 | Owner: onboarding lead; one analyst; 20 hours of engineering help | Weekly 20-minute blocker review; recognize fastest onboarding each month | Average days to go-live; review if above 17 days for two weeks; reviewed every Friday |
Tip: if a row has a blank in any column, the objective is incomplete. Most weak plans fail in the last two columns, which is where leading and controlling live.
Examples by business function
These scenarios are hypothetical and meant to show the pattern.
Sales. A sales manager sets a quarterly target (planning), splits territories and assigns a sales development rep to each account executive (organizing), runs coaching sessions on discovery calls (leading), and reviews pipeline coverage weekly against a threshold (controlling). When the forecast slips, she checks which function broke before blaming the reps.
Operations. An operations manager planning a warehouse peak season forecasts volumes, builds a temporary shift plan, briefs and motivates seasonal staff, and tracks pick accuracy and dock-to-stock time daily. A drop in accuracy triggers retraining instead of a general scolding.
HR. A people team rolling out a new performance review process defines the timeline and goals, assigns a review owner per department, communicates why the change matters and handles the manager pushback, and tracks completion rates weekly until every review is done.
Product. A product lead plans a release scope, organizes squads around features, keeps designers and engineers aligned during trade-off debates, and measures adoption and defect rates after launch. Those numbers feed the next roadmap.
Finance. A finance manager plans the budget calendar, assigns close tasks with deadlines, keeps the team steady through quarter-end pressure, and compares actual spend against budget each month to decide where to adjust.
Do's and don'ts
| Do | Don't |
|---|---|
| Write plans with numbers and dates | Write plans that read like slogans |
| Name one owner per workstream | Assume "the team" will own it |
| Spend real time on leading: one-on-ones, feedback, removing blockers | Treat leading as a personality trait you either have or don't |
| Choose a few early control signals | Track dozens of metrics nobody reads |
| Feed control results back into the next plan | Treat controlling as the end of the cycle |
| Use POLC to diagnose which function is weak | Use it to blame an individual |
| Pair the model with others, like management skills | Treat POLC as a complete theory of management |
Limits of the model
POLC is a teaching framework, and it has real limits.
First, it describes functions, not skills or roles. It tells you what managers do, not what makes a good one, which is why it's often paired with a skills view such as management skills.
Second, the tidy order hides how interdependent the work is. As OpenStax notes, managers often perform several functions at once.
Third, the model says little about politics, culture, or ethics, and it can read as if management happens in a vacuum. Any list of functions leaves things out.
Finally, it was built around a manager with a team and formal authority. Many people now manage through influence, across functions, without direct reports. The functions still apply, but you'll have to adapt how you plan, organize, lead, and control when you can't assign work by decree. Our piece on extreme ownership is one lens on leading without hiding behind structure.
Putting it into practice
Take one team and one objective. Fill in one row of the planning sheet above and look at the blanks. Whichever column you struggle with is probably your weakest function right now, and that's the one to work on first.
The four functions are old, familiar, and a little dry. That's fine. A good checklist doesn't need to be exciting. It needs to catch the thing you were about to forget.

Senior Operations & Growth Strategist
On this page
- Where the four functions came from
- Key Facts
- The four functions, one by one
- Planning: decide where you're going
- Organizing: put people and resources behind the plan
- Leading: get people moving and keep them moving
- Controlling: check results and correct
- How the functions fit together
- POLC compared with Fayol, POSDCORB and other models
- How to apply the four functions: a step-by-step routine
- Step 1: Write the goal and the finish line
- Step 2: List the work and the resources
- Step 3: Assign owners and decision rights
- Step 4: Set the leading rhythm
- Step 5: Choose the control signals
- Step 6: Review and feed forward
- Template: POLC planning sheet
- Examples by business function
- Do's and don'ts
- Limits of the model
- Putting it into practice