How to Develop Accounting Staff Without Relying on Shadowing

By Vincent Howard, CPA | Managing Partner, Howard, Howard and Hodges | SkillAbility for Accounting Firms

Last updated: 2026  |  12-minute read

Who I Am and Why You Should Listen

I’ve been in public accounting since 1990. I founded my own firm in 1993, merged it in 2001 to form Howard, Howard and Hodges, and grew it from three people to 50 staff across four locations and multiple states. Our firm was named PASBA Firm of the Year.

For years, if you’d asked me whether my firm developed its staff, I’d have said absolutely — we were busy, they were learning, everyone was growing. What we actually had was a collection of habits wearing the costume of a system. “Sit with Sarah.” “Ask your manager.” “Review last year’s file.” Every one of those felt like development in the moment; none of it was designed, measured, or repeatable. Since 2020 I’ve built a development platform that more than a thousand accounting professionals across dozens of PASBA member firms have moved through, and the difference between habit-based and system-based development shows up plainly in the data — in ramp-up times, error rates, retention, and how often managers get interrupted. This article is the practical playbook for making that switch.

Why Accounting Staff Development Is Usually Too Vague

Ask a managing partner if they want stronger staff and you’ll get an immediate yes. Ask them what “stronger” specifically means — which capabilities, verified how, by when — and the answer usually dissolves into generalities. That vagueness isn’t a personal failing; it’s the industry norm. Research across organizations found that 36% rely on managerial observation and general awareness, rather than data, to track skills — and 78% admit their skills mapping is outdated or nonexistent.

You can’t develop toward a target you haven’t defined. “Get better at the work” isn’t a development goal; “independently complete a full monthly close, documented to firm standard, within benchmark time, by day 60” is. The first step of real development is boring but decisive: define what capable looks like, per role, in writing — the tasks, the quality standard, the speed, and the judgment expected at each level.

And here’s why the stakes just went up: with accountant unemployment at 1.0% and experienced talent scarce, 45% of hiring managers say they now prioritize high-potential candidates and invest in their development when the finished specialist isn’t available. Translation: whether you planned to or not, your firm is now in the development business. The market stopped selling finished accountants. You either build them — or you don’t have them.

Most firms don’t have a staff development system. They have a collection of habits — “sit with Sarah,” “ask your manager,” “fix it when review notes come back.” That’s not development. That’s survival, distributed across your most expensive people’s calendars.

1. Start With Role-Specific Capability, Not Generic Training

A bookkeeper, a tax preparer, a staff accountant, a senior, and a manager are not points on one generic curve — they’re different roles requiring different capabilities, and each needs its own development path:

Generic training treats all of these as “staff.” Role-based pathways treat them as what they are: distinct capability sets, each buildable on schedule. (For the manager transition specifically, see why your best staff keep getting promoted into failure.)

2. Stop Using Live Client Work as the Classroom

The deepest habit to break: letting a new or developing staffer’s first attempts at a skill happen on a paying client’s file. It feels efficient — they’re learning and producing! — but it’s the most expensive classroom in existence. Mistakes are made on real deliverables, corrections consume manager review capacity, errors that slip through reach clients, and the learner builds confidence slowly because every stumble has consequences attached.

Client work has a legitimate role in development: it’s the test, not the lesson. Someone should arrive at their first live engagement having already learned and practiced the skill — so the client file confirms readiness rather than hosting the learning curve. That’s the difference between a pilot’s first flight with passengers and their five-hundredth hour in the simulator. Accounting firms routinely put passengers on the training flight and call it development. (This is the core failure of shadowing — see structured training vs. shadowing.)

3. Build Structured Practice Before Real Production

If client work is the test, structured practice is the course. The components that make practice actually build capability:

• Sample files and realistic scenarios — full simulated client work (a complete year of books, a realistic return) where mistakes are expected, cheap, and instructive.
• The firm’s real software — QuickBooks Online, Accounting CS, UltraTax, Xero, configured your way. Capability built in a generic demo environment evaporates on contact with the real stack.
• Real workpapers and reviewable outputs — practice should produce the same artifacts production does, documented to firm standard, so the standard is learned from day one rather than retrofitted through review notes.
• Progressive complexity — basic processing before asset transactions, single entities before consolidated messes, execution before judgment.
• Gates, not calendars — progression unlocked by demonstrated competence (80% assessment thresholds on the work product itself), not by time served or videos watched.

This is the engineered version of “learning by doing” — all the developmental power of experience, none of the client-facing risk or manager drag. (It’s also the answer to the theory question we tackled in why the 70-20-10 rule is not enough — this article is the practical build-out of that argument.)

4. Measure More Than Completion

“Completed the module” tells you someone clicked through content. Development measurement tracks whether capability is actually forming:

1. Accuracy — is the work right, and are errors decreasing across attempts?
2. Time against benchmarks — is completion time trending toward the standard for their experience level? (Benchmarks from 1,000+ trainees: how long ramp-up should take.)
3. Documentation quality — can a reviewer follow the workpapers without rework?
4. Review notes — falling in number, and never repeating? A correction that doesn’t stick is the loudest signal in development.
5. Escalation judgment — do they know what they can handle versus what to raise?
6. Manager interruption load — the clearest independence signal there is: are their questions-per-day falling week over week?

Firms that track these know exactly who is developing, who is stuck, and who needs intervention — in week two, not month six. Firms that track completion know who watched the videos.

5. Add Coaching Where It Actually Matters

None of this eliminates the human layer — it relocates it to where humans are irreplaceable. When a structured system carries the basics (workflows, software, recurring tasks, first mistakes), your managers and seniors stop being the walking help desk and start doing the coaching only they can do: judgment on ambiguous situations, firm standards and their reasons, client nuance and history, and the “why” behind decisions.

That’s a better use of your scarcest capacity and a better experience for the learner — coaching lands differently when it’s refining a foundation instead of substituting for one. And it directly protects the review bandwidth that gates your firm’s growth. (The full argument: your managers are not too busy to train — your training system is broken.)

6. Connect Development to Advancement People Can See

Here’s the piece firms forget, and it costs them their best people: development that leads nowhere visible doesn’t retain anyone. The academic research on public accounting is direct — career growth opportunities are directly linked to employee turnover intentions in public accounting firms; people stay where they can see themselves progressing. And the broader workforce data agrees: continuous learning has become a primary retention strategy, but without clear pathways, training becomes overwhelming rather than empowering.

So make the pathway explicit: execution capability leads to review readiness, review readiness to advisory skill and client confidence, advisory skill to leadership and — for the right people — ownership. Show every staffer where they are on that map and what unlocks the next stage. The same organizational research finds the failure mode everywhere: 70% of organizations struggle with retention and skill obsolescence at the same time — two faces of the same failure. Firms that build the pathway solve both at once: capability rises and people stay to keep climbing it. (The advisory rung of that ladder: developing advisory skills in accountants.)

Development without a visible destination is just homework. Development with a pathway is a reason to stay.

Frequently Asked Questions

How do you develop accounting staff?

Through a structured system rather than shadowing and habit: define role-specific capability targets in writing (a bookkeeper, tax preparer, senior, and future manager each need distinct pathways); build structured practice on sample files and realistic scenarios inside the firm’s actual software, gated by assessments at roughly 80% thresholds; reserve live client work as the test of readiness rather than the first place skills are attempted; measure development signals beyond completion — accuracy trends, time against benchmarks, documentation quality, review-note repetition, escalation judgment, and manager interruption load; relocate coaching to judgment, standards, and client nuance once a system carries the basics; and connect the whole progression to visible advancement, since career growth opportunity is directly linked to retention in public accounting firms.

Why is shadowing a poor way to develop accounting staff?

Because shadowing is exposure, not development. It produces inconsistent results (staff learn whichever senior they sat beside, including their shortcuts and bad habits), covers only whatever work happens to arise during the window, verifies nothing (no gate confirms a skill was actually learned), consumes the firm’s most expensive capacity through constant interruptions, and pushes first attempts onto live client files where mistakes are costly. It also fails at the judgment layer entirely: watching a senior work doesn’t reveal the reasoning inside their head. Structured development inverts each weakness — designed practice on sample files, one documented firm standard, gated verification, safe mistakes, and coaching reserved for the judgment that only humans transmit.

What should an accounting staff development plan include?

Six components: role-based pathways defining what capable means for each position (bookkeeper, tax preparer, staff accountant, senior, future manager) with explicit quality, speed, and judgment standards; structured practice on full sample files and realistic scenarios in the firm’s real software stack, producing genuine workpapers documented to firm standard; progressive complexity with assessment gates so advancement reflects demonstrated competence rather than time served; measurement of accuracy, benchmark time, documentation quality, review-note trends, escalation judgment, and manager interruption load; a coaching layer where managers develop judgment and standards on top of the system rather than re-explaining basics; and a visible advancement map connecting execution to advisory skill to leadership, so staff can see where development leads.

Should new accounting staff learn on live client work?

No — live client work should test readiness, not host first attempts. Using client files as the classroom means mistakes land on real deliverables, corrections drain manager review capacity, slipped errors reach clients, and learners build confidence slowly because every stumble carries consequences. The effective sequence is structured practice first — full simulated client work on sample files in the firm’s actual software, where errors are expected, cheap, and instructive — verified by gated assessments, and only then live assignments that confirm the capability transfers. The analogy is flight training: the simulator hosts the learning curve; the first flight with passengers confirms it. Firms that reverse this put clients on the training flight and pay for it in rework, review load, and risk.

How do you measure accounting staff development?

Track capability signals, not completion. The six that matter: accuracy (is the work right, with errors decreasing across attempts?); completion time against role-specific benchmarks (trending toward standard?); documentation quality (can a reviewer follow workpapers without rework?); review notes (falling in number and never repeating — a repeated correction is the loudest warning in development); escalation judgment (knowing what to handle versus raise); and manager interruption load (questions-per-day falling week over week — the clearest independence proxy, and the one almost no firm tracks). Measured this way, development status is visible in week two rather than month six, letting the firm intervene early with targeted support or recognize a mis-hire while it’s still cheap to address.

Does staff development improve retention at accounting firms?

Yes, with direct evidence in public accounting: research in The British Accounting Review found career growth opportunities are linked to employee turnover intentions in public accounting firms — people stay where they can see progression. Broader 2026 workforce research reinforces it: continuous learning has become a primary retention strategy, 70% of organizations struggle with retention and skill obsolescence simultaneously (two faces of the same failure), and structured development addresses both at once. The mechanism matters, though: development retains when it’s connected to a visible advancement pathway — execution to advisory to leadership — with clear stages and unlocks. Training without a destination reads as homework; a mapped pathway with the staffer’s name on it is a reason to stay and climb.

The Bottom Line

The market has made the decision for you: with accountant unemployment at 1%, and nearly half of hiring managers now buying potential and building the rest, every firm is in the staff-development business. The only real choice left is how — a designed system, or the inherited collection of habits: sit with Sarah, ask your manager, fix it when the review notes come back.

The system isn’t mysterious. Define what capable means per role. Practice it on sample files in your real software before it ever touches a client. Gate advancement on demonstrated competence. Measure the signals that reveal independence forming — above all, the manager interruption load. Spend your coaching where humans are irreplaceable. And put a visible pathway under all of it, because development that leads somewhere is also the reason your best people stay. That’s how you develop accounting staff without shadowing — and without burning your managers as the fuel.

You are not losing to firms with better people. You are losing to firms with a development system — building the same raw talent you’re hoping figures it out.

Want a development system instead of a collection of habits?

Book Your Free 10-Minute Structural Alignment Review →

In ten minutes we’ll show you how SkillAbility develops accounting staff intentionally — role-based pathways, structured practice on sample files inside the software your firm already uses, gated assessments, independence metrics, and a visible route from execution to advisory judgment to leadership — so your people are built by design instead of by shadowing, repetition, and manager rescue.

To your firm’s capacity,

Vincent Howard, CPA
Managing Partner, Howard, Howard and Hodges
SkillAbility for Accounting Firms

© 2026 SkillAbility for Accounting Firms. 45-Day Out-of-Pocket Performance Guarantee applies to qualifying onboarding engagements. Contact us for full terms.