Being Busy Is Not an Asset Class
Take a team of eight people working forty hours each. On paper, the company owns 320 hours of weekly capacity. By Friday afternoon every calendar is full, messages have accumulated faster than anyone can answer them, meetings have run into other meetings, and several employees have eaten lunch while looking at spreadsheets.
Management concludes that the team is operating at full capacity.
Then somebody asks what actually moved.
Perhaps 110 hours produced customer work. Another 70 disappeared into meetings. Forty went to correcting errors from previous work. Thirty-five were spent preparing status updates, reports, and internal presentations about the work. Twenty-five went into administrative tasks. Another forty vanished into switching between projects, waiting for decisions, finding information, and returning to tasks after interruptions.
All 320 hours were occupied.
The company still received only 110 hours of direct productive output.
The arithmetic becomes uncomfortable quickly because organizations are very good at measuring whether people are occupied and much worse at measuring whether the occupation is economically useful.
Utilization is a seductive number
Managers naturally dislike unused capacity. An employee sitting with an empty calendar looks inefficient, especially when salaries continue to be paid. The obvious response is to fill the calendar.
This can produce remarkable utilization figures and terrible throughput.
Suppose a design team can realistically complete ten projects per month when each person has some spare capacity for revisions, unexpected problems, customer questions, and coordination. Management sees the unused time and schedules additional work until everyone is allocated at 100 percent.
Now every unexpected revision displaces something else. A client question interrupts planned work. One delayed approval blocks several tasks behind it. Employees begin juggling more projects simultaneously because nothing can move cleanly through the system.
The team may still appear exceptionally busy. It may even become busier than before.
Output can fall.
This is familiar in manufacturing and logistics, where a production line operating every machine at maximum local utilization can create inventory piles and bottlenecks elsewhere. Office work merely hides the queue inside inboxes, project boards, calendars, and human memory.
Spare capacity has a cost, but so does operating without any.
Activity creates convincing evidence of itself
Busy work has one financial advantage over valuable work: it is extremely easy to prove that it happened.
Meetings generate calendar entries. Emails generate sent-message counts. Reports produce files. Task systems fill with completed tickets. Presentations acquire slides. Hours can be recorded against projects.
The evidence is abundant.
A good commercial decision that takes twenty minutes may be worth more than three days of documentation. A salesperson may spend four hours researching accounts and produce nothing visible until one conversation creates a €100,000 contract. An engineer may prevent a serious failure by spending an afternoon thinking before changing anything. A manager who cancels an unnecessary project can create value by ensuring that several hundred hours of activity never occur.
This creates an awkward management problem. Motion is visible immediately. Value often appears later, indirectly, or as something that no longer needed to happen.
Companies therefore drift toward rewarding the measurable evidence of effort.
People notice.
If being visibly occupied is what the organization rewards, people become very good at being visibly occupied.
Meetings are expensive before anyone orders coffee
Consider a weekly one-hour meeting attended by twelve employees.
It is tempting to describe that meeting as one hour.
Financially, it consumes twelve labor hours before preparation, follow-up, travel between locations, or the time required to regain concentration afterward.
If the average fully loaded employment cost is €45 per hour, the meeting costs roughly €540 each week. Over 48 working weeks, that is €25,920.
This does not make the meeting wasteful. A meeting that prevents one large error, coordinates an important launch, or produces decisions worth considerably more than €25,920 may be excellent value.
But the correct unit is twelve hours, not one.
The same multiplication applies to internal reporting, recurring calls, approval chains, training sessions, and status rituals. Small demands imposed on many people become material expenses surprisingly quickly.
A twenty-minute weekly status call for thirty employees consumes ten labor hours every week. If nobody can explain what decision improves because those ten hours were spent, the company has built a recurring subscription to its own bureaucracy.
Rework is particularly good at looking productive
A team discovers an error, investigates it, schedules a meeting, corrects the work, retests it, updates the documentation, informs the customer, and adds three new controls intended to prevent recurrence.
Get Andreas Jäger’s stories in your inbox
Join Medium for free to get updates from this writer.
The week is extremely busy.
Perhaps most of that work is necessary once the error exists. It still represents capacity spent restoring the company to the position it expected to occupy already.
This distinction matters because organizations sometimes congratulate themselves for heroic recovery while giving less attention to the process that created the emergency.
The same is true of rushed approvals, unclear requirements, duplicated data entry, badly designed handoffs, missing documentation, unstable systems, and decisions that repeatedly travel upward because nobody knows who is authorized to make them.
Each defect creates work.
More work raises utilization.
High utilization can therefore coexist quite comfortably with low operational quality.
A company should be suspicious when its busiest employees spend much of their time repairing yesterday.
The queue is part of the cost
Busy systems also create waiting.
An employee needs a decision from a manager whose calendar is full for four days. A contract waits for legal review. Design waits for product. Product waits for engineering. Engineering waits for a specification. The client waits for everyone.
Each individual may be working constantly, yet the work itself spends most of its life stationary.
This is why throughput is often more revealing than activity. How long does an order, request, proposal, product change, support issue, or decision take to travel from beginning to completion?
A process requiring six hours of actual labor may take three weeks because those six hours are distributed among five overloaded people.
The company records six productive hours.
The customer experiences three weeks.
Financial consequences appear in delayed revenue, slower response, increased work in progress, more coordination, more status requests, and a greater probability that priorities change before the original task is finished.
Busyness begins manufacturing additional busyness.
Look at the work portfolio, not the calendar density
The useful question is not whether employees have enough to do. It is whether scarce capacity is allocated to work with an adequate return.
A practical audit can start with four categories over a representative month: work that creates revenue or customer value, work that protects the business from meaningful risk, work required to operate the company, and work created by the company’s own friction.
The fourth category deserves attention.
Repeated corrections, duplicate reporting, unnecessary approvals, meetings without decisions, manual transfers between incompatible systems, searching for information, and status communication generated by excessive work in progress all belong there.
Some amount is inevitable. Zero-friction organizations exist mainly in consultant presentations.
But measure the proportion.
If a €2 million payroll supports a company in which 30 percent of working capacity is routinely consumed by avoidable internal friction, the problem deserves something stronger than another productivity workshop.
It represents roughly €600,000 of labor capacity before considering what that capacity could have produced elsewhere.
Sometimes the productive decision leaves a blank space
A manager cancels two recurring meetings. A team reduces simultaneous projects from seven to four. One approval layer disappears. Friday afternoon remains partly unscheduled so urgent customer work can be absorbed without destroying Monday.
The calendar now looks less impressive.
That may be progress.
The purpose of capacity is to produce useful outcomes, absorb uncertainty, and allow the organization to act when something valuable appears. Filling every available hour can maximize visible activity while eliminating exactly that flexibility.
Nobody lists “three empty hours on Thursday” as a corporate asset.
Sometimes it is one.
Before admiring a packed calendar, I would want to know what is moving through the business, how quickly it finishes, how much has to be done twice, and what all that activity produces after the salaries are paid.
Busy is a description of resource consumption.
The balance sheet requires more information.
