A Short Message Is Not Always a Sharp Message: Use DiSC Before Assuming Intent

Photo: Theo Decker / Pexels. Illustrative stock image.
When a colleague sends a brief message, separate the words on the screen from the meaning you assign to them. DiSC can provide a starting point for discussing communication tendencies, but it should not replace a direct question about intent. The practical goal is a message the recipient can understand and act on.
In a growing South Florida business, managers may coordinate work through email, chat, and shared systems across languages and locations. A message that feels efficient to its sender can leave its recipient uncertain about urgency, tone, or what needs to happen next.
Start with the work question
Consider this hypothetical message: “Need this fixed today.” The recipient might read frustration, impatience, or disappointment into it. Yet the first operational problem is simpler: the message does not identify the required change, the deadline, or the reason it matters.
Before diagnosing anyone's style, clarify the request. Which part needs revision? What would an acceptable result look like? Does “today” mean before a customer call or before the end of the recipient's workday?
A clearer version could be: “Please update the delivery date in the proposal before our 2 p.m. customer call. Use the date operations confirmed this morning. Let me know by noon if anything prevents that.” Clarity makes interpretation less necessary.
Use DiSC as a conversation starter
Everything DiSC describes behavioral styles and provides assessment-based learning to help people understand themselves and others. Its publisher emphasizes that no style is better or worse than another. That is a useful foundation for a discussion about preferences.
Ask colleagues what helps them process a request. Some may prefer the decision first, followed by details. Others may need background before they can evaluate the proposed action. Treat their answers as information about this working relationship, rather than rules attached to a letter.
Avoid statements such as “You are a C, so you always overthink,” or “That is just how D styles speak.” A preference does not excuse disrespect, and a profile does not establish what someone intended in a particular exchange.
Agree on a shared message structure
A small team does not need a complicated communications manual. It can agree on a few elements for requests that affect deadlines or customer commitments.
Identify the action, the owner, the required timing, and any material constraint. Put supporting detail where it is easy to find. If a deadline is flexible, say so. If a decision is still open, distinguish a request for input from a final instruction.
The sender should also choose the right channel. A short chat may be appropriate for a routine clarification. A sensitive performance issue or unresolved disagreement may need a private conversation, followed by a factual written summary.
Repair misunderstandings without creating another one
When a message lands badly, describe your interpretation as an interpretation. “I read that as urgent and was not sure whether you wanted a full revision” invites clarification. “You were rude” starts with a conclusion about the other person.
The sender can respond without defending every word: “I meant the delivery date only. I can see that I did not make that clear.” Both people can then agree on the next action.
Managers should model this repair themselves. Asking employees to communicate better while continuing to send vague instructions gives the team two different standards. The useful standard is visible in everyday work, including messages from the owner.
Should everyone write in the recipient's preferred style?
Adapt where it helps understanding, while preserving consistent business expectations. Employees should not have to guess the sender's personality to know what a request means. A shared standard supports everyone; individual preferences add context.
Try one communication experiment this week
Choose one recurring exchange that creates friction, such as a quote revision or a status request. Agree on a clearer message format, use it for a week, and review whether fewer clarifications were needed. Discuss actual examples without circulating private assessment results.
Your takeaway: ask what the message requires before assuming what it says about the person. Use DiSC to improve the conversation, not to close it.
Leyda Lazo and Human Capital Consultants International (HCCI) connect communication development with the work managers lead. Through corporate training and HRO FullScope, those conversations can become practical team agreements. Contact HCCI to discuss the communication patterns your team wants to improve.




Comments