Some Mistakes in Written Communication

I haven’t been arrogant in a long time, now it’s time.

These days, I’ve been thinking a lot about strengthening written communication networks. Because it bothers me a lot that written communication networks are becoming increasingly complex. The problems I identified in this regard and my solution suggestions are as follows:

E-mail Flows Are Not Systematic

As you know, there are 4 basic components in an email: Subject, Content, Recipient, and CC.

The subject section already includes ‘About’ information. We don’t need to write ‘About’ over and over again. Let’s use OOP standards, let’s take advantage of inheritance.

The content section should give information about the ‘content’. Unfortunately, an empty e-mail misses this point.

The recipient part refers to the person primarily responsible for this e-mail. I act reactively and feel responsible in all e-mails in which I appear as the ‘recipient’.

The CC section is generally used to provide information. If I’m CC’ed on an email, I can act proactively and step forward, or I can choose to stay back.

Creating Subject-Based Communication Groups, Not Team-Based

Instant communication tools (Slack, WhatsApp, etc.) are in our lives to facilitate communication. I think that having 8 people in one channel, 7 people in another channel without only one of these 8, and 9 people with +2 external stakeholders in another channel, and the fact that these people are not separated based on roles, causes serious confusion.

One-to-one Communication Habit Instead of Team Communication

I think this is a huge problem. I think the root cause should be investigated, found, and eliminated. Of course, I do not mean that every communication should be done publicly, but if there is a structure that has the potential to nourish team dynamics, why should this be done behind closed doors!

ps: These are purely my personal views and reflect my personal perspective.