What your email reveals about your leadership (3)

Somewhere this week, a decision worth real money will die in an inbox, and no one will notice it happening.

Not because anyone objected. Not because the idea was bad. It will die because the email that carried it buried the ask under four paragraphs of throat-clearing, never quite said what it needed, from whom, or by when, and left every recipient with the same quiet, deniable thought: this probably isn’t mine to answer. So, no one answers. The thread goes cold. Weeks later someone asks what happened to that initiative, and the honest reply is that it drowned in plain sight, in a message everyone technically received, and no one truly read.

We have spent two weeks on what email is: a permanent record and a silent trainer of behaviour. Now the practical question both of those truths have been driving toward. If every message you send is written into the organisation’s memory and teaches your people how to operate, then writing a clear one is not a matter of tidiness. It is a leadership act, and writing a muddy one is a failure of leadership dressed up as busyness.

Start with the discipline that fixes most of the damage at once: lead with the ask. The single most common flaw in a leader’s email is that the reader has to excavate. The request, if there is one, sits in the fourth paragraph, after the context, the caveats, and the history. Invert it. The decision or action you need goes in the first line, in plain words, naming who must do what and by when. Everything else is support. A reader in a hurry, and every reader is in a hurry, should know within one sentence whether this message is theirs to act on.

Then write for the person who is scanning, not studying. Give the context in a few tight lines, name the owner of each next step, and offer a single point of contact for questions. You are not composing an essay; you are handing someone the shortest possible path from reading to doing. Respect for the reader’s time is not a soft courtesy. It is the difference between a team that moves and a team that stalls, because every muddy email is a tax you levy on everyone downstream, paid in the minutes they spend decoding what one minute of your discipline could have made obvious.

Two habits from earlier in this series come home here. First, the honest CC. Copy only the people who genuinely need to know or act, and never use the copy line as a quiet weapon or a way to spread your own risk, because, as we saw last week, an inflated CC line does not inform; it intimidates. Second, version the truth. For anything consequential, say plainly which version you are referring to and where the final one lives, so the permanent record you are creating stays trustworthy rather than becoming a museum of conflicting drafts nobody can reconcile.

And then there’s the discipline almost no one practices: the discipline of not answering. Before you reply, ask whether the message is even yours to answer. Sometimes the most useful thing you can do with an email is forward it, untouched, to the person who should own it, or wait a day so that someone closer to the work steps up before you do. Every question you answer that belonged to someone else is a small theft of their growth, however helpful it feels in the moment. Restraint is a form of delegation, and delegation is how you build people who no longer need the email at all.

Now the necessary warning, because everything I have just described can curdle. A leader who discovers the power of structure sometimes overcorrects into bureaucracy: approval matrices for trivial choices, changelogs on documents no one will ever audit, and a formal protocol wrapped around a decision that needed a single confident sentence. That is not discipline; it is discipline’s impostor, and it slows an organisation to a crawl while feeling productive. The real skill is judgement, knowing which emails carry enough weight to deserve the full architecture and which deserve one clear line and a send. The heavy machinery is for the heavy decisions. Most of what you send is lighter than you treat it.

So, sit with these before you write your next message. When you compose an email, are you making the reader’s job easier, or only your own? How many of the messages clogging your team’s week exist only because an earlier one was unclear? And where have you added a process that protects you but quietly slows everyone else, and are you honestly sure the trade is worth it?

Here is your challenge. For one week, hold every consequential email to a single standard: the ask in the first line, the owners named, the next step explicit, and nothing in the copy line you could not defend out loud. Then watch what happens to the speed of the people around you.

Everything so far has been about writing better emails. But the highest discipline of all is not about what you write. It is about what you have the wisdom to leave unwritten, the messages a leader should never send, and the conversations that email quietly destroys. That is where we finish next week.

About the author:

Dr Toye Sobande is a strategic leadership expert, executive coach, lawyer, public speaker, and award-winning author. He is the CEO of Stephens Leadership Consultancy LLC, a strategy and management consulting firm offering creative insights and solutions to businesses and leaders. Email: [email protected]