Why would I want to read an article?
Projects explain what happened. Case studies explain how a problem was solved.
Articles ask whether there is something broader to learn from those experiences.
Their primary purpose is to answer a simple question:
What observations are worth considering?
The articles collected here explore recurring themes that have emerged through documentation initiatives, developer experience projects, governance activities, and professional practice. They discuss patterns, tensions, and assumptions that may not be obvious while delivering a project but often become clearer when viewed across multiple engagements.
They are intended for readers who enjoy stepping back from immediate deliverables to consider how documentation practices evolve, why certain challenges continue to appear, and what they might suggest about the future of technical communication.
Featured Articles
Follow the links below to read more about each article
The Expertise Paradox
When Good Technical Writing Is Mistaken for Artificial Intelligence
As artificial intelligence becomes increasingly capable of generating convincing content, traditional assumptions about authorship, expertise, and professional capability are being challenged. This article explores the relationship between technical writing and AI, the limitations of AI detection tools, and what professional expertise may look like in an AI-enabled world.
The Evidence Gap
What AI revealed about measuring documentation work
Documentation teams are often asked to demonstrate value using measurements inherited from publishing. This article explores why those metrics may be insufficient, how AI unexpectedly revealed previously invisible work, and why documentation may be better understood as a mechanism for preserving institutional memory.
The Self Service Illusion
Why organisations invest in self-service while people seek human assistance
Self-service initiatives often appear successful, yet familiar questions continue to be asked, and confidence quietly migrates towards conversations, chat messages, and personal notes. This article explores why access to information and trust in information are not always the same thing.
What Documentation Reveals
Documentation as evidence of how organisations adapt to change
Documentation teams are often asked to improve content, migrate platforms, or modernise delivery. Yet many initiatives struggle for reasons unrelated to documentation itself. This article considers whether documentation reveals how effectively an organisation manages knowledge, ownership, decision-making, and change.
Rather than asking whether documentation is good or bad, it may be more useful to ask what it reveals about the systems that created it.
Themes and Topics
The articles published here explore recurring themes that have shaped my work throughout my career.
- Documentation Transformation
- Information Architecture
- Documentation Governance
- Developer Experience
- Content Strategy
- Human Expertise in an AI-Enabled World
Encouraging Reflection
The articles included here are intended to encourage thoughtful consideration rather than persuade readers towards a particular viewpoint. Technical communication often involves balancing competing priorities, navigating constraints, and making decisions in complex environments.
For that reason, many of the questions explored do not have simple answers. My aim is to share observations, explore implications, and provide perspectives that help readers think more deeply about the role documentation plays within organisations and the wider profession.
The most valuable outcome of any article is not necessarily agreement. It is to help readers see a familiar challenge in a new way.
