Industrial Engineering

Industrial Engineering is a way of thinking

By Lesego Modiakgotla · 8 October 2026 · 6 min read

Industrial Engineering is often described in technical terms: work study, process design, capacity planning, layout, quality and productivity. Those tools matter. But underneath them is something more useful and more widely applicable—a way of thinking about how outcomes are produced.

At its core, Industrial Engineering asks a simple question: how does the work actually happen, and how could the system be designed so that good results become easier and poor results become harder?

I trained as an Industrial Engineer, and in more than fifteen years since—through Lean Six Sigma, Business Excellence and leadership roles—that question has shaped how I approach almost every problem. This article sets out the core principles of Industrial Engineering thinking and how leaders can use them well beyond the factory floor.

What Industrial Engineering really is

Many people meet Industrial Engineering through its tools: time studies, process maps, line balancing, statistical process control. It is easy to conclude that the discipline is simply a toolkit for making factories more efficient.

The tools are the visible part. The more valuable part is the mindset behind them. An industrial engineer is trained to treat results as evidence, to assume that a process is producing exactly what it was designed to produce, and to look for the cause in the system before looking for blame in the people. That mindset applies equally to a hospital ward, a finance department, a sales pipeline or a household budget.

No engineer would redesign a production line using imaginary data. Yet leaders regularly redesign strategies, structures and processes on the basis of what they assume is happening rather than what is actually happening. Industrial Engineering thinking is, above all, a refusal to do that.

It also requires a certain kind of honesty. Before you can improve a process, you have to accept its current performance as it really is, not as the plan says it should be. Acceptance is not surrender. It is the starting point for every measurement, every improvement project and every credible target. A baseline that flatters the team is worse than no baseline at all, because it sends improvement effort in the wrong direction.

Observe the work before you judge it

Industrial engineers are trained to observe before concluding. They watch the process, time the steps, follow the material and the information, and talk to the people doing the work. This habit protects against one of the most common errors in management: making decisions about work that has not been seen.

Reports, dashboards and meeting summaries are useful, but they are already interpretations. Going to where the work happens shows you the waiting, the workarounds and the informal fixes that never appear in a report. It also shows respect. People can tell the difference between a leader who has seen their work and a leader who is guessing about it.

The same principle applies beyond the factory or the office. Before trying to fix a habit, a team or a business, it helps to observe what is really happening rather than what we assume is happening.

Understand the system and find the root cause

Every outcome is produced by a system of inputs, steps, constraints and decisions. When one part changes, others are affected. Industrial Engineering trains people to look at the whole flow—not only at the point where a problem becomes visible.

A delay at the end of a process often begins much earlier. A quality defect may originate in a design choice, a supplier specification or an unclear instruction. Seeing the system means following the problem back to where it starts. That is what root cause analysis is really for: not to produce a neat diagram, but to stop treating symptoms.

Useful questions at this stage are simple ones. Where does this problem first appear in the flow? What changed just before it started? Does it happen across different people, shifts or sites, or only in one place? What would have to be true for this result to make sense? The answers usually point away from individual effort and towards the conditions people are working in.

This is also why systems whisper before they fail. A machine running just outside its normal range, a process taking a few seconds longer than expected, a small rise in rework—experienced engineers treat these as early signals. The purpose of measurement is not simply to record performance. It is to detect weak signals while correction is still inexpensive.

Reduce waste in processes, meetings and decisions

Lean thinking identifies forms of waste that add effort without adding value: waiting, unnecessary movement, overproduction, excess inventory, over-processing, defects, unnecessary transport and unused human potential. Once you learn to see these, you notice them everywhere—in meetings, in approvals, in reports nobody reads, in daily routines.

Consider a typical approval process. A request waits in an inbox, is checked by one person, waits again, is checked by another, and returns for a correction that could have been prevented with a clearer form. Very little of the elapsed time is spent adding value. Most of it is waiting and rework. Nobody designed it to be wasteful. It drifted that way, one sensible-looking addition at a time.

Reducing waste is not about working harder. It is about removing the effort that should not be required in the first place. Often the most valuable improvement is not adding a new step, system or report, but taking one away.

Leaders are not exempt. A weekly meeting that restates information already available, a report produced for a committee that no longer reads it, or a decision escalated three levels because nobody is sure who owns it—these are all forms of waste. They consume the most expensive resource an organisation has: the attention of capable people.

Design conditions that make good outcomes easier

Perhaps the most powerful idea in Industrial Engineering is that behaviour is strongly shaped by design. If the right action is difficult and the wrong action is easy, people will drift towards the wrong action, regardless of good intentions. Good design reverses that: it makes the right action the natural one.

This is why system design is often more effective than exhortation. Clear standards, visual controls, error-proofing and well-designed handovers do more for performance than repeated reminders to be careful. When the same failure appears across different people and shifts, the repetition is evidence. The environment may be reproducing the outcome, and retraining individuals will not fix a system that keeps making the mistake easy.

No engineer would redesign a production line using imaginary data. Yet we often attempt to redesign our lives using imagined realities.

From Reality Always Wins, Chapter 5

Applying Industrial Engineering thinking to leadership

You do not need an engineering degree to use this way of thinking. These five habits translate directly into leadership and everyday decisions:

1. Look before you judge. Observe the situation directly before deciding what is wrong. Spend time where the work happens, not only where it is reported.
2. Follow the flow. Trace problems back to where they begin. Ask “why” until you reach a cause you can actually change.
3. Remove what does not add value. Simplify before adding anything new. Every extra step, approval or report should earn its place.
4. Design for the outcome you want. Change the conditions, not only the intentions. Make the right action the easy one.
5. Measure and adjust. Let results tell you whether the change worked. Processes drift, so improvement is never a single project that reaches permanent completion.

The same logic has shaped my life outside work. Recovering from Guillain–Barré Syndrome, and later learning to cycle seriously, taught me that the body and the road behave like any honest system: they respond to preparation, not enthusiasm. Observing honestly, adjusting patiently and designing better routines worked there just as it does in a business.

A disciplined respect for reality

Industrial Engineering is, in many ways, a disciplined respect for reality. It refuses to accept assumptions in place of observation, and it treats every result as information rather than as an accident. That is why it translates so naturally into leadership and life.

The system you design will produce the results it is designed to produce—whether you intended it or not.