We Need Someone Technical on the Call
summary
Practical playbook for when to join technical calls: assess cost by converting salary to an hourly rate, prefer written support tickets with clear tried steps and a bolded action, rely on solid API documentation, and assemble exactly four people — technical contact, their technical counterpart, an advocate, and the second in command. Walk an API deprecation scenario: set agenda, record the call, stay on topic, elevate the second in command, create follow-up tickets and measure retro improvements so calls stop repeating.
AI-written summary · about
chapters (4)
related talks
45mHow to Communicate Technical Ideas to Non Technical Audiences
45mBuilding Relations with Technical Support
31mHow to Effectively Communicate Technical Ideas to Non Technical Audiences
52mTutorial: How to Advocate for Your Communication Needs
17mTalk the Talk: How to Communicate with the Non-Coder #bbuzz
40mCorporate Success: The Unwritten Curriculum
46mCracking the cadence of your software engineering 1:1s
45mHow to Communicate Technical Ideas to Non Technical Audiences