The studio sat above a bakery, and by mid-morning the whole room smelled of cardamom and the whole room was also, somehow, failing to get anything done. Imagine a five-person design and web shop, invented for this telling but built from habits small teams genuinely fall into, that decided to try setting quiet hours for notifications and learned what the practice can and cannot do.
The winter nobody finished anything
The studio’s founder noticed the pattern first, though nobody wanted to name it. Projects that should have taken a week were taking three. Everyone was clearly working, since the shared chat scrolled constantly, but the deliverables kept slipping. In the team’s weekly meeting a developer said, half joking, that they had spent the morning “answering things” and could not say what they had actually built.
The founder handed out sticky notes and asked everyone to tick a mark for one day: each time something pulled them off a task, make a mark. By evening, the notes were covered. One designer had stopped counting after a few dozen marks. The tally did not blame anyone. It simply showed that the studio’s tools had been left on their loudest settings, and that each person’s afternoon belonged to whoever pinged first.
The proposal
The idea that came out of that meeting was modest. Nobody wanted to ban chat or make the studio feel like a library. Instead the team agreed to try daily quiet hours: a block in the morning and a shorter one after lunch, during which chat, email and project-tool alerts would be silenced for everyone. Outside those blocks, people would reply as usual.
The sceptic in the group, a producer who spent most days talking to clients, raised the obvious objection. What if a client needed something at once? The team’s answer became the most important part of the whole arrangement: a short exception path. A phone call would always come through. A specific channel, used only for emergencies such as a site being down, would be allowed to alert at any hour. Everything else would wait.
What went on the exception list
After some debate, the list had three entries:
- Phone calls to the studio’s shared number, which the producer would answer in rotation.
- The monitoring alert for client websites, which pointed to whoever was on call that week.
- A direct message from the founder, used so rarely that everyone agreed it counted.
Newsletters, social notifications, general chat, tool comments and calendar suggestions were all set to wait.
The first week was uncomfortable
It would be tidy to report that the quiet hours worked at once. They did not. On the first morning the developer kept reaching for the phone out of habit, and the designer admitted to feeling oddly guilty about being unreachable. A client emailed twice, and the producer, tempted to jump in, held back until the block ended and then replied to both at once. Neither client minded in the slightest.
By the third day something shifted. The room was quieter in a way that felt more like concentration than silence. The developer finished a feature that had been hanging around for days. The designer remarked that they had completed an entire layout without once losing the thread. Nobody made a speech about it. They simply carried on.
What the team learned about timing
The studio’s experience highlights a distinction that is easy to overlook. A quick answer is not the same as a useful answer. When a message arrived during a quiet block and waited an hour or two, the eventual reply was often better: the sender had sometimes solved the problem themselves in the meantime, or had added the missing detail. Waiting turned several vague questions into clear ones.
The team also found that quiet hours changed how people wrote messages. Knowing a reply might take a while, they started including the full context, the deadline and the specific question in the first message. Threads shortened. This was a side effect no one had planned for, and it saved more time than the silenced alerts did on their own.
Those who like to think about how businesses plan their digital services may find a parallel in the way a roadmap for new clients of digital services sets out stages and expectations in advance. Quiet hours are a similar kind of advance agreement, only applied to attention rather than deliverables.
The hiccup in month two
Stories like this tend to leave out the setback, so here it is. In the second month, a client’s contact form stopped working during a quiet block. The monitoring alert was on the exception list, so it fired, and the on-call developer fixed the problem within the hour. The system worked. But the producer noticed that two other things the team had assumed were urgent, a request to move a meeting and a question about invoice wording, had also been silenced, and that nothing bad had come of it.
The conclusion the team drew was to leave the exception list alone. Instead, they added a ritual: when a quiet block closed, one person scanned the muted channels aloud for anything that had been missed. In practice the scan took a couple of minutes and rarely turned up anything pressing, which was itself reassuring.
Learning during the quiet hours
One designer began using part of the morning block to study something outside the usual client work. They were curious about aviation and had been browsing the Wingversity site, which describes itself as an online learning platform aimed at aviation careers, noting only that the site calls itself a preview with sample content. Whether the interest led anywhere was beside the point for the studio. What mattered was that a protected block gave a curious person space to explore without interruption.
The founder took the hint and added a rule: the first quiet block of the week could be used for learning of any kind, not just client work. Morale, which had sagged through the winter, picked up noticeably.
A conversation about the client side
Early in the second month, the producer asked for ten minutes in the weekly meeting to talk about clients. The worry was not that anyone was being neglected but that expectations were unspoken. So the team drafted two short sentences for every proposal and email footer: replies are sent in set windows each working day, and for a true emergency, ring the studio line. Clients who read it mostly nodded. One said it was a relief to know when to expect an answer, rather than guessing whether silence meant trouble.
Looking back at what changed
After a quarter, the founder reviewed the team’s output and, more importantly, asked everyone how the days felt. The replies were consistent. People reported fewer scattered afternoons. They said they could tell when they were at their best and could protect that time. The developer summed it up in one line that went on the studio wall: protect the hour, and the day takes care of itself.
There were still trade-offs. A couple of clients preferred quicker chat replies and were told, politely, about the rhythm; most adapted. The team continued to adjust the windows when projects heated up, shifting a block earlier or shortening it before a launch. The practice remained a living agreement, not a rule carved in stone.
Lessons you can borrow
- Measure before you change. The sticky-note tally made the problem visible and the solution feel fair.
- Keep the exception path small and explicit. A short list builds trust that nothing critical will be missed.
- Expect an awkward first week. The urge to check is a habit, and habits take a little time to loosen.
- Close each block with a two-minute sweep. It turns anxiety about missing things into a quick, routine check.
- Let people use the time for learning. Protected hours are valuable for growth as well as for deliverables.
Should your own team be working out how to grow without losing its calm, it may help to read about a blueprint for planning digital growth alongside any attention agreement you make. Planning and protected focus tend to reinforce each other: a plan tells you what deserves your best hours, and quiet hours give you those hours.
As for the studio above the bakery, the cardamom still drifts up the stairs every morning. The difference is that now someone notices it, pauses, smiles, and then goes back to work with nothing buzzing in their pocket.

