Skip to content

How to Avoid Ineffective Communication (Part One)

March 9, 2023

This article mainly discusses some suggestions for communicating and collaborating with others at work.

1. Introduction

In daily life, we communicate with others. Some of these communications may be out of habit and courtesy, or just casual conversations. However, when we initiate work-related communication with others, there is always a clear reason. For example, seeking help, collecting opinions or suggestions, etc.

Therefore, unlike daily-life communication, workplace communication requires more attention to methods and approaches, focusing on achieving the goals behind the communication.

2. Types of Communication and Goals

Workplace communication always has a clear reason, and thus a clear expected goal, which can generally be divided into the following categories:

Reason Goal ------------ ------------------------------------------------------------------ Conveying meaning Let the recipient understand the conveyed content Assigning tasks Ensure the recipient understands the task content and can carry it out normally Status updates Inform the recipient about the current status of your assigned tasks and future expectations Seeking help Enable the recipient to fully understand the detailed situation of the problem you are facing and provide sufficient information to solve it

Different reasons and goals for communication may vary in actual implementation.

2.1 Conveying Meaning

"Conveying meaning" is commonly used in situations such as introducing regulations or making requests.

When conveying meaning, unless it's something obvious that doesn't need explanation (such as: The last person to leave the company should turn off the lights), providing specific reasons, examples, etc., will better help the recipient understand the matter, ensuring that the message is truly implemented.

Negative Example (Over-interpretation)

Team Leader Team Member Remember to add comments while writing code! Okay! (Spent one week adding comments to every line) Don't comment every single line
Writing so many useless ones wastes time!
(Didn't you ask me to do this??)

Positive Example

Team Leader Team Member Remember to add comments while writing code For example, complex algorithms, special exception handling, temporary modifications
You'll forget why you wrote them after some time
Okay!

2.2 Assigning Tasks

"Assigning tasks" is very common in the workplace, but since it usually involves leaders assigning tasks to subordinates, problems often arise without the leader realizing it.

Some leaders, due to being busy, may habitually assign tasks to new employees or those newly taking over responsibilities as if they were experienced hands, assuming the other party already knows everything. This hardly qualifies as effective communication, and the work is unlikely to make real progress, ultimately only making the leader busier.

Thus, when assigning tasks, unless the person is experienced, all necessary information should be provided together with the assignment. If necessary, confirm the general scope of the work to avoid confusion and aimlessness, or even deviation from the task goal.

Ultimately, ensure the other party "has understood all the information needed to complete the task." Even if there are unclear parts, ensure they know where to find the answers (e.g., reference documents, colleagues to consult, etc.).

Negative Example (Incomplete Information Provided)

Leader Newcomer Organize the information of new clients for the past 3 months. Okay (I seem to know nothing?) Where can I find the client information? It's in the CRM system, the address is http://xxx.company.com Okay (I don't have an account?) I need an account to log in, who should I contact? Ask Zhang San to create an account for you. Okay (Entered the system, it's so complicated, I don't know how to use it, and I'm afraid to click randomly) Is the customer information here? Why do you have so many questions! Can't you figure it out yourself? Alright ... (Under immense pressure, not sure who to ask next)

Positive Example

Leader Newcomer Organize the information of new clients for the past 3 months. First, get a CRM system account from Zhang San,
then ask Li Si about the specific operations; he has done this before.
Okay

2.3 Status Updates

Having work assignments means having status updates. These updates can range from simple verbal reports to comprehensive weekly reports. Regardless of the format, they should clearly state which project’s which task, its current status, and future expectations.

Secondly, during the course of work, if difficulties arise causing delays or preventing progress, they should be reported immediately rather than waiting for someone else to inquire.

Finally, everyone in the workplace should always be mindful of the "authority" associated with their position. For instance, developers can decide how a feature is implemented and suggest additions or deletions, but do not have the authority to directly add or remove features. When encountering matters beyond their authority, they must report upwards proactively and never act independently.

Negative Example (Incomplete Information Provided)

Team Member Team Leader Function XXX is almost done. What function XXX?? The XXX function from Project A. Oh, what does "almost" mean? Can testing begin? Not yet. ?? What part is missing? Just the final email-sending part isn't ready yet. Oh, when will it be ready? The deadline is tomorrow. It should be okay. (Why can't you say everything at once?)

Positive Example

Team Member Team Leader The XXX function of Project A is ready for testing.
However, the final email-sending part needs to wait until tomorrow.
Good.

Negative Example (Never reporting until the end)

Team Member Team Leader (Silently developed for a week) The XXX function of Project A is due tomorrow, how's it going? Not enough time. Why not enough time? Haven't you been working on this function for a week? This section requires third-party integration, which took me five days. Why didn't you tell me earlier??

Positive Example

Team Member Team Leader (Roughly reviewed the requirements) This time, the XXX function of Project A has a tricky part that requires third-party integration.
We probably won't finish within a week.
Okay, I'll adjust accordingly.

2.4 Seeking Help

"Seeking help" is perhaps the most common form of workplace communication. Any two colleagues could engage in this type of interaction.

The most important thing in this kind of communication is never assume the other party already understands the full picture. Always start by clarifying the background and providing necessary information (such as complete screenshots, URLs, various IDs, etc.). Moreover, URLs and IDs should be provided in text form for easy copying rather than screenshotting text.

Negative Example (Too Narrow Question)

Colleague A Colleague B Can DataKit collect data from the XXX system? No. (Indeed, there's no corresponding collector) (Looks like this client can't be served)

Positive Example

Colleague A Colleague B I have a client who uses an old XXX system installed years ago, and it keeps logging out automatically from time to time.
Is there any way to monitor it?
You can use YYY functionality.

Negative Example (Vague Question)

Colleague A Colleague B How do I send emails? I don’t know how to answer you. (Who are you? What are you doing? What effect do you want?)

Positive Example

Colleague A Colleague B I have a feature that sends welcome emails to users upon successful registration.
Is there a unified sending interface for these emails, or should I implement it myself?
No need to do it yourself, just call the API of XXX
Documentation is here http://xxx.company.com

Negative Example (Indirect Question)

Colleague A Colleague B The page is showing an error! What error? [Image: Screenshot of a small portion of the error] Where is this screenshot from? The event list here. What is your workspace ID? [Image: Screenshot of workspace ID] No, I can't copy text from your screenshot. wksp_xxxxxx (So exhausting...)

Positive Example

Colleague A Colleague B I encountered an error when clicking details on the event list page.
The error message is xxxxxxxxxxxxx
Workspace ID is wksp_xxxxxxxx.
[Image: Screenshot of the entire window] Got it, let me check.

3. Communication Examples to Avoid

Incorrect communication not only fails to obtain effective information but also easily causes annoyance. Such errors in communication should be avoided in the workplace.

3.1 Impatience and Lack of Respect

Colleague A Colleague B Can DataKit collect data from the XXX system? What client are you? What scenario? Just tell me if it's possible or not? ??? (I can directly answer "No", but I feel it shouldn't be this simple)

Colleague A Colleague B When will Guance's XXX feature be available? This feature is already scheduled, and we will notify you upon release. Just tell me when it will be available, my client is waiting. ??? (I understand your urgency, but this logic seems off)

3.2 Taking Things Out of Context, Refusing to Think

Colleague A Colleague B Can Guance implement the XXX feature? Currently, it's not available because it's not a common feature
But you can achieve this effect through YYY method, requiring ZZZ operation.
So it means this feature doesn't exist, right? ??? (That's technically correct, but something feels off)

3.3 Three-Word Sentences, Poetic Style

Colleague A Colleague B Are you there? I have a question. Can I ask you? About DataKit. Do you know it? Can it collect data from the XXX system? ??? (A bunch of short messages, resulting in just one sentence, exhausting...)

Comment: A large number of message notifications in a short period creates significant psychological stress, interrupting ongoing work. Fragmented short sentences are inconvenient to include in "to-do later" or "task" lists. It's best to explain everything in one go.

3.4 DingDing in Hand, Everything is Dinged

Colleague A Colleague B [Ding] Are you there? ??? (You've dinged me, so clarify what's up!)

Comment: DingDing's "Ding" feature is practically useless. Urgent matters should be handled via phone calls, non-urgent ones through messages. "Ding" is suitable only for announcements, not chats.

3.5 Text Only, Never Calls

Colleague A Colleague B Are you there? There's an urgent matter! Are you there? Hurry up, the client is waiting! ??? (If it's urgent, why not just call?)

Comment: Text-based communication has limitations in efficiency. For truly urgent matters, a phone call is recommended (note: a regular phone call, not an internet-based one).

3.6 Calling for Every Matter

Colleague A Colleague B [Call] [Call] [Call] [Call] ??? (I have my own work to do, don't interrupt me with unnecessary calls!)

Comment: Phone calls should be reserved for urgent communication. They are efficient but also disruptive, so avoid overusing them.

Colleague A Colleague B How to install DataKit? It's in the documentation. What is the data structure returned by the XXX feature? It's in the documentation. What does YYY mean? Google it.

Comment: Read the documentation thoroughly. If you have questions, search first. Directly asking others may seem proactive but actually wastes their time.

Epilogue

Good communication not only improves work efficiency and reduces errors but also makes both parties feel good. In summary, it comes down to one phrase: "Think for the other person."

Finally, wish everyone smooth communication and successful work!