The cost of interrupted work: more speed and stress

The cost of interrupted work: more speed and stress

This is the latest issue of my newsletter. Each week I cover the latest research and perspectives on developer productivity. Subscribe here to get future issues.


Join us on April 3rd: DX’s CTO, Laura Tacho, is hosting a live discussion with Nathen Harvey (DORA) on when not to use the DORA metrics.


This week I read The Cost of Interrupted Work: More Speed and Stress, a paper by Gloria Mark, Daniel Gudith, and Ulrich Klocke. This study investigated the effects of interruptions on work performance.?

Surprisingly, this study found that interruptions actually push people to complete tasks faster. But there's a catch – they also increase stress, frustration, time pressure, and effort.?

My summary of the paper

The researchers set out to measure the impact of interruptions on how quickly and effectively people can perform tasks. They also looked at whether the context of interruptions makes them more or less disruptive.?

To answer these questions, they asked a group of participants to complete a given task of writing and responding to a number of emails in a simulated office environment. Participants were periodically interrupted by a "supervisor" with questions, which they had to address immediately. The researchers then measured how quickly and accurately the participants completed their tasks. This was compared to a control group that didn't face any interruptions.

Here’s what they found:?

Interruptions push people to work faster

The first question was whether it matters if the interruption is related to the task at hand or not. The researchers found that this does matter: their study showed a significant difference between interruptions types and their impact on time to perform the task. “Different context” interruptions cause tasks to take longer.?

Surprisingly, they also found that participants who were interrupted completed the task faster than those without interruptions. The interruption context didn’t matter. The researchers thought this might be because people who were uninterrupted wrote longer emails, and they were right: participants with no interruptions wrote the longest emails. There was no significant difference, however, between the number of errors made. This suggests that while uninterrupted participants might put more time and effort into their emails, potentially making them higher quality (we don’t know - the study didn’t explore this), their accuracy was no better than that of participants who were interrupted.

They also cause more stress

During the study, participants gave feedback on their stress levels, frustration, effort, and the sense of time pressure they felt after tasks. These measures (stress, frustration, etc) are collectively considered mental workload measures.?

The analysis shows a significant difference in mental workload across interruption types: the participants who were interrupted had higher levels of stress, frustration, effort, and time pressure than those who were not interrupted.?

These results suggest that interruptions lead people to change not only work rhythms but also strategies and mental states. People compensate for being interrupted with a faster and more stressful working style.?

The authors offer their interpretation of the results from this study:?

“When people are constantly interrupted, they develop a mode of working faster (and writing less) to compensate for the time they know they will lose by being interrupted. Yet working faster with interruptions has its cost: people in the interrupted conditions experienced a higher workload, more stress, higher frustration, more time pressure, and effort. So interrupted work may be done faster, but at a price.”?

Final thoughts

This study provides another perspective on the impact of interruptions. Instinct might say that interruptions cause delays, but this study shows that people actually complete tasks more quickly when interrupted, albeit at the expense of increased stress and frustration.?


Who’s hiring right now

Here’s a roundup of new Developer Experience job openings:

Find more DevEx job postings here.


That’s it for this week. Thanks for reading.

-Abi

Richard Marmorstein

Developer Platform - Hume AI

11 个月

Is this measuring the effect of *interruption* i.e. forcing people to switch tasks, or is it just measuring the effect of reducing the time available to complete a task? They need a control group that doesn't get interrupted but gets time knocked off their clock at the same intervals as the treatment group is interrupted.

回复
Nikita Belokopytov

Engineering Strategy, Management, Coaching and Consulting

11 个月

Seems to make total sense. CTOs who have 16 stakeholders breathing down their necks have completely different work approaches from ICs with only 1-2 stakeholders to manage. That's also why for higher leadership positions, skills of self organization, stress management and an ability to distance themselves emotionally from their work are essential for success.

回复
Jen C.

Software Developer ????????♀? Technical Leader

1 年

New super powers emerging in the aftermath of prolonged and persistent interruption through switched priorities, dogpile initiatives, unclear requirements, micro-management of implementation approach, etc. ???

Maxim Saplin

ツ Technology, AI in Software Dev, Open-source

1 年

Taleb's, "Antifragile: Things That Gain from Disorder," discusses how certain systems and people actually benefit from volatility, shocks, and stressors...

Lucy Harrison

AI Innovator! Teaching product orgs how to incorporate AI into the all aspects of their biz!

1 年

Very interesting?

回复

要查看或添加评论,请登录

Abi Noda的更多文章

  • Operationalizing developer productivity metrics

    Operationalizing developer productivity metrics

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    4 条评论
  • Backstage is dominating the developer portal market

    Backstage is dominating the developer portal market

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    29 条评论
  • Attending an academic research conference

    Attending an academic research conference

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    1 条评论
  • Accelerating engineering velocity at Block

    Accelerating engineering velocity at Block

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    4 条评论
  • Rolling out developer productivity metrics

    Rolling out developer productivity metrics

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    4 条评论
  • Software Quality

    Software Quality

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    8 条评论
  • Measuring developer productivity: A clear-eyed view

    Measuring developer productivity: A clear-eyed view

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    3 条评论
  • Getting exec buy-in for developer productivity initiatives

    Getting exec buy-in for developer productivity initiatives

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    4 条评论
  • The best of engineering enablement in 2024

    The best of engineering enablement in 2024

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    3 条评论
  • 2024 benchmarks for the DX Core 4

    2024 benchmarks for the DX Core 4

    Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on…

    8 条评论

社区洞察

其他会员也浏览了