Measuring Developer Goals

Alexander Polomodov and Alexander Kusurgashev review Measuring Developer Goals, Google's work on treating developers as users of an internal platform. A strict method sits behind the simple idea: researchers first connect goals with real work, then choose tools and quality signals.

Goals must be durable, consistent, relatable, sensical, and observable. Decomposition prevents a local indicator from being mistaken for the final outcome, but introduces a risk of local optimization. Google's process combines earlier research, expert interviews, engineer surveys, and validation against actual behavior.

The resulting map describes development stages and goals inside each one. It abstracts away from Jira, a wiki, or a particular code-review tool and treats development as a business process. Telemetry must follow an end-to-end journey through the toolchain, or a long loop will remain hidden behind green component statuses.

Code quality is broader than code review: it includes design, tests, coverage, and feedback. Surveys reveal whether dissatisfaction comes from overload rather than the tool, while logs show the actual journey. A universal product remains difficult, but a standardized company can already apply the method systematically and reduce the risk of unsupported decisions.