Abstract
Customers asked for “fewer alerts” more often than for any other notification change this spring. We interviewed eight people on distributed teams to learn what they meant. The request covered three different needs. People with caregiving duties wanted to know urgent messages would be held for them. Team leads wanted to hand the rules to their team, so exceptions stopped coming through them. On-call engineers wanted only the messages that change the diagnosis during an incident. A single global quiet-hours switch serves none of these well. We recommend three explicit controls: hold, delegate and filter.
How we listened
- Participants
- 8People on teams that span two or more time zones. Details in the interview index.
- Recruitment
- PanelCommon Thread’s customer research panel, screened for a request for fewer alerts in the last 90 days.
- Method
- 45 minRemote, semi-structured interviews. Each participant walked through their last week of notifications on a shared screen.
- Window
- 14–25 JulAll eight interviews took place in July 2026, recorded and transcribed with consent.
- Analysis
- 2 researchersAffinity mapping, first separately, then together. Disagreements were resolved in a joint review; three notes changed group.
- Limits
- Small sampleSelf-selected, existing customers only. Read the limitations before quoting a count.
The Caretaker needs assurance, not silence
Four participants described caregiving duties outside work: school pickups, a parent’s hospital appointments, a child at home sick. None of them asked to hear nothing. They asked to know that if something urgent arrives while they are away, someone has it, and it will reach them within a known time.
[I-3 · 00:14:22]“Urgent can still wait ten minutes if I know it is held.”
[I-2 · 00:21:05]“I turn everything off at pickup, and then I check my phone at every red light anyway.”
[I-7 · 00:31:48]“What I need is someone to have it. Not for it to disappear.”
What one switch does to them
The switch hides messages without saying what happens to them. Three of the four check the app during their own quiet hours because nothing tells them an urgent message is covered [I-2] [I-3] [I-7]. The fourth has stopped using quiet hours: “If it goes quiet, I assume I’ve missed something” [I-5]. Silence without a guarantee costs them more attention, not less.
The Lead needs a policy the team owns
Three participants lead teams of between 6 and 14 people. They did not ask for fewer alerts for themselves. They asked to stop being the person who decides, message by message, whether something may interrupt someone else’s evening.
[I-5 · 00:09:37]“I want the team to choose without asking me.”
[I-1 · 00:27:10]“Every exception to quiet hours comes to me as a DM. I’ve become the switch.”
[I-6 · 00:18:44]“We made a rule for the night shift, but it lives in a pinned message nobody can enforce.”
What one switch does to them
The switch is personal. It has no place for a team rule, so the rule lives in chat and the lead enforces it by hand. I-1 counted eleven exception requests in the week before the interview. Two of the three leads had written their team’s rules into a pinned message, and neither could tell who had read it [I-1] [I-6].
The Specialist needs the few messages that matter
Three participants carry on-call duty for production systems. During an incident they cannot turn quiet hours on, and they do not want to. They want the channel to show what changes their understanding of the problem: a new error, a confirmed cause, a decision.
[I-4 · 00:12:03]“Show me only what changed the diagnosis.”
[I-8 · 00:33:19]“During an incident the channel is forty people asking for an update. I mute it and miss the one line that matters.”
[I-7 · 00:24:56]“Quiet hours don’t apply to me when I’m on call. That’s exactly when I need less.”
What one switch does to them
The switch is all or nothing, and on call it has to stay off, so they get everything. All three had muted an incident channel at least once to think, and two missed a status change while it was muted [I-4] [I-8]. What they lack is a view of the incident that leaves out every message that did not change it.
Why one switch fails all three
A global quiet-hours switch answers one question: should I be interrupted right now? The three negotiations ask different questions. The Caretaker asks who has a message while they are away. The Lead asks who decides what counts as urgent. The Specialist asks which messages change the work in front of them. A yes-or-no setting carries none of these. Seven of eight participants had built a workaround – checking anyway, pinned rules, muted channels – and the eighth had stopped using quiet hours.
The three negotiations describe situations people are in, and one person can be in more than one. I-5 leads a team and has a child at home; I-7 is on call two weeks a month and a parent the rest of the time. A setup that asks people to pick a type would fail both. The controls have to combine: a hold after 17:00, inside a team rule, with a filter that switches on during an incident.
| Control | Asked for by | Answers | Must guarantee |
|---|---|---|---|
| Hold | Caretakers I-2, I-3, I-5, I-7 |
Who has my messages while I am away? | An urgent message goes to a named backup after a set wait (participants suggested ten minutes) and reaches the person at a stated time. The sender sees that it is held, and until when. |
| Delegate | Leads I-1, I-5, I-6 |
Who decides what counts as urgent? | The team sets one rule that every member can see. Changes are logged with who made them. Exceptions follow the rule, not a message to the lead. |
| Filter | Specialists I-4, I-7, I-8 |
Which messages change my work? | During an incident, only status changes, new findings and decisions come through. Nothing is deleted; the rest arrives as one summary when the incident closes. |
What this study cannot tell us
- Eight people from our own panel. Panel members are existing customers who opted in to research. They are more engaged than average, and all eight already used notification settings. We heard nothing from people who left Common Thread over notifications.
- Caregiving came up unprompted. The guide did not ask about duties outside work, so the Hold group may be larger than four.
- No incident was observed. The three on-call participants described past incidents from memory, and none was interviewed within a week of one. Filter needs here are recalled, not watched.
- Small teams only. All three leads manage 14 people or fewer. We do not know how Delegate works where an admin or compliance team owns notification policy.
- Self-reported, not measured. “I check anyway” has not been compared with app-open data during quiet hours. The baseline in the next steps fixes this.
- Both researchers work on notifications. We may have been primed to hear controls. A researcher from outside the team reviewed the affinity map but did not code transcripts.
Who we talked to
Attribution is role, team type, tenure, company size and interview date. No names or pseudonyms; numbers follow interview order. The ink marks show which negotiations each person voiced.
- I-1
Engineering manager · platform team, 3 time zones
- Tenure
- 4 years
- Company size
- 1,000+
- Interviewed
- 14 Jul 2026
- Voiced
- Delegate
- I-2
Support specialist · customer support team, 3 time zones
- Tenure
- 2 years
- Company size
- 51–200
- Interviewed
- 15 Jul 2026
- Voiced
- Hold
- I-3
Account manager · sales team, 2 time zones
- Tenure
- 1 year
- Company size
- 11–50
- Interviewed
- 16 Jul 2026
- Voiced
- Hold
- I-4
Site reliability engineer · infrastructure on-call rotation, 4 time zones
- Tenure
- 5 years
- Company size
- 1,000+
- Interviewed
- 17 Jul 2026
- Voiced
- Filter
- I-5
Design lead · product design team, 4 time zones
- Tenure
- 6 years
- Company size
- 201–1,000
- Interviewed
- 21 Jul 2026
- Voiced
- Delegate Hold
- I-6
Operations lead · logistics operations team, 2 time zones
- Tenure
- 3 years
- Company size
- 51–200
- Interviewed
- 22 Jul 2026
- Voiced
- Delegate
- I-7
Backend engineer · payments team with on-call rotation, 3 time zones
- Tenure
- 2 years
- Company size
- 201–1,000
- Interviewed
- 23 Jul 2026
- Voiced
- Filter Hold
- I-8
Support engineer · escalations team, 5 time zones
- Tenure
- 4 years
- Company size
- 1,000+
- Interviewed
- 25 Jul 2026
- Voiced
- Filter
Direction
Replace one global quiet-hours switch with three explicit controls: hold, delegate and filter.
Next steps
Measure two workarounds before changing anything: app opens during a person’s own quiet hours, and incident channels muted during an active incident.
- Owner
- Product analytics
- By
- 14 Aug 2026
Test paper prototypes of hold, delegate and filter with six of the eight participants. Each session shows both precedence orders from the tension below.
- Owner
- Research
- When
- Week of 17 Aug 2026
Decide whether a team rule or a personal hold wins, using the test results, before any Delegate design work starts.
- Owner
- Notifications design lead
- By
- 28 Aug 2026
Open the research tension
Which wins: the team’s rule or my hold?
Delegate and Hold collide. When a team rule says an incident reaches everyone, and a person’s hold says it goes to their backup, one of them has to give way. Participants split. Two leads wanted the team rule to win: “If the building’s on fire, the rule is the rule” [I-1] [I-6]. Two caretakers said a hold that a team rule can break is no hold at all [I-2] [I-3]. I-5 is both a lead and a caretaker, and gave both answers in the same interview [I-5].
We have not resolved this. The August concept test will show participants both orders and ask what they would expect to happen, and what they would do if it did not.