Ask a small agency, a freelancer, or any team that hands work to a client where their week really goes, and you’ll often get the same sheepish answer: revisions. The first draft of anything — a design, a page, a report, a proposal — is usually the easy part. It’s the second, third, and fourth pass that eats the calendar. A card that should have been a one-hour job quietly turns into a week of “just one more tweak,” and the strangest part is that almost none of it shows up on your board.
That’s the real problem. Most boards are great at tracking work the first time through and completely blind to rework. A card sits in “in progress,” goes out for feedback, comes back, goes out again — and the whole time it looks like a single task making no progress, when really it’s been around the loop four times. If you’ve ever wondered why a “nearly done” project refuses to actually finish, the revision loop is usually where it’s trapped. Here’s how to make that loop visible, and then how to tame it.
Why revision work hides on most boards
A standard board has columns like To Do, Doing, and Done. That layout assumes work moves in one direction. But feedback doesn’t work that way — it sends things backward. When a draft comes back with changes, you’ve got two bad options: drag the card all the way back to To Do (where it looks brand new and loses its history), or leave it parked in Doing while it waits on someone else.
Most people choose the second, and that’s how rework becomes invisible. The card looks like it’s being actively worked on, but it’s actually sitting idle, waiting for a client to reply or a reviewer to look. Multiply that across a handful of projects and you get a board that looks busy while very little is genuinely finishing. You can’t manage a problem you can’t see, so the first fix is simply to make the loop show up.
Give revisions a place to live
The single most useful change is to add a column for work that’s waiting on review — call it In Review or With Client. When a draft is done and needs eyes on it, it moves there instead of lingering in Doing. Now the card is honestly represented: it’s not being worked on, it’s waiting on someone else’s input.
Then, when feedback arrives, the card doesn’t vanish back to the start. It moves back one step into Doing with the notes attached, and everyone can see it’s gone around the loop. That little backward move is the whole point — it turns an invisible rework cycle into something you can actually count. After a week or two you’ll start to notice which kinds of work bounce the most, which is the first clue about where your process is leaking time.
If a lot of your work waits on an outside client, it helps to keep that review stage transparent to them too. A simple way to do that is to give clients read-only access to the board so they can see exactly which cards are sitting in With Client waiting on them — which, more often than you’d expect, is where the real delay lives.
Cap the rounds before you start
Visibility tells you the loop exists; a limit keeps it from spinning forever. The healthiest teams decide, up front, how many revision rounds a piece of work gets. Two is a sensible default for most client work: one round of substantive feedback, one round of polish, done.
This isn’t about being rigid or refusing to fix real problems. It’s about naming the budget so everyone treats it with care. When a client knows they have two rounds, their feedback gets sharper and more complete, because they’re not assuming an endless string of future chances to nitpick. And when your team knows the cap, they stop gold-plating the first draft — they ship something solid, get real reactions, and improve from there. If a project genuinely needs a third round, that becomes a deliberate conversation (and often a billing one), not a silent default that quietly doubles the work.
Collect feedback, don’t let it dribble
A huge amount of rework pain comes not from the number of changes but from how they arrive. Feedback that trickles in — a comment now, a text an hour later, a “oh, one more thing” the next morning — forces you around the loop again and again for changes that could have been a single pass. Each trickle is a context switch, and context switches are expensive.
The fix is to insist that feedback comes in batches. When a card is in review, all the notes for that round go onto the card together before it moves back for changes. A short checklist on the card helps here — the same idea as using card templates so you’re not rewriting the same checklist every time — so a reviewer runs through the whole thing in one sitting rather than reacting piecemeal. One round in, one batch of changes out. That discipline alone can cut your revision loops in half.
Decide which feedback actually matters
Not all feedback is equal, and treating every comment as a mandatory change is how two rounds balloon into five. When the notes come back, take a minute to sort them: what’s a genuine problem, what’s a reasonable improvement, and what’s simply a matter of taste? The must-fix items are non-negotiable. The nice-to-haves can be weighed against the time they cost. The pure preferences — especially ones that contradict an earlier instruction — deserve a polite question, not an automatic yes.
This is the same muscle you use when you prioritize a backlog: separate the essential from the optional so your effort lands where it counts. A revision round handled this way produces a focused batch of meaningful changes instead of a scattershot response to every stray thought — and focused changes are the ones that actually get a project approved.
Close the loop cleanly
The last step is making “approved” mean something definite. When a card clears its final review, it moves to Done and stays there — no reopening it next week for a forgotten tweak. If a genuinely new need appears after approval, it becomes a fresh card with its own small scope, not a reanimation of the old one. Keeping that line crisp is what finally lets finished work feel finished, for you and for the client.
The takeaway
Revision work isn’t a failure — it’s how good work gets good. The problem is only that most boards hide it, so it spins out of control without anyone noticing. Give feedback a place to live with a review column, cap the rounds so the loop can’t run forever, insist that notes arrive in batches, and sort the must-fixes from the nice-to-haves before you touch the work. Do that, and the ping-pong settles down into something predictable. A tidy kanban board won’t stop clients from having opinions — but it will make sure every one of those opinions moves your work toward done instead of in circles.