Beyond Code: The Power of Thought Leadership in Engineering
summary
Argues engineers should push ideas beyond code by proposing concrete changes such as adopting DORA metrics, implementing an automation suite tweak from suppliers, and running a Miro-based risk register before release; cites marketing stats — 50% of C-suite value thought leadership more in downturns, 61% say it demonstrates product value, 48% want provocative ideas — and shows accessibility advocacy and hands-on testing as concrete moves that win stakeholder buy-in.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:52Why thought leadership matters
- 4:17Defining thought leadership
- 8:48Engineering beyond code
- 10:13Engineers as thought leaders
- 13:03Ripple effect of leadership
- 15:54Building your voice
- 18:39Introvert or extrovert both lead
- 19:43Employees and suppliers as leaders
- 20:45Start your leadership journey
- 21:28Q&A: Avoiding burnout
- 22:54Q&A: Introducing ideas
- 24:15Q&A: Balancing roles
related talks
58mHow to survive and thrive as an engineering leader
49mEngineering Leadership in Turbulent Times
47m‘Engineering' for Software - How to Amplify Creativity
22mWhat the Best Engineering Leaders Do Differently
38mWho is a Lead Engineer today
17mThe Soul of Engineering: How to be the Solution
42mThe Art of Engineering Diplomacy - Driving Significant Changes in Large Org.
30mEngineering in Overdrive: How to Thrive When Tech Evolution Goes Full Gas