I have made the same hiring mistake twice, so I feel qualified to warn people off it. Both times my team was drowning, both times the obvious fix looked like another pair of hands, and both times a chunk of the work I hired for turned out to be work no person should have been doing at all.

Key takeaways

  • Separate every task into decisions (need a human) and procedures (need doing by anyone competent).
  • Procedures hide inside roles that look like judgment roles, which is how teams over-hire.
  • Procedure work is invisible to promotion conversations, so leaving talented people on it quietly caps their careers.
  • Much of the procedures pile is recurring browser work, which is now delegable without a new hire.

The hiring mistake I made twice

The obvious fix for an overloaded team is capacity. But a lot of what looks like workload is procedure dressed up as judgment. Ask an analyst what they do and they describe recommendations. Watch the week and a third of it is assembling the data underneath the recommendations, which is transport, not analysis.

Decisions need a human, procedures need doing

Here is the line I wish I had drawn earlier. A decision needs judgment, taste, and accountability. A procedure needs to be done correctly and repeatedly, and it does not care who does it. Every team I have run leaks the most time on recurring browser procedures: pulling weekly numbers from several dashboards, checking a set of sources each morning, moving records between two systems that were never introduced.

Why procedure work quietly caps careers

This is the part managers miss. Advancement compounds on visible judgment, and procedure work is invisible to every promotion conversation. The person known for sharp calls moves up. The person who spent those same hours compiling the spreadsheet under the call does not, even if they worked harder. Leaving a talented person on transport is not just wasted hours. It is a quiet ceiling.

The procedures pile is now delegable

What changed my approach is that the procedures pile no longer requires a hire, because much of it is repetitive browser work and the tools have caught up. One of my leads moved her recurring routes, the metrics rounds, the source sweep, the record transfers, to the browser automation at allyhub.com. It runs the routines in her own browser session and lands them in one summary she reads in fifteen minutes. Setup was a couple of evenings and some corrections it kept, and after that the routine ran on its own and got quicker each time rather than needing to be re-taught. Her reclaimed hours went into client calls, the highest-value and most-postponed thing on her list.

Two rules for any delegation

Keep review in the loop, because delegation without review is abdication and the failure modes are just quieter with software. And reassign the freed time on purpose, because capacity freed without a destination refills with the same low-value work inside a month.

Run the one-week audit first

The diagnosis is cheap. Take one representative week, sort every block into decision or procedure, and look at the ratio. For most knowledge teams the procedure share lands between a quarter and a third. That number is your real staffing plan, and a surprising amount of it does not need a hire at all.