Why Dinner Gets Interrupted by “Just One Quick Thing”

The food is on the table when the phone buzzes. "Sorry, just one quick thing: where do we keep the spare key for the storeroom?" A minute later: "Also, what price did we give the school for the chairs?" Neither question is urgent in a dramatic sense. Both are genuinely needed by someone who is still at work, or planning tomorrow, and who has nowhere else to look.

Answering takes a few minutes. Finding the quoted price means opening an email thread on the phone. The conversation at the table carries on without them. The scene is illustrative, not drawn from a particular person or business.

This piece is about that interruption. Not the long after-hours email or the crisis call, but the small question that is quick for the person asking, and less quick for the person answering.

Quick to ask is not the same as quick to answer

A question that takes ten seconds to type can take much longer to answer. The person receiving it has to stop what they are doing, recall the context, perhaps look something up, write a reply and then return to where they were. If they are at dinner, the return is to a conversation that has moved on.

Research on interruptions suggests the cost is not only time. In a controlled study by Gloria Mark and colleagues at the University of California, Irvine, people who were interrupted while working on email-based tasks finished them faster, with no loss of quality, but reported more stress, higher frustration, more time pressure and more effort. It was a workplace task in a laboratory, not a family dinner, and the findings should not be stretched too far. It does support a simple point: the cost of an interruption can be felt rather than seen.

South Africa's Basic Conditions of Employment Act provides for a daily rest period of at least twelve consecutive hours between ending and restarting work, with limited exceptions by agreement. The Act sets minimum standards for employees, and owners are not covered by it. Whether a single message breaches it is a legal question beyond this piece. The more useful observation is that the law treats time between shifts as rest, and a stream of small questions turns that time into standby.

Why the questions keep coming

Consider an illustrative case: a Pietermaritzburg furniture business with about 15 staff. The operations manager has been there longest and knows where everything is, what was promised to whom and how the awkward jobs are done. None of it is written down. When anyone hits a gap, in the day or the evening, they ask her.

The mechanism tends to have a few parts:

Knowledge lives in one person. Prices, locations, procedures and promises are held in memory or buried in that person's inbox.
Asking is easier than looking. Even when the answer exists somewhere, a message to the person who knows is faster than a search, for the person asking.
There is no agreed meaning of urgent. Without a shared understanding of what justifies an evening message, every question can feel worth sending.
Messages arrive the moment they are written. A question composed at 7pm for a task at 8am lands at 7pm, because that is when the sender thought of it.

Mellorca has looked at how knowledge gets trapped in when business knowledge lives in inbox history and at single-person dependency in how to know whether your business depends too much on one person. The working-hours cost of constant messages is covered in the cost of interruptions and context switching, and the wider spill of work into home in the inbox that follows you home.

The human tax: presence and attention

The main cost here is presence: being at the table without fully being there. Even when no message arrives, a person who knows they are the only source of answers may keep the phone face up, half-expecting one. That expectation is a small but steady claim on attention.

It would be wrong to say everyone experiences this the same way. Some people are glad to help and see a quick answer as part of a job they care about. Others would rather be left alone after hours but feel unable to say so. Mellorca cannot know which applies to any given person, and does not suggest that answering a message damages a family. The narrower point is that the choice to be available is often made by the way knowledge is stored, not by the person.

What could change

Answer once, record once. When a question is asked, put the answer somewhere others can find it: a shared document, a job card, a short how-to. The next person looks there instead of messaging.
Start with the questions that recur. A list of the ten questions the knowledgeable person is asked most often is a practical first knowledge base, and it can be written in an afternoon.
Agree what counts as urgent. A short shared rule, such as "after six, phone only for safety, a customer stranded or a delivery that cannot go", lets everything else wait until morning without anyone feeling rude.
Send later, not now. Many tools let the sender schedule a message for the next working morning. Microsoft's Outlook documentation, for example, describes schedule send and delayed delivery options. A sender who thinks of a question at night can still write it then.
Use quiet hours on the receiving side. Messaging apps commonly allow notifications to be muted at set times. Microsoft Teams mobile, for example, offers quiet hours and quiet days, and notes that others do not see that quiet time is on unless a status message says so.

In the illustrative furniture business, a shared page of locations, standard prices and agreed exceptions, a simple urgency rule and scheduled sending might stop most evening questions reaching the operations manager. The ones that still arrive would be the ones that really could not wait.

Trade-offs

Writing things down takes effort. Someone has to record the answers and keep them current, or the shared page becomes another place where wrong information lives.
Quiet hours can delay what matters. A strict rule without an urgent route risks a real problem going unanswered. The urgency rule has to come first.
Being needed can be valued. For some people, being the one who knows is part of their standing in the business. Recording that knowledge should recognise them, not sideline them.
Delayed messages still arrive. Scheduled sending moves the question to the morning; it does not remove it. Only recording the answer does that.

Why it matters

The business case for recording knowledge is resilience: fewer mistakes, faster answers and less risk when someone is away. The human case is about evenings. When answers are written down and urgency is agreed, the person who used to be asked everything gets to be where they are.

That is the dividend: presence at the table, and attention that is not on standby. Whether that evening is spent with family, alone, or on something else entirely is for them to decide.

Sources and further reading

Delay or schedule sending email messages in Outlook - Microsoft Support (last verified 10 October 2026)
Quiet time in Microsoft Teams for mobile devices - Microsoft Support (last verified 10 October 2026)
https://ics.uci.edu/~gmark/chi08-mark.pdf (last verified 10 October 2026)
https://www.labour.gov.za/DocumentCenter/Acts/Basic%20Conditions%20of%20Employment/Act%20-%20Basic%20Conditions%20of%20Employment.pdf (last verified 10 October 2026)