"We need better visibility" is one of the most common things business owners say about their operations, and one of the least precise. It can mean a dashboard, a weekly report, a project board, a call with each manager on Monday morning, or simply a wish to stop being surprised. Because the phrase covers so much, businesses often buy or build something that answers a different question from the one they had.
This article sets out a working definition of operational visibility, separates it from the things it is often confused with, and gives a simple test for whether a business has it.
Operational visibility is the ability of the people responsible for work to see, without asking anyone, what state that work is in, who has it, how long it has been there and what needs attention now.
Where the idea comes from
Manufacturing worked this out long before software did. The Lean Enterprise Institute defines visual management as placing tools, parts, activities and indicators of performance in plain view so that the status of the system can be understood at a glance by everyone involved. Its definition of the andon, a signal board or light used on production lines, adds a second element: a tool that highlights the status of operations at a single glance and signals whenever an abnormality occurs.
Those two definitions contain most of what operational visibility means in an office, a workshop or a service business. Status is visible to everyone involved, not just to managers. And abnormality is signalled, rather than discovered by someone reading a report.
The five things visibility has to show
1. State
Every important piece of work has a recorded stage: received, quoted, approved, scheduled, in progress, waiting on the customer, complete. The stages are defined, so "in progress" means the same thing to everyone, and work cannot be in two stages at once. Without defined states, there is nothing to see, only activity.
2. Ownership
At every stage, one named person or team is responsible for moving the work on. Work that sits between teams with no owner is where visibility most often fails, because nobody's list includes it.
3. Age
The Kanban Guide treats work item age, the time since a piece of work started, as one of four essential flow measures, alongside work in progress, throughput and cycle time. Age is the measure most businesses lack. Knowing that there are 40 open jobs is information. Knowing that six of them have been open three times longer than normal is visibility.
4. Flow
Visibility includes the movement of work over time: how much is arriving, how much is finishing and how much is waiting. A team can look busy and productive while the queue in front of it grows every week. Flow measures show whether the business is keeping up, and where work waits rather than moves, a pattern described in when work sits waiting more than it moves.
5. Exceptions
Finally, visibility highlights what needs attention: the overdue job, the order missing a part, the client waiting on a reply. This is the andon principle. Most of the work most of the time needs nobody's attention. The value lies in surfacing the few items that do, early enough to act cheaply.
What operational visibility is not
| Often confused with | Why it is different |
|---|---|
| Reporting | Reports summarise what has already happened. Visibility shows what is happening now and what is at risk. |
| Dashboards | A dashboard is one possible display. Without defined states, owners and ages behind it, it shows totals that cannot be acted on. |
| Having data | A business can hold every transaction and still not see work in progress, because most systems record the end of work rather than its middle. |
| Surveillance | Visibility is about the state of work, not about watching individuals. Its purpose is to help people finish work, not to score them. |
| Asking around | If status requires a phone call or a message thread, the business has access to people, not visibility of work. |
The difference between holding data and being able to see the business is explored further in the difference between having data and having visibility. The limits of adding more screens are covered in why more dashboards do not automatically create better decisions.
Visibility looks different at each level
A common mistake is to design visibility only for the owner or management team. The Lean definition says "everyone involved" for good reason. Different people need different views of the same underlying information:
- The person doing the work needs to see their own queue, in order, with anything urgent or ageing highlighted.
- The team leader needs to see the whole team's work in progress, where it is stuck and who is overloaded.
- Management needs flow across the business: whether arrivals and completions are balanced, which stages are bottlenecks, and the small number of exceptions that need a decision.
All three views should come from the same record of work. When each level builds its own tracker, the business ends up with three versions of the truth and a meeting to reconcile them.
An illustrative example
Consider an illustrative Gqeberha engineering services business with about 35 staff, handling equipment repairs for industrial clients. Its owner asked for "better visibility" after two large clients complained about late repairs in the same month. The first suggestion was a monthly dashboard of jobs completed and revenue.
That dashboard would have shown nothing new. The business already knew how many jobs it finished. What it could not see was that repairs waiting on imported parts had no owner once the part was ordered, and that some had been waiting more than a month without anyone telling the client.
Instead, the business defined seven job stages, made "waiting on parts" a stage with an owner in procurement, and recorded the date each job entered its current stage. The workshop saw its own queue in order of age. The owner saw a short list of every job older than its normal turnaround. Within weeks, the Monday meeting stopped being a round of status updates and became a discussion of the six or seven jobs that needed a decision.
A test for operational visibility
For the three or four processes that matter most, try answering these questions without asking anyone:
- How many items are currently in progress, and in which stage is each one?
- Who owns each item at this moment?
- Which items are older than normal for their stage?
- Is more work arriving than finishing this week?
- What, right now, needs a decision or an intervention?
If all five can be answered from the business's own systems in a few minutes, the business has operational visibility for that process. If the answers require messages, meetings or someone assembling a spreadsheet, it has reporting at best. The usual reasons for the gap are set out in why management has poor visibility into the business.
Trade-offs
Visibility asks something of the people doing the work: they must update the state of work when it moves. That only happens reliably when updating the record is part of doing the work, not an extra step. A system that requires double entry to keep a board current will soon show a board that is out of date. Visibility also needs restraint. A view that highlights everything highlights nothing. The aim is a small number of clear signals that people trust and act on, so the business finds out about problems while they are still cheap to fix.
Sources and further reading
- Visual Management - Lean Enterprise Institute (last verified 10 October 2026)
- Andon - What Is It? - Lean Enterprise Institute (last verified 10 October 2026)
- The Kanban Guide - May 2025 (latest) - Kanban Guides (last verified 10 October 2026)
Related Mellorca reading
- Why Work Gets Lost Between Teams
- Where Operational Errors Really Come From
- How Much Manual Work Is Hiding Inside Your Business?