ENGL 301 is coming to an end and as my final post I am reflecting on what I have learned throughout the course. Before this course, I imagined technical writing was as simple as using an abrupt impersonal tone. However, when I tried to replicate that tone, my writing still felt too informal and stuffy. This course showed me that technical writing is more than just trying to sound impersonal, it’s a mind-set. Technical writing is putting your readers first, and giving them only what they need to know. Nothing is unclear, imperative or redundant. I have been successful in learning many of the technical writing techniques and still struggle with others.
What I learned
At the start of the course, I quickly learned the first things I needed to eliminate from my writing. I used too many verb and people phrases, such as “I will need to be able to” or “my findings were”. These are still be prevalent in my personal writing, but I needed to eliminate them from technical pieces, as they bog down the message and waste time
A big shift happened in unit 3 when we were introduced to the You-Attitude. In many way’s this seems like the root of technical writing. The You-Attitude is about writing for the readers benefit. It presents information to the reader in the easiest way for them to digest, which is presenting how it will affect them. This way readers don’t have to interpret or glean what the outcomes will be. Also, the You-Attitude is respectful and cognisant of the reader’s ego and does not make imperatives that could offend. The You Attitude made a big difference to my writing and is an important aspect with any professional communication.
Struggles
Some techniques took longer to master. A common piece of feedback I received was to not end sentences with two letter words. At first, I didn’t understand why this is important, but the more I practiced self-editing the more apparent it became. Those sentences are usually awkward and ungraceful, like they had been cut short. While they may not be strictly grammatically incorrect, it’s not the kind of tone I want in my writing.
I also struggled with using imperatives. I suppose I felt they were more succinct, or maybe I’m just naturally a bossy person, but either way it’s not a considerate way to write. In business communications, imperatives put a real condescending tone in the writing, which is not part of the You-Attitude.
Projects
I am pretty happy with most of the work I produced in ENGL 301. I enjoyed the chance to update my resume and create a LinkedIn profile. These are both things I had been meaning to do, so it was a real bonus that they were included in course work. My formal report was a daunting task and ended up consuming much of my time. I decided to investigate the feasibility of the Garibaldi at Squamish resort proposal. As professor Paterson pointed out in my proposal feedback, I may have bitten off more than I could chew. Garibaldi at Squamish will change the Sea to Sky corridor and as a past, and hopefully future inhabitant, I am keenly interested in the outcome. I had yet to make up my mind on the project and curiosity kept me interested in the work. Much of my time was spent doing the analyses of climate and GIS. I wanted to present my own work in the report and not just recite from other sources. In the end I think it came out pretty well and is good practice for writing reports in the work place.
Future
I enrolled in this course because technical writing has a direct application to my future career. I would like to work as an environmental consultant, investigating remote environments and reporting on my findings. Producing reports is a key aspect to this industry and will likely take much of my time. Surveys of employers in the industry constantly site writing as a highly valued skill that is often lacking in new graduates. This gives me a leg up on the competition and enhances my employability.