Bridging the gap between engineering and customer success
summary
A lightweight, repeatable program called Bug Dives documents and walks through specific customer bugs with a document with links and a live context → investigation → diagnosis → fix walkthrough that shows logs, code paths, hypotheses and the final patch. It shifts diagnostic work toward customer success by teaching concrete debugging steps, produces reusable troubleshooting notes, lasts multiple years at Nylas, and measurably increases team confidence and the speed at which similar bugs get resolved.
AI-written summary · about
chapters (9)
- 0:00Intro
- 2:07Knowledge Transfer Sessions
- 3:31Customer Issue
- 4:07The Gap
- 4:57Bug Exploration
- 5:48Bug Dives
- 7:45Three Components of a Strong Bug Dive
- 9:19Bug Dive Example
- 10:10Conclusion
related talks
27mDebugging product engineering organizations
26mDebugging Product Teams
06mHow Automated Tools Can Communicate Effective Strategies for Fixing Bugs
17mZero Bug Policy
11mWorking with sharp tools - A case study of Continuous deployment
32mOpening Keynote: The Good Bad Bug: Fail Your Way to Better Code
25mWhat I Learned
51mZero-bug policy success