And the Planning Assumptions Firms Get Wrong.
By William Englehaupt
Walk through almost any accounting firm during busy season, and the signals are familiar: calendars packed wall-to-wall, inboxes filling faster than they can be cleared, and professionals praised for constantly stepping up to meet demands. In many firms, this visible intensity is taken as proof of productivity. If people are busy, the thinking goes, work must be getting done.
MORE Audit & Assurance
But “busy” is not a productivity metric. It is a symptom. And when firms mistake it for performance, they quietly undermine quality, predictability, and morale.
Accounting is not alone in this trap, but the profession is especially vulnerable to it. Long hours and constant responsiveness feel reassuring in high-risk environments. They create the appearance of control. What they rarely produce is a reliable flow.
Why firms default to “busy”
Firms manage busyness, not because leaders enjoy exhausting their teams.
Busyness is visible. Hours logged and meetings attended are easy to observe and easy to reward. Progress, judgment, and clean completion are harder to see. And constant motion can be mistaken for diligence. Leaders equate activity with safety.
Finally, many firms already have detailed plans. Modern audit platforms include project plans and milestones. The problem is not the absence of tools. It is that the assumptions underneath those plans are rarely examined.
As one military strategist observed, “No plan survives first contact with the enemy.” In professional services, that “enemy” is reality. Mike Tyson put it more bluntly: “Everyone has a plan until they get punched in the mouth.”
When leaders lack reliable signals about capacity and completion, they default to what they can see: effort.
The hidden costs of optimistic planning assumptions
Most firm plans assume ideal conditions: steady capacity, linear progress, and clean handoffs. Real work behaves very differently.
Hidden inside every engagement is a “hidden factory” of rework: clarification cycles, review notes, late-breaking scope changes, client delays, data quality issues, that surface only after work begins. None of this is clearly shown in the plan, but all of it consumes capacity.
When plans assume 100% utilization and ignore rework load, teams are mathematically set up to fail. The result is predictable: work slips, stress rises, and leaders respond by pushing harder — reinforcing busyness as the dominant signal.
The plan did not fail because people were inefficient. It failed because the capacity assumptions were unrealistic.
Where “done” breaks down
A second, compounding problem is how teams define completion.
In many teams, “done” means “I worked on it” or “I sent it for review.” From a planning perspective, that is not completion. It is work-in-process.
Until work is done-done — completed, reviewed, accepted, and requiring no further clarification — it continues to consume capacity. Plans that treat partially completed work as finished systematically understate workload and overstate progress.
Lack of clarity on what is done-done is why teams appear constantly busy even when plans show tasks as “complete.” The work is not done-done, and the system knows it.
Using sprint thinking to fix planning realism
One practical way firms can correct these assumptions is by borrowing a discipline from agile environments—not software rituals, but sprint thinking.
Sprint planning forces teams to answer hard questions upfront:
- Given the real capacity, what can we actually finish this period?
- What does “done-done” mean for each deliverable?
- How much rework and review capacity must be reserved?
- What work explicitly does not fit in this sprint?
By shortening planning horizons and committing only to work that can be done-done within that window, teams reduce work-in-process, surface constraints earlier, and create more reliable flow.
Importantly, sprint thinking makes capacity visible, with line-of-sight from one week to the next. It replaces optimistic planning with explicit trade-offs.
Replacing “busy” with better signals
When planning assumptions improve, the signals leaders should watch change naturally.
Instead of tracking hours and responsiveness, firms can observe whether sprint commitments are met, whether work exits review cleanly, whether rework load is shrinking, and whether teams are carrying less half-finished inventory forward from one phase to the next.
These signals are quieter than busyness, but far more predictive of quality and predictability.
Productivity is a design choice
Accounting firms do not need more tools or more effort. They need better planning assumptions.
Productivity is not created by filling every hour or assuming ideal conditions. It is made by designing systems that acknowledge real capacity, account for rework, and define completion unambiguously.
Busyness is not a strategy. Realistic planning — grounded in capacity and done-done outcomes — is.