Editorially revised on 9 October 2026.
Examine the interaction without guessing another person's mind
Emotional intelligence at work is often discussed in terms of awareness and communication. For practical use, distinguish what someone actually said or did, your own reaction and what you do not know about their intention. A short message, a quiet colleague or a critical comment is not enough to diagnose a personality, feeling or motive.
Harvard professional-development guidance discusses noticing one's own reactions and considering communication with others. That provides a narrow starting point; it does not validate the worksheets here as an EQ test or prove that these examples cause salary growth, hiring success or universal agreement. Harvard emotional-intelligence guidance.
The original cases below are fictional task interactions. They are not clinical advice, personality assessments or instructions for an employer's complaint process. Their purpose is to make interpretation, clarification and follow-up visible. A courteous conversation can still leave a task unresolved.
Keep six parts of the record separate
Record the observable event, your reaction, the unknown, the clarification, the authorised next action and the follow-up. You can describe your own feeling honestly without assigning the same feeling to someone else. For example, I felt defensive after reading the message does not establish that the sender intended to insult you.
| Record part | Useful question |
|---|---|
| Event | What words or action did I actually observe? |
| Reaction | What did I notice in my own response? |
| Unknown | Which intention or context am I assuming? |
| Next step | What can I clarify or do within the actual rules? |
| Follow-up | What task outcome still needs checking? |
This is an editorial case record, not a validated scale. Completing the fields does not establish a high or low level of emotional intelligence. It can help you inspect one interaction more carefully and avoid turning an assumption into a fact.
Case one: a brief task message feels dismissive
Fictional setting: Nandita receives a message saying Send the revised table today. She expected feedback on a longer draft and feels that her work was ignored. The message does not explain which revision is required or why the sender was brief.
Observable event: the sender requested a revised table today. Nandita's reaction is frustration. The unknowns are the intended changes, the required time and the reason for the message's brevity. None is resolved by deciding that the sender does not respect her work.
Practice response: I can prepare the revised table. Could you confirm which columns need changing and the time you need it? I also have questions about the draft feedback; should we review those separately?
The response addresses the task without pretending the reaction did not occur. It separates the immediate instruction from another conversation about feedback. If the sender clarifies the columns, Nandita can act on that information. If they do not, she should record the unresolved instruction and use the appropriate task channel rather than claiming the ambiguity disappeared.
Follow-up check: were the changes and deadline actually confirmed? The reply being polite is not proof the work requirement is clear. The fictional case contains no assertion about the sender's emotional state or a measured improvement in the relationship.
Case two: feedback is specific, but your first interpretation is broad
Fictional setting: a colleague says the opening paragraph does not identify the report's purpose. Omar initially interprets this as criticism of his whole ability to write. The colleague has commented on a paragraph, not issued an assessment of every report Omar has produced.
Observable event: a specific opening is unclear to the reviewer. Omar can recognise his own defensive response while returning to the output. A useful clarification is what the reader needs to know at the start, rather than a demand that the reviewer reassure him about his character.
Practice response: Which part of the purpose was missing from the opening? I can revise that paragraph and ask you to check whether the new version states the task clearly.
Proposed action: Omar revises the opening to name the report's purpose and requests another check. That is an action plan. Until the review happens, it is not a verified outcome. If the next comment concerns another issue, he should inspect that issue rather than report that every writing problem is solved.
Follow-up check: can the reviewer identify the purpose from the revised opening? This is evidence about that paragraph. It is not a personality score, proof of emotional maturity or a guarantee of a future promotion.
Case three: communicate a delay without promising certainty
Fictional setting: Pooja must combine two approved sections into an internal document. One section is still waiting for its owner's approval. A colleague asks when the finished document will arrive. Pooja feels uncomfortable giving an incomplete answer, but she cannot approve the missing section herself.
Observable event: one dependency is unresolved. Pooja knows which approved material is available and who owns the remaining decision. She does not know when approval will arrive. The pressure to reassure a colleague does not make that unknown into a confirmed delivery time.
Practice response: I have the approved first section. The second is still with its owner for approval, so I cannot confirm the finished document's time yet. I will ask for the approval status and update you when we have that decision. If a partial document would help, we need the responsible person's permission before sending it.
This response can acknowledge the colleague's need while preserving the approval boundary. Empathy does not require an inaccurate promise. The task may still be delayed after the conversation, and the record should say so.
Follow-up check: was the approval status obtained, and was any proposed partial release authorised? Do not describe asking for an update as receiving one. The fictional case supplies a way to make uncertainty visible, not proof that communicating it always resolves the dependency.
Case four: another person's silence remains uncertain
Fictional setting: a teammate does not speak during a planning discussion. You wonder whether they disagree. The observable fact is that they have not contributed verbally; the reason is unknown. Silence could have several explanations, and this guide does not identify one from body language.
A task-focused invitation is: We have not heard your view on the proposed handover. Is there a detail we should check before the owner decides? Give the person an opportunity to respond without requiring them to disclose private reasons for being quiet.
If they identify a task concern, address that information. If they decline or the context does not allow a response, do not invent agreement or disagreement. Record the decision and the evidence available to its owner. Participation and approval may also follow actual organisational rules.
The follow-up is whether a relevant concern was raised and considered. It is not whether you successfully read the teammate's feelings. A respectful invitation can be worthwhile even when it does not reveal their internal state.
Keep serious issues outside a friendly-misunderstanding assumption
If a situation involves threats, harassment, discrimination, retaliation or immediate danger, use the relevant organisational reporting or emergency route. These cases do not replace safety or conduct procedures. You do not need to confront someone alone or diagnose their motives before seeking appropriate help.
The UN Ombudsman resource supports preparing for difficult conversations and exploring workable options in its institutional context. It does not establish Indian legal procedure or guarantee harmony. UN conversation guidance. Follow the actual rules and responsible channels for your setting.
For ordinary task disagreements involving owners and approvals, see the conflict-resolution guide. For individual practice rather than workplace cases, use the emotional-intelligence skills log. Keep a task outcome separate from a claim about emotional ability.
Common questions
Does understanding a colleague mean agreeing with them?
No such requirement is established here. You can ask about their perspective while retaining task, approval and safety boundaries. Understanding the request and deciding whether it is authorised are separate questions.
Can I judge someone's EQ from one meeting?
The case record does not support that judgement. It records observable actions and unresolved context, not a validated psychological measurement. Avoid labelling another person's personality from a single reply or silence.
How do I know the interaction improved?
Identify the specific observation: a clarified instruction, a checked revision or an approved next step. Do not turn one useful observation into a salary claim, relationship guarantee or universal score.