Mastering Communication for Database Professionals: Up, Down & Lateral
summary
Argues that technical merit loses unless communication matches direction: use SCQA three-slide pitch and lead with business impact when communicating upward, frame proposals around fear and greed (time, cost, market share vs. revenue); involve peers by showing concrete deployment and DB changes when moving laterally; use full technical detail and task lists downward; control narratives externally to protect hiring. Shows two real cases: a 30-slide pitch rewritten to three slides and later adopted, and a data‑center→cloud migration that forced project cuts and an extended data center contract to buy time.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:45Know your audience
- 4:16Upward communication
- 8:27Leadership buy-in
- 10:56Lateral communication
- 13:24Downward communication
- 14:50External communication
- 16:36Interactive session
- 19:10Management motivators
- 21:51Unrealistic expectations
- 24:51Deadline negotiation case
- 27:43Closing & Q&A
related talks
17mEmpowering Engineers With a Database DevOps Strategy
38mGetting Along With Your Db Ops Team
27mDevOps and the Database Bottleneck
30mWorking with DBAs in a DevOps World
31mDevOps Practices for the Database Team
11mLightning Talk: Continuous Delivery…except for Database Changes
44mAgile Data Warehousing/Business Intelligence: Addressing the Hard Problems
41mLightning Talks