Main content
Fatigue, boredom, and objectively-measured smartphone use at work
- Jonas Dora
- Madelon van Hooff
- Erik Bijleveld
- Sabine Geurts
- Michiel Kompier
Date created: 2018-10-12 12:00 PM | Last Updated: 2021-03-11 11:18 PM
Category: Project
Description: Nowadays, many people take short breaks with their smartphone at work. The decision whether to continue working or to take a smartphone break is a so-called labor vs leisure decision. Motivational models predict that people are more likely to switch from labor (work) to leisure (smartphone) the more fatigue or boredom they experience. In turn, fatigue and boredom are expected to decrease after the smartphone was used. However, it is not yet clear how smartphone use at work relates to fatigue and boredom. In this study, we tested these relationships in both directions. Participants (N = 83) reported their current level of fatigue and boredom every hour at work while an application continuously logged their smartphone use. Results indicate that participants were more likely to interact with their smartphone the more fatigued or bored they were, but that they did not use it for longer when more fatigued or bored. Surprisingly, participants reported increased fatigue and boredom after having used the smartphone (more). While future research is necessary, our results a) provide real-life evidence for the notion that fatigue and boredom trigger task disengagement and b) suggest that taking a short break with the smartphone may have phenomenological costs.
This is the project for Fatigue, boredom, and objectively-measured smartphone use at work
Analysis and results contains the analysis script as well as the entire workspace for the study.
Data contains the data file for the study. These contain the demographics, the hourly self-reports, and the calculated smartphone use data for each participant. Additionally, it contains a code book that explains …
Files
Files can now be accessed and managed under the Files tab.
Citation
Recent Activity
Unable to retrieve logs at this time. Please refresh the page or contact support@osf.io if the problem persists.