Updated 20 October 2026.
A reliable commitment names what you will deliver, when you expect to deliver it, and what the promise depends on. Before saying yes, check your capacity. If the conditions change, tell the affected person while they still have time to adjust.
The Speed of Trust by Stephen M. R. Covey, with Rebecca R. Merrill, connects trust with observable conduct. The official Speed of Trust action cards describe keeping commitments, including informing the other party when you cannot keep one. Our commitment record below is a practical application, not a validated measure of trust.
Find the promise hidden in ordinary language
“I will take a look” may sound casual to you and like a promise of an answer to someone else. Clarify whether you are offering to investigate, produce a draft, or finish the work.
Also check words such as soon, ready, and complete. A document can be ready for internal review while still missing the approval needed for customer use. Naming the stage prevents two people from relying on different versions of the same promise.
Do this before the work begins. A clarification after someone has planned around your statement is still useful, but it may come too late to avoid disruption.
Define a commitment in five lines
Write:
- The deliverable and its intended use.
- The person responsible for it.
- The date or event it is needed for.
- The dependencies and unresolved questions.
- The point at which you will raise a risk.
You do not need a complex system for a small promise. A clear message can contain the whole record. The important part is that the other person can confirm whether it meets their need.
A worked example: a customer handover
Imagine a consultant offering to send a migration guide on Wednesday. The customer plans to use it in a Thursday rehearsal. The consultant can draft the guide, but a colleague must verify one technical step.
A clearer proposed commitment is to send a reviewed guide by Wednesday afternoon, with the technical check due Tuesday. If that check is unavailable, the consultant will raise the risk on Tuesday rather than wait until the delivery time passes.
No successful outcome is assumed. The point is that the customer can now assess the dependency and decide whether the plan is adequate. A confident promise without that information would give them less control over their own preparation.
Make changes explicit
When a promise becomes doubtful, state what changed, what remains possible, and which alternatives you can offer. Avoid hiding the change in a vague progress update.
The other person may need the original scope, a smaller reviewed deliverable, or a different date. Ask which tradeoff is acceptable rather than making that choice silently on their behalf.
If the original promise was already missed, acknowledge that plainly and agree on the next step. A revised date does not erase the cost of the first miss.
Review reliability without reducing people to a score
At the end of a project, look for recurring causes of broken expectations. Were dependencies ignored? Did the team use different definitions of done? Was it difficult to raise risks early?
A count of kept promises cannot capture every aspect of trust or the fairness of the workload. Use the record to improve coordination, not to turn complex working relationships into a simplistic ranking.
The team-trust learning path provides related reading. For recall, explain the difference between promising a finished guide and promising to investigate its requirements. Then rewrite one current commitment so the recipient can tell exactly what they may rely on.
Continue with ReadSprint
Open the related book summary to revisit the book's broader ideas. Use the free Book-to-Action Plan to organize your own takeaways into practice and review phases; the tool arranges the entries you supply rather than validating the method or predicting results.
Source checked 20 October 2026: FranklinCovey’s Speed of Trust action cards, behavior 11. The source supports the attributed book concept. The scenarios, questions, and practice steps in this article are original ReadSprint suggestions; example outcomes are hypothetical.
