A commitment is usually made at a good moment: a conversation, an annual report, a response to an incident. At that moment the intention is sincere and the attention is high. The problem arises later, when the context has disappeared and the commitment only exists as a memory held by a few people, or as a sentence in a document that no one opens anymore.
Recording it is therefore not the problem. The problem is what happens afterward: who guards the commitment, when it expires, and what happens when the deadline approaches without anything having been done. Without a fixed place and a fixed rhythm, a commitment does not disappear with a bang, but gradually, until someone from outside asks about it and there is no answer beyond "we are working on it."
Most organizations are good at writing down a commitment. An action list, a report, an internal memo: there is usually a place where the text is stored. Where it goes wrong is in the translation from text to ownership. A commitment without an owner is not a commitment, it is a wish. And a commitment with an owner who does not know he is the owner is not one either.
That is also the reason why what you do with a commitment from a predecessor is a separate question. Commitments do not automatically survive role changes. Whoever takes over a role inherits the expectations of his predecessor, even if he never expressed them himself.
Recording what you are going to do is one thing. Demonstrating that it happened is something else, and that requires a form that does not depend on the memory of one person. A demonstrable commitment has a status that can be checked at any moment, a deadline that does not silently shift, and a trail of what was actually done — not what was promised to be done.
This distinction only becomes tangible the moment someone from outside comes back to an earlier statement. At that point, what matters is no longer the intention, but whether there is something with which progress can be shown. Whoever does not have that trail must reconstruct it under time pressure, and reconstruction under time pressure is rarely convincing.
Every commitment has a deadline, even if it is not explicitly stated. "In the short term" and "in the next phase" are deadlines without a date, and precisely those are the hardest to guard, because no one knows exactly when they expire. The question who guards a deadline and how you demonstrate that it happened addresses exactly this point: a deadline without an owner expires unnoticed, and a deadline with an owner who is not reminded expires almost as quietly.
What is at stake here is not symmetrical. Failing to keep a small commitment — a brief response, a follow-up, a conversation that was promised — often costs more trust than the absence of a large investment. A large promise is judged on its content and on the complexity of its execution; a small commitment is judged on character. Whoever fails to keep it shows what his word is worth, regardless of the reason. More on this can be found on the page about what a small commitment costs you if you do not keep it.
Many organizations already report on commitments, in an annual report, a progress update, or a response to a question from a regulator. But reporting that is not itself built from a trail of status and deadline often merely repeats the original promise in different words. That feels like demonstrating, but it is not. The question how you report on commitments and how you demonstrate that it happened makes this distinction further visible: reporting tells what you say, a trail shows what was done.
Not every commitment belongs on the boardroom table. But some do, particularly those with social or financial impact if they are not kept. Which signals reach that table and which do not is a choice that is often made implicitly, until the moment a commitment that no one at the highest level knew about suddenly becomes public. See which signals belong on the boardroom table for that consideration, and how you prevent commitments from arising that no one knows about for the problem that precedes it.
The Trust Baseline begins with an internal survey alongside an external stakeholder survey, and the difference between those two pictures is the first outcome. In addition, we are building a commitment tracker and a signal rhythm: a fixed place for commitments, their deadlines and their status, with a rhythm that periodically brings progress back to the people who are responsible. This is not a statement about what stakeholders think — we do not know that until they say so themselves — but a way to make visible internally what has been promised and what has happened with it. The tool is under construction. Those who wish to use it can sign up for the waiting list.
Recording, guarding and periodically reporting back on commitments is largely repeatable work: retrieving statuses, flagging deadlines, compiling overviews. Whoever wants to know which part of that work can be taken over by AI and which part remains human work can have that calculated per task with the werkscan from FTE TO AI.
Vraag maar. Het interessantste antwoord komt meestal van wie u nog niet heeft gesproken.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.