Stressful projects are rarely short of communication. The updates go out, the dashboards refresh, the steering pack lands on time. What they run short of is contact: people talking to each other about what is actually true, what is slipping, and what they need from one another. The gap between those two things decides more outcomes than the plan does.
Pressure makes the gap wider. Under stress, people go quiet at exactly the moment the work needs them to speak. Updates turn into performances. Bad news travels at the speed of courage, which under pressure is slow. Teams that collaborated easily in calm weather begin to protect their own patch, because when things feel dangerous, sharing a problem can feel like admitting a fault.
Change multiplies all of this. When the ground is moving, silence does not read as neutral. People fill it with their own version of events, and the version they write is usually darker than the truth. That is why clear communication matters most when there is least time for it. It is not decoration on the delivery. It is load-bearing.
The sentences that hold a project together
The communication that saves stressful projects is not voluminous. It is short, plain and slightly uncomfortable. I am stuck. This will be late. I was wrong about that estimate. What do you need from me. A team that can say those sentences early, and hear them without punishment, will recover from almost anything. A team that cannot will discover every problem at the worst possible time.
Collaboration under stress is mostly the willingness to say those sentences, and the safety to receive them well. Neither appears on demand. They are built earlier, in the ordinary weeks, through small honest exchanges that teach people what happens when they tell the truth. By the time the project is burning, it is too late to install trust. You can only spend what was saved.
The mistake our era invented
Every era has found its own way to get the human side of change wrong. Memos from the top floor. Cascade briefings nobody believed. Town halls with one microphone and no questions. Ours has invented something new: the temptation to hand the entire human channel to a machine.
The tools are good. I use AI every day at Company31, and it drafts announcements, FAQs and update emails faster and more consistently than most communications teams can. That is precisely the danger. When the writing becomes free, the volume goes up, the polish goes up, and it becomes easy to believe the communicating has been done. It has not. A message has been sent. Communication is what happens when someone feels heard, and no model does that on a person's behalf.
The same logic is reaching the people functions. Pulse surveys, sentiment dashboards, engagement scores refreshed weekly. The data has its uses. But a dashboard can tell you that morale has dropped without telling you that the person closest to the deadline has stopped speaking in meetings. An HR function that manages wellbeing from a screen, and a chief people officer who can quote the sentiment score but has not sat with a delivery team in months, are not watching the project. They are watching a report about it.
People under pressure do not remember the wording of the update. They remember who came to find them.
If our era has one mistake available to it that no previous era could make, it is this: automating the appearance of care while quietly withdrawing the substance of it. Most project mistakes are survivable. Estimates recover, scope adjusts, plans are rebuilt. What does not easily recover is a team that has concluded nobody is actually there.
The oldest remedy
The remedy is old and unfashionable. Walk the floor. Be where the work happens. Ask how it is going and stay long enough to hear the second answer, because the first one is almost always fine. Notice who has gone quiet. Have the conversation that has no form attached to it and produces no data at all. This is not surveillance, and people can tell the difference immediately. Surveillance watches for failure. Presence watches for strain.
The objection is always time, and AI has just removed it. If the machine now writes the first draft of everything, the hours that used to go into wordsmithing are sitting there, waiting to be reinvested. That is the division of labour worth building: let the tools carry the drafting, so the humans can carry the relationships. Spending the saved time producing more messages is spending a gift on the exact thing that was already the problem.
The projects that hold together under stress are not the ones with the most polished communications. They are the ones where people kept telling each other the truth, and where someone senior kept showing up in person to make that safe. The messages can be automated now. The showing up cannot. That part of the work has not changed, and I hope it never does.