In this article
Harvard Business Review identifies consistency as one trust-building behaviour. This article turns that narrow principle into a practical audit of ordinary management moments.
Leadership trust lives in small commitments
A promise does not need to be dramatic to matter. “I will review this tomorrow” creates an expectation that another person may build into their schedule.
Look at commitments you make casually: introductions, approvals, follow-ups, feedback and decisions deferred until a later meeting.
If your diary cannot support the promise, make a smaller one. “I can review the summary by Thursday; I cannot check every attachment this week” is more dependable than an enthusiastic yes you cannot honour.
Keep a short commitment list alongside your normal task system. The point is to notice obligations to other people, not create another elaborate productivity method.
Explain changes before people discover them
Plans change. Trust depends partly on how you handle the change.
If you cannot meet a commitment, update the affected person before the missed deadline when possible. Explain what changed, the practical effect and the revised plan.
Avoid overexplaining to protect your image. The colleague primarily needs to know what they can now rely on.
A useful update is: “I cannot approve this today because the required cost check is incomplete. I will resolve it with finance tomorrow morning and update you by noon. Please do not promise the customer a confirmed date yet.”
That update includes a constraint, a next action and a boundary. It is more useful than disappearing until the issue is resolved.
Make the basis of a decision visible
People do not need access to every confidential detail to understand your reasoning. Explain the criteria, relevant constraints and uncertainty you can share.
For example: “We chose the option that meets the required service date within the approved budget. The alternative offered more features but did not meet the timing.”
If confidentiality prevents explanation, say so accurately. Do not invent a convenient justification to avoid an awkward conversation.
Invite questions about the reasoning where appropriate. You may still hold the decision, but colleagues should be able to identify a missing fact or unintended consequence.
Distinguish a final decision from a working view. Treating a tentative comment as settled instruction is a common source of confusion that you can reduce through explicit language.
A hypothetical trust repair
Imagine a manager promises to review an employee’s development proposal but postpones it twice without explanation. The employee stops preparing ideas because the review seems unlikely to happen.
The manager acknowledges the specific miss: “I committed to two dates and did not update you when I could not meet them. That made your preparation difficult.”
He agrees a shorter review next Tuesday and asks the employee to send the two decisions requiring attention. He then protects the time and follows through.
One completed meeting does not prove that trust is restored. The employee may reasonably wait to see whether the changed behaviour continues.
This hypothetical illustrates repair through a visible commitment rather than a request to “trust me.”
Be accurate about what you know
Saying “I do not know yet” can be responsible when paired with a way to find out. Pretending certainty creates a future correction that other people may have to absorb.
Use three categories in important updates: confirmed, expected and unresolved. Explain what would change the expectation.
Do not use uncertainty to avoid deciding. Some choices must be made before every fact is available. State the judgement, its basis and the review trigger.
Admit errors promptly. A correction should identify what was wrong, what is now understood and who needs to act differently as a result.
Apply your standards to yourself
If you ask employees to flag risks early, respond to your own risks in the same way. If you expect preparation, arrive prepared or explain why the discussion must change.
Unequal standards are especially visible around time. Repeatedly arriving late while criticising others’ punctuality communicates whose commitments count.
That does not mean every role has identical obligations. Explain relevant differences without using seniority as a general exemption.
Fairness also requires checking whose contributions you notice. A colleague who speaks less may still be doing essential work. Recognition based only on visibility can distort the team’s understanding of value.
Run a ten-minute commitment audit
Review the last week and identify one promise kept, one promise missed and one expectation left unclear. Choose a repair for the missed commitment and a clearer phrase for the ambiguous one.
Ask a trusted colleague: “Where is it difficult to know what you can rely on from me?” Listen for an example rather than a reassurance.
For broader guidance, read Peak Belt’s trust-and-credibility article and new-role trust guide, alongside TrueNorth.
Do not confuse popularity with trust
A colleague can trust your judgement while disagreeing with a decision. Avoid measuring the relationship solely through friendliness, quick agreement or visible enthusiasm. Ask whether people understand the requirement and can raise a relevant concern. A difficult but well-explained choice may be more dependable than a comforting promise you cannot keep.
Choose one outstanding commitment today. Either complete it or give the affected person an honest, usable update. That is a small leadership action with an observable result.
AI-assisted researched guidance from PeakBelt. Hypothetical examples are labelled in the text. See our editorial approach.