You know the scene. Wednesday, the daily standup, and someone on the team says: “OK, I’ll reach out to legal about that contract.” Everyone nods, topic closed, we move on. The following Wednesday someone asks what happened with the contract. Silence, and then the sentence I’ve heard on every project I’ve ever run: “I thought that was going through you.”
Nobody is lying here, and nobody is dodging. That person genuinely remembers the conversation differently. They remember the topic came up, they remember someone said something. They don’t remember that they were the one who took it on.
A promise said out loud weighs less than you think
The standup is short, fast and spoken. That’s its strength, because people say things there they would never put in an email. It’s also its weakness, because anything that only gets said out loud has a half-life shorter than a sprint.
Over the years I’ve noticed that commitments made at the standup disappear for three reasons.
First, they’re phrased as maybes. “I could take a look,” “I’ll try to get back to that,” “I’ll ping them if needed.” It sounds like agreement, but in practice nobody promised anything. The speaker leaves themselves a way out, and the listeners hear a commitment.
Second, they have no deadline. “I’ll reach out to legal” without “by when” is a task that could be done today or next quarter, and both versions match what was said.
Third, nobody writes them down where the team actually works. Tasks on the project board have an owner and a date. Tasks said at the standup live in the memory of a few people, each in a slightly different version.
Why PMs don’t catch it by reflex
For a long time I was convinced this was a team problem. People don’t keep their promises, so they need reminding. Only when I started watching where exactly things came apart did I realize that a good part of the responsibility sat with me.
At the standup, a PM’s reflex is to guard the clock. Fifteen minutes, blockers, done. When someone says “I’ll handle it,” the PM feels relief, because the topic has an owner, and moves on to the next item. They don’t stop to check whether that “I’ll handle it” is a commitment or just politeness.
On top of that there’s the fear of micromanaging. Asking “by when?” about every little thing sounds like control, so we don’t ask. And a week later we come back to the topic as if it were a surprise, even though it never was one.
The one-line habit
What works for me is so simple that I avoided it for a long time, because it seemed too trivial.
When something at the standup sounds like a commitment, I repeat it out loud in one sentence with three parts: who, what and by when. “So you’re writing to legal about the contract, and by Friday we’ll have their answer, or at least know when it’s coming.”
Right after the meeting, that one line goes where the team looks every day anyway: the project board, the team channel, next to the other tasks. It doesn’t go into my private notebook, because a commitment only I can see is still only my problem. Even if a tool writes the meeting’s action list for you, the line is worth saying out loud first, because the tool records the task, not whether anyone really took it on.
That repetition does more than it seems.
First, it turns a maybe into a statement. When you hear your own “I could take a look” translated into “so you’re checking it by Thursday,” you have two seconds to say “Thursday isn’t realistic, let’s make it Monday.” And that’s a good thing, because that conversation had to happen anyway. Before, it simply happened a week too late, after the deadline had already passed.
Second, the whole team hears it. If someone remembered the agreement differently, they say so right away, in the same meeting.
Third, the deadline stops being something the PM imposes. Someone said it themselves, and the PM only repeated it and wrote it down.
What about micromanaging?
This is the objection I hear most often, and I understand it well. Nobody likes having every sentence repeated back to them.
That’s why I don’t repeat everything. Only what falls outside the project board, meaning things that were born in conversation and don’t have a place yet. Usually that’s one or two items per meeting, and sometimes none.
There’s also one thing worth telling the team once, at the start, plainly: I do this because I forget things myself. It’s true, and it changes how the whole habit is received. The team then sees it as a shared way of making sure nobody has to remember for everyone.
When the line is there, and the task still isn’t
It happens that I did everything right, the line is on the board, and on Friday there’s still no answer from legal. That’s a good result too, because at least I know it on Friday.
At the next standup I don’t ask “why didn’t you do it?” That question frames the conversation as a reckoning, and the answer usually sounds like an excuse. I ask: “what’s changed since Friday, and what deadline is realistic now?” Most of the time it turns out the task got stuck on something nobody saw coming: the lawyer was on vacation, the contract needed a third person’s signature, the answer came back, but with a question. Then I update the line, a new date and possibly a new owner, and we move on.
The most important thing is that a commitment that didn’t happen doesn’t disappear along with its deadline. The old line stays, only the date changes.
A test for next Wednesday
At your next standup, count how many times you hear something like “I’ll handle it” or “I’ll take a look.” Don’t react, just write them down. A week later, check how many of those things actually happened and how many people remember promising them.
If the result doesn’t surprise you, you don’t need this habit. If it does, start with one line at the next meeting.
All situations described in this article are based on real events, but contain no company names, no individual names, and no data from any specific project.
