The Bottleneck You Can't Name: Reading Your Board Right
Your job board shows every work item, but not where the real delays live. Here's how to read a board so you can find and fix the true bottleneck in your practice.
Most practices that adopt account practice management software do the same thing first: they build a board. Every job becomes a card, every card gets a column, and for a week or two it feels like the fog has lifted. You can finally see the work.
Then reality sets in. The board is full, cards keep piling up on the left, and somehow turnaround times haven't improved. You know something is stuck, but you can't say exactly what. The board shows you everything and, in a way, that's the problem — it shows you so much that the actual constraint hides in plain sight.
Finding your real bottleneck isn't about adding more columns. It's about learning to read the board you already have.
A full column is not a bottleneck
The instinct is to look for the column with the most cards and declare that your problem. It rarely is. A stacked column often just means work arrives there in batches — the pile clears in a day once someone sits down to it.
The real bottleneck is the stage where cards sit the longest, not where they pile the highest. A column with three cards that have each been there eleven days is far more dangerous than a column with twenty cards cycling through in an afternoon.
This is why raw card counts mislead. What you actually want to measure is time-in-stage: how long a job lingers before it moves. In good accounting client management software, each card carries its own history — when it entered a status, who touched it, how long it waited. That timeline, not the visual pile, is where the truth lives.
The three shapes a bottleneck takes
Once you start watching time-in-stage, most delays fall into one of three shapes.
1. The waiting-on-client stall
Cards park in a "waiting for information" or "query sent" column and stop moving. The work isn't slow — it's blocked. Nobody in the practice is holding it, so nobody is accountable for it, and it quietly ages.
The fix isn't more chasing. It's making the wait visible and owned. Every blocked job needs a follow-up date and a person, so it resurfaces instead of vanishing. A client portal helps here too: when the client can see exactly what you're waiting on, a chunk of these stalls clear themselves without a single email.
2. The single-person choke point
This is the classic. Everything flows fine until it hits review — and review is one senior person's desk. Cards bank up behind them not because the work is hard, but because one human is the only door the work can pass through.
You'll spot it on the board as a column that fills only in front of a specific name. The temptation is to hire. Often the better move is to change the flow: push some review steps down, standardise the work so less review is needed, or split the reviewer's queue by job type so nothing waits behind unrelated work.
3. The invisible handoff
The sneakiest shape. A card technically moves — it changes column — but nobody actually picks it up on the other side. It's "in" preparation, but the preparer doesn't know it's landed. The delay isn't in the work at all; it's in the gap between one person finishing and the next person realising it's their turn.
These cost you days you never see, because on the board the card looks active. The only way to catch them is to notice that a job entered a stage and then nothing happened for four days. That's not slow work — that's a silent handoff.
Reading the board like a system, not a to-do list
A to-do list asks "what's left?" A workflow asks "where does work slow down?" Those are different questions, and they lead to different management.
Try these three reads on your own board this week:
- Age, not count. Sort each column by how long cards have been there, oldest first. The oldest card in each stage is your canary. Ask it one question: why hasn't this moved?
- Flow, not snapshot. Look at where cards came from and how fast they cleared last month. A stage that used to take a day and now takes four is telling you something changed — capacity, a departed staff member, a new client mix.
- Blocked, not busy. Separate jobs that are genuinely being worked from jobs that are merely open. A card can look alive for a fortnight while doing nothing at all.
Do this and the board stops being a wall of anxiety and starts being a diagnostic instrument.
Why one system makes the read possible
You can't read a bottleneck if the evidence is scattered. When the job status lives on a board, the client's query lives in an inbox, the WIP lives in a timesheet tool and the deadline lives in a spreadsheet, no single view tells you why a job is stuck. You end up reconstructing the story by hand, client by client — which is exactly the manual work good client accounting software is meant to remove.
This is where consolidating on one platform earns its keep. In Finye, the same job card that sits on your board also holds its status history, the client queries attached to it, the time logged against it, and the compliance deadline it's racing. When a BAS is sitting in review too long, you don't have to guess whether it's blocked on a client, banked behind a reviewer, or simply forgotten in a handoff — the card shows you. Two-way Xero sync and the client portal mean the client-side delays surface on the same card too, rather than hiding in someone's email.
That single, honest view is the point. Tax return software gets returns out the door; it doesn't tell you why the return sat idle for nine days first. Practice management is the layer above the work — and reading it well is how you find capacity you already have before you go looking for more staff.
Start with one stage
Don't try to optimise the whole board at once. Pick the single stage where your oldest cards live, name which of the three shapes it is, and fix just that. Give blocked jobs an owner and a date. Split the choke point. Make handoffs announce themselves.
Fix the true constraint and the whole board speeds up behind it. Fix a full-but-fast column and nothing changes at all. The difference between the two is learning to read what your board is actually telling you.