#28 Why you need to leverage your written communication to build likability
Name one tech job that is not interdependent. You cannot. If we need to work through people to achieve desirable outcomes in tech, we need to know how to build likability through writing.
Photo by Mitchell Luo on Unsplash
Tech is fast-paced. Tech is competitive. Tech is complex.
But before all else, tech is interdependent.
Teams of diverse profiles from engineering to design, research, and product rely on each other to deliver high-quality results quickly. This interdependence highlights the importance of building strong relationships with colleagues.
Why likability?
From the outside, it may seem that tech is all about the work: the code, the design, the data, the research piece.
However, these pieces only work if we are building strong relationships with our colleagues. Professional relationships have many aspects, and likability is one of them.
Lack of likability can lead to serious consequences, including being fired. On the other hand, if you are likable (assuming you have the necessary hard skills), you will contribute to your team's functions: folks will collaborate better with you and be more willing to move in ways that can help you achieve your goals.
The link between likability and written communication
Many tech companies adopted back-to-office policies post-COVID. The reasoning behind this was that folks collaborated better in person.
This perception may borrow from the notion that likability increases if people are physically together.
However, regardless of this, it continues to hold that emails, chat messages, Jira boards, Confluence, Miro, and other communication tools made tech workers communicate through writing.
On some occasions, tech workers share the same workplace. On other occasions, folks work remotely or commute to different office spaces. At the end of the day, what unites them is the written communication.
Therefore, it is crucial that we nail likability through written communication even if we work from the office.
3 questions to measure your likability:
Does your written communication lead to misunderstandings? (e.g., How many follow-up clarification messages do you need to send afterward?)
Does your written communication lead to conflict? (e.g., Do you get replies that are not collaborative?)
Is your written communication ignored? (e.g., Are you making requests that get ignored?)
Characteristics of writing that help likability
There are no fixed rules. However, these points can help:
Clarity: Using jargon and overly technical language intimidates or frustrates those who are not familiar with them. Instead, using plain English helps maintain a straightforward and more approachable language. This is easier to like.
Consistency: It is hard to build trust and establish a positive reputation without being consistent. Written communication that is consistent in tone and style can be more likable.
Respect: A patronizing tone and words that could be taken as rude would not be perceived as likable. Instead, asking questions instead of jumping to conclusions and creating inclusivity can foster a more likable environment.
There’s much more to say on this, of course. Do you agree? Disagree? Ping me, I’m curious.
👋🏽 I’m Mel…
I use UX Research methods to provide actionable career insights to tech professionals. Whether you're looking to switch careers, advance in your current role, or gain a deeper understanding of your strengths and improvement areas, I'm here to help.
🙇🏻♀️ DM me to book your free discovery call for career coaching
✍🏽 Check out my writing on Medium and Substack for practical advice and inspiration
🩷 Ping me to exchange ideas, share experiences, or say hello.