A commitment is made in a conversation, a panel, a response to a journalist's question, or an explanation to a nearby resident. At that moment there is no form, no system, no colleague taking notes. The commitment exists in the head of the person who made it and in the head of the person who heard it. Everything that happens afterward depends on whether one of those two still remembers it at the moment it becomes relevant.
Most commitments that are not honored are not deliberately ignored. They are forgotten, because there was no place for them to go after the moment they were spoken. The person who made the commitment has since moved on to something else. The role may have changed hands. There is no file in which the commitment can be found, and therefore also no moment at which someone asks whether it has been honored.
This is different from a project that is delayed. A project usually has an owner, a schedule, a steering group that keeps an eye on it. A commitment to an external party rarely has that. It falls outside the regular project structure, precisely because it arose in a moment of interaction and not in a moment of planning.
Organizations that recognize this problem generally do not have a shortage of good will. There is no resistance to honoring commitments. What is missing is a fixed place where a commitment is recorded after the moment it is spoken, a deadline for which someone is held accountable, and a way to show afterward that it happened. Without those three elements, honoring a commitment depends on one individual's memory, and memory is not a system.
The question how do you record a commitment and how do you demonstrate that it happened touches the core of this problem: recording and demonstrating are two different steps, and the second step is often forgotten as long as the first is already painful enough to organize.
A commitment without an owner is a commitment that no one monitors. Someone needs to know that a particular commitment is theirs to handle, when it expires, and what needs to happen as the deadline approaches. Without that assignment, a commitment only becomes visible again at the moment an external party asks about it, and by then the initiative has already shifted to the other side. The question who monitors a deadline and how do you demonstrate that it happened is about exactly this point: monitoring is a role, not an automatism.
There is a tendency to monitor large investments and grand promises more seriously than small, informal commitments. That is a risky assumption. A small commitment that is not honored stands out because it was small and concrete: everyone could check whether it happened, and everyone saw that it did not. A large investment that fails to materialize is often easier to explain away with circumstances. The question what does a small commitment you fail to honor cost you and how do you demonstrate that describes why exactly this kind of commitment weighs more heavily in the impression a stakeholder retains than the broad outlines of a strategy.
Commitments that no one knows about also arise at the moment a role changes hands. A predecessor gave an explanation to a council, made a promise to a group of suppliers, made a statement in an interview. If that commitment has not been recorded, it leaves with the person who made it. The new official starts without that file, and the external party who remembered the commitment is still waiting. The question what do you do with a commitment made by a predecessor and how do you demonstrate that it happened addresses this handover moment, which is often the weakest point in the chain.
Recording and monitoring solve the problem of forgetting. They do not solve the problem of demonstrating. An external party who asks whether a commitment has been honored does not want to hear an internal assurance; they want to see a trail. Reporting on commitments is therefore a separate component, apart from the recording itself. The question how do you report on commitments and how do you demonstrate that it happened is about this final step: the difference between knowing that something happened and being able to show it.
This page itself is about the starting point of that trail: how a commitment can be prevented from remaining invisible in the first place. The elaboration of recording, monitoring, and demonstrating in one continuous process can be found at how do you prevent commitments that no one knows about and how do you demonstrate that, where these separate components come together.
A commitment that is not honored is one moment. The pattern of how an organization deals with commitments is something else: that pattern forms over time and is exactly what a commitment tracker provides insight into, regardless of whether an individual case has been resolved or not.
Recording and monitoring commitments is largely repeatable work: noting a commitment, linking a deadline, keeping a status, compiling a report at the moment it is needed. That is exactly the kind of work for which it can be determined which part AI can take over and which part a human must continue to do. FTE TO AI's work scan calculates per task which portion of that work is eligible for takeover, so that anyone who wants to set up this process knows in advance where employees' time will and will not still be needed.
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.