The Empowered Software Engineer - unlocking engineering potential
summary
Claim: most companies run feature factories so 37% of their software is never or rarely used and of the remaining 63% about 80% of features are unused. Teams get problems not tickets and must be assigned problems not tickets, use design thinking and the business model canvas, master goal setting and decision making, and accept accountability for outcomes. Examples: Netflix pivots to streaming, Kodak fails to pivot, Zappos wins by adding free returns. Success requires discovery, prototypes, measuring customer metrics, and iterating until it works.
AI-written summary · about
chapters (16)
- 0:00Empowered software engineers
- 2:54Digitization demands empowered engineers
- 9:29Cost of unused software
- 13:44How top companies innovate
- 15:54Feature factory trap
- 17:24Empowered engineering teams
- 23:27Engineers beyond coding
- 28:29Six skills for engineers
- 30:37Goal setting for engineers
- 34:33Decisions with incomplete info
- 38:48Design thinking in engineering
- 43:27Empathy for better products
- 47:31Accountability over outputs
- 47:52Business models for engineers
- 51:01Constraints and leverage
- 57:18Monday takeaways
related talks
47m‘Engineering' for Software - How to Amplify Creativity
01h 01mEngineering for Software - How to Amplify Creativity
31mImproving engineering effectiveness: A journey for the entire organization
35mEngineering for Software - How to Amplify Creativity
25mEgoless Engineering
43mIncorporating Engineers into the Entire Product Lifecycle
46mPanel Discussion: The Agentic Software Factory That Enterprises Actually Need
46mLeading with Radical Transparency: Empowering Product Teams