Agency Review Bottleneck Test

Find out in 2 minutes whether your agency needs another senior, or a written definition of done.

Nothing you enter leaves your browser.

Why most review queues are a definition problem

Most senior review time goes to checking rules, not making judgment calls.

Wrong template, wrong date range, missing disclaimer, broken link. Those have one right answer. When the answer is not written down, every reviewer carries their own version of it, so hiring more reviewers makes the work less consistent, not faster. This test shows you which problem you have. The full method is in my agency operations guide.

Run the test

Answer three short steps and you get a diagnosis, the numbers behind it, and next steps.

  1. 1. Team
  2. 2. Speed
  3. 3. Review log
Step 1: Your team
People who create deliverables. Example: 5

People who approve work before it goes out. Example: 2

Accounts you deliver for right now. Example: 30

How to run the 3-week review log

You run the log by writing down every change a reviewer asks for, then sorting each one into rule or judgment.

  1. Pick one deliverable your seniors always review.
  2. For 3 weeks, every reviewer writes down each change they request, as it happens (not a weekly summary).
  3. Sort each change into two piles: broke a rule, or needed judgment.
  4. Count the piles and enter them above.
  5. If the rule pile is large, write a definition of done before you hire anyone.

Real example: W3whiz

I ran this exact diagnosis on my own white-label team, and it took us from 30 to 37 accounts with the same 7 people.

I run W3whiz, a 7-person white-label SEO team: 2 seniors and 5 juniors. Two years ago we turned down 5 accounts because I could not say whether we had capacity. Production took 3 days. Delivery took 11. Every deliverable sat in a queue for 2 senior reviewers.

For 3 weeks our seniors logged every change they requested. About 70% were rule checks. Only 30% were real judgment. So we wrote a definition of done for each deliverable, enforced it with template checklists before work reached review, and kept an exception log.

 BeforeAfter
Accounts3037
Turnaround11 days3-4 days
Senior review time~30 hrs/week~20 hrs/week
Team7 peopleSame 7 people

Read the LinkedIn article

Methodology and assumptions

The tool divides your review changes into rule and judgment, compares the split to fixed thresholds, and flags queue and load problems.

Formulas

Thresholds

Assumptions

FAQ

These are the questions agency owners ask me most about the review bottleneck.

What counts as a "rule" change vs a "judgment" change?

A rule change has one right answer you could write down in advance: wrong template, wrong date range, missing disclaimer, broken link, naming error. A judgment change needs context or opinion: which priorities to lead with, whether it fits the client, strategy, risk. If two seniors could disagree on the fix, it is judgment. If they would not, it is a rule.

Why would hiring another reviewer make things worse?

Without a written definition of done, each reviewer applies their own version of the rules. The same work gets different feedback depending on who reads it, so you get more rework and more inconsistency, not more speed. The checking is still done by hand, just by more people.

How long should I log for?

We logged for three weeks. That covers a full reporting cycle and a few audits, and it is short enough that people keep doing it. One week can show a direction if your review volume is high. Fewer than about 30 logged changes is a thin sample, so treat the result with care.

Can AI fix this for me?

AI can draft and check mechanical rules, but only after the rules are written down. If there is no definition of done, AI drafts make your review queue longer, because you get more output to check against rules nobody wrote.

My agency is small. Does this still apply?

Yes. Even with one senior and two producers, the senior's time is the bottleneck, and a lot of it is usually rule checking. The thresholds come from a team of seven, so treat the numbers as a rough guide for very small teams. Writing a definition of done takes a few hours and helps at any size.

Do you store my data?

No. Everything runs in your browser and nothing you enter into the tool is sent or stored. The share link holds only numbers in the URL hash, which browsers do not send to servers.

Send me your two piles and I'll tell you straight

Not sure what your numbers mean? Book 30 minutes. Bring your rule count and your judgment count and I will tell you what I would do.

Book a 30-minute call

Embed this tool on your site

Copy the snippet below to put this test on your own page, with a link back here.

Please keep the attribution link visible.

Tool by Asif Dilshad