I learned the hard way that everything I thought made me a good leader in an office was actually a crutch. In a room, I could read the table and adjust mid-sentence. I could catch someone in the hallway before a misunderstanding hardened. I could fill an awkward silence with energy and pull a meeting back from the edge by sheer presence. None of that survives the move to remote. The hallway is gone. The room is gone. What is left is what I write, and for a while what I wrote was not nearly good enough to carry the weight I was suddenly asking it to carry.
That is the quiet shift that remote work has forced on leadership. In a distributed company, your leadership is mostly your writing. The decisions you communicate, the direction you set, the feedback you give, the standards you hold, almost all of it now arrives as text that people read when you are not there to explain it. Clarity in writing has become the most important leadership skill of the decade, and most leaders are dramatically underinvested in it because for their whole careers it never mattered this much.
Charisma does not travel through a screen
Charisma is a real and useful thing in a room. It is also almost entirely a synchronous, in-person phenomenon, and it does not survive the transfer to text. The leader who could electrify an all-hands in person often writes a flat, forgettable update that lands with a thud, because the things that made them compelling, presence and timing and energy, do not exist on the page. What remains is whether the thinking is clear, and clear thinking is a different muscle than commanding a room.
This is genuinely good news, and I say that as someone who relied on presence for years. Writing is learnable in a way charisma mostly is not. You can get measurably better at clear writing through deliberate practice, while you cannot really practice your way into magnetism. Remote leadership rewards the skill that anyone can build and discounts the trait that you mostly either have or do not. That is a fairer game, and it favors the leaders willing to do the unglamorous work of getting their thinking onto the page well.
Vague writing is vague thinking made visible
Here is the part that took me longest to accept. When my writing was muddy, it was almost never a writing problem. It was a thinking problem that writing had exposed. In a meeting I could gesture at a half-formed idea and let the conversation finish it for me. The collective energy of the room papered over the fact that I had not actually decided what I meant. Writing strips that cover away. A blank page does not nod along. It forces you to know what you think, and a lot of the time I discovered I did not.
This is why writing is such a brutal and useful tool for leadership specifically. A leader's main job is to reduce uncertainty for the people around them, to take a confusing situation and hand back clarity about what matters and what to do. If you cannot write the decision down clearly, you have not made it clearly, and shipping that fog to your team in text means they each resolve the ambiguity differently and quietly drift apart. The discipline of writing the thing forces the clarity that the team needs, before the team ever sees it.
Example: Picture a leader who sends a strategy update they are happy with. Within a day, three people execute against three different interpretations of the same paragraph. The words were fine. The thinking underneath had three unresolved forks in it, and because nobody was in a room to ask "wait, which do you mean," each person picked a fork and ran. The writing was not bad so much as the decision was incomplete, and the page exposes that in a way a meeting never would.
Write for the reader who is not in the room
The mechanical shift that helped me most was learning to write for absence. In an office you write assuming you will be there to clarify. Remote, you have to write assuming you will not be, and that changes almost everything. You front-load the conclusion instead of building to it, because a reader skimming on a Tuesday should get the point in the first two lines. You make the decision and the reasoning explicit, because nobody can read your tone or ask a quick follow-up. You anticipate the obvious questions and answer them inside the document, because every question you leave open becomes an interruption or, worse, a wrong assumption.
Writing for the reader who is not in the room also means respecting their time as if it were your own, which it functionally is across a whole team. A rambling update from a leader does not just cost the leader's time. It costs every reader's time, multiplied, plus the cost of the misunderstandings that vague writing seeds. I have come to think the single most valuable edit a leader can make is cutting their own writing in half and watching how much clearer it gets. The discipline of brevity is the discipline of having actually decided what matters.
The skills that actually move the needle
When leaders ask me how to get better at this, I steer them away from style and toward structure, because structure is where the real gains are. A few things matter far more than the rest.
- Lead with the answer. State the decision or the point in the first lines, then support it. Make the reader the editor of how much detail they need, not a detective hunting for your conclusion.
- One document, one job. A decision memo is not a status update is not a brainstorm. Mixing them produces writing that does every job badly. Decide what the document is for before you write a word.
- Make the reasoning visible. In person you can be asked why. In writing you cannot, so the why has to be on the page or your team will assume one, and they will assume wrong.
- Edit for the skim. People read leadership writing fast and under load. Headings, short paragraphs, and a clear first line are not decoration. They are how the message actually gets through.
None of these are about being a beautiful writer. They are about being a clear one, which is the only kind that matters for leading distributed teams. The goal is not prose anyone admires. It is prose nobody misreads.
The hardest case, and the one that exposed my own gaps fastest, is feedback. In an office I gave most feedback in passing, softened by tone and a smile and the chance to read the other person's face and adjust on the spot. Remote, written feedback lands with none of that cushioning. The same words that feel supportive when spoken can read as cold or even harsh on a screen, because the reader supplies the tone, and a person who is already anxious will supply the worst one. So I had to learn to write feedback that carries its own warmth: to state plainly what I saw, why it matters, and what specifically would be better, and to make the care explicit rather than assuming it would be inferred. It is more work than a hallway word, and it is also better, because it forces me to actually know what I am asking for instead of gesturing at it. Vague feedback in person is forgettable. Vague feedback in writing is just confusing, and confusing feedback from a leader does real damage.
Build a company where the writing compounds
The last thing I would say is that this is not only an individual skill, it is a system you build. The leaders who thrive remote do not just write well, they create an environment where good writing accumulates instead of evaporating in chat. Decisions get written down where the work happens, so the reasoning is still there in three months when someone needs it. The default for anything important is a document, not a meeting, which forces the clarity up front and leaves a durable record behind.
This is part of why we built Atlas the way we did, with the decision, the task, and the discussion living in one place rather than scattered across a chat tool, a doc tool, and a project tool that never talk to each other. When the writing lives next to the work it governs, the clarity you fought for as a leader keeps paying off long after you wrote it, instead of scrolling out of sight by Friday. Remote leadership is mostly a writing job. The companies that understand that build the muscle on purpose, in the leaders and in the systems, and it shows up as teams that move in the same direction without anyone having to be in the room.