Nobody Keeps a List of What They Are Waiting On
Every tool your team uses files a commitment under the person who owes it, which means the person waiting for it has no record at all. This looks at why a promise made to you disappears so quietly, why you end up absorbing the cost instead of asking, and what a work record has to hold for the waiting side of an agreement to survive.
The thing you asked for three weeks ago
Somewhere on a call a while back you asked someone for something. Not a big thing. A number you needed, an answer from their side, a file, a sign-off, an intro to somebody they know. They said yes, and they meant it, and one of you said a day out loud. Then the call ended and everybody went back to work.
It never arrived. You noticed roughly ten days later, in the middle of doing something else, and by then you had already worked around it. Maybe you rebuilt the number yourself from worse inputs. Maybe you shipped without the sign-off. Maybe whatever needed it quietly stopped mattering. What did not happen is the part worth looking at. Nothing anywhere recorded that a thing was promised and did not come.
Every tool you use is organised around the person who owes
Look at where a commitment goes to live after somebody makes one. It goes into a ticket with an assignee, or a task with an owner, or a line in someone's own notes, or their head. In all four cases it is filed under the person who has to do it. That is a sensible default, because they are the one who has to act, and a tool that did not organise work that way would be strange to use.
The consequence is easy to miss. The person who is waiting has no row. No field points at them, nothing lands in their list, and no view anywhere shows the set of things other people said they would send them. The one who cares most about whether it arrives is the one the system has nothing for. When the thing does not come, there is no place where its absence shows up, so it does not fail. It just stops being mentioned.
The promise lives in two heads and only one of them is looking
Assume everybody is competent and acting in good faith, because usually they are. The person who promised has thirty other things and a full calendar, and yours moved down the pile in the ordinary way things move down a pile. They have not decided to skip it. It is simply not in front of them, because the moment that would have put it in front of them was a sentence at the end of a call.
On your side it is different. You have exactly one reason to keep it loaded, which is that your own work depends on it. But all you have to hold it with is memory, and memory is not a good tool for holding somebody else's obligations across three weeks and a hundred other conversations. So the item sits in two heads, and the head that could act on it is not looking at it, and the head that is looking at it cannot act.
The cost of asking climbs while your grounds for asking fade
Follow-ups have a social price and it goes up sharply with time. On day two, asking is nothing. You send a line, they say it is coming Friday, everyone moves on. At three weeks the same message reads differently to both of you. It now carries an implied accusation, and it arrives with three weeks of silence behind it that you also failed to break, so it can feel like something you have to apologise for rather than a normal part of working together.
At the same time, the thing that would let you ask cleanly is disappearing. The specific version of the ask, the one that says you mentioned Tuesday on the pricing call and that the forecast has been sitting on it since, is by far the easiest to answer and the least personal, because it points at the work. But it requires remembering what was actually said and when. Three weeks on, you have the gist and not the sentence, so you soften it into something vague like checking in on that thing, which is the hardest possible message to act on. The strong ask is the one that expires first.
So you absorb it, and absorbing looks like competence
What people do instead is take the gap on themselves. You rebuild the missing input, you route around the person, you drop the piece of work that needed it, or you make the decision without the answer you asked for and hope you got it right. This is the reasonable move in the moment. Escalating over one forgotten thing costs more relationship than the thing is worth, and doing it yourself takes an afternoon.
From the outside it reads as initiative. Somebody wanted something, did not get it, handled it anyway, and never made a fuss. Nobody notices there was a hole, including the person who left it, who genuinely does not know the thing they forgot was load bearing. So the cost is real, it lands entirely on one person, and it produces no signal at all. It is the most expensive kind of failure a team can have, because it is invisible and it repeats.
Which leaves your team judging its follow-through on censored evidence
Add that up across a year and something odd happens to what a team knows about itself. The only broken commitments that get counted are the ones that blew up loudly enough to be undeniable, the missed customer date, the thing that stalled a launch. Every commitment that somebody quietly covered looks, in the record, like it was kept. So the team's sense of how often it delivers on what it says in meetings is built from a sample that excludes exactly the cases in question.
That is why the resolution to get better at follow-through keeps getting made and keeps not working. It is being made by people looking at a handful of dramatic examples, and it produces a rule about the dramatic cases, while the ordinary ones that make up almost all of the volume stay exactly as invisible as before. It also quietly distorts how reliable people seem, since a reputation ends up set by which of someone's misses happened to be visible rather than by how many there were.
This is not a character problem, and treating it as one backfires
The temptation once you see the pattern is to make it about who keeps their word. Start a list, note who slips, bring it up. It is the obvious move and it fails in a specific way. The thing you want from people on calls is fast, honest commitment, somebody saying they will get you the number by Thursday without a negotiation about it. If committing in a meeting starts carrying a chance of being cited later, people stop doing it. You get hedging, and yes I will look into it, and nothing you can hold at all.
The failure is not in the promise, which was sincere when it was made. It is in the distance between the moment it was said and the moment it was needed, and in the fact that nothing but two memories spans that distance. Fix the span and most of the behaviour fixes itself, because almost everybody delivers a thing they are actually reminded of at a moment when it still makes sense to do it.
What a record has to hold for the waiting side to work
Five things, captured when the agreement is made rather than reconstructed later. What was promised, in concrete terms and not as a topic. Who promised it. Who is waiting, which is the field every existing tool leaves out. The timing that was said out loud, in the words that were used, including a soft one like end of the week, because a soft date honestly recorded is far more useful than a hard one invented afterwards. And the part that does the most work, what the waiting person needed it for.
That last field is what changes the follow-up from a question about a person into a question about the work. There is a real difference between asking whether someone did the thing they said and saying that the forecast has been blocked since Tuesday and you need the number to finish it. The second is easier to send, easier to receive, and easier to act on, and it is only available if somebody wrote down the reason at the time. It is also the field that tells you when to stop waiting, because once you know what it was for you can see whether that thing still matters.
Why deciding to write it down yourself does not last
The obvious personal fix is to keep your own running list of what other people owe you. A few people do this and it works for them. Most attempts die within a month, for two reasons that have nothing to do with discipline. The first is that it feels bad. Maintaining a private ledger of your colleagues' unmet obligations sits somewhere between bookkeeping and keeping tabs, and people put it down because of how it feels to keep it, not because they forget to.
The second is timing. The moment to write the entry is the last thirty seconds of a call, which is precisely when you are moving to the next one or relieved to be done. Any capture that depends on a person choosing to act at that moment will hold for a while and then stop, and it will stop quietly rather than visibly, so you will not notice for weeks. The version that survives is the one that forms out of the conversation itself, so that what was agreed and who was waiting are already recorded by the time anybody would have had to decide to write them down.
A check you can run this week
Sit down and list everything you are currently waiting on from another person. Not your tasks, theirs to you. Most people get three or four, feel like that is everything, and then keep remembering more for the next two days, which is itself the answer. Then go through your list and try to say, for each one, when they told you it would come and what you wanted it for.
If you can do that for most of them, your team is holding this better than usual. If you stall on the dates, notice what that means. Every one of those is a thing you will either chase vaguely, absorb without telling anyone, or forget until it surfaces as a problem with a different name. None of those outcomes will be recorded anywhere as a promise that did not land, which is why next quarter will look much the same.
FAQ
Is this not what a task tracker is for? Assign it to them and watch the list.
That works for the subset of these that are actual tickets, and it is worth doing when they are. Most of them are not. A number, an answer, an intro, a sign-off, a file, a decision somebody owes you: these get asked for in the last two minutes of a call and never enter the system at all, because creating a ticket for a colleague to send you something feels heavier than the thing itself. The ones that do get filed land in the other person's list, which is not a list you are reading every day. Either way the waiting side ends up unrepresented.
Could a shared list of open requests fix it?
Only if it fills itself. Every team that has tried this has the same experience: the list is accurate for about three weeks, then it holds the things somebody remembered to add, which skews towards the formal and away from the quick verbal asks that make up most of the volume. A half-populated list is worse than none, because the absence of an item starts reading as evidence that nothing was promised. The useful version is not a place to log requests, it is a record that already contains them because it formed while the conversation happened.
Is chasing people not a normal part of managing work?
Chasing is fine and it is not the problem. The problem is chasing without specifics. A follow-up that names the thing, the day it was mentioned and what is blocked on it is a normal working message that most people are glad to get, because it is easy to answer. A follow-up that says you are circling back on that thing puts the work of reconstruction on the other person and usually gets a polite non-answer. What decays over three weeks is not your willingness to ask, it is your ability to ask the good version.
What about things you are waiting on from outside your company?
Those are harder, because you have no visibility into the other side at all. You cannot see their tracker or their workload, and you often cannot ask twice without it costing something in the relationship, particularly with a customer, an investor, or a partner who is doing you a favour. The only record that can exist is your own side of the conversation, which makes capturing what was said and when it was said the entire game. It also matters more, because an external commitment that fails quietly tends to be the one that turns up later as a surprise in a renewal or a close.
Does this turn into surveillance of who keeps their word?
It should not, and the design choices that prevent it are specific. The record is attached to the piece of work, not compiled into a profile of a person, so you retrieve by what you are waiting for rather than by who is slowest. It holds what was agreed and what it was needed for, not a judgement about whether somebody is reliable. Access stays with the people already involved in the work. And the point is to close the loop earlier, while a reminder is still a normal message, rather than to accumulate evidence for a later conversation. A system that produces a ranking of who slips most will get you carefully worded promises and nothing else.