It's the Empathy, Stupid!
summary
Argues that management only cares about revenue, cost and risk and shows how to translate developer requests into those terms: converting a 5–10 minute dev tooling delay into €4,000/month saved convinced leadership to buy RAM, costing analysis flips a one-hour full-team sprint review into a €750 vs €600 efficiency paradox, a ride‑share feature becomes €60,000/month by estimating 20,000 extra rides at €25 with a 12% fee, and unpatched libs are framed as a 2 million euro risk to trigger loss aversion; use SWAG and one‑hop OKRs.
AI-written summary · about
chapters (14)
- 0:00Introduction and welcome
- 2:33Common management conflicts
- 6:49Sender-receiver problem in communication
- 12:10Management disconnect and Excel sheets
- 16:52Changing communication with leadership
- 21:11Senior management’s core priorities
- 23:17Speaking leadership’s language
- 26:09Calculating costs and revenue impact
- 31:10Feature prioritization battles
- 35:03Quantifying technical debt risks
- 38:14Engineers must think in business value
- 40:42Team goals aligned with company objectives
- 43:14Cheat sheet for leadership arguments
- 44:39Q&A and closing
related talks
45mBeyond Estimates
17mCreating Happy Engineers - Anecdotes from the Trenches
01h 01mLies Developers Tell Themselves
18mFrom developer productivity to engineering impact
20mHow to keep everyone happy (on a shoestring)?
55mAgile Engineering
56mGetting Buy-In: Overcoming Larman's Law
13mLeading with empathy: Turning good developers into great engineers