Technical Authors: Do you need a new job title

The Traditional Job Title

• • • A Technical Author meant someone who wrote manuals, user guides, or specifications.
    • The focus was on producing text-heavy deliverables that explained systems, processes, or products.
    • The work was bound and recognisable — you delivered documents.

The Modern Reality

Today, we do far more than write:

• • • Information architecture: structuring knowledge bases, designing content workflows, or building taxonomies.
    • Content strategy: deciding what to document, why, and in what format (DMS, CMS, wiki, KB, PDFs, APIs, microcontent).
    • Process design: defining review loops, approval gates, and compliance documentation.
    • Tools & technology: working with Asite, SharePoint, Git, MadCap Flare, Confluence, or API documentation platforms.
    • Training & enablement: running workshops, teaching engineers to write, or creating templates and style guides.
    • Governance & compliance: PCI/DSS, ISO 27001, GDPR, and other regulated frameworks often fall into our remit.
    • In short, the “writing” is still there, but it’s often 20–40% of the role. The rest is closer to content management, knowledge management, or even business analysis.

The Tension

If your business card says Technical Author, but you spend most of your time on:

• • • structuring SharePoint sites,
    • managing metadata,
    • training colleagues,
    • support
    • Or developing a documentation strategy,

…then the title undersells both your contribution and your market value. It can also confuse managers, who may assume you’re “just a writer” and overlook your broader impact.

Evolving Job Titles

Some organisations have already rebranded the role. Common alternatives:

• • • Technical Writer (US equivalent, though still too narrow).
    • Content Designer (favoured in government/service design circles).
    • Documentation Manager or Information Manager.
    • Knowledge Manager (especially when linked to systems like Confluence or Asite).
    • Content Strategist (if you lead on planning/documentation governance).
    • Information Architect (if your role is very structural and metadata-driven).
    • Document Management (SharePoint) administration

Why a Title Change Matters?

• • • Recognition: Reflects the breadth of what you do.
    • Career Progression: Opens paths into strategy, KM, or management.
    • Market Value: Recruiters and hiring managers may undervalue a “technical author” compared to a “knowledge manager” or “content strategist.”
    • Personal Motivation: Titles can shape how you (and others) view your role.

A Balanced View

That said, there’s value in keeping “technical author” alive — it is still a recognised profession, and many industries (engineering, aerospace, IT) rely on that clarity. The trick is whether your work is still 80% authorship or whether the writing part has become a byproduct of a much larger scope.

Conclusion:

If you now spend more time on governance, strategy, architecture, and training than writing, then yes, the title Technical Author may no longer serve you. It hasn’t reached “end of life” as a profession (there’s still plenty of need for core documentation specialists), but your role might have evolved into something broader. The challenge is to choose a new title that captures both your expertise and the value you bring.