Tag: compliance documentation

Don’t Overlook the Technical Author: A Question for Project Managers

Project managers often bring technical authors in too late. Experienced technical authors can reduce delivery risk by shaping documentation early—supporting IT audits, ITIL-aligned processes, ISO 27001/ISO 9001 controls, disaster recovery packs, incident and change management, and operations manuals. Know your technical author before you assume their limits.

Tweet
Pin
Share
0 Shares

Here is a question for project managers:

How many projects did you manage where the team treated the technical author as an afterthought or excluded them entirely?

It happens more often than it should. Project managers view documentation as something to “do at the end”, once the teams finish the proper work and the delivery pressure is at its peak.

That is when teams discover the cost of leaving documentation too late.

By the time the project is in closure mode, you have already missed the point where a technical author adds the most value.

The mistake: assuming the technical author is “just a writer”

Many project managers underestimate what an experienced technical author actually does. They think we:

      • only polish text,
      • rewrite technical material in plain English,
      • only fix formatting.

That is only one part of the job.

Technical authors understand IT operations and governance. They have documented services for years. This experience extends to audits. They know how to gather evidence.

What an experienced technical author may already know

A technical author may already have delivered documentation for:

      • IT audits and compliance preparation
      • Disaster recovery (DR) documentation
      • Operations manuals and runbooks
      • Incident, problem, and change management processes
      • Service transition documentation
      • Knowledge base and repository design
      • Information governance and document control
      • Data centre migration documentation
      • ITIL-aligned documentation structures
      • ISO 27001 and ISO 9001 aligned document frameworks

These are not theoretical skills. They come from being repeatedly embedded in delivery and operational environments across different organisations and clients.

The risk: documentation gaps that become delivery risks

When you exclude technical authors from early planning, projects often run into the same problems:

      • They discovered the documentation gaps late.
      • Missing operational detail that prevents handover
      • Inconsistent terminology and process steps
      • Rework caused by unclear ownership and review routes
      • Poorly structured repositories that no one can navigate
      • Evidence gaps that become audit risks
      • Last-minute “document sprints” that no one has time for

These issues are rarely “writing problems” but planning problems which are avoidable.

Know your technical author before you assume their limits

Every technical author has a unique history. Some come from engineering, some from software and infrastructure, some from compliance-heavy environments, and some from service operations.

You will not know what capabilities you have access to unless you ask.

Here is a simple, early-project habit that saves pain later:

Sit down with the technical author and establish what they’ve done before.

Ask questions like:

      • What types of projects have you supported?
      • What frameworks do you work with (ITIL, ISO 27001, ISO 9001)?
      • What operational documentation have you delivered (DR packs, ops manuals, runbooks)?
      • What documentation risks do you expect on a project like this?
      • What do you need from the team to avoid last-minute document chaos?
      • You may find they know more about documentation governance, operational readiness, and audit evidence than you expected.

Documentation is not an output. It is part of the delivery.

Documentation is not a box to tick at the end.

It is part of how projects:

      • reduce operational risk
      • pass audits
      • transfer knowledge
      • support teams
      • enable safe change
      • transition into BAU without firefighting

A technical author is not “just the person who writes things down”.

A strong technical author is often one of the few people on a project who thinks in terms of:

      • structure
      • lifecycle
      • traceability
      • usability
      • governance
      • evidence

Last point: never overlook the technical author

If you want better delivery outcomes, involve documentation earlier and treat it as a work stream with ownership and design—not a clean-up job.

Never overlook the technical writer.

Because the best technical authors are not just documenting your project.

They can make it work.

Have you ever consulted your technical author on previous deliverables to identify and reduce project risks?

When Is a Document Strategy Not a Strategy?

A practical guide for organisations that want governance to work

Tweet
Pin
Share
0 Shares

A practical guide for organisations that want governance to work

In many organisations, a document strategy looks impressive.

      • It has executive sponsorship.
      • It references digital transformation.
      • It talks about lifecycle, governance, compliance, and knowledge reuse.

And yet — nothing changes.

      • Documents are still duplicated.
      • Templates are ignored.
      • Review cycles drift.
      • Audit findings repeat.

At that point, the issue is not the document strategy itself. The issue is how the organisation treats the strategy document as the outcome, rather than as a mechanism for decision-making.

This article examines when a document strategy stops being strategic — and how to recognise the difference between a living governance framework and a glossy artefact.

What is a document strategy?

A document strategy should define:

      • How information is created

      • How it is controlled

      • How it is reviewed

      • How it is distributed

      • How it is kept or archived

      • Who is accountable at each stage?

In regulated environments — particularly those aligned with ISO 27001, ISO 9001, PCI-DSS, nuclear, defence, or financial services — this is not optional. Documentation underpins audit defensibility and operational resilience.

However, a document strategy becomes ineffective when it fails to influence real-world behaviour.

1. If it avoids constraints, it is not a strategy

A genuine strategy makes trade-offs.

It defines constraints such as:

        • Budget limits

        • Tooling capability

        • Cultural maturity

        • Political appetite for enforcement

        • Regulatory exposure

If a document strategy attempts to optimise for:

        • Speed

        • Full compliance

        • Zero friction

        • Maximum flexibility

        • Minimal cost

Simultaneously, it is not strategic. It is aspirational.

For example:

      • You cannot have complete audit traceability without adding some process overhead.

      • You cannot maintain full template discipline while allowing unlimited author freedom.

      • You cannot achieve a single source of truth without closing down local storage practices.

Strategy requires subtraction. If nothing is excluded, nothing is prioritised.

2. If it does not change governance, it is Theatre

A document strategy must show up in operational systems.

You should see its fingerprints in:

      • Metadata schemas

      • Document numbering conventions

      • Version control rules

      • Approval workflows

      • Access permissions

      • Review cycles and SLAs

      • Archival and retention schedules

If your strategy claims to be a “single source of truth” but documents continue to sit on local drives, shared mailboxes, and uncontrolled Teams folders, then the strategy has not reshaped behaviour.

If it promises improved knowledge reuse but there is no taxonomy, no tagging discipline, and no ownership of content review, it remains rhetoric.

A useful test is this:

      • Did the strategy alter the document lifecycle?

      • Did it remove duplicate repositories?

      • Did it redefine what “approved” means?

      • Did it assign clear accountability?

If not, it is governance theatre.

3. If it cannot be operationalised, it is Philosophy

Strategic language often becomes abstract.

      • “Drive digital transformation.”

      • “Enhance collaboration.”

      • “Embed knowledge excellence.”

These statements are ambitions, not mechanisms.

Operational strategy answers concrete questions:

      • Who owns lifecycle integrity?

      • What is the RACI model?

      • What happens when review deadlines are missed?

      • What constitutes a controlled document?

      • What is the escalation path for non-compliance?

      • What is the maximum tolerated duplication level?

If delivery managers and technical authors cannot convert the strategy into day-to-day rules, then it is conceptual rather than actionable.

In high-compliance sectors, this gap becomes visible during audits. Auditors increasingly test evidence of implementation, not the existence of documentation.

4. If it does not influence decisions, it is Decorative

A real document strategy shapes:

      • Recruitment decisions

      • Tool selection

      • Investment priorities

      • Change control

      • Incident response

      • Audit preparation

If no board paper references it, if no funding decision cites it, and if no hiring decision reflects it, then it is decorative.

A strategy that is only opened during audit season is not embedded.

5. If it is written only for executives, it will fail

Authors write strategies in executive language:

“We will implement a structured document lifecycle aligned to industry best practices.”

Delivery teams interpret this as:

“Another template change.”

If engineers, technicians, and operational staff cannot explain what the strategy means for their daily work, the communication has failed.

Clarity is structural. Not cosmetic.

In environments where engineers write occasionally rather than professionally, a well-designed template with enforced styles often achieves more than a 30-page style guide.

If the strategy does not account for real author behaviour, it will be bypassed.

6. If it ignores culture, it is naive.

People do not resist governance for ideological reasons. They resist friction.

If your document strategy increases:

      • Form complexity

      • Metadata burden

      • Approval latency

      • Review bottlenecks

Without demonstrating value, users will route around it.

A realistic strategy accounts for:

      • Author maturity

      • Training capability

      • Tool usability

      • Political support for enforcement

It does not assume ideal behaviour.

The Digital Strategy Problem

Digital strategies often attempt to solve everything at once:

      • Content management

      • Knowledge management

      • Collaboration

      • Automation

      • AI

      • Governance

      • Records management

      • Compliance

      • Cultural change

This breadth dilutes focus.

A disciplined document strategy might say:

For the next 24 months, our priority is lifecycle control and audit defensibility. Automation and AI integration are out of scope.

That level of constraint is strategic clarity.

A Practical Test for Organisations

To assess whether your document strategy is real, ask three questions:

      1. What decision did we make differently because of this strategy?

      2. What did we deliberately choose not to do?

      3. Who would notice if we ignored it?

If no one would notice, it is not a strategy.

What a real document strategy looks like

A credible document strategy:

      • Defines constraints

      • Forces trade-offs

      • Embeds into tooling configuration

      • Alters decision rights

      • Clarifies accountability

      • Survives audit scrutiny

      • Is understood at operational level

      • Drives measurable change

In regulated and compliance-heavy environments, strategy is not narrative. It is architecture.

If it does not reshape structure, authority, and process, it is branding. Branding is not a strategy.