The Bottleneck Board: Finding Where Jobs Actually Get Stuck
Most firms feel busy without knowing where work piles up. Here's how to read your job boards to find the real bottleneck — and fix it.
Every practice owner has had the sinking feeling: the team is flat out, everyone's working late, and yet jobs still aren't going out the door. Deadlines creep up, WIP balloons, and no one can quite say why. The instinct is to blame capacity — "we need another accountant" — but more often the problem isn't how much work you have. It's where that work gets stuck.
A bottleneck is the single stage in your workflow that limits how much finished work leaves the firm. Fix the bottleneck and throughput rises across the whole practice. Add resources anywhere else and you just build a bigger pile in front of the same jam. This article is about learning to see the jam.
Why busy doesn't mean productive
Accounting work moves through stages: information gathering, preparation, review, client sign-off, lodgment or delivery. Each stage has a different capacity. Prep might churn through ten jobs a week, but if review can only clear six, four jobs a week accumulate in front of the reviewer — usually a partner or senior — no matter how fast everyone upstream works.
The tell-tale signs are familiar:
- Work-in-progress keeps rising while completed jobs stay flat
- The same one or two people are always the reason something's late
- Jobs sit "nearly done" for days waiting on one action
- Junior staff finish early and ask for more while seniors drown
- Deadline weeks turn into all-nighters even though the work started on time
None of these are capacity problems in the way they feel. They're flow problems, and you can only fix what you can see.
Reading your board like a factory floor
If your jobs live on a board with columns for each stage, the board is already telling you where the bottleneck is. You just have to read it. The bottleneck is almost always the column where cards pile up on the left and thin out on the right. Work arrives faster than it leaves.
Look at three things:
1. Column counts over time
Take a snapshot of how many jobs sit in each column at the same time each week. A healthy workflow has roughly even counts, or counts that shrink toward completion. A bottleneck shows up as one column that's consistently fatter than its neighbours — and getting fatter.
2. How long jobs sit in each stage
Throughput isn't just about counts, it's about dwell time. A job might only spend an hour of actual work in the "review" stage but sit there for six days waiting for someone to pick it up. That waiting time is invisible on a timesheet but obvious on a board that timestamps when cards move. The stage with the longest gap between "arrived" and "work started" is your bottleneck.
3. Where things bounce backwards
Rework is a hidden bottleneck. If jobs regularly get kicked back from review to prep because of missing information or errors, your review stage isn't slow — it's doing two jobs' worth of work each time. The fix isn't more reviewers, it's better inputs upstream.
Common bottlenecks in accounting firms
In practice, the jam usually sits in one of a handful of predictable places.
Partner review. The most common one. Everything funnels to one or two senior people for final sign-off, and they're also doing advisory work, client calls and running the firm. Review becomes a part-time activity squeezed between everything else.
Waiting on the client. Jobs stall in a "waiting for information" limbo. This looks like a client problem, but it's often a chase problem — no one owns following up, so cards sit untouched for weeks.
The information-gathering stage. If prep can't start until source documents arrive, and requests go out ad hoc, the whole pipeline starves at the front. Everyone downstream is idle while the queue upstream is empty for the wrong reason.
Everything on one person. Sometimes a single staff member is the only one who knows a particular client, handles a particular software, or does a particular task. They become a bottleneck by default.
Fixing the bottleneck (not everything else)
Once you've found the constrained stage, the fixes are usually cheaper than hiring.
- Protect the bottleneck's time. If review is the constraint, block dedicated review time and stop interrupting it with other work. The bottleneck should never be idle and never be doing tasks something else could do.
- Move work off the constraint. Can a senior reviewer do a lighter first-pass review, with a manager clearing the routine ones? Can you introduce a checklist so only genuinely tricky jobs reach the partner?
- Improve the inputs. Reducing rework at review often means tightening the prep checklist. A job that arrives complete moves through review far faster than one that needs three clarifications.
- Don't overload it. Releasing work faster into a bottleneck doesn't help — it just grows the pile. Match the pace of work entering the constraint to the pace it can clear.
- Automate the waiting. If the jam is client information, automated reminders and a portal where clients upload documents remove the manual chase entirely.
Making the bottleneck visible in Finye
All of this depends on having your work in a place that shows flow, not just a list of tasks. In Finye, jobs live on boards with a column per workflow stage, so a growing pile in one column is immediately obvious. Because cards are timestamped as they move, you can see how long jobs actually dwell at each stage — not just where they are, but how long they've been stuck. Combined with WIP and time data, that turns a vague "we're flat out" into a specific, fixable answer: review is the constraint, and jobs are sitting there four days on average.
Recurring jobs and templates keep the upstream stages consistent so review gets clean inputs, and the client portal takes the "waiting on the client" stall off your team's plate. But the first step is simply looking at the board and asking the honest question: where does work actually pile up?
The habit worth building
Finding the bottleneck isn't a one-off exercise. The moment you fix one constraint, the bottleneck moves somewhere else — that's how flow works. A firm that reviews its boards weekly, watching for the fattest column and the longest dwell times, stays ahead of the jam instead of discovering it during deadline week.
Busy is not the goal. Finished work leaving the firm is. Learn to see where it gets stuck, and you'll spend far less on capacity you didn't actually need.