The state of mobile release management.

How mobile releases really work, from the engineering managers and engineers behind them. Broken out by team size and release cadence.

Read the findings for a team like yours
Team size
How often you releaseWeekly
Small teams · Weekly releases
The stunt plane
93% of EMs lose three or more hours every week to status updates.
Read this segment
Key findings · All teams

What holds for every mobile team

These findings come from every engineering manager and engineer surveyed, across all team sizes and release cadences. For the numbers behind a team like yours, pick your segment above.

What a release costs

What a release costs mobile teams

A third of every release cycle goes to busywork.

~5 hrs lost per release, on average. Engineers lose about five hours per release to manual steps, context switching and coordination. 37% lose six or more.

What frustrates them · top three causes named
Manual steps49%
Context switching across tools42%
Coordination with other teams41%
Engineers who lose six hours or more per release37%
One release cycle
Release work67%
Busywork33%

Automation doesn't plug the leak.

50% of teams with significant automation still lose 6 to 10 hours per release. Half of teams with significant automation investment still lose 6 to 10 hours per release to low-value work.

Lose 6 to 10 hours per release · engineers
Significant automation50%
Little or none43%
All respondents37%

Most EMs call releases a significant source of frustration.

65% call the release process a significant or top source of frustration. Release coordination overhead is one of the causes they name most: the status updates, handoffs, approvals and chasing.

What frustrates them · top three causes named
Tooling and CI reliability61%
Release coordination overhead54%
Waiting on other teams40%
Every 100 EMs

Get the full report.

Every finding across all six segments, ready to pass along to your team.

Benchmark your team