Monday’s report can arrive on time every week because a manager spends Sunday afternoon finishing it. The business may regard that as a reliable reporting process, especially if nobody asks when the work gets done. That can happen without anyone deciding to build an exhausting workplace. People see what needs to be done and do it, especially when colleagues or customers are depending on them. The extra effort resolves the immediate problem and can become routine before anyone reconsiders the workload. The report’s arrival gets recorded; the time that went into it may never appear in the next week’s plan.
The work is costing more than the plan says
Suppose a recurring task is scheduled for an hour because the person who usually does it can finish in about an hour. They know which information is usually wrong and when to check another source before proceeding. Some of that knowledge may never have been documented because they’ve been doing the task for years.
An hour may be a sound estimate for that employee. It doesn’t follow that someone else can complete the same work in the same time, even with adequate instructions. A newer employee needs longer while learning to make those judgments. If the company uses the experienced employee’s speed as the standard for everyone, its plan may underestimate what the team needs.
Other work can be missing from the estimate altogether. Someone notices a bad handoff and fixes it before it becomes a customer problem. That intervention takes time, but the task may still be recorded against its original allowance. When demand rises, the day gets longer because more of these repairs are needed. The company can appear properly staffed while employees supply the hours the plan left out.
Good people can hide weak systems for a long time
An experienced employee may catch a recurring mistake so reliably that nobody else knows how often it happens. Their manager trusts them with more difficult work, which is reasonable enough. But unless someone deals with the source of the mistake, they’re now responsible for the new work and for continuing to catch the old problem.
That can be difficult to see in a list of responsibilities. The job description records the work they’ve been assigned, while colleagues continue asking for help because this is the person who knows what to do. Their availability becomes part of how other people plan their own work, even though the employee’s time has already been allocated elsewhere.
Exhaustion can grow from that pattern without one dramatic increase in workload. The business keeps asking reliable people to compensate in one more place. What began as helping out becomes part of what everyone assumes they can keep doing, and eventually declining a request means leaving a problem nobody else is prepared to handle.
Normal working hours are a useful test
Look at what would change if everyone worked the hours the business officially expects them to work. A weekly report that depends on Sunday afternoon would need time during the week, which means making room for it among the manager’s other responsibilities.
It doesn’t automatically follow that the business needs more employees. The manager may spend hours reconstructing information because two systems disagree. Resolving that problem could make the report fit into the week. Hiring someone to help prepare it could relieve the immediate pressure while leaving the unnecessary work in place.
The same examination matters when comparing teams. A team producing more than another may have found a better way to work, or its members may routinely give the company more hours. Before adopting its output as the new standard, we need to know how it was achieved. An occasional push gives us little basis for assuming people can sustain that pace every week.
Founders make the hidden capacity especially hard to see
Small businesses can run for years on work the owner never thinks to price properly. Doing the bookkeeping after dinner may feel like a normal part of owning the company. Early on, it may also be the most practical arrangement, when there isn’t enough money to pay someone else and the owner is willing to do it.
The economics can continue depending on that arrangement long after the business has become established. The owner’s evening remains available, so there’s little immediate pressure to change how the bookkeeping gets done. Profit can look healthy without showing what it would cost to complete that work during the day or pay someone to take it over.
Retirement makes that cost harder to ignore because the work has to belong to someone else. But an owner shouldn’t have to reach retirement before finding out what their regular contribution amounts to. Counting it gives them a basis for deciding whether they want to keep providing it and what the company would need if they stopped.
Automation comes after understanding the work
When someone spends hours each week reconciling two reports, it’s reasonable to ask whether the task can be automated. Before removing it, though, I want to know why the reconciliation exists. The reports may simply need to be combined, in which case software can eliminate work nobody benefits from doing manually.
They may also disagree because two parts of the company mean different things by the same number. The person reconciling them may understand which definition applies to the decision being made. That needs to be established before anyone builds an automated version, or the resulting report could present a number without the qualification that made it useful.
AI makes more of this work possible to automate, including tasks where it isn’t obvious how much judgment the employee contributes. Someone reading routine material may also be checking whether its source can be trusted. The time spent reading tells us little about what would be lost if that check disappeared.
At ShanVic, we examine what people are doing during that time before deciding what to automate. We may be able to remove most of the copying while preserving a review that still needs someone’s attention. That gives us a more realistic estimate of the time we can save and the responsibility that remains.
The next plan is based on the last rescue
A deadline rescued by extra work can make the original schedule look more realistic than it was. If a similar project is planned using the completion date alone, the next team may receive the same amount of time without anyone accounting for the evenings that made the first delivery possible. People may meet that deadline, too. Each project then appears to confirm the estimate, even as the people doing the work become less able to sustain it. By the time someone is clearly exhausted or decides to leave, the company may have used those results to make commitments well beyond the current project.
Better personal boundaries can make the gap visible without resolving it. When people stop supplying extra hours, unfinished work remains and somebody has to decide what to do about it. The business now has a more accurate view of its capacity, but it still needs to adjust the commitments it made using the old estimate.
Count the capacity honestly
A business doesn’t need to eliminate every difficult week. It does need to recognize when extra effort has become a regular requirement and include it in the assessment of what the work takes. Repeated evening work deserves attention even when the people doing it have become accustomed to it.
The business may discover that the work requires more time than it has provided. That needs to affect the next schedule, even if people met the last deadline by working through the weekend.