Lena Reinhard at LeadDev West Coast 2023
summary
Claims a shift from vague “efficiency” to concrete tradeoffs between Effectiveness and efficiency and gives a repeatable process: map the org, set clear success criteria (the flashlight), measure current state (GPS) and watch changes. Recommends choosing 3–4 shared metrics (mix leading/lagging, e.g. DORA signals), asks HR for cost per employee hour, runs biannual reviews, weekly boss updates via a push-template, a 30‑minute Friday strategy window, and publishes a cheat sheet and bitly link with templates and metric guidance.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 4:14Engineering leadership core
- 9:52Efficiency vs effectiveness
- 11:38Steps to team efficiency
- 17:19Organizational success criteria
- 23:21Choosing team metrics
- 25:09Team performance review
- 26:36Daily efficiency practices
- 29:48Adapting strategies
- 32:00Summary
related talks
44mEnhancing the Performance of Engineering Teams
47mCan We Measure Developer Productivity?
43mMeasuring Developer Productivity: The Good, the Bad and the Data
33mMeasuring Developer Productivity: the good, the bad and the data
45mShift Your Leadership
31mHow Do You Measure Devel...
32mHow to evaluate team effectiveness with a data first approach
33mBeyond developer productivity: what's next?
