Meetings produce agreements. Calendars fill with new meetings. A few weeks later, someone asks about an item from the earlier meeting and three people remember three different outcomes.
Jim Marsh, author of Culture OS and Managing Principal of JEM Premier Coaching, has publicly described Commitment as named owners, visible commitments, and reliable closure. A commitments log is one practical way to put those three parts into daily use. The log design and examples below were written for this article and are not a template from the book.
What a commitment is
A commitment is a specific promise from one person to deliver something by a date, made in a way others can see. "We will review the vendor options" is an intention. "The procurement lead will send the vendor comparison to the leadership team by Thursday" is a commitment. The difference is a name, a deliverable, and a date.
Not every task belongs in the log. Include items other people depend on: cross-team deliverables, decisions that unblock work, and anything promised to a customer or executive.
The five columns
Keep the log small enough to scan in a minute. Five columns are enough.
- Commitment: The deliverable, described so a stranger could tell if it was done.
- Owner: One name.
- Due date: A calendar date, not "soon" or "next sprint."
- Who is waiting: The person or team that depends on it. This makes the stakes visible.
- Status: On track, at risk, or closed. Add the date when it changed.
Place it where the whole team can see it without asking: a shared document, a board, or a tracker the team already uses. The tool matters less than the habit of looking at it together.
Named owners
If two people share a line, split it into two lines with separate deliverables. Shared ownership feels collaborative, but in practice each person assumes the other will move first. When a team is large, a single accountable name on each commitment keeps conversations specific.
Visible commitments
Visibility changes behavior because peers can plan around each other. When a colleague can see that a deliverable is at risk, they can adjust their own schedule or offer help before the date passes. It also removes the need for status-chasing messages, which are a cost for everyone involved.
Reliable closure
Every item ends in one of three ways: delivered, renegotiated openly, or withdrawn with a reason. Quietly letting a date pass is the outcome to design against. Create a norm that moving a date is acceptable when done early and with a note: "At risk. New date proposed: the 20th. Reason: the data source changed."
Leaders set the tone here. If someone flags a risk and the response is criticism, the log will fill with optimistic statuses and surprise misses. If the response is a short problem-solving conversation, people will report honestly.
A ten-minute review
Use a fixed sequence in your regular leadership meeting:
- Read the items due before the next meeting. Each owner confirms or flags.
- Read anything marked at risk. Decide whether to help, renegotiate, or reprioritize.
- Close the items finished since last time, and say who they unblocked.
An illustrative case: a leadership team of eight keeps a log of fewer than twenty open items. The review takes ten minutes, and members stop sending each other follow-up messages because the status is already visible. Treat that as an example of what to aim for, not a promised outcome.
Start with one initiative
Do not log every task in the company. Pick the live initiative that matters most this quarter and capture its commitments for the next thirty days. Adjust the columns after two weeks based on what the team actually uses. The Culture-to-Execution Sprint includes work on communication and accountability agreements for intact teams working on one live priority.