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)

โš– เชธเชพเชฅเซ‡ เชธเชฐเช–เชพเชฎเชฃเซ€ เช•เชฐเซ‹

Active ListeningPublic SpeakingConflict Resolution

โ“ 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.

เช–เชพเชคเชฐเซ€ เชจเชฅเซ€ เช•เซ‡ เช† เช•เซŒเชถเชฒเซเชฏ เชคเชฎเชพเชฐเชพ เชฎเชพเชŸเซ‡ เช›เซ‡?

เช•เชฐเชฟเชฏเชฐ เชฎเซ‡เชš เชŸเซ‡เชธเซเชŸ เช†เชชเซ‹ โ€” เช…เชฎเซ‡ เชฏเซ‹เช—เซเชฏ เชŸเซเชฐเซ‡เช•เซเชธ เชธเซ‚เชšเชตเซ€เชถเซเช‚.

เชฎเชพเชฐเชพ เชถเซเชฐเซ‡เชทเซเช -เชซเชฟเชŸ เช•เซŒเชถเชฒเซเชฏเซ‹ เชถเซ‹เชงเซ‹ โ†’

เชคเชฎเชพเชฐเซ‹ เช†เชฆเชฐเซเชถ เช•เชฐเชฟเชฏเชฐ เชชเชพเชฅ เชถเซ‹เชงเซ‹

2,521 เช•เชพเชฐเช•เชฟเชฐเซเชฆเซ€เช“เชฎเชพเช‚ เช•เซŒเชถเชฒเซเชฏ-เช†เชงเชพเชฐเชฟเชค เชฎเซ‡เชšเชฟเช‚เช—. เชฎเชซเชค.

เช•เชฐเชฟเชฏเชฐ เชฎเซ‡เชš เชŸเซ‡เชธเซเชŸ เช†เชชเซ‹ โ€” เชฎเชซเชค โ†’