рдореБрдЦреНрдп рдордЬрдХреБрд░рд╛рдХрдбреЗ рдЬрд╛
JobCannon
рд╕рд░реНрд╡ рдХреМрд╢рд▓реНрдпреЗ

Communication

Write clearly, speak confidently, convey ideas effectively

тмв рд╢реНрд░реЗрдгреА 1рд╕реЙрдлреНрдЯ рд╕реНрдХрд┐рд▓реНрд╕
рдордзреНрдпрдо
рдкрдЧрд╛рд░рд╛рд╡рд░реАрд▓ рдкрд░рд┐рдгрд╛рдо
18 рдорд╣рд┐рдиреЗ
рд╢рд┐рдХрдгреНрдпрд╛рд╕ рд▓рд╛рдЧрдгрд╛рд░рд╛ рд╡реЗрд│
рдордзреНрдпрдо
рдХрд╛рдард┐рдгреНрдп
12
рдХрд░рд┐рдЕрд░реНрд╕
рдПрдХрд╛ рджреГрд╖реНрдЯрд┐рдХреНрд╖реЗрдкрд╛рдд

Communication (written + verbal + visual + presentation) is the foundational soft skill. Required across ALL careers, adds $15k-$40k at senior levels. Built through deliberate writing practice, public speaking exposure, and feedback loops. 12-18 months of sustained practice (journaling, presenting, writing daily) moves from 'adequate clarity' to 'people understand on first read and want to hear more'. Multiplier skill: every other skill you have is 50% less effective if you can't explain it.

Communication рдореНрд╣рдгрдЬреЗ рдХрд╛рдп

Communication is the foundational soft skill spanning written (email, Slack, documents, proposals), verbal (presentations, meetings, public speaking), visual (diagrams, slides, data viz), and body language. Effective communication makes every other skill you have 50% more effective: great ideas fail without clear explanation; mediocre ideas with excellent communication succeed. In 2026, remote-first work makes async written communication the #1 channel (email, Slack threads, docs), followed by synchronous verbal (Zoom calls, presentations). The skill compounds: a junior who writes clearly gets better feedback, learns faster, and advances; a senior who speaks poorly limits their influence to their immediate team. Communication is a multiplier skill. Technical excellence without communication ceiling = tech lead max; add communication = VP Engineering / CTO. Purely management-track? Communication is 80% of the job.

ЁЯФз рд╕рд╛рдзрдиреЗ рдЖрдгрд┐ рдкрд░рд┐рд╕рдВрд╕реНрдерд╛
Notion (documentation templates)Loom (async video recording)Keynote (presentations)Google Slides (collaborative decks)Grammarly (writing polish)Hemingway Editor (clarity check)Slack/Teams etiquette (async writing standards)Toastmasters (public speaking)BLUF method (Bottom Line Up Front)Pyramid Principle (idea structuring)

ЁЯОУ рдкреНрд░рдорд╛рдгрдкрддреНрд░реЗ

Toastmasters Competent Communicator
BBC Future of Work communication cert
'On Writing Well' by William Zinsser (study path)

тЪЦ рдпрд╛рдВрдЪреНрдпрд╛рд╢реА рддреБрд▓рдирд╛ рдХрд░рд╛

тЭУ FAQ

Should I learn async writing or public speaking first?
Async writing first. 80% of professional communication is written (email, Slack, docs, proposals). Public speaking confidence comes after you've proven you can articulate ideas clearly in text. Start with one Slack post per day written with care, brevity, structure, impact. After 2 months of daily writing, add one weekly presentation to a small group (3-5 people).
How do I improve my technical writing for non-technical audiences?
Three passes: (1) write what you know, dump knowledge without worrying about clarity; (2) cut jargon, replace every industry term with a 5-word explanation (or delete the term); (3) test with a non-expert, do they understand the first paragraph without asking questions? Technical writing skill is measured by how much a reader doesn't have to ask you.
What's the difference between good and great presentation skills?
Good: people understand your point. Great: they remember the story 3 weeks later. Story structure is learnable: setup (why this matters) тЖТ tension (what's broken) тЖТ resolution (what we do). Add one memorable visual (not a bullet list) per minute of talk. Practice removing filler words (ums, likes, you knows), record yourself, count them, target zero.
How do I write emails that actually get responses?
BLUF method (Bottom Line Up Front): lead with the ask in the first sentence. Example: 'Need your feedback on proposal by Friday.' Then: context, details, deadline. Tests show BLUF emails get 40% faster responses than context-first emails. Most people skim; give them the answer in the first 15 words.
Remote presentations, what's different from in-person?
Tighter pacing (attention drops faster on video), more frequent pause points (ask for questions every 3 slides, not at the end), close your laptop behind the desk (not visible), script your opening 30 seconds (kills nervous energy from blank start). Use breakout rooms instead of full-group Q&A, people speak more in small groups.
How do I get feedback on my writing without annoying people?
Use structured requests: 'Is my main point clear in the first paragraph?' (yes/no) beats 'Does this make sense?' Ask one question, not three. Find one trusted reader, could be a peer, could be a Slack bot like grammar checkers. The feedback loop: write тЖТ ask тЖТ incorporate тЖТ write again тЖТ same person тЖТ 3 cycles and clarity jumps.
What percentage of communication is visual vs verbal vs written?
Context-dependent: technical roles (80% written, 15% verbal, 5% visual), sales (50% verbal, 30% visual, 20% written), design (40% visual, 40% written, 20% verbal). Strength in the dominant mode matters most. But every senior role requires competence in all three, you'll present slides one day, write a strategic doc the next, communicate a decision via Slack.

рд╣реЗ рдХреМрд╢рд▓реНрдп рддреБрдордЪреНрдпрд╛рд╕рд╛рдареА рдпреЛрдЧреНрдп рдЖрд╣реЗ рдХрд╛, рдпрд╛рдЪреА рдЦрд╛рддреНрд░реА рдирд╛рд╣реА?

рдХрд░рд┐рдЕрд░ рдореЕрдЪ рдХрд░реВрди рдкрд╛рд╣рд╛ тАФ рдЖрдореНрд╣реА рдпреЛрдЧреНрдп рдорд╛рд░реНрдЧ рд╕реБрдЪрд╡реВ.

рдорд╛рдЭреНрдпрд╛рд╕рд╛рдареА рд╕рд░реНрд╡реЛрддреНрддрдо рдХреМрд╢рд▓реНрдпреЗ рд╢реЛрдзрд╛ тЖТ

рддреБрдордЪрд╛ рдЖрджрд░реНрд╢ рдХрд░рд┐рдЕрд░ рдорд╛рд░реНрдЧ рд╢реЛрдзрд╛

реи,релреирез рдХрд░рд┐рдЕрд░рдордзреНрдпреЗ рдХреМрд╢рд▓реНрдпрд╛рдВрд╡рд░ рдЖрдзрд╛рд░рд┐рдд рдЬреБрд│рдгреА. рдореЛрдлрдд, ~3 рдорд┐рдирд┐рдЯреЗ.

рдХрд░рд┐рдЕрд░ рдореЕрдЪ рдХрд░реВрди рдкрд╛рд╣рд╛ тАФ рдореЛрдлрдд тЖТ