Time to first change
Also known as Time to first contribution, First change time
Definition
Time to first change is the elapsed time from a defined starting event, such as joining a team or creating a service, to a developer's first accepted code change in that environment. The start and completion events must be defined for the comparison to be meaningful.
Define the first change
The measure can begin when a developer joins a team, receives repository access, starts a service, or enters an onboarding workflow. It can end when a pull request opens, merges, deploys, or creates a user-visible result. Those boundaries answer different questions.
For example, time from repository access to a first merged change measures part of the contribution path. It does not measure whether the developer understood the architecture or whether the change was valuable. A tiny documentation change and a production feature also carry different context.
Use the distribution to find friction
Look at median and tail values, then inspect the stages between the start and first change. Long tails may indicate missing access, unreliable setup, unclear ownership, unfamiliar code, review queues, or work that was not ready to begin. Compare new starters with similar roles and keep the work type visible.
The measure is most useful when it leads to a concrete improvement, such as a better service template, a clearer runbook, or a second reviewer. Do not use it as a target for individuals.
How Weave can help
Weave can show the repository and review portion of the first-change path, including waiting and quality patterns around initial contributions. Platform telemetry and qualitative onboarding feedback complete the path and help explain why the time changed.
How this relates to Weave
Weave can help teams inspect the first accepted changes and the workflow around them, including change size, review waiting, quality, and rework. It does not observe every onboarding step, so pair it with platform events, documentation feedback, and conversations with new team members.
Explore Engineering intelligence