How could remote work digital boundaries be explored in relation to ux, digital design and technology for a 4800 word dissertation topic

- Paraphrase Do Not Disturb (DND) is a mode that suppresses incoming notifications (calls## Do Not Disturb (DND) — how defaults vs customization affect evening interruptions - Paraphrase Do Not Disturb (, messagesDND) is a mode that suppresses notifications. Whether DND is set as a default or left for users to customize strongly affects how, app often people get interrupted in the alerts). evening. - Key terms - In the Do Not Disturb context of (DND) remote work — mode that silences or, D hides incoming notifications and alerts. - DefaultND helps — the setting a prevent work system uses automatically unless the user-related interruptions changes it. - during evenings Customization — when a user changes settings (e by blocking.g., schedule, exceptions). or sil - Interruptions — notifications thatencing notifications break attention until the or activities. - user turns Boundary management it off — how or a people control access to scheduled window their time ends. and attention- Key. - terms Why it - matters here Do Not Disturb - Defaults (DND) shape behavior — a: if setting that DND is off mutes by default, many or hides users stay exposed to notifications to evening notifications due to avoid interruptions inertia (status quo bias).. - - Customization enables fit: users can schedule DND for their local evening or allow exceptions Default — (family, urgent work), the pre reducing unwanted interruptions. - Fr-set behavioriction and discoverability matter: a system if customizing DND is hard to find or complex, users won’t set it even when uses unless they want fewer interruptions. - Social and the user organizational norms interact: even with DND on, coworkers’ expectations ( changes itimmediate replies) can lead users to disable or override it. - Follow-up questions / next steps - Do you want to focus empirically (logs, diaries) or designally (UI (e patterns, presets) in a dissertation? - Which user groups matter most (parents.g.,, different DND time zones, shift workers)? off by default).- Further - Customization — reading / user changes references to settings - (e.g., The Design scheduling D of EverydayND from 7 Things —pm–7am Don Norman). - (Background Notification suppression — the) technical ( blockingsearch: or hiding of alerts Don Norman Design of while DND is Everyday Things active.) - Boundary - management — Search query how people for empirical control access to their time and attention. studies: "Do- Why Not Dist it matters here urb defaults - Reduces customization evening evening interruptions: D notifications UXND directly study" prevents notification pings that pull people back into work after hours. - Defaults shape use: if DND is off by default, many users remain exposed to evening alerts; a helpful default (e.g., nightly DND) protects most users without requiring effort. - Customization increases fit: scheduled DND, exceptions (e.g., urgent contacts), and quick toggles let people tailor protection to their needs and contexts (time zones, caregiving duties). - Usability trade-offs: too many options or hidden DND controls increase friction, so users may not enable helpful protections; poor defaults can perpetuate overwork norms. - Follow-up questions / next steps - Do you want to study defaults (what most users experience) or customization (how users tailor DND)? - Consider a simple empirical design: compare evening interruption rates and perceived boundary control across (a) default-off, (b) default-on nightly DND, and (c) user-scheduled DND. - Further reading / references - The Design of Everyday Things — Don Norman (Background) (search: Don Norman Design of Everyday Things) - Search query for empirical studies: "Do Not Disturb notifications remote work evening interruptions UX study"