Blog

The promises that slip: keeping track of what you said on calls

“I’ll send that over” is easy to say and easy to forget. A few habits keep casual promises from quietly slipping.

The promises that slip are rarely the big ones. Nobody forgets the contract renewal. What slips is “I’ll send you that doc”, “let me check and get back to you”, “I’ll loop in Sam”. Said casually, near the end of a call, to be helpful.

You forget. The other person doesn’t. A week later they ask about it, and a small thing has become a small breach of trust.

Why they slip

Most of our systems capture topics, not commitments. Meeting notes say “discussed export limits”. They rarely say “I promised Dana the export limits doc by Friday”. Task lists hold what you decided to do at your desk, not what you said out loud in the middle of a conversation.

A spoken promise has no home. So it lives in your memory, which is exactly where it is most likely to get lost between the next three calls.

Five habits that keep them

1. Say it back with a date

Turn vague into specific while you are still talking. “I’ll send it over” becomes “I’ll send you the export limits doc by Friday.” A date makes it real for both of you, and easy to check later.

2. Keep every promise in one place

Not in the call notes, a sticky note and your inbox. One list, where every promise goes the moment you make it. If you can’t write during the call, write immediately after, before the next thing starts.

3. End every call with a twenty second recap

“So: I’m sending the export doc by Friday, you’re checking with your security team.” It feels formal the first few times. It catches most misunderstandings before they happen, and it tells the other person you were listening.

4. Follow up the same day

A short message after the call, restating what you promised, does two things. It puts the promise in writing, and it often takes care of the promise itself, if it was a link or a doc you can send right away.

5. Look at open promises once a week

Five minutes on Friday, reading the list: what is done, what is late, what you need to renegotiate. Telling someone “this will take until Tuesday” before the deadline keeps trust. Going quiet does not.

A task is something you decided to do. A promise has someone waiting on it.

Where Stuart fits

This is one of the reasons we built Stuart. During a call, it notices when you make a promise and keeps it, linked to the moment you said it. After the call, your promises sit in one list on your Mac, next to the tasks from your notes. Ticking one off feels good. Not having to remember it in the first place feels better.

Stuart, for MacAnswers from your own work, with a source for every sentence.
See how it works

More from the blog

Where was I? Getting back into code after an interruption

A meeting, a message, a weekend. Here is why coming back to code is slow, and five small habits that make it fast.

Write your standup from what you actually did

Standups go wrong when they are written from memory. Here is a simple format, and the commands that pull the truth from your own work.