Some months ago, I suggested that our job title does not support a technical author’s career progression as we take on additional tasks, such as project management.
It defines us as writers, even though many of us have quietly become something much broader.
My question:
How many technical authors have gradually taken on additional responsibilities without ever changing their job title?
And how many of us have done project management work simply because no one else understood how documentation actually works?
It happens more often than people realise.
Technical authors rarely stay confined to writing manuals.
Over time, most experienced technical authors develop deep knowledge of systems, processes, and operational environments. That knowledge naturally pulls them into wider roles.
Research shows that technical writing is often a springboard into roles such as project management, product management, quality assurance, and business analysis because writers accumulate extensive organisational and technical knowledge.
Many technical authors never formally move into new roles; we simply absorb extra responsibilities.
Documentation work is already project management
Much of what experienced technical authors do already overlaps with project management.
Senior documentation roles often include:
-
-
- Prioritising work
- Defining documentation strategy
- Coordinating contributors
- Managing review cycles
- Reporting progress
-
These are recognised project-management responsibilities in documentation environments.
Many technical authors manage:
-
-
- Documentation schedules
- Review cycles
- Deliverables
- Risks
- Dependencies
- Stakeholders
-
Without ever being called project managers.
The skills overlap is not accidental
Project management research identifies core skills such as:
-
-
- Communication
- Organisation
- Leadership
- Technical understanding
-
These are the same skills technical authors use every day.
Technical authors succeed because they:
-
-
- Interview subject matter experts
- Coordinate contributors
- Structure complex information
- Track document progress
- Identify gaps
- Solve process problems
-
These are not purely writing activities.
They are delivery activities.
The reality on many projects
Project managers often understand delivery milestones but not documentation lifecycle requirements.
This creates a gap into which technical authors step.
Many of us have found ourselves responsible for:
-
-
- Incident management documentation
- Disaster recovery documentation
- Operations manuals
- ITIL-aligned processes
- ISO 27001 documentation
- ISO 9001 quality documentation
- Data centre migration documentation
- Knowledge repositories
-
Not because it was in the job description. Because someone had to do it.
The Unofficial Project Manager
It is not unusual for a technical author to become the unofficial project manager for documentation.
Technical writers may even move formally into project management or leadership roles, or manage documentation teams and projects as their careers progress.
But many never do.
The title stays the same.
The responsibilities expand.
When the project manager doesn’t understand the documentation
One common situation is where:
-
-
- The project manager understands schedules and budgets
- The technical author understands deliverables and structure
-
When documentation is poorly planned, the technical author often becomes the person who:
-
-
- Defines what must be delivered
- Structures the repository
- Establishes review routes
- Identifies missing inputs
- Keeps documentation moving
-
Without that intervention, documentation often becomes chaotic.
The hidden expertise
Experienced technical authors often know far more than their job titles suggest.
Years of working across projects create knowledge in areas such as:
-
-
- IT service management
- Information governance
- Document control
- Audit preparation
- Operational readiness
- Knowledge management
-
This knowledge is rarely visible on an organisation chart.
But projects depend on it.
Know your Technical Author
Many organisations underestimate technical authors because of the title.
“Author” sounds narrow.
“Writer” sounds administrative.
The reality is usually very different.
Some technical authors have quietly been:
-
-
- Documentation strategists
- Information managers
- Process designers
- Governance specialists
- Delivery coordinators
-
And sometimes project managers in everything but name.
The real question
So here is the real question:
How many technical authors have been doing project management work for years without being recognised for it?
And perhaps an even better question:
Is the title technical author no longer big enough to describe the role?