A one-line reply, no greeting, no acknowledgment of the question behind the question, sent back thirty seconds after the message arrived. The sender sees a fast answer and calls it efficient. The research on what actually happens on the receiving end of that message tells a more complicated story.
What a curt message actually does to the person reading it
In a series of three experiments described in a 2007 paper in the Academy of Management Journal, the researchers Christine Porath and Amir Erez exposed participants to a rude authority figure, a rude third party, or an imagined incident of rudeness, then measured how well those participants performed on a routine task and a creative one. Across all three conditions, rudeness reduced performance on both kinds of task, and it reduced how willing people were to help someone else afterward. Porath and Erez traced the effect to something specific: rudeness disrupted the cognitive processes the task required, not just the participants’ mood. People were measurably worse at solving problems and generating ideas after being on the receiving end of curtness, whether they had experienced it directly or simply watched it happen to someone else.
This is a pattern across three separate experiments within one paper, not a single result standing alone, though it remains one research team’s set of findings rather than a large, independently replicated literature. The effect size and the exact mechanism would benefit from further testing outside a lab setting. But the direction of the finding runs against the intuition that a blunt exchange simply saves everyone time. If the person on the other end of an abrupt message performs worse on whatever they do next, the message has not saved time so much as moved a cost from the sender to the recipient.
The same pattern shows up specifically in email
A more recent study looked at whether this extends to the kind of terse digital communication common in office and remote work. In research published in Organization Management Journal, the researchers Jone Pearce, Kimberly McCarthy, John Morton, and Sarah Lyon found that people who were exposed to an uncivil email performed worse on a subsequent task than people who were not, and that the effect could spread to a third party who had nothing to do with the original exchange, simply from witnessing it or hearing about it. The University of California, Irvine, where the research was conducted, describes the effect as a kind of contagion, where curtness in one exchange lowers the performance and evaluation of people well outside it.
This is one study of email specifically, again not a settled consensus on every digital interaction, but it points at something a purely time-based accounting of communication misses. An abrupt email might take fifteen seconds to write instead of two minutes. If it measurably lowers the recipient’s performance on their next task, and possibly a colleague’s performance too, the fifteen seconds saved has to be weighed against a cost that does not show up in the sender’s own workday at all.
Why teams that feel safer tend to do better work
A separate body of research points at a related mechanism operating over a longer timeframe than a single message. The organizational researcher Amy Edmondson, in a 1999 study in Administrative Science Quarterly of 51 work teams inside one manufacturing company, introduced the concept of team psychological safety, a shared sense that the team is safe for interpersonal risk taking. Teams with higher psychological safety showed more learning behavior, meaning they were more willing to ask questions, flag mistakes, and raise concerns, and that learning behavior was associated with better team performance.
Google later ran its own internal, multi-year review of what separated its highest performing teams from the rest, an effort the company calls Project Aristotle. This is a company-run study, not a peer-reviewed paper, and its methods and full data have not been published for outside academic scrutiny in the way Edmondson’s research has. According to Google’s own account of the project, of everything the team analyzed across around 180 groups, psychological safety came out as the strongest single factor associated with team effectiveness, ahead of who was on the team or how experienced its members were. Google’s account describes this converging with Edmondson’s earlier academic finding, though it is worth being clear that one is a company’s internal analysis and the other a peer-reviewed field study, and the two should not be treated as a single unified body of evidence just because they point the same direction.
Where abruptness fits into that picture
None of this research measured “abruptness” as its own defined trait, and curtness is not identical to the rudeness or incivility these studies actually tested. A short message is not automatically an uncivil one. But the mechanism these studies describe, that a sharp or dismissive tone measurably disrupts the recipient’s thinking and can make people less willing to flag a problem or ask a clarifying question, applies most directly to communication that reads as dismissive rather than merely brief. An abrupt style that a recipient experiences as curt or careless risks landing in the territory these experiments actually tested, even when the sender intends only to save time.
What this does not settle
This is a handful of separate studies, from different research groups, using different methods, not a single settled account of exactly how much any specific instance of bluntness costs a team. The research does not say brevity itself is the problem, and plenty of short, direct communication carries no incivility at all. What it does suggest is that the efficiency case for abruptness rests on an incomplete ledger: it counts the seconds saved on the way out and leaves off whatever gets lost in the recipient’s next hour of work, and in whether they feel able to flag the next problem before it becomes a bigger one.
None of the studies here were run inside a technology company specifically, and workplace norms around pace and tone vary considerably across industries and teams. A fast-moving engineering team that has deliberately built a culture where blunt, no-frills feedback is the norm, and where everyone involved reads it that way rather than as a slight, is a different situation from an isolated curt message landing on someone who was not expecting it. What the research consistently measured was the recipient’s experience of being treated dismissively, not the objective word count or response time of a message. A short reply delivered inside a relationship of trust does not carry the same signal as the same words sent from someone the recipient barely knows.
