OE-1.5 Controlling & Performance

What this is and why it exists

Control closes the loop that planning opened. Measure, compare against the plan, correct.

If that sounds familiar, it should. It is the same feedback idea an electronics student already knows from control systems, applied to organisations instead of plants. The vocabulary differs; the structure does not.

There is one failure mode to watch for throughout, and it is why this unit matters. A control system that measures whatever is convenient to measure will drive the wrong behaviour.

The vocabulary

• Control — measuring, comparing against the plan, and correcting.
• Standard — what performance is compared against.
• Budgetary control — control instruments that run on money.
• Non-budgetary control — everything else: inspections, audits, reports, observation.
• Direct control — correcting an error after it has happened.
• Preventive control — designing so the error cannot occur.
• Productivity — output measured against the input used to produce it.
• Reporting — how results travel back up.

The mental model

The control process is a loop: set a standard, measure what happened, compare, correct. Everything else in this unit hangs off those four steps. The engineering intuition transfers directly, including the awkward parts. Delay in the loop makes correction overshoot, and a noisy measurement produces corrections that are noise.

The instruments split by whether they run on money. Budgets are the dominant form, and they are also the form whose distortions are the best documented. A budget spent by December because it will otherwise be cut in January is a control system producing a behaviour nobody wanted.

Which brings us to what makes control effective rather than merely present. Timeliness and cost matter as much as accuracy. Information that arrives after the decision was taken is not control, it is history. And a control that costs more than the loss it prevents is not control — it is overhead wearing control's clothing.

Productivity deserves care, because it is the number most likely to be misused in an argument. It is output against input, and both terms can be chosen to produce whatever conclusion is wanted. Take the number apart instead. What was counted as output, what as input, over what period. That is worth more than any definition of it.

The distinction that matters most in practice is direct against preventive control. Direct control catches the error; preventive control designs so it cannot occur. Preventive is cheaper over any long period, and it is harder to justify because its success is invisible. Nobody is thanked for the incident that did not happen, which is exactly why organisations under-invest in it.

And reporting is the part of control everyone actually experiences. Keep one sentence: a report nobody reads is a control that does not exist. It costs the time to produce and delivers nothing.

What you should now be able to explain or do

Describe the control loop and connect it to feedback as you already understand it. Choose between budgetary and non-budgetary techniques for a situation. State what makes a control effective, including cost and timeliness. Take a productivity figure apart into what was counted as output and as input. Distinguish direct from preventive control and say why the second is under-invested in. Say why an unread report is not a control.

Check yourself