Most people think it’s difficult start a career as a business consultant. I used to think the same in my early 20s when I started in IT. In retrospect, I should have made more efforts to establish myself as a consultant earlier; the benefits certainly outweigh the downsides. As luck would have it, I was forced into a consultancy role when I lost my 9-5 job. Time to learn to hustling and bring in business. Harvard Business Review refers to it as The Hustle Strategy. More on that later. Continue reading 12 Steps To Getting Started as a Consultant
Which of these would you hire to join your Technical Writing Dept? Someone with great writing skills but little technical knowledge or, for example, a Computer Science graduate with deep technical knowledge but average writing skills? We’ve been talking about this on LinkedIn and here are some thoughts.
Why Writing Skills Are More Important
- Technical writing is about writing. Words are the foundation upon which the rest is built.
- If you don’t have the writing skills, then regardless of how well you know the application, you can’t explain how it works.
- Your ability to drill down and describe complex functions may be beyond your grasp.
- To resolve this involves arranging sessions & workshops with developers, IT architects etc, all of which cost time/money.
- If writing skills were not necessary, programmers could write the user guides! Ever see a well-written user guide from a 22 year old Java developer? There are exceptions but…
- Technical writing is about communication. Technical writers are trained to interview people and extract the relevant information. Of course, listening skills are not exclusive to technical writers but many (that I know) feel they grasp the importance of this more than others.
- Writing skills give you the tools to communicate – and to help/teach others to communicate.
FYI – One of the trends I see in Tech Comms, is the changing role of the Technical Writer / Technical Communicator into an educator, facilitator, and becoming the central point of contact for technical information distribution (i.e. technical information coordination).
The counter argument is as follows.
Why Technical Skills Are More Important
- Technical knowledge is the starting point. You need to know how the system works, otherwise all the writing skills in the world may be of little use. If you don’t know what it actually does, what can you begin to write?
- Most ‘non-technical’ technical writers (e.g. graduates with English degrees) waste/take up developers’ time asking questions about how the application works, instead of actually generating content. While there is some leeway here with new technologies, developers have their own deadlines and can’t be expected stop coding to explain the innards to the application.
- Those with technical skills can hit the ground running – it’s the responsibility of the Technical Editor to refine the text.
- Those with technical skills know which questions to ask. As they understand the application/industry/codebase they can ask the hard questions that ‘non technical’ writers would not see in the first place.
Which would you hire?
If you were running a technical writing dept, which type of person would you hire?
A technical writer with strong technical skills, but prone to the occasional typo, or someone with perfect grammar, sound writing skills, but low on technical knowledge?
PS – you can connect with me on LinkedIn here – http://www.linkedin.com/in/ivanwalsh
“Don’t worry” she said. “No one reads this stuff anyway. Just get it done.” Sounds familiar? Continue reading Are technical documents a waste of time?
Technical Writing attracts women. They’re very good at it and make great team leads.
Maybe I’ve been very lucky but I believe women are far better as technical writers than men.
Here are five areas where I think they have the edge of the guys.
When in entered technical writing, I assumed my days would be spent cranking out user guides on Adobe FrameMaker. Little did I know that a large part of my day would be spend chasing developers for specs, calling testers for bug reports, and working with customers (often non-English) to update the release notes.