In many small and mid-sized businesses there is a quiet pattern in how colleagues speak to each other. For most of the month there is polite silence: a few messages, a weekly check-in that gets postponed. Then a delivery fails, a system goes down, or a customer escalates, and suddenly everyone is in a group chat, on a call, and talking more than they have all month. The team connects, and connects well, but only when something is broken.
This piece looks at why that happens, what it costs the people involved, and how a team can build ordinary, low-pressure contact into the rhythm of work without adding more meetings. It is a hypothesis about a common pattern, not a diagnosis of any particular team.
Why a crisis is the easiest reason to talk
An emergency removes every barrier to conversation. Nobody wonders whether a message is an interruption, because the reason for sending it is obvious. Nobody worries about hierarchy, because the problem is bigger than the org chart. Nobody has to invent an agenda. The urgency supplies a shared purpose, a clear deadline and a permission slip to ask for help.
In calm weeks, none of that is present. A question that is not urgent feels like a cost imposed on the other person. A check-in with no agenda feels self-indulgent. Colleagues who are busy, often working from different sites or on different shifts, read silence as a sign that things are fine. So the default becomes saying nothing until there is something unavoidable to say.
Over time the team learns a lesson nobody intended: contact is for problems. A call from a colleague starts to mean bad news. People brace when the phone rings. The relationship that exists between two people is built almost entirely out of stressful moments, which is a poor foundation for trust.
What the research on incidents and safety suggests
The discipline of incident management, as summarised in general reference material, is built around the idea that how a team responds to an unplanned disruption depends heavily on the preparation done before it. Roles, communication channels and escalation paths that are agreed in advance make the response faster and calmer. The reverse also holds: a team that has never practised talking to each other will improvise under the worst conditions.
The idea of psychological safety, developed in organisational research, describes a shared belief that a team is a safe place for speaking up with questions, concerns or mistakes. Reference summaries of that research describe it as something built through everyday interactions, not something created in the moment of a crisis. A team where people only speak when things go wrong has had very few chances to find out that speaking up is safe.
Crisis management as a field also stresses that communication is a core part of the response, not an afterthought. What is less often said is that the quality of communication in a crisis mostly reflects the quality of communication before it. None of this establishes how common the pattern is in South African businesses; no survey is claimed here. It is a reasoned expectation drawn from general research.
An illustrative case
Consider an illustrative example, not a real case: a Pretoria-based company that installs and maintains solar and backup power systems for small businesses. It has twelve staff: a head office team of four, six field technicians and two people who handle dispatch and customer calls. Most weeks the technicians work alone or in pairs and report through a job-card app. The office sees their updates but rarely talks to them.
When a client's inverter fails on a Friday afternoon, everything changes. Dispatch calls the technician, the technician calls the supplier, the owner joins the thread, and a stream of messages follows until late in the evening. The team handles it well. Everyone is warm and quick and helpful. By Monday the thread is silent again.
The cost does not show up in the job. It shows up in what happens in between. A technician who noticed that a particular model keeps tripping on load-shedding restarts never mentioned it, because there was no natural moment. A dispatcher who is struggling with the volume of calls does not say so, because nobody asks. A new employee reads the group chat and concludes that this is a workplace where you speak up only when the building is on fire.
The human tax: presence and energy
The first cost is presence. People are physically at work, or logged in, but not really in contact with each other. They know colleagues by their emergencies rather than by their working habits, their strengths or their circumstances. When a colleague is having a hard month, nobody notices, because there has been no ordinary contact against which to notice a change.
The second is energy. Crisis-only contact means that every conversation is high pressure, and the nervous system learns to associate colleagues with stress. Switching quickly into emergency mode and back again is tiring, and the teams that do it well are often the ones paying for it in quiet exhaustion. The Mellorca article on constant alerts becoming background anxiety describes how that low-level readiness wears people down, and what a week without firefighting would feel like describes the contrast.
What could realistically change
The aim is not to schedule more meetings. It is to create small, regular, low-stakes moments where talking is normal, so that the crisis conversation is the same people having a harder version of a familiar exchange.
- Replace one status meeting with a short conversation. If a weekly update is mostly reading out numbers, put the numbers in a shared record and use the time to ask what is getting in the way. The piece on the meeting that could have been a shared record covers how to make that swap without losing visibility.
- Create a place for non-urgent questions. A channel or board that is explicitly for things that can wait for a day gives people permission to ask without feeling they are interrupting.
- Debrief after the fire, not just during it. A short, blame-free review a few days after an incident turns the emergency into shared learning and gives the team a regular reason to talk about what worked.
- Agree the roles before they are needed. Who calls whom, who owns the customer, who decides. The more of this is settled in calm weather, the less improvisation is needed under pressure. Mellorca's discussion of improvised incident response shows what happens when it is left to the moment.
- Notice the good days. A message that says a job went well, a handover was smooth, or a problem was caught early is a contact that carries no bad news.
None of these require software, and none will work if they are imposed as another compliance ritual. They work when a manager does them first and visibly.
The business outcome
Problems tend to surface earlier, because the people who see them have an easy way to say so. Incidents are resolved faster because roles and relationships are already in place. Knowledge that used to stay with individual technicians reaches the people who can use it, and the cost of each emergency in time and goodwill falls.
The human dividend
The dividend is presence: the sense of being part of a team that knows you, not only a team that needs you when something fails. Colleagues who speak regularly in ordinary circumstances are more likely to notice when someone is struggling, and more likely to be believed when they say they need help.
The trade-offs
- Regular contact takes time. Every check-in competes with billable or urgent work, and some weeks it will be the first thing dropped.
- Forced contact backfires. Mandatory social events or scripted check-ins can feel like surveillance and make the silence worse.
- Remote and shift work make it harder. Technicians on the road and staff on different shifts need different rhythms, and no single arrangement will suit everyone.
- Some people prefer quiet. The goal is available contact, not constant contact.
Why it matters
A team that talks only when something breaks is a team whose relationships are built from its worst moments. Making ordinary contact easy, safe and brief does not remove the emergencies, but it means people meet them as colleagues who already know each other.
Sources and further reading
- Incident management - Wikipedia (last verified 10 October 2026)
- Psychological safety - Wikipedia (last verified 10 October 2026)
- Crisis management - Wikipedia (last verified 10 October 2026)
Related Mellorca reading
- When Screens Sit Between Colleagues Who Sit Together
- The Family Dinner That Competes With a Group Chat
- The Employee Whose Expertise Is Trapped in Data Entry