Atlassian's 2024 survey finds developers and their bosses blame different things for lost time
A 2024 survey of more than 2,100 people shows engineers and their leaders disagree on why work drags, and that matters before you buy any AI tool.
The short version
- The survey covered over 2,100 developers and managers across industries worldwide.
- 97% of developers say they lose significant time to inefficiencies.
- Sixty-nine percent lose eight hours or more per week, which Atlassian puts at 20% of their time.
- Developers blame tech debt and thin documentation; leaders point to understaffing and the growing scope of the job.
- Leaders see AI as the best fix, but two out of three developers report no significant gains yet.
Why it matters
Companies are spending heavily on AI tools for their engineers, and this survey suggests the people buying and the people using may not agree on the problem. The same gap can show up in any workplace. Asking the people who do the work where their time goes is cheap, and it can keep a budget from going to the wrong fix.
An older study, back in the conversation
A comment on an Atlassian blog post pointed readers back to the company's State of Developer Experience Report from 2024. This is not new research, but its findings still bear on how companies decide what to fix. As atlassian.com described it, the work was done with DX, a company that sells software for measuring how engineering teams perform, and with Wakefield Research.
The survey reached more than 2,100 developers and managers across a range of industries around the world. Its aim was to compare what the people writing software experience day to day with what their leaders believe is happening.
"Developer experience" here means how much friction a developer meets in daily work: slow tools, unclear instructions, old code that is hard to change. It is a different thing from perks like free snacks, and Atlassian says leaders now understand that.
Where the time goes
The headline finding is about lost time. Atlassian reports that 97% of developers lose significant time to inefficiencies. Sixty-nine percent lose eight hours or more every week, which the company calculates as 20% of their working time.
Fewer than half of the developers believe their leaders know this is happening. Fewer than half also think their organization treats developer experience as a priority. So the problem is costly, and many of the people living with it feel unseen.
The survey also asked why time is lost, and here the two groups split. Developers mostly name tech debt, meaning old shortcuts in the code that make every later change harder, and a lack of good documentation. Leaders instead point to understaffing, the widening of what a developer is expected to do, and the amount of technical knowledge the job demands.
Atlassian's concern is practical. If leaders diagnose the wrong cause, they may spend money and effort on fixes that do not touch what developers actually struggle with.
The AI expectation gap
The sharpest example of the mismatch is artificial intelligence. Leaders in the survey believe AI is the most effective way to raise both productivity and developer satisfaction. Two out of three developers say they are not yet seeing significant productivity gains from AI tools.
Atlassian does not argue that AI is useless. It says AI could help with tech debt, repetitive chores, gaps in documentation and constant interruptions. But it says leaders need to look beyond tools that write code, and study each pain point on its own before choosing a solution.
That fits a wider pattern: a tool can look obviously useful from the top of an organization and feel marginal at the desk where the work happens.
Why leaders' metrics fall short
The report adds that most leaders admit the numbers they track do not measure developer productivity well. Many also appear to treat productivity and experience as the same thing, though they are related but not identical. Atlassian stresses that both depend heavily on context, and no single metric or set of metrics fits every team.
There is also a retention angle. Developer experience matters to 63% of developers when they decide whether to stay in a job. Two out of three consider leaving when they are unhappy with it.
Atlassian offers its own numbers as evidence that investing pays off. It says developer satisfaction at the company rose 25 percentage points over two years, from 49% to 74%. This is the company's account of its own results, so treat it as an example, not independent proof.
The simple fix on offer
Atlassian's main advice is plain: ask developers what slows them down. The company argues that developers want to be productive and will say what gets in the way if asked. It compares skipping this step to hunting around the house for a phone that is already in your hand.
It also says progress will not be a straight line, because incidents and events will dent morale from time to time. What counts, in its view, is that developers feel their problems are understood.
One caution: this is a vendor-sponsored survey, and the source gives few details on how respondents were chosen or split between developers and managers. The central pattern is still worth noting, since it is easy to test in your own team.
What to watch
- Whether newer surveys show developers reporting real gains from AI tools, or the gap with leaders persisting.
- Whether companies start measuring developer experience directly instead of relying on productivity numbers alone.
Try it
Before your team adopts a new tool, ask the people who will use it for their top three time-wasters, and compare their list with your own guess.
Sources and links
First reported by atlassian.com. Written by the SI Agent News Desk from the reporting above.Written with AI from the source above. Every number is checked against the source. Spot a mistake? Corrections.
Liked it? Say why
Add a line for other readers.
No account needed. We never show your email. Comments with links, ads or abuse are held and not shown. Your comment shows after a quick check.