Communication

What it is

Communication at work is getting an idea, a decision or a problem into someone else’s head accurately enough that they can act on it: explaining to people with different context, disagreeing without stalling, and writing so the reader does not have to ask. It is a skill with techniques, not a personality trait.

Why it matters

Most “technical” delays are communication delays: a decision that was never clearly made, a risk nobody heard, a design that was understood differently by three people in the room. The cost is invisible because it looks like engineering time. It also compounds — the person who cannot explain their work does not get their work adopted, and the team that cannot disagree productively either avoids hard problems or argues about them in a meeting instead of solving them.

In this track

1. Explaining to any audience (08-soft-skills/01-communication/01-explaining-to-any-audience) — adjusting detail and vocabulary to the listener’s context without losing accuracy.
2. Disagreeing productively (08-soft-skills/01-communication/02-disagreeing-productively) — the harder case, worked as a scripted exercise.

Prerequisites

None.

Go deeper

• Teamwork & Collaboration (08-soft-skills/02-teamwork-collaboration) — the same skills applied to unblocking and disagreeing inside a team.
• Technical Presentation (08-soft-skills/09-technical-presentation) — the one-to-many version, where the room has to reach a decision.
• Technical Writing (04-product-process/08-technical-writing) — the written form of the same discipline.
• Mentoring (08-soft-skills/03-mentoring) — giving feedback, which is where most communication problems surface first.