The signal
The business does not only accumulate customers and revenue. It accumulates routines. Reports, meetings, approvals, customer updates, manual checks, promotions, discount reviews, dashboard reviews, and internal rituals all arrive with a reason attached. A client missed an update. A discount got approved too loosely. A fulfillment issue slipped through. A founder wanted visibility before the next payroll run.
That reason may have been valid. The problem is that recurring work rarely gets a renewal date. The team keeps paying the time cost because continuing feels safer than stopping, even when the original risk has already moved somewhere else.
Why this matters now
Growth creates work twice. First it creates the obvious work: more customers, more tickets, more orders, more hires, more handoffs. Then it creates the quiet layer underneath: more check ins, more trackers, more approvals, more status updates, more review loops. Nobody calls that a new headcount plan. It just becomes the way the company operates.
Service businesses feel this fast. A weekly status meeting that used to save client relationships can become a room full of people reciting updates that already live in the project system. Manual client updates can protect retention when the account is fragile, then become expensive theater once the account has a stable cadence and clean reporting.
SaaS companies build the same drag in different clothes. A legacy report that once exposed churn risk keeps getting sent after the product team has moved to better instrumentation. An approval step added after one bad enterprise concession stays in place for every contract, including the obvious renewals. The work survives because it sounds responsible.
D2C operators carry their own version. A recurring promotion that once moved dead inventory becomes a margin habit. A fulfillment check that once caught carrier issues keeps running after the warehouse process has changed. Nobody wants to be the person who removes the control and then owns the first miss.
The mistake to avoid
The mistake is treating every recurring activity as proof of discipline. Some routines are controls. Some are customer protection. Some are decision support. Keep those. The waste sits in the routines that no longer change a decision, reduce a risk, protect revenue, or improve the customer experience.
Operators usually ask the wrong question: "Do we still do this?" That question invites habit to defend itself. The better test is sharper: "What value does this work still create, and who would notice if it disappeared?" If the answer is vague, the routine is no longer operating work. It is residue.
A useful renewal test has teeth. The report must name the decision it changes. The meeting must name the handoff or risk it resolves. The approval must name the downside it prevents. The promotion must name the economic job it does now, not the job it did six months ago.
This is not a campaign against process. A good company needs controls. The point is to stop confusing inherited overhead with standards. Standards protect outcomes. Overhead protects feelings.
The first move
Start with five recurring activities that consume time every week or month. Choose the visible ones first: a standing meeting, a manual report, a client update, an approval step, a promotion, or a review ritual. For each, write one sentence that names the decision, customer outcome, revenue protection, or risk reduction it creates today. If nobody can write that sentence clearly, do not debate the philosophy of productivity. Change the routine.
The move this week
By Friday, put each activity into one of four buckets: stop, reduce, automate, or redesign. Stop the work that has no clear owner or value. Reduce the work that matters less often than its cadence suggests. Automate the work where judgment has already disappeared. Redesign the work that still matters but asks too much time from the wrong people.
Then set a review date for anything that survives. Recurring work should not get permanent status by default. If it wants space on the calendar, in the dashboard, or inside the team's attention, it should be able to re earn its place.