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

- Paraphrase: Defaults in chat apps and email often let work messages reach people outside work hours (notifications, presence indicators, auto-sync), which makes it harder to keep clear time and attention boundaries when working remotely. - Key terms: - Notification — an alert (sound/visual) that a new message arrived. - Presence/status — indicator of whether someone appears “online”, “away”, or “do not disturb”. - Auto-sync/push — automatic delivery of new messages to a device without manual refresh. - Default setting — the pre-set option a tool uses until a user changes it. - Boundary breach — an interruption or expectation that work can happen outside set work times. - Why it matters here: - Defaults determine most experiences: Many people never change settings, so defaults decide who gets interrupted and when. - Specific defaults create expectations: If others see you “active” or get instant replies, they assume you’re available, increasing off-hours requests. - Health and productivity effects: Frequent off-hours interruptions raise stress and reduce recovery time, harming wellbeing and focus. - Common default settings that cause breaches (tool-specific) - Slack - Default: Push notifications for direct messages and mentions on all devices. - Effect: Instant interruptions across phone and desktop, including evenings. - Default: Presence shows as “active” when app is open. - Effect: Colleagues assume availability even if not working. - Default: Notifications persist until dismissed. - Effect: Ongoing pressure to respond quickly. - Microsoft Teams - Default: Chat and call notifications enabled; status auto-updates to “available”. - Effect: Spontaneous call/meeting pings and perceived constant availability. - Default: Meetings can be scheduled across recipient time zones without warnings (org setting). - Effect: Meetings land outside recipients’ work hours. - Email (Outlook/Gmail) - Default: Push delivery / sync enabled on mobile; new mail badge visible. - Effect: Work email appears immediately on phones, prompting checking outside work time. - Default: “Send” without scheduling; recipients often expect quick replies. - Effect: Cultural pressure to answer fast, even off-hours. - Cross-tool behaviours - Default: Calendar visible with full details and real-time status. - Effect: Others schedule meetings into perceived free slots or expect availability based on calendar presence. - Default: Organization-wide settings (admin) enable persistent presence/notifications. - Effect: Individual attempts to set boundaries can be undermined by org-level defaults. - Why these defaults are sticky and harmful - Many users never explore settings; defaults become norms. - Visibility (presence, read receipts) creates social pressure to respond. - Mobile push + always-on culture blurs work/personal time. - Practical design levers to reduce breaches (brief) - Gentle defaults: mute non-urgent notifications outside work hours. - Clear status options: make “off work” easy and visible. - Scheduled delivery: allow sending messages to arrive during recipient work hours. - Org policies: set meeting scheduling rules and default quiet hours. - Follow-up questions / next steps - Which population are you targeting (industry, role, time zones)? That affects which defaults matter most. - Do you want to study user behaviour, organizational policy, or design interventions? Pick one for a focused dissertation. - Further reading / references - The Design of Everyday Things — Don Norman (Background) (search: Don Norman Design of Everyday Things) - Search query: "notification defaults Slack Microsoft Teams work-life balance study" (use this if you need peer-reviewed empirical studies; exact papers vary by context)