Leadership is often discussed as a collection of personal qualities: confidence, empathy, decisiveness or vision. Those qualities can matter, but they are difficult for a team to use unless they become observable behaviour. A colleague cannot plan around your intention to be supportive. They can plan around a dependable check-in, a clear decision or a promise you revisit before it expires.
This guide treats leadership as a practical operating rhythm. It is not a personality test or a universal recipe. Your authority, working environment and team’s experience will affect what is appropriate. Start with one habit, explain why you are trying it and ask whether it helps.
Before the meeting, name the decision
A meeting invitation often names a subject without naming the work. “Project discussion” leaves people guessing whether they should prepare options, share information or wait for an announcement. Before inviting others, write one sentence explaining the decision needed and the limits around it.
For example: “We need to choose which customer issue to address first; the budget is fixed, but the sequence is open.” Identify who makes the final decision and who needs to contribute. If a decision has already been made, say so. Asking for input that cannot influence anything can undermine trust.
Close with a brief record: the decision, its owner, the main reason and the condition that would justify revisiting it. The point is not elaborate documentation. It is preventing different memories from becoming different plans.
During the conversation, delay your explanation
Leaders often have information others do not, which makes explaining feel helpful. Yet explaining too early can shut down information you need. In a check-in, ask what has changed, what is getting in the way and what the person needs you to understand. Leave enough space for an answer that was not prepared in advance.
Reflect back what you heard before proposing a solution. “You are waiting on access, and the deadline has not changed—is that right?” distinguishes understanding from agreement. You can acknowledge a constraint without immediately accepting every proposed response.
Amy Edmondson’s work on psychological safety is relevant here: people need conditions in which interpersonal risks, such as admitting uncertainty, are possible. That does not mean removing accountability. It means avoiding a situation where important information becomes too costly to share.
After the promise, close the loop
Keep a small record of commitments you make to the team. Include what you promised, who is waiting and when you will respond. Review it before your next conversation rather than relying on memory or your inbox.
If you cannot deliver, renegotiate early. Explain what changed, what you can still do and when the next update will arrive. “I have not secured the additional support; I will bring you the available options on Thursday” is more dependable than silence followed by an apology.
This habit also applies when someone raises a concern you cannot resolve. Tell them what action was taken, what cannot be shared and whether there is another appropriate route. Respect confidentiality; closing a loop does not entitle everyone to private details.
Make the habit small enough to survive pressure
Choose a cue already present in your working day. Before sending a meeting invitation, add the decision sentence. After a one-to-one, record your own commitments. Before a weekly review, check the oldest unresolved promise.
Peter Gollwitzer’s work on implementation intentions offers a useful principle: connect an intended action to a recognisable situation. You do not need a complicated tracking system. A short “when this happens, I will do this” rule can make the practice easier to remember.
Do not turn the habit into a compliance exercise for your colleagues. First notice whether your own behaviour is becoming more predictable. Then invite a specific response: “Did the decision note help you act, or did it leave something unclear?”
Review the effect, not your leadership image
After a few repetitions, examine a concrete example. Was a decision easier to understand? Did a concern surface earlier? Did a colleague have to chase the same promise again? Consider counterexamples as carefully as encouraging ones.
If the habit adds work without helping, change it. A team dealing with an urgent incident may need shorter updates; an experienced specialist may need more autonomy and fewer check-ins. Reliability is not rigid repetition. It is making your approach understandable and adjusting it openly when circumstances change.
Further reading: Amy C. Edmondson, The Fearless Organization; Peter M. Gollwitzer’s research on implementation intentions; Peter F. Drucker, The Effective Executive. These references inform the discussion; no endorsement is implied.