Communication Style Tags Can Reduce Workplace Miscommunication

Melissa Mikus frames workplace miscommunication as a practical failure with measurable costs: people often do not know how to communicate with one another in the way the other person will understand, process, or act on. Her proposed fix is deliberately small: make each person’s preferred communication mode and working conditions visible where colleagues already look — in an email signature, social profile, internal directory, messaging profile, or similar workplace surface.

The problem does not require obvious conflict. It can begin with a single word. Mikus describes approving a board presentation by replying “Sure” to a project manager’s Slack message. She had reviewed the deck, thought it was strong, and had no feedback. But because she was on another call and did not want to delay the project, she answered with one brief word.

The project manager, Charlie, read “Sure” as something closer to “Meh, this is OK, I guess.” By the next morning, he had produced a revised presentation. The factual work was already done; the failure was in the signal. A short approval became hours of avoidable work, sleeplessness, and possibly tears.

Teams lose time not only because people disagree, but because they misread approval, urgency, silence, brevity, or format preferences. Mikus asks how often teams go down the wrong path on a project, feel stalled by unclear progress, or spend hours or days in a dispute “that wasn’t even a disagreement in the first place.”

Mikus cites two figures to establish that this is not merely interpersonal inconvenience: 86 percent of employees and executives blame workplace failure on ineffective communication, and US businesses lose 1.2 trillion dollars a year as a result of miscommunication. This is not just about being “nice and diplomatic.” Miscommunication is expensive, damages morale, stalls progress, and increases turnover.

Mikus’s proposed intervention is a “communication style tag”: a short, visible description of how someone communicates best and how others can help them show up effectively. It should contain two kinds of information.

First, it should state the person’s best communication channels and working norms: email, phone, text, Slack, working hours, protected focus time, or similar constraints. Second, it should explain how that person does their best work or what commonly trips them up.

Her own example is concise: “Thrives best in morning meetings. Provide detailed context in advance for fastest decision making.” The on-screen mock-up places this kind of tag at the bottom of a LinkedIn-style profile, where it reads: “Thrives in morning meetings. Loves detailed context to enable fastest decision making.” Other mock-ups show the same idea inside a messenger profile, an email contact panel, and an internal company directory. The placement is part of the intervention: the preference is useful only if it is visible at the moment someone is deciding whether to send an email, book a meeting, write a Slack message, or call.

The point is not to create another document nobody reads. The information should appear in places already used in normal work: email signatures, social profiles, internal directories, or collaboration tools. The tag is meant to be available in real time, not buried in an onboarding packet or team charter.

The tag is also not a demand that everyone’s preference be honored all the time. Mikus explicitly acknowledges that teams cannot accommodate everybody 100 percent of the time. Her more limited claim is that the information gives people better choices. If a colleague is known to need written context, a manager can send the prompt before the meeting. If someone turns off chat to protect focus, a lack of response becomes less likely to be interpreted as avoidance or disinterest.

Mikus’s strongest example of style mismatch comes from joining a fintech startup and needing to build a strategic roadmap for the CEO. She identified Kate, a long-tenured and knowledgeable colleague, as someone she needed to consult. Mikus describes herself as an extrovert who loves brainstorms: a conference room, a whiteboard, ideas thrown against the wall.

She put “Roadmap discussion” on Kate’s calendar and arrived ready to generate ideas live. Kate responded with what Mikus calls a “total blank stare.” Mikus did not know whether Kate was disinterested or intimidated, and she ended the meeting awkwardly and frustrated.

Later that day, Kate sent an email containing five strong, well-developed ideas. The meeting had not failed because Kate lacked insight. It failed because the format had been designed around Mikus’s communication comfort zone. Kate’s better format was asynchronous writing, where she could process and respond thoughtfully.

That experience led Mikus to ask her team to create communication style tags. Kate’s tag became: “Email for fastest response during the day. Prefers written comms to enable thoughtful, clear responses.” In the visual shown on screen, a messenger-style profile for “Kate Introvert” phrases it similarly: “Email for fastest response during the day. Responds best to written comms to enable thoughtful, clear response.”

Communication preference can hide or reveal capability. Kate had the ideas Mikus needed. The wrong format temporarily made those ideas unavailable.

Mikus uses shorter cases to show how quickly colleagues assign meaning to behavior when the actual explanation is a communication norm.

Mike did not respond to messages on the internal messaging system for hours, days, or sometimes at all. Mikus says she catastrophized: Did he dislike her? Did he think her questions were silly? The explanation was simpler. Mike was an extrovert who turned off Messenger during the day because otherwise he would spend the day chatting with colleagues. His tag directed urgent matters to text and noted that he preferred live interaction.

Kelley ignored meeting invitations when they lacked agendas because agenda-less meetings made her anxious. Matt balked at shorthand messages over Slack, Teams, or similar tools because he preferred detailed spreadsheets and long emails. Liz favored voice memos over long texts. Lewis held daily stand-ups but refused late-afternoon meetings because he needed that time to think.

The recurring failures are ordinary: unanswered chats, ambiguous approvals, agenda-less meetings, badly timed conversations, and mismatched expectations about how much context is enough. Mikus’s point is that teams often treat those moments as signs of attitude or competence when they could instead treat them as missing working information.

Mikus places responsibility especially on leaders, managers, and anyone tired of workplace friction to “go first.” Creating a tag is not enough if it remains private or performative. The advice is to normalize the practice with teams and make it highly visible so people can use the information day to day.

She also extends the logic beyond formal teams. The same information can help with clients, colleagues, friends, and personal relationships. Her example is domestic: her partner Charles asked on a Sunday evening whether she wanted to RSVP that night for a white-water rafting trip. Mikus immediately had practical questions: Was it glamping? Were there showers? Who was going? She jokes that Charles should know her better, but the work point remains: a visible reminder that she needs advance context to make fast decisions could improve the interaction.

In Mikus’s framing, the communication style tag turns preference into usable data. It is not a personality label; it is operational information. When people tell others how best to work with them, she argues, teams communicate more effectively, build trust, move faster, feel less strained, and work better together.