Skip to content
Research Insights Made Simple
September 21, 2026 · Solo online talkResearch Insights Made Simple #30

Developer Productivity: Google’s Human-Centered View

Developer Productivity for Humans · Alexander Polomodov

/ Research Insights Made Simple #30 · Developer productivity

Slide contents

  1. 1. Developer Productivity: Google’s Human-Centered View

    Developer Productivity for Humans · Alexander Polomodov

  2. 2. Activity alone does not explain outcomes

  3. 3. Speed, ease, and quality belong together

  4. 4. Choose a model for the decision

  5. 5. A goal outlives its tools

  6. 6. A goal needs an understandable endpoint

  7. 7. Logs connect steps across tools

  8. 8. Surveys measure human experience

  9. 9. Disagreement between methods sharpens the question

    Logs: what happened

    Survey: how it felt

    Interview: why and in what context

    Experiment: an intervention’s effect

  10. 10. A useful metric supports a decision

  11. 11. Waiting changes developers’ behavior

  12. 12. Predictability helps people choose an action

  13. 13. Validate focus measures with people

  14. 14. Hybrid work depends on context

  15. 15. A first change does not complete onboarding

  16. 16. Mentor effort belongs in the outcome

    What the newcomer learned

    Who helped and at what cost

    What became reusable

    Where obstacles recur

  17. 17. Quality has four distinct objects

  18. 18. Refactoring needs an account of its benefit

  19. 19. Debt depends on the desired future

  20. 20. Removing debt changes the work mix

  21. 21. Debt management requires a decision

  22. 22. Real collaboration extends beyond reporting lines

  23. 23. Local acceleration can transfer costs

  24. 24. Creativity includes clever reuse

  25. 25. Sharing context builds team capability

  26. 26. Start AI design with developers’ needs

  27. 27. A useful pause leaves room for reflection

  28. 28. Effort saved can become effort shifted

  29. 29. Fast output can conceal understanding debt

  30. 30. A prototype still needs operational readiness

  31. 31. Producing code does not establish verification skill

  32. 32. The first month starts an improvement cycle

  33. 33. Trust in the program requires feedback

  34. 34. Evaluate the ability to achieve goals

    Goals give activity its meaning

    Consider speed, ease, and quality together

    Include the whole team and future work

    AI calls for verification and learning