It’s easy to trick yourself into believing that you are a good writer just because you write often and that you get some resemblance of readership, and then your friends tell you your writing is doing good. But more often than not, you are not really a good writer. At the end, it’s based on that one metric: Can people understand what you are trying to communicate in a specific context.
For example, on this blog, majority of the content written are stories, insights or ideas told by yours truly based on what I have experienced or learnt. Therefore you will see that the content tend to be longer and come with some sort of introduction, body and conclusion in my own style and word choices.
But in cases like a resume, it’s a whole different beast. You have to communicate in a clear and succinct manner, using action words to demonstrate your skills and abilities so that hiring managers can make his or her decision quickly.
And it’s the same thing with your performance reviews, reports or even emails.
Now, you may be thinking that I could always go for courses to teach me how to write good resume, etc. That should solve a lot of problem.
Yes and no. Going for courses can serve as the foundation on which you can build on. It was that thinking that got me going for technical writing courses too. However, it doesn’t guarantee you can write good. You can only become good if you do it often with intent to improve.
And right now, I know for a fact that I won’t be able to craft a good technical document for my readers even though I went through technical writing course. It’s because I didn’t specifically seek out positions, roles or even tasks that requires me to do that. It put me in a position where I don’t have the experience or feedback to enable me to think like my reader.
Yet it didn’t stop me from having the thought that I’m good at writing. A delusion on my part.
It was that delusion that got me in a situation where I shared what I’ve done or achieved at work in my performance review using the style similar to how I write on my blog. When I first wrote it, it made perfect sense. I believe I was clear and the idea was complete. But when my manager attempted to read out loud what I wrote and fail to understand, it became clear to me that I was wrong.
Was it saddening?
Definitely but all is not lost.
She suggested that I could write it like how I write my resume. The idea was to communicate what I’m supposed to do, how I do it and what I’ve achieved in addition to my main tasks using the shortest number of words that catch the attention of my management.
So it was a good lesson. I want to be a better writer. A writer who can communicate ideas clearly that is both relevant and can grab people’s attention.