“This really should have been a meeting.”
“This really could have been an email.”
These statements are usually treated as jokes, or as shorthand for personality differences at work. One signals engagement and collaboration. The other is often read as resistance, rigidity, or disengagement.
But they’re not jokes. They’re signals.
They reflect two different ways people reduce ambiguity, and two different assumptions about what makes communication clearer.
For many non-autistic professionals, “this really should have been a meeting” reflects a genuine belief that talking things through in real time produces shared understanding. Meetings feel clarifying.
For many autistic professionals, “this really could have been an email” reflects a different but equally rational strategy: stabilizing meaning, reducing interpretive noise, and conserving cognitive energy.
Not because meetings are inherently bad, but because meetings often increase ambiguity rather than resolve it. When meetings make information less clear instead of clearer — because meaning depends on tone, timing, and unspoken inference — the issue isn’t efficiency, it’s cognitive labor. Asking why something wasn’t “just an email” turns out to reveal far more about how workplaces define clarity, whose communication styles are treated as default, and whose effort remains invisible.
Most professional environments operate on an unexamined belief:
More interaction leads to more clarity.
This assumption shows up everywhere:
The underlying logic is that face-to-face communication (e.g., meetings, calls, real-time discussion) is inherently better because it includes more cues: tone, facial expression, body language, immediacy.
In organizational psychology, this belief is formalized in a communication framework often summarized as richer is better. Face-to-face interaction sits at the top. Written communication sits near the bottom.
On paper, the logic feels obvious.
In practice, autism exposes where it breaks.
Most communication models assume that social cues are easy to interpret, mutually intelligible, and low-cost to process.
For many autistic adults, those assumptions don’t hold. Meetings don’t simply add information. They add interpretive volatility. Tone can contradict content. Facial expressions may feel ambiguous or performative. Unspoken expectations multiply. Real-time pressure penalizes precision and reflection.
What’s often labeled “nuance” becomes noise. Meaning shifts depending on delivery rather than substance. Ultimately, clarity becomes unclear and unstable.
By contrast, written communication (e.g., emails, shared documents, asynchronous messages) often provides what autistic communication relies on most:
So when an autistic professional says, “This really could have been an email,” they’re not disengaging from collaboration. They’re choosing a format where meaning holds still long enough to be understood.
Here’s what standard workplace communication rarely accounts for:
Who is doing the work to make understanding happen?
In meetings, autistic professionals often carry disproportionate cognitive labor:
This labor is invisible and rarely acknowledged. And, it’s treated as the natural cost of professionalism.
So when meetings are described as “easier,” “clearer,” or “more efficient,” an important question goes unasked:
Easier for whom?
What’s framed as “better communication” is often communication optimized for people who decode social cues effortlessly, while others expend significant energy just to keep up.
Autism doesn’t flip the communication hierarchy upside down. Instead, autism reveals that the hierarchy was never neutral.
The assumption that more cues automatically reduce ambiguity only holds when cue interpretation is shared, intuitive, and low effort. Autistic experience shows that:
Written communication isn’t “lean” in these contexts. It’s precision-preserving. Meetings aren’t inherently superior. They’re high-variance environments.
This is an argument against defaults, not against meetings.
When organizations insist that “this really should have been a meeting,” they’re making an unspoken decision about whose cognition defines clarity—and whose labor is expected to absorb the cost.
More inclusive workplaces ask different questions:
Inclusion isn’t just about being invited into the conversation.
It’s about how much work participation requires.
When someone says, “This really should have been a meeting,” they’re often naming what works for them: immediacy, shared context, relational cues.
When someone says, “This really could have been an email,” they’re often naming something else: precision, stability, and a format that reduces invisible labor.
The problem isn’t that one statement is wrong.
The problem is that only one is usually treated as legitimate.
The real question isn’t whether something should have been a meeting or an email.
It’s whose clarity we prioritize by default, and whose labor we assume is free.
"*" indicates required fields