Technical Competence
The clue is in the name: technical communicator. But what does it really mean to demonstrate technical competence and why is this important?
Introduction
Technical communicators are often required to write about a wide range of topics and, over the course of their careers, may need to produce content in areas where they are not subject matter experts. Most develop broad general knowledge across multiple domains, however they may lack the specialised expertise required for a specific technical field.
This raises an important question: is it possible to write effectively about a subject that you do not fully understand?
When is technical knowledge a pre-requisite?
Certain specialised fields—such as law, medicine and engineering—demand a solid foundation of technical knowledge to ensure that documentation is accurate, relevant and comprehensible to its intended audience. In these cases, the communicator must understand not only the subject matter but also how end users within that domain work, interpret information and apply it in practice. Some background knowledge and experience are therefore critical to writing effectively in these contexts.
When is technical knowledge not required?
A contrasting view is that writers need not be experts in the content itself, as long as the material they receive is technically accurate. The communicator’s strength lies in shaping, structuring and expressing information clearly, concisely and logically. They must be able to identify gaps, ask relevant questions and verify ambiguous details to ensure the information is presented correctly and serves its purpose.
My perspective
Through my company, Cambridge Technical Communicators, I have worked on numerous projects where I was not initially familiar with the domain.
In one project, I interviewed software engineers to understand how their code supported website applications. In another, I developed user documentation for an electronic semiconductor product aimed at electrical engineers. In both cases, my subject knowledge was limited.
While I contributed significantly to content layout, formatting, organisation and language quality, my ability to assess whether the technical information was accurate or sufficient was limited. I could reliably answer, “Is this clear and grammatically correct?” but not “Is this the information the user needs and is it technically correct?”
A lack of deep technical understanding is workable to a point, provided the writer has the aptitude and contextual awareness to grasp core concepts. Beyond that point, however, it can become counterproductive to involve a communicator who lacks the fundamental knowledge needed to assess accuracy or completeness.
Developing technical competence
Writers entering a new organisation or domain can build technical competence over time through study, practice and experience. This may involve completing relevant training courses, reading industry literature or working closely with experts to understand the products, systems and technologies being documented.
Producing accurate and reliable documentation may also require direct interaction with the technology—such as testing software, interfaces or APIs—to confirm that the product behaves as described. Developing enough technical understanding to perform these checks effectively can improve both the writer's confidence and the output quality.
Conclusion
To produce accurate, relevant and user-focused technical content, communicators must develop a solid understanding of the concepts, tools and processes central to their subject matter. This includes gaining familiarity with relevant coding languages, systems or domain-specific tools, allowing for meaningful communication with experts and deeper comprehension of the material.
The technical communicator must find the right balance. When knowledge is limited, collaboration with subject matter experts is essential to define direction and ensure content accuracy. As understanding increases, the communicator can take a more proactive role—defining, structuring and authoring content with minimal support.
Over time, consistent curiosity and diligence lead to true technical competence. By progressively building expertise, technical communicators not only enhance the quality of their work but also evolve into subject matter experts in their own right.