Articles
The waiting-on-you list every operator should keep
Updated 5 min read By Operators team
The one list every operator should keep is a list of what is waiting on you: the approvals, signatures, reviews, decisions and replies that someone else cannot move forward without. It is not a to-do list. Each item on it is blocking another person right now. Across several companies, it is the list that tells you where you are the bottleneck.
The key points
- A waiting-on-you item has a person on the other end who is stuck.
- It is shorter than a to-do list, and more urgent per line.
- Across several companies, the requests are spread over many tools and logins, so they are easy to miss.
- It works best read at fixed times, cleared quick-items-first.
- Waiting on others is a separate list with a separate job.
Why this list, above all others
When you run one company, being a bottleneck is visible. People walk over and ask. When you run four, nobody can see your queue. The designer at one company does not know you have three board packs and a payroll approval in front of their review. They only know they are waiting.
Being slow on your own task costs you an hour later. Being slow on someone else’s request costs them a day now. That is why this list comes first.
What belongs on it
| Belongs | Example |
|---|---|
| Approvals | An expense, a bill, a hire, a price change |
| Signatures | A contract, an offer letter, a board consent |
| Reviews | A pull request, a draft, a design, a plan |
| Decisions | Which supplier, which candidate, which date |
| Replies | A direct question in chat or email that only you can answer |
| Agent requests | An AI agent asking you to approve what it drafted |
| Does not belong | Where it goes instead |
|---|---|
| Your own ideas and projects | A to-do list or a project board |
| Things you are waiting for from others | A waiting-on-others list |
| Reading for later | A reading list |
| Recurring deadlines | A calendar of fixed dates |
The test is simple: is someone stuck until I act? If yes, it is on the list. If no, it goes somewhere else.
Why it is hard to keep across companies
Requests come from everywhere. A review is in one company’s code tool. A signature is in another company’s e-signature account. A reply is owed in a third company’s chat. An expense approval sits in a fourth company’s finance tool. Each tool shows its own slice, behind its own login.
The usual fallback is keeping the list in your head, which works until the week it does not. Others do an inbox tour every hour, which works but costs them their focus, as the article on the cost of context switching explains.
There are three ways to keep the list honestly:
- By hand. A paper card or a note, rewritten every morning from each tool. Cheap and reliable for one or two companies, slow beyond that.
- In each tool. Use each tool’s own “assigned to me” or “needs my review” view, and visit them in a fixed order. Works if you have few tools.
- Gathered for you. A board that reads each tool and collects the requests into one list per company. That is what the Waiting on you section in Operators does, and the guide to it shows how.
Whichever you choose, the discipline is the same.
How to work the list
Read it at fixed times
Two or three times a day is enough for most operators. First thing, after lunch, and before you stop. Reading it constantly turns it back into an inbox.
Clear the quick ones first
Go top to bottom. Anything that takes under two minutes, do now. A quick approval at 8am unblocks someone for the whole day. Anything longer gets a time in your calendar today or tomorrow, so it stops being a vague worry.
Say no, or pass it on
Some items should never have been yours. A review someone added you to out of habit, a decision a manager can make. Hand it back with a short note. Each one you return makes the list shorter next week.
Decide in a fixed order when it is long
On heavy days, a fixed order prevents dithering. A good start is:
- Requests that block someone outside the company, such as a signature for a customer.
- Requests that block money, such as payroll or a supplier payment.
- Requests that block a team, such as a review.
- Everything else.
Keep it short
A waiting-on-you list that grows every week means you are holding too many decisions. Look at what sits there longest. Often it is:
- Small approvals that could have a limit, so people approve them without you.
- Reviews where someone else could review instead.
- Decisions that a clear rule would settle, so nobody needs to ask.
The article a founder’s guide to approvals covers which decisions should wait for you and which should not.
Waiting on others is a different list
It is tempting to put “waiting for the lawyer’s comments” on the same list. Resist it. Waiting on others needs a different action: a chase, on a date. Keep those as items with a chase date, and look at them during your weekly review.
A one-week experiment
For one week, keep a waiting-on-you list and nothing else in front of you. Write down every request where someone is waiting on you, from every company, and the time you cleared it. At the end of the week, look at the gaps. You will probably find a request or two that waited days for something that took a minute.
What to do next
Questions people ask
- What is the difference between a waiting-on-you list and a to-do list?
- A to-do list holds work you plan to do. A waiting-on-you list holds only things where someone else is blocked until you act. It is shorter, and each item has a cost to other people every day it waits.
- What should go on a waiting-on-you list?
- Approvals, signatures, reviews, decisions, replies and answers that someone has asked you for and cannot move without. Not your own ideas or projects, which belong on a to-do list.
- How often should I check it?
- At fixed times, two or three times a day, rather than all day. Check first thing, after lunch and before the end of the day.
- Should I keep a list of what others owe me too?
- Yes, but keep it separate. Waiting on you and waiting on others are different jobs with different actions, and mixing them makes both harder to read.
Related
- Guides How to see what is waiting on you across every company Use the Waiting on you section of Today to see every review, approval, signature and reply that only you can clear, across all your companies. 5 min read
- Articles A founder's guide to approvals, what should wait for you Which decisions should wait for a founder's approval and which should not, with a simple test, written limits and a way to hand the rest to your team. 5 min read
- Articles The real cost of context switching across several companies Why switching between companies costs more than switching between tasks, what research says about switch costs, and how to make fewer switches. 5 min read