# Fix menu: one fix per hot spot

Change one thing. Log the next fortnight. Check if the hot gap dropped.

## WAIT is biggest (drafted to checked)
The work is done and sitting there. This is the jam the Harvard paper found.
- Book two 20-minute check slots a day in the calendar. Same times every day. "When I get to it" is the jam.
- One named checker per job. Shared ownership means nobody checks.
- Cap the pile: if more than 5 drafts are waiting, stop making new ones until the pile is under 5.
- Check in batches of the same type. Five proposals in a row is faster than five different jobs.

## Lots sent back (high sent-back rate)
The check is doing the thinking that should happen before the job.
- Write 5 pass/fail lines before the job starts (use check-template.md).
- Give them to the AI with the brief and tell it to check its own draft against each line, with evidence, before it hands over.
- Keep the check in its own file the AI can read but doesn't edit. (Same idea as the Claude Code team's verification write-up: the work shouldn't be able to change the test that judges it.)
- Every time something gets sent back for a new reason, add a line. Delete lines that never fail after a month.

## SHIP is biggest (checked to sent)
The work is approved and still not out the door.
- Template the handoff: same format, same place, same send step every time.
- Write down the send steps once. If it's more than 5 steps, that's your next automation.
- Send at the moment of approval, not "later today".

## MAKE is biggest (asked to drafted)
Good news. That's the gap AI actually shrinks.
- Move the first draft to AI if it isn't already.
- Save the brief that works as a template so every request starts the same way.
- Then scan the next job.

## Don't
- Don't fix a jam with more drafts. More output makes the pile bigger.
- Don't report "we made 40 this month". Report how many finished and how long they waited.
