Business analysis has established itself as a standard in structured career paths. Business analysts operate within a framework that includes certifications from BCS and IIBA, as well as a global knowledge base represented by the BABOK. They play a vital role in driving business success. However, why hasn’t technical authoring training kept pace with the discipline and received the same level of recognition?
Yes, there are training courses for technical authors—but for those of us with real-world experience, most courses offer little new. They often cover areas we’ve long since mastered: writing, using templates, and understanding basic tools. That leaves a pressing question:
Why hasn’t the technical writing profession grown to support mid- to senior-level authors with meaningful, strategic development?
The Perception Problem: Writers vs. Strategists
Part of the issue lies in perception. People often view technical writing as a “support function”—a downstream activity added after the “real” work is done. In contrast, business analysts work upstream, shaping project and product design.
Because of this, organisations rarely invest in upskilling technical writers beyond entry level. We receive tool-specific training, such as MadCap Flare, FrameMaker, and DITA, as well as refresher courses on grammar and plain English. Training in information strategy, content governance, and integrating documentation with Agile processes is essential, yet it is rare. These skills are vital for technical writers to excel in high-performing digital teams.
Why Experienced Technical Authors Avoid Most Training
As a senior technical author, I know training courses are available on the market, but I’ve yet to find any that add value to what I already know.
Here’s why most courses don’t appeal to experienced writers:
-
-
- Too basic, they cover foundational topics like sentence clarity, structure, and Microsoft Word formatting.
- Tool-led, not strategy-led: Courses focus on software, not how to use documentation to improve business outcomes.
- One-size-fits-all: Most assume a junior audience, not someone managing document lifecycles or architecting knowledge bases.
-
This gap motivated me to independently pursue learning through peer networks, mentoring, and cross-disciplinary knowledge, often without formal recognition or support.
What Training for Technical Authors Should Look Like
If we’re to upskill and advance, we need training that goes beyond surface-level writing mechanics.
High-Value Topics for Mid-to-Senior Technical Authors:
| Focus Area | Why It Matters |
|---|---|
| Information Architecture & UX Writing | Create usable, intuitive, and findable documentation across systems and platforms. |
| Agile/DevOps Documentation Integration | Align with sprint cycles and release documentation iteratively. |
| Content Governance & Strategy | Build scalable systems for content reuse, version control, and quality assurance. |
| Metadata and Taxonomy Design | Essential for working in SharePoint, Asite, or any modern content repository. |
| API & Developer Docs | More projects now require integration-level documentation and OpenAPI familiarity. |
| AI-Assisted Authoring learn | how to partner with, not be replaced by, content generation tools. |
| Accessibility and Inclusive Writing | Meet compliance, usability, and ethical standards for broader audiences. |
The Bigger Issue: Lack of a Unified Knowledge Base
Business analysts have the BABOK, project managers have PRINCE2 and PMBOK, and technical authors? We have fragmented resources, small communities, and ad hoc training.
There is currently no universally accepted body of knowledge that technical authors follow. No recognised framework exists that organisations can use to:
-
-
- structure roles,
- develop teams, or
- plan career paths for technical writers.
-
Until we establish such a structure, we will continue to be seen as individual contributors rather than strategic enablers.
What Needs to Change
To elevate the profession of technical authoring, we need:
-
-
- Advanced Masterclasses for experienced authors.
- Courses that blend strategy, tech, and communication, not just software skills.
- Advocacy from inside the profession—to influence HR, procurement, and leadership views.
- Recognition of our roles in content strategy, product success, and compliance.
-
Final Word: It’s Time to Professionalise the Profession
Training for technical authors exists, but unless it reflects the real-world complexity of our roles, it won’t be worth our time or investment.
Technical authors are no longer just documenters—we’re architects of information. Our training, recognition, and role in organisations must reflect that.
Let’s continue the conversation
Have you taken a valuable course? Do you want to help shape better training for technical authors? Let’s talk.