Most performance issues in knowledge work are not productivity problems. They’re visibility problems.
I’ve seen this pattern repeatedly across projects, teams, and organizations. People are working hard, sometimes harder than ever, but the work itself isn’t visible in a way that supports delivery. When that happens, “productivity” becomes the label people use to describe the symptom.
But it’s rarely the real issue.
What’s missing is a shared view of the work as it moves through the organization.
Productivity Is Often the Wrong Diagnosis
In most knowledge work environments, activity isn’t the problem. Work is happening. Meetings take place. Decisions are being made. Tasks move forward across teams and tools.
The real question isn’t whether people are working. It’s whether everyone can see the work in the same way. That’s where things begin to break down.
Engineering sees one picture. Sales sees another. Finance has a third. Each team understands its own part of the work, but no one has a complete view of how everything fits together.
What looks like poor execution is often something else entirely: fragmented visibility.
This is usually the point where organizations conclude they have a productivity problem.
More often than not, they have a visibility problem.
How Visibility Slowly Disappears
Visibility rarely disappears overnight.
It erodes quietly as work spreads across tools, meetings, email threads, and departments.
Before long:
- Work is tracked in multiple places, but nowhere completely.
- Decisions are made in meetings but never reflected in the systems managing the work.
- Ownership is clear within individual teams, but becomes blurred as projects cross functions.
- People begin maintaining their own spreadsheets, notes, or trackers simply to understand what’s happening.
That’s usually when delivery starts feeling far more difficult than it should.
Researchers studying communication visibility have reached similar conclusions. When work becomes more visible, coordination improves, and knowledge flows more effectively. But visibility without structure creates noise instead of clarity. Simply making more information available doesn’t help unless teams share common processes, ownership, and definitions.¹
Visibility Before Productivity
I used to think productivity was the foundation of execution. I don’t anymore.
Productivity isn’t something organizations fix directly. It emerges when teams share the same understanding of the work.
That means:
- Clear ownership.
- Shared definitions of progress.
- Consistent ways of tracking work.
- A reliable view of what is happening across the project.
When those elements are in place, teams naturally become more effective, not because people are working harder, but because they’re working from the same reality.
Without that shared reality, even excellent teams can appear disorganized.
Designing Work That Can Be Seen
One lesson I’ve learned is that most teams don’t need another collaboration platform. They need fewer places for information to live.
When visibility is designed intentionally, small things begin to change.
- Meetings become shorter because less time is spent re-establishing context.
- Decisions happen faster because everyone starts with the same information.
- Status updates become factual instead of interpretive.
- Accountability shifts from asking people for updates to understanding how work is progressing through the system.
The system starts supporting the work instead of slowing it down.
You Can’t Scale What You Can’t See
Visibility isn’t a reporting function. It’s part of the operating system of execution. The goal isn’t more oversight or more tracking. It’s less fragmentation.
That often means simplifying where work lives, clarifying ownership, and ensuring information flows consistently across teams instead of stopping at organizational boundaries.
Accountability works best when people can see the work clearly, not when they’re constantly being asked to explain it.
When visibility is strong, alignment becomes something the system enables rather than something managers have to enforce.
Productivity Is the By-Product
I still care about productivity. I just think we’ve been looking for it in the wrong place.
In most knowledge work environments, performance problems are less about effort than they are about visibility. When work is fragmented, even high-performing teams can look misaligned. When work becomes visible, structured, and shared, execution becomes more predictable, and productivity tends to improve on its own.
The more organizations struggle with productivity, the more convinced I become that they should start by looking at visibility instead.
Teams don’t become productive because someone tells them to work harder. They become productive because everyone can see the same work, understand who owns it, and know what happens next.
That’s why I no longer think visibility is simply a reporting problem. I think it’s the operating system behind execution. And when that operating system works, productivity stops being the goal.
It becomes the by-product.
