Talk the Talk: How to Communicate with the Non-Coder #bbuzz
summary
Clear claim: technical teams must translate core ideas into concrete, testable messages for non-coders to get resources and domain input. Practical techniques include diagrams with highlighted paths, demos and interactive questions, and pretesting explanations on a naive listener. Examples: Apache Drill shifts messaging from architecture to user scenarios; India’s Aadhaar uses MapR low-latency ms authentication at ~1.2 billion identities, forcing cross-team clarity. Homework assignment: create one diagram and a five-minute pitch and validate it with a non-technical person.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:39Your message can get lost in technical jargon
- 5:27Communication helps set reasonable expectations • What resources are required - will your team have what it needs?
- 5:38Domain knowledge is important: Example is loT
- 6:15Example: Changing a society
- 9:50Best ways to communicate
- 12:33Essential Concepts: The core of what you do Not the same as generalized statements
- 13:05Build understanding in layers
- 13:24Example: Practical Machine Learning
- 14:48Co-occurrence Analysis
- 14:59From Indicator Matrix to New Indicator Field
- 15:56Lessons - Summary It's worth fixing the problem • Find the essential concepts in what you do
related talks
45mHow to Communicate Technical Ideas to Non Technical Audiences
45mHow to Communicate Technical Ideas to Non Technical Audiences
31mHow to Effectively Communicate Technical Ideas to Non Technical Audiences
42m“Non-assertive” Conversations with the Business
31mStorytelling for Engineers
30mHow to talk like an Engineer
45mTelling Your Technical Story
51mTech talks: Upload your ideas to other human beings