Storytelling for Engineers
summary
Claims that applying a simple storytelling framework to engineering communication increases understanding, voluntary compliance, and memory, and reduces follow-up noise; shows a concrete formula: TL;DR one-line summary then X changed in Y due to Z, include explicit action and labeled graphs. Uses examples from CI and remote test execution (Bazel, distributed build and linking farms, CI “Q”), cites that only ~1 in 10 emails is useful and that remote tests save hundreds of seconds per run, and gives templates and PR-link practices that actually cut questions.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:08The problem with email
- 4:41Storytelling as a solution
- 7:05Knowing your audience
- 11:07Crafting the narrative
- 12:48Analyzing bad communication
- 16:22Data vs. insights
- 19:28A formula for better emails
- 23:14Summary and takeaways
- 25:45Q&A session
related talks
23mStorytelling And Tech
24mStorytelling with data
45mHow to Communicate Technical Ideas to Non Technical Audiences
40mStorytelling for Technical Products - What We Can Learn from
31mHow to Effectively Communicate Technical Ideas to Non Technical Audiences
34mThe Art and Science of Communication
01h 00mHow to Pitch Your Ideas so People Listen
15mIt Works on My Machine: Why Engineers Are Misunderstood (and What They Can Do About It)