Why POLC Training Often Fails — and What Organizations Can Do Instead

Your managers are missing deadlines. Supervisors spend too much time chasing people for updates. Employees wait for instructions instead of acting. Meetings keep returning to the same problems.

Someone says, “We need POLC training.”

It sounds reasonable. POLC has been taught to managers for generations, and the four functions cover much of what managers are expected to do. But before you ask a training provider for a course outline, there is another question worth asking:

What must move in the business?

That question can lead you to a very different kind of management development.

What is POLC?

POLC stands for Planning, Organizing, Leading, and Controlling. Planning is deciding what should be achieved and how to get there. Organizing means arranging people, responsibilities, resources, and work. Leading involves guiding, influencing, motivating, and helping people accomplish the work. Controlling means monitoring what is happening against what was expected, then making corrections when necessary.

The framework has deep roots in management thinking. In 1916, French industrialist Henri Fayol published Administration Industrielle et Générale, where he described five management functions: planning, organizing, commanding, coordinating, and controlling. Over time, management writers combined much of commanding and coordinating into what we now call leading. The familiar four-function POLC framework grew from that evolution. (AIU)

POLC remains useful because it gives managers a simple way to think about the breadth of management work. If you are new to management, it helps you see that your job is not merely to finish tasks yourself. You must think ahead, arrange the work, lead people, and make sure results stay on course.

The problem is not POLC.

The problem begins when POLC becomes the starting point for deciding what your managers need to learn.

The training request is a clue, not yet the diagnosis

Imagine Ana, an HR leader in a growing company. Several department heads tell her that their supervisors need stronger management skills. Projects are delayed, managers spend too much time following up, employees wait for instructions, and meetings generate discussion without enough movement.

Someone recommends POLC training. Ana sees the logic. If supervisors can plan more clearly, organize work properly, lead their people, and control results, perhaps these problems will disappear.

She starts looking at programs. One provider offers a two-day POLC seminar. Another divides the program into four modules. Another includes case studies, assessments, exercises, and certificates.

Before Ana chooses among them, however, she needs to understand something more important:

Why are the projects late?

The answer may have little to do with whether the supervisors understand POLC. Priorities may change so often that nobody knows what should stop. Supervisors may assign activities without clarifying the expected result. Work may move across departments without clear ownership. Employees may send difficult decisions upward because waiting for approval feels safer than making the wrong call.

Those situations can produce the same visible symptoms, but they are not the same problem. Each may require a different response.

This is why a request for leadership training, POLC training, or any other management program should be treated as useful information rather than a finished diagnosis. Someone has noticed that something is not working. The next job is to find out what is not moving, where the work gets stuck, and what keeps creating the current result.

POLC can describe management without diagnosing the business

Consider the word planning. When someone says, “Our managers need to improve their planning,” many different problems may be hiding inside that sentence.

Managers may fail to define the expected result before work begins. They may accept too many priorities. They may build plans without involving the people who must execute them. They may create sound plans that senior leaders repeatedly disrupt with urgent requests. Or perhaps the managers plan perfectly well, but nobody has the authority to say no when more work is added.

All of those can be described as planning problems. Calling them by the same name does not make them the same problem.

The same applies to organizing, leading, and controlling. A company may ask for leadership training when managers actually lack decision authority. It may ask for accountability training when ownership disappears during handoffs. It may ask supervisors to improve follow-through while its weekly meetings reveal problems only after deadlines have been missed.

A framework can help you look at management.

It should not stop you from looking at the work.

Topic-first training starts designing too early

Once POLC becomes the program, the four letters begin controlling the curriculum. Planning needs a module. Organizing needs a module. Leading needs its models and exercises. Controlling needs enough content to complete the framework.

Soon the organization has a complete course.

That completeness can be reassuring. Every major function seems covered, participants receive useful concepts and worksheets, and the trainer can demonstrate that all the promised topics were delivered.

But a complete curriculum can still miss the problem that caused the organization to invest in training.

A supervisor may learn several planning techniques when the real barrier is that senior managers keep introducing new priorities without removing anything. A manager may learn delegation principles while employees continue returning difficult decisions because authority remains unclear. Participants may understand accountability perfectly while work still moves through a system where nobody owns the handoff.

The course can be excellent. Participants can enjoy it. Evaluation scores can be high.

And the problem can survive.

That is why the larger idea behind Build Leaders Who Move Work starts somewhere else. Instead of first asking what leadership topics people need, begin by asking what important work leaders must help move. Your governing Strategic Learning reference makes the same distinction: the intervention follows the problem; the problem should not have to fit the program title.

Begin with the result that matters

Return to Ana’s organization. Suppose she investigates further and discovers that one business measure has become a serious concern. The company promises customers that installations will be finished within five working days, but the average has climbed to eight.

Now there is something concrete to investigate.

The question is no longer, “What should supervisors learn about POLC?” It becomes, “Why are installations taking eight days, and where can supervisors credibly influence that result?”

The team follows the work and notices a recurring problem during handoffs. Sales completes its part and passes the request to Operations. Operations discovers that important information is missing and returns it. Sales assumes Operations already owns the case. Operations believes Sales still owns the missing information.

While the departments sort out responsibility, the customer waits.

You could classify this as an organizing problem. That may be correct, but the label still does not tell a supervisor what to do when the next handoff occurs.

Looking at the work reveals something more useful: ownership must remain visible when work crosses from one team to another.

Now development has something specific to address.

Find the moment where the result gets lost

Business results are created through many small, recurring moments. A supervisor assigns an important job. Two departments hand work from one team to another. An employee encounters an exception and decides whether to act or escalate. A manager sees an early warning and decides whether to intervene. A meeting reaches its last ten minutes and the team either names an owner or leaves with another vague agreement.

These moments matter because they are where management becomes behavior.

If you want to Make Execution Daily, find the moments where an important result is being won or lost. Then examine what people currently do there.

This is also where managers can participate in diagnosing their own development. Ask them to bring actual situations: When does this happen in your team? What do you normally do? Why does that response make sense at the time? What usually happens next?

Now people are not discussing management in the abstract. They are examining the game they are actually playing at work.

Turn the problem into behavior people can see

Suppose the company discovers that installation delays often begin when ownership becomes vague during handoffs.

“Improve organizing skills” is still too broad. So is “strengthen accountability.” Both describe desirable outcomes, but neither tells a supervisor what to do differently.

The current behavior may look like this: a supervisor sends work to another department and assumes that ownership has transferred.

The required behavior can be much clearer: before the handoff is considered complete, the supervisor clarifies the result being transferred, names who owns the next move, confirms the information needed by the receiving team, and agrees on the next checkback point.

Someone can observe that behavior. Supervisors can rehearse it using real cases. Managers can coach it. Teams can improve the practice after trying it.

And the organization can determine whether anything changes.

This is the movement from a broad management concept to daily behavior.

Give managers something they can use when the situation returns

Understanding the desired behavior still may not be enough. Managers need a practical way to respond when the same situation appears next Tuesday.

For the handoff problem, the organization might build a simple template around four questions: What result are we moving? Who owns the next move? What information must travel with the work? When will we know the handoff succeeded?

The template matters because it enters the moment of work. It is not another handout to remember after training. A supervisor can use it during an actual handoff and see what happens.

That is the logic behind a Minimum Lovable Play: make the move small enough to try in real work, useful enough to repeat, and visible enough to improve.

If you are designing supervisory training, this is an important distinction. You do not need to cover every supervisory competency merely because supervisors might someday need it. Start with the recurring situations where supervisors are helping or slowing the work, then choose the few behaviors worth practising now.

Sometimes the learner is not the problem

Suppose the supervisors begin using the new handoff practice. For several weeks, fewer cases bounce between Sales and Operations. Ownership becomes clearer.

Then the old behavior slowly returns.

The easy explanation is that the training did not stick. Perhaps managers need a refresher course. Perhaps supervisors lack discipline.

But Ana looks deeper and finds another problem. Sales is measured on how quickly customer requests leave its queue. Operations is measured on processing only complete requests. Sales therefore has an incentive to move work out quickly, while Operations has an incentive to reject incomplete requests immediately.

The supervisors are trying to build one behavior inside a system that rewards another.

No training program can win that fight indefinitely.

People work inside performance measures, approval rules, meeting rhythms, workload, incentives, tools, permissions, and the behavior of their own managers. These conditions continuously tell people what the organization really values. A workshop may encourage one practice while the surrounding system makes the old behavior easier, safer, or more rewarding.

That is why organizations must also Build Learning Systems and Proof. When a useful behavior struggles to survive, do not ask only what is wrong with the learner. Ask what around the learner keeps making the old behavior sensible.

Your Strategic Learning content architecture makes this an explicit design principle: real-work practice has to be supported by managers, systems, and evidence rather than treated as something participants must somehow sustain after the workshop.

Measure the movement, not only the training

There is nothing wrong with measuring attendance, assessment scores, completion rates, and participant feedback. They tell you useful things about the learning experience.

But notice what they measure: the program.

They do not necessarily measure the reason the organization paid for the program.

If the original concern was that customer installations now take eight days instead of five, that business measure still matters. The organization should continue watching it.

At the same time, the final business metric may take time to change. Earlier evidence can tell you whether the new behavior is entering the work. Are fewer handoffs being returned? Are incomplete requests caught sooner? Can employees identify the owner of the next move? Are supervisors spending less time resolving the same ownership disputes?

Those signals do not replace the business result. They help explain whether the organization is moving toward it.

This changes the conversation after training. Instead of asking only, “Did people enjoy the workshop?” leaders can ask, “What did people try? What changed? What got in the way? What should we repeat, improve, or stop?”

Now learning produces information the organization can use for its next decision.

Does this mean POLC is no longer useful?

No. POLC remains a useful management framework.

For a newly promoted manager, it can provide a helpful map of the role. A management fundamentals course may legitimately teach POLC because understanding the framework is itself one of the learning objectives. It can also give managers a shared language when talking about their work.

POLC can remain useful after the business problem has been identified. A team struggling to make choices about priorities may benefit from stronger planning practices. A handoff problem may expose weaknesses in organizing. A manager struggling to move people toward an important change may need help with leading. A team that discovers problems too late may need stronger ways to monitor progress and make corrections.

The difference is that you now know why that part of POLC matters.

The mistake is not teaching POLC. The mistake is assuming that because the organization has a management problem, a complete POLC curriculum is automatically the answer.

What organizations can do instead

When someone requests POLC training, leadership training, supervisory training, communication training, or another familiar program, there is no need to dismiss the request. Use it to begin the diagnosis.

Find out what has been happening that caused people to ask for training. Identify the business, customer, team, or work result that needs movement. Then look for the recurring moments where the current result is being created. Observe what managers do in those moments, what makes their response reasonable, and what needs to happen differently.

Once the behavior becomes visible, give people a practical way to respond. Let them practise it using real work. Examine whether the systems around them support or fight the new behavior. Then follow enough evidence to decide whether the intervention deserves to continue, change, expand, or stop.

Training may still be part of the answer. Sometimes it will be a major part.

But the answer may also involve coaching, clearer authority, a redesigned huddle, a new handoff routine, changes in measures, a decision workshop, manager support, or several of these working together.

The intervention follows the work. The work does not have to fit the intervention.

From POLC training to leaders who move work

This shift changes what leadership development is trying to accomplish.

Instead of asking how many management topics can fit into a program, begin with what managers need to help move. A supervisor who clarifies the expected result before delegating is doing management. A manager who helps employees make sound decisions without unnecessary escalation is doing management. A department head who stops a lower-value initiative to protect an important strategic priority is doing management.

We can still use POLC to describe those actions. But the development process now moves in the opposite direction.

Do not begin with Planning, Organizing, Leading, and Controlling and hope people later find places to apply them. Begin with the result that matters. Find where it is being won or lost. Identify the management behavior that can influence it. Give managers something practical to use. Strengthen the system around the behavior. Then follow the proof.

Do not move from POLC to work. Move from the work to the management behavior that matters.

That is the difference between covering management topics and building leaders who can move important work.

Before you book another POLC program

If someone in your organization says, “Our managers need POLC training,” they may be right. Keep the request on the table.

But before comparing course outlines, ask:

What must move because we make this investment?

Spend enough time with that question to understand what is really happening. You may discover that managers genuinely need new knowledge. You may find that they already know what to do but lack a practical way to do it. You may uncover a management system that rewards the behavior the organization is trying to remove.

Once you understand the work, you can make a much more intelligent training decision.

And if POLC training remains part of the answer, you will know exactly what you expect it to help accomplish.