Rey Columna
All guides

How to Catch Dropped Commitments Before They Blow Up

Most dropped commitments were never written down where anyone would see them again. They were said in a meeting, typed in a thread, or agreed in a hallway. To catch them, sweep those places once a week, turn every "I'll do it" into an owner and a date, and follow up early.

By Rey Columna, CTOPublished 5 min read

On this page

What counts as a commitment

Anything someone said they'd do that another person is now counting on. Some examples:

  • "I'll send the design doc by Friday."
  • "Let me check with the platform team and get back to you."
  • "We'll fix that after the release."
  • "I'll review your PR today."
  • "I'll talk to Sam about it."

Many of these never become tickets because they're small or feel too obvious to track. Those are the ones that slip.

Where commitments get dropped

Look in the places where talk happens and tracking doesn't.

  1. Meetings with no notes. Someone says "I'll take that," and the meeting moves on.
  2. Long chat threads. The promise is in message 14 of 40. Nobody scrolls back.
  3. Email. A reply says "will do," then it sinks in the inbox.
  4. Handoffs. Someone changes teams or goes on leave. Their open promises don't move with the work.
  5. Cross-team asks. "Can your team look at this?" "Sure." Then it's nobody's job.
  6. "After the release" items. The release ships. The follow-up doesn't.
  7. Your own promises. Leaders say "I'll look into it" a lot. Those count too.

The 20-minute weekly sweep

Do this once a week. Friday afternoon or Monday morning both work.

Step 1: Scan your meetings (5 minutes)

Open your calendar for the past week. For each meeting that mattered, ask:

  • Was anything agreed?
  • Who said they'd do it?
  • Was a date mentioned?

If there were notes, scan them for "will," "I'll," "we'll," "follow up," and "next step."

Step 2: Scan your threads (5 minutes)

Search your chat and email for the same words from the past week. Focus on threads you were in, and threads about your team's projects.

Step 3: Write each one down (5 minutes)

Use one simple list. For every commitment:

What Owner Due Status
Send design doc for search v2 Ana Fri Not started
Check with platform on rate limits Teo No date Unknown
Fix flaky deploy test after release Team No date Not started

Anything with "No date" or "Team" as the owner is a warning sign. Without one owner and one date, nobody will notice when it slips.

Step 4: Pick the risky ones (5 minutes)

Flag anything that is:

  • Past due or close to it.
  • Blocking another person or team.
  • Owned by someone who's out, overloaded, or switching teams.
  • Your own.

Those are the ones you follow up on this week.

Sweep checklist

  • Reviewed last week's meetings for agreed actions
  • Searched chat and email for "I'll," "we'll," "follow up"
  • Every item has one named owner
  • Every item has a date
  • Flagged items that are late, blocking, or owned by someone stretched
  • Closed or followed up on my own promises first

How to follow up without blaming anyone

Keep it about the work and assume good intent. In most cases somebody forgot. They didn't stop caring.

Things you can say:

  • "Quick check on the design doc for search v2. Still on for Friday, or should we move the date?"
  • "You mentioned checking with platform on rate limits. Did that happen, or do you want me to take it?"
  • "This one has been sitting since the release. Who should own it?"
  • "I said I'd look into the on-call schedule and I haven't. I'll have an answer by Wednesday."

Each one names the item and offers a way out: a new date, a new owner, or dropping it. Dropping a commitment on purpose is fine. The problem is dropping it without telling anyone.

Make it less likely to happen

The sweep catches what slipped. These habits stop more from slipping.

  1. End every meeting with owners and dates. Spend the last two minutes reading them back. "So Ana has the doc by Friday, Teo checks with platform by Tuesday."
  2. Move promises out of chat. When someone says "I'll do it" in a thread, reply with a ticket link or ask them to add one.
  3. One owner per item. If "the team" owns it, nobody does.
  4. Hand off promises, not just tickets. When someone leaves a project, ask: "What did you tell people you'd do?"
  5. Close the loop in public. When something is done, say so in the same place it was promised, so nobody has to ask.
  6. Use 1:1s. Run through open items together. See how to prep for 1:1s in 10 minutes.
  7. Review weekly. Pull open commitments into your weekly priorities review. See how to run a Monday priorities review.

Warning signs you're missing commitments

  • People ask "did anyone ever...?" in meetings.
  • The same topic keeps coming back with no progress.
  • Another team escalates something you thought was handled.
  • You find out about a missed deadline from someone outside your team.
  • You say "I thought someone was on that."

If you hear these more than once in a month, your sweep isn't catching enough. Widen it.

FAQ

Isn't this what a project tracker is for?

Partly. Trackers are good for planned work. Many commitments are small promises made in meetings and chat that never become tickets. The sweep is for those.

Won't following up feel like micromanaging?

Not if you keep it light and offer options. A short check-in before something is late feels like help. A check-in after it blew up feels like blame.

What if I'm the one dropping things?

Start the list with your own promises. Clear or re-date them first. It sets the tone for everyone else.

How far back should the sweep go?

One week is enough if you do it every week. If you're starting fresh, go back a month once, then keep it weekly.

Want in early?

I'm building Sasshi, an iPhone app for engineering leaders. It's in the works, with invite-only early access. Its AI, Scout, reads your calendar, email, Slack, meeting notes, project boards and code activity, read-only. Each morning it surfaces 3 to 5 blind spots, like silent risks and undocumented decisions, with receipts and a one-tap next step. Nothing is sent without you. See how it works.

Email me for early access

Only used to contact you about Sasshi. No spam, no sharing. Ask me to delete it anytime.

Sources

No outside sources are cited. This is a practical routine, not research. Names in the examples are made up.