Clear communication is making the important thing obvious to the reader or listener: intent, tradeoffs, and the next step. It shows up in writing, in meetings, in product copy, and in how you explain a technical decision without hiding behind jargon.
What clarity requires
- Audience first: who must act, decide, or understand after this message?
- Structure before polish: outline the claim, the evidence, the ask
- Plain language as a courtesy, not as a downgrade of rigor
Habits that help
- Write short first drafts; cut ruthlessly; read aloud when something feels fuzzy
- Prefer one main idea per message; split long threads into separate decisions
- Ask for a restatement when alignment matters: “What did you take away from that?”
See also (chapter 1)
- Asking the right questions for framing problems before you sell the solution
See also chapter 2: Introduction, Personal requirements and future assumptions, Macro-areas, Problems, products, and exclusions, Skills for exploration. Related notes: Ideation and connecting ideas, Creativity, Taste, judgment, and product sense, Marketing, distribution, and sales, Critical thinking and bias awareness, UI/UX and design execution.