Commit to Commit

Summary

“Commit to commit” is a communication pattern for situations where a decision cannot be made immediately. Instead of offering an open-ended promise to follow up, acknowledge the problem, give a specific short deadline for returning with a decision or commitment, and then follow through.

Why it matters

Predictable follow-up turns uncertainty into a manageable coordination problem. Broken or vague promises erode morale and trust, while explicit commitments give customers, peers, managers, and teams clarity about when the next decision will arrive.

Key ideas

• Do not react before you have enough context to make a responsible commitment.
• A follow-up promise should include a concrete date or time, not only “I’ll get back to you.”
• Keep the window short; an unfulfilled follow-up quickly becomes another source of uncertainty.
• The pattern applies upward, downward, and sideways: it is useful with customers, managers, peers, and family.
• Clear commitments align teams around direction and priorities while leaving room to understand the problem and build a solid answer.

Practical applications

• When receiving a complex request, restate what you heard and name the exact time you will return with a decision or next step.
• Put the follow-up on the calendar or task list immediately so the commitment has an operational reminder.
• If the promised decision changes, communicate before the deadline with the new context and a revised commitment.
• Use the pattern in incident response, code review, project planning, and one-on-ones where ambiguity otherwise lingers.

Open questions

• What is the shortest useful follow-up window for different classes of engineering or customer decisions?
• How should teams distinguish a genuine need for more investigation from avoidable indecision?

Related notes

• An Engineer's Guide to Communication