Clear information. Practical processes. Documentation people can actually use.
Good documentation should make work easier to understand, easier to perform, and easier to maintain.
Alongside my creative practice, I bring extensive professional experience in technical writing, process documentation, process analysis, and the development of practical information for operational environments.
My work focuses on taking complex, fragmented, or inconsistent information and turning it into documentation that is clear, structured, and useful. This may involve understanding how a process currently works, speaking with the people who perform it, identifying gaps or inconsistencies, mapping workflows, and translating that knowledge into procedures, guides, and other documentation that people can confidently follow.
I am particularly interested in projects where documentation needs to do more than simply exist. It should reflect the real process, support the people using it, and provide an accurate and maintainable source of knowledge for the organisation.
Documentation Services
I can assist organisations with the development, review and improvement of a wide range of operational and procedural documentation.
This includes:
- Standard Operating Procedures
- Process and workflow documentation
- Technical and procedural documentation
- User guides and operational manuals
- Knowledge base and reference material
- Policies, procedures, and supporting instructions
- Business process documentation
- Process maps and workflow diagrams
- Existing-documentation review and improvement
- Content restructuring and simplification
- Documentation governance and version control
- Information and knowledge organisation
Projects may involve developing documentation from the ground up or working with existing material that has become outdated, inconsistent, fragmented, or difficult to use.
Process Documentation
The strongest documentation usually begins with understanding the process itself.
Before writing, I seek to understand how work is actually performed, not simply how it is assumed to operate.
This can involve conversations with subject matter experts and operational staff, reviewing existing material, observing workflows where appropriate, comparing documented and actual practice, and identifying areas where information is unclear, duplicated, or missing.
From there, I can help document the current process, clarify responsibilities and decision points, and create a structure that is easier for people to understand and follow.
Where useful, processes can also be represented visually through workflow diagrams and process maps, including work developed in Microsoft Visio.
The objective is not unnecessary complexity. It is clarity.
Standard Operating Procedures
A good Standard Operating Procedure should guide the reader confidently through a task without requiring them to interpret vague instructions or search elsewhere for essential information.
I develop SOPs with particular attention to:
- Logical sequencing
- Clear responsibilities
- Plain and consistent language
- Decision points and exceptions
- Safety and operational requirements
- Supporting references and related documents
- Version control and ownership
- Ease of maintenance
- Practical usability for the people performing the work
Where possible, I prefer to develop procedures in consultation with the people closest to the process. Their experience often reveals important details that cannot be discovered by reviewing existing documents alone.
Process Mapping & Analysis
Documentation projects often reveal opportunities to better understand how work flows across an organisation.
My background includes process analysis and mapping, including documenting current-state and future-state processes, identifying gaps and duplication, and working with stakeholders to clarify how information, responsibilities, and activities move through a process.
Process maps can help organisations:
- Understand complex workflows
- Clarify roles and responsibilities
- Identify bottlenecks or unnecessary duplication
- Support procedural documentation
- Capture organisational knowledge
- Assist with change and transition
- Provide a common reference point for stakeholders
The emphasis is always on creating something people can understand and use, rather than producing complexity for its own sake.
Documentation Review & Improvement
Not every project requires new documentation.
Sometimes the greater value lies in improving what already exists.
I can review existing procedures, manuals, guides, and process documentation to identify areas where content may be:
- Outdated
- Inconsistent
- Repetitive
- Difficult to navigate
- Written in overly technical language
- Missing important information
- Poorly structured
- Misaligned with current practice
- Difficult to maintain
Existing content can then be reorganised, rewritten, or consolidated into a clearer and more consistent documentation set.
This can be particularly valuable for organisations that have accumulated documents over many years or across multiple teams and now need a more coherent approach.
Knowledge & Information Documentation
Important organisational knowledge often exists in many places at once: within documents, shared drives, systems, email conversations, informal instructions and, most importantly, in the experience of individuals.
When that knowledge is not captured effectively, organisations can become dependent on particular people or vulnerable when roles change.
I can help bring that information together into structured knowledge resources that are easier to find, understand, and maintain.
This may include:
- Knowledge articles
- Reference guides
- Operational information
- Process libraries
- Supporting documentation
- Information architecture and document organisation
- Content migration and restructuring
- SharePoint-based documentation and information environments
My experience includes working with document and information migration into SharePoint environments, together with the organisation and restructuring of existing information.
How I Work
My approach begins with listening.
Documentation cannot be developed well without first understanding the people, processes and environment behind it.
Depending on the project, this may involve:
Discovery and research
Reviewing existing documentation, systems, process information, and other source material.
Stakeholder consultation
Speaking with subject matter experts, process owners, and operational staff to understand how the work is performed in practice.
Process analysis
Identifying the sequence of activities, responsibilities, decision points, dependencies, gaps and inconsistencies.
Structure
Determining the clearest way to organise the information before beginning detailed writing.
Drafting and mapping
Developing procedures, guides, process maps, or other documentation using clear, consistent language.
Review and validation
Working with stakeholders to confirm that the documentation accurately reflects the process.
Refinement
Incorporating feedback, improving usability, and ensuring that the final material is consistent and maintainable.
The result should be documentation that feels straightforward to the person using it, even when the process behind it is complex.
Professional Experience
My documentation experience has developed across a range of operational, corporate, and project environments.
It includes work involving technical and process writing, Standard Operating Procedures, process analysis, process mapping, operational documentation, knowledge resources, document migration, and information management.
I have worked directly with stakeholders and operational teams to understand processes, document current practice, identify gaps, and transform complex information into clear written and visual material.
My background has also involved environments where accuracy, governance, procedural consistency, operational risk, and the ability to maintain reliable records are important.
Tools and approaches I have worked with include Microsoft Visio, Microsoft SharePoint, Microsoft Office, process mapping, workflow analysis, stakeholder interviews, document governance and structured procedural writing.
What I bring to documentation work is not only writing ability, but the capacity to investigate, question, organise and understand the information before attempting to explain it.
Writing for the Reader
One principle sits behind all of my documentation work:
The document is written for the person who needs to use it.
That may sound obvious, but procedural documentation can easily become shaped around organisational structures, technical language, or the knowledge of the person who created it rather than the needs of the reader.
I aim for documentation that is:
- Clear
- Accurate
- Logical
- Concise
- Consistent
- Easy to navigate
- Appropriate to its audience
- Practical in real-world use
Complexity should exist only where the process itself requires it.
Good documentation should reduce uncertainty, not create more of it.
Selected Project Support
I can contribute to documentation projects involving:
- Creation of new SOP or procedure libraries
- Review and modernisation of existing documentation
- Process discovery and documentation
- Process mapping
- Operational knowledge capture
- Documentation associated with organisational change
- Knowledge and information-management initiatives
- Documentation governance and standardisation
- SharePoint documentation and information restructuring
- Short-term documentation uplift projects
- Contract and project-based technical writing
Engagements can range from an individual procedure or process through to broader documentation programs requiring research, stakeholder consultation, and structured development.
Working Together
The best documentation begins with understanding.
Whether the requirement is a new Standard Operating Procedure, an undocumented operational process, a confusing collection of existing material or organisational knowledge that needs to be captured before it is lost, my role is to make that information clearer, more structured and more useful.
I bring together writing, research, process thinking, and attention to detail, while remaining focused on the people who will ultimately rely upon the documentation.
If your organisation has a process that needs to be understood, knowledge that needs to be captured, or documentation that needs to become clearer and more practical, I would be pleased to discuss how I could contribute.
Good documentation turns knowledge into something that can be understood, shared, and carried forward.