How Can I help you? | Michael Clark

Technical Authoring, Documentation Strategy and Information Management

If your organisation depends on policies, procedures, operating documents, SharePoint, Confluence or controlled documentation, the quality of that information matters. Poor documentation wastes time, creates risk and leaves teams guessing when they need clear answers.

I help organisations plan, write, structure and improve technical documentation so that information is accurate, usable and easier to manage.

Documentation problems I can help solve

  • Technical documentation for IT, infrastructure and transformation projects
  • Policy, process and procedure documentation
  • Documentation strategy and document lifecycle control
  • SharePoint, Confluence and document management structure
  • ISO 27001, ITIL, GDPR, PCI and audit-support documentation
  • Knowledge capture from subject matter experts

Why documentation needs structure

Documentation projects rarely fail because people cannot write. They fail because the work is not scoped, ownership is unclear, content is duplicated, review cycles are weak, and nobody controls the information after publication.

A technical author brings structure to that problem. The work includes discovery, interviews, document planning, content design, version control, review management and long-term maintenance thinking.

Core services

Technical authoring

Clear, structured technical documents, operating guides, installation guides, process narratives and user-focused content.

Documentation strategy

Planning documentation estates, identifying gaps, reducing duplication and defining how documents should be owned, reviewed and maintained.

Information management

Improving how information is organised, named, stored, retrieved and trusted across repositories such as SharePoint and Confluence.

SharePoint and Confluence governance

Supporting repository structure, ownership, document control and governance for teams that need trusted information.

Useful articles

Start with the information problem

If your documentation is scattered, duplicated, outdated or difficult to trust, the first step is to understand the information problem before writing more content. A structured approach can reduce risk, improve findability and make documentation more useful to the people who rely on it.