Communication Skills: The Most Underrated Tech Skill
You can out-engineer almost everyone at your level by learning to write three good paragraphs — the bar is honestly that low. The engineer who explains the trade-off crisply in Slack wins the room; the one with the "better" solution who cannot explain it loses. This post is a practical toolkit for levelling up communication fast: lead with the decision not the context, cut 30% again after you thought you were done, use bullets for trade-offs and prose for emotions, always end with a clear next step. In tech, writing is leverage. A good document moves a company. A bad one wastes a quarter.
Communication Skills: The Most Underrated Tech Skill
The engineer who explains the trade-off in a crisp Slack message wins the room. The one with the "better" solution who cannot explain it loses. This has been true for fifteen years and will be true for fifteen more. It is the single most undervalued skill in tech, and the bar to exceed most of your peers is shockingly low.
Why communication is leverage
Your best ideas are only as useful as other people's ability to act on them. If your idea is great but your communication is fuzzy, it dies in translation. If your idea is good and your communication is clean, it propagates, gets built on, and compounds.
Writing, specifically, is the highest-leverage communication. A well-written doc influences decisions in rooms you are not in. A well-written Slack message turns five people into action without a meeting. A badly-written one triggers four follow-up meetings, most of which are about figuring out what you meant.
Four rules that level up communication fast
- Lead with the decision, not the context. Most writing buries the main point at the bottom
- Write shorter. Then cut 30% more. Tight writing signals clarity of thought
- Bullet trade-offs, prose for emotions. Structure where it helps, flow where it connects
- Always end with a clear next step. If the reader does not know what to do, you failed
Rule 1: Lead with the decision
The default structure most people use: here is the context, here is the problem, here is what I thought about, here is what I concluded. By the time the reader reaches the conclusion, half of them have skimmed away.
Flip it. Start with "I recommend X." Then give the reasoning. Readers who trust you can stop after the first line. Readers who need the reasoning can read on. Both are served.
Rule 2: Cut 30% more
Every draft is too long. Always. After you finish, go back and cut 30%. Kill qualifying phrases like "I think" and "it seems that" when you actually mean "it is." Kill filler words. Kill paragraphs that restate the previous paragraph.
This is painful. The stuff you cut often feels important. It almost never is. Short, clear writing is a sign of confident thinking. Long, hedged writing is a sign of someone who has not finished thinking yet.
Rule 3: Structure matches content
Some content is best as prose. Some is best as bullets. Decision docs, trade-offs, lists of tasks — bullets. Narratives, reasoning, emotional content — prose.
The common mistake is picking one default and forcing all content into it. Engineers tend to over-bullet because it feels structured. Marketers tend to over-prose because it feels human. The best communicators switch mid-document when the mode needs to change.
Rule 4: End with a clear next step
Readers do not know what to do unless you tell them. "Thoughts?" is not a next step. "Please respond by Friday with any objections, otherwise I'll proceed" is a next step. Every message, every doc, every email should end with either an action (for the reader) or a decision (yours).
If you cannot end with a clear next step, your doc is probably not done. Go back and figure out what you are actually asking for.
The daily practice
- Before hitting send on any non-trivial message, re-read once for length and clarity
- Write the TL;DR of every doc after you finish. If you can't, the doc is not done
- Keep a copy of the three best internal docs you have ever written. Reference them when writing new ones
- Study writers you admire — not content, structure. How do they open? How do they transition? How do they end?
- Practise with small stakes — README files, PR descriptions, status updates. Low-cost reps, high-return skill
The leverage math
A good doc shipped to a 20-person team is read by 20 people and influences 20 people's decisions for a week. Its leverage is massive compared to the 30 minutes it took to write.
A bad doc on the same topic gets read, misunderstood, generates four "can we chat about this" requests, eats three hours of meeting time across the team, and results in slightly worse decisions. Its leverage is negative compared to the time invested.
Same time. Different output. The skill is the multiplier.
In tech, writing is leverage. A good document moves a company. A bad one wastes a quarter.