~/talk

Building a Culture For Developer Productivity

links:none on file
links:none on file
slides:none on file

Argues that productivity means high-quality software at speed and that leaders should measure blockers not output, run small developer focus groups and short surveys, and track whether managers act on results; Atlassian reports a 25% improvement in developer satisfaction after this approach. Recommends milestone-based delivery and carving time for tech debt, uses feature-flagging and experimentation tooling (Split) and Harness engineering insights to surface bottlenecks, and says developer-facing SDK work and iterative releases measurably improve outcomes.

AI-written summary · about

  1. 0:00Developer productivity culture
  2. 3:43Defining productivity
  3. 7:11Why output metrics fail
  4. 8:39Leadership role in productivity
  5. 11:25Managers undermining joy
  6. 16:24Actions for culture
  7. 18:29Developer feedback surveys
  8. 22:16Psychological safety in surveys
  9. 25:26Practical survey changes
  10. 27:31Measuring developer experience
  11. 29:37Impact on external customers
  12. 32:25One key step for leaders
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.