Nearly every EM loses three or more hours a release cycle to status updates.
96% spend three or more hours, and the load grows with the company: 55% of EMs at companies of 5,000 to 9,999 employees spend six to 10 hours, against 13% at 500 to 999.
How mobile releases really work, from the engineering managers and engineers behind them. Broken out by team size and release cadence.
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.
Every release takes time out of the roadmap: EMs spend about five hours of each release cycle on status updates, and an engineer on release duty finishes about half of their sprint work. For a team releasing every two weeks, the status updates alone come to more than three working weeks of an EM's year.
96% spend three or more hours, and the load grows with the company: 55% of EMs at companies of 5,000 to 9,999 employees spend six to 10 hours, against 13% at 500 to 999.
On average, EMs expect 52% of planned sprint work from whoever is acting as release manager.
EMs estimate 48% on average, and the share rises with the number of people a release touches.
37% of engineers lose six or more hours per release to non-productive or low-value work.
Only 2% of EMs say fewer than one in 10 of their releases slip.
Release coordination overhead is a top-three frustration for more than half, second only to CI and tooling reliability. At companies of 5,000 to 9,999 employees, 80% call releases a significant or top frustration.
The cost comes from coordination, and it grows with every person a release touches. About 27 people act on a typical release, status is spread across tools and conversations, and the knowledge of how to run a release sits with a few people. As a company adds teams, approvals and apps, release dates get harder to hold just when the business needs the roadmap to be reliable.
77% of EMs say their releases need 21 or more people to take action before they go live, and 26% say more than 30.
EMs on those releases also carry more status work: 51% spend six or more hours a cycle on updates, against 12% when 20 or fewer people are involved.
On average, EMs can find status without asking someone or checking several tools 58% of the time.
Only 7% of EMs are very confident any engineer on the team could run a release end to end, and senior engineers run releases on 47% of teams.
Release problems reach leadership as late dates and as quality issues users see first, and a bad mobile release can't be pulled back instantly. When mobile drives much of the revenue, what happens in a release shows up in the business numbers, and EMs see as much risk ahead in their people as in their code.
Governance gates follow, and they grow with the company: 66% of EMs at companies of 5,000 to 9,999 employees name security, privacy and compliance approvals, against 33% at 500 to 999.
Post-release quality is a close second. EMs who run releases themselves hear more about visibility: 23% name it, against 13% overall.
On teams with a release tool, people risks lead by a wide margin: 74% of EMs name team sustainability and 72% knowledge concentration.
At companies of 5,000 to 9,999 employees, it edges past lack of adequate testing to the top of the list.
83% of EMs say better release processes would speed up their roadmap, and the teams least convinced have some of the worst numbers. EMs and engineers describe a release from two sides: EMs see the coordination around it and the slips, engineers the manual work inside it, and few engineers connect that work to missed deadlines. With each side seeing only part of the cost, nobody puts a number on the whole of it, so it rarely makes it onto the roadmap as something to fix.
“We've automated our releases.”
of engineers on teams with significant automation still lose 6 to 10 hours per release.
27% of engineers say their team has invested significantly in release automation, and they lose more of these hours than engineers overall (37%).
“Release inefficiencies don't cause our missed deadlines.”
of engineers see an incident that delays features or forces a hotfix at least once every three to five releases.
43% of engineers say release inefficiencies are somewhat unlikely to cause missed deadlines, and 31% are neutral. Yet 66% believe 60% or more of past incidents could have been prevented with a more transparent, centralized release process.
“Better release processes wouldn't change our roadmap.”
of releases slip on average on teams that expect little or no impact, against 42% across all teams.
17% of EMs expect little or no impact on the roadmap, and 33% of those teams report low or minimal investment in automated testing and QA, against 10% overall.
“Releases aren't a big frustration for us.”
of releases slip on average on teams running releases from chat or spreadsheets.
Only 28% of teams running releases from chat or spreadsheets call releases a significant or top frustration. Those teams lose 57% of release time to busywork, against 35% on teams with a release tool.
Six measures across the six segments. The darker the cell, the higher the share.
EMs spending three or more hours per cycle on status updates
Every finding across all six segments, ready to pass along to your team.