Slide 1 of 4
A week, because a day proves nothing
The first day is unrepresentative in both directions — everything is novel, and nothing has accumulated. Five days shows you the actual shape.
RevTech Launchpad
DoLesson 5 of 6Work the queue
Working your own queue for a week
Run the daily rhythm for five working days and come out with a calibrated queue and a written list of what needs fixing.
25 minBeginner
Part 1 of 3
What the exercise is actually for
The point of the practice week is not to get through your queue, you would do that anyway. It is to build the rhythm while you are still deliberate about it, and to gather evidence about what is arriving badly while you can still see it clearly.
Both halves have a shelf life. The rhythm is easy to establish in a week when you are paying attention to it and hard to establish later by resolution alone. And the clarity about what is wrong is highest in the first days, before familiarity turns a recurring annoyance into just how the queue is.
Part 2 of 3
How to run it
Work the queue at the two times you picked in the earlier lesson, and resist working it continuously in between. Continuous queue-working feels responsive and is the actual failure mode: it fragments the day, and it means every item is handled in whatever state of attention you happen to be in when it arrives.
Start each pass with overdue items (they carry the red rail for a reason) then work today. Aim to leave nothing overdue overnight, which is an achievable standard for most roles and a useful one because it keeps the backlog from becoming the thing you manage instead of the work.
Keep a running note as you go: one line for every item you rejected or edited, with the reason. It takes seconds per item and it is the entire deliverable of the week.
- Two passes a day at fixed times; do not graze the queue between them
- Overdue first, then today
- One line in the note per rejection or edit, with the reason
- Nothing overdue overnight
Part 3 of 3
Read the week on Friday
On the fifth day, read your note rather than your queue. What you are looking for is repetition: the same kind of item edited the same way four times is not four judgment calls; it is one defect showing up four times. Those repeats are your fix list, and they are worth more than any impression of how the week felt.
Judge the week on Friday and not before. Early days are noisier than settled ones, instructions are still rough, thresholds are untuned, and the system has not yet been corrected by the feedback you are in the middle of generating. Reading Tuesday as a verdict on the model is how teams talk themselves out of something that was two days from working.
Do this in the product
Run the week
- Confirm the two queue times are in your calendar as recurring blocks for the next five working days.
- Each morning: clear overdue items first, then work today's.
- Each evening: catch what arrived during the day, and leave nothing overdue overnight.
- For every rejection or edit, add one line to a running note with the reason.
- Do not work the queue between your two passes.
- On Friday, read the note and mark every issue that appeared more than twice.
- Send the repeats to whoever configures the agents — that list is the week's output.
Key questions
You should be able to answer each of these from memory before opening it. Recalling the answer is what makes it stick; recognizing it when you read it does not.
Why work the queue at two fixed times rather than continuously?
Continuous queue-working feels responsive and is the failure mode. It fragments the day and means each item is handled in whatever state of attention you happen to be in when it arrives.
What is the actual deliverable of the week?
The running note: one line per rejection or edit, with the reason. On Friday the repeats in that note are the fix list, and they are worth more than any impression of how the week felt.
Why judge the week on Friday rather than Tuesday?
Early days are noisier because instructions are rough and thresholds are untuned. Reading Tuesday as a verdict is how teams talk themselves out of something that was two days from working.
What to take away
- Run it for a week at a fixed time, not whenever you remember.
- Write the reason on every rejection, even when it feels obvious.
- Read the week on Friday. The pattern in your own rejections is the finding.
Teach this lesson
The argument in 4 slides, for presenting it to your team
Slide 2 of 4
Two passes a day, at the times you chose
- Start of day: clear overdue, then work today
- End of day: catch what arrived, leave nothing overdue overnight
- Do not work it continuously — that is the failure mode, not the goal
Slide 3 of 4
Keep a running note
One line per item you rejected or edited, with why. By Friday the repeats in that list are your fix list.
Slide 4 of 4
Judge on Friday, not on Tuesday
Week one is noisier than week four. Reading Tuesday as a verdict is the single most common way teams abandon something that was working.
Demo
Try the demo.
See agents carry the repeatable work of GTM across sales, marketing, customer success, and RevOps. Every action prepared, reviewed, and recorded. Fictional data, real product.
Explore the demo