Clear, credible and appealing content that supports decisions, compliance and product adoption
Sales & Marketing
Communication models that make complex products tangible, attractive and easier to sell
I’m a Communications Specialist and Senior Technical Writer — drawn to everything TechDoc, TechSafety, and TechMarketing. I love both order and creativity, building on semantic layers, shaping information architecture, and connecting with passionate people across different industries.
I’m building a place for the things I care about most — documentation, safety, security, systems engineering, AI security, AI empowerment, information architecture, and technical product marketing.
A space where complex systems become understandable, where rules turn into real responsibilities, and where communication helps people work safely and confidently — and begin to envision what empowered, thoughtful technology could become.
New rules for AI systems demand something many organisations underestimate: documentation that is complete, accurate and traceable. At the same time, language models are reshaping how documentation is written, structured and consumed.
AI TechDoc Press covers both sides — what must be documented, and how to build content that people and machines can rely on. Additional topics include systems engineering, safety, security, CRA, global AI regulation and mental models.
Vision and mission
Our vision
A world in which every intelligent system comes with documentation that people can trust and machines can read — and in which the people who write it are recognised as the ones who make complex technology understandable, safe and accountable.
Our mission
AI TechDoc Blog turns AI regulation, standards and semantic methods into working knowledge for the people who document technology. We define terms with care, build open glossaries, learning paths and example projects, and show page by page how to create documentation that is complete, traceable and ready for human readers and AI systems alike.
Three slogans I love
1
“Good documentation is not a compliance by‑product. It is the evidence that a system is understood.”
Regulators ask for documentation, but its real value lies elsewhere: a system that can be described clearly, completely and traceably is a system its makers truly understand. Documentation is where that understanding becomes visible — and verifiable.
2
“Technical documentation is complexity made clear.”
Complex products do not need complicated explanations. Good technical writing untangles the structure, puts things in the right order and gives every reader exactly what they need to act with confidence.
3
“Storytelling based on facts makes good products shine from the inside out.”
Facts alone rarely stick, and stories without facts do not hold up. Combined, they reveal what makes a product genuinely good — its quality, its care and the thinking behind it — so that it shines on its own merits.
Every publication is written for practitioners: the technical writers, engineers, compliance specialists and information architects who turn requirements into working documents. The tone is calm, the sources are cited, and the examples are real enough to reuse.
Topics
EU AI ActConformity documentationInstructions for useRisk management recordsMetadata modelsTaxonomiesKnowledge graphsTerminology managementContent reuseRetrieval-ready content
Blog and Press
Two roles, one purpose
AI TechDoc Blog and AI TechDoc Press share a name and a subject, but they do different jobs. Together they cover the whole way from understanding a development to acting on it.
AI TechDoc Blog · this website
The reference you work with
A lasting workspace: glossaries with sourced definitions, the AI learning path, EPPO example projects, knowledge vaults, white papers and blog notes. Everything is structured, interlinked and kept up to date, so you can look things up, learn step by step and reuse what you find.
Evergreen and structured — revised, not archived
Glossaries, learning paths and example projects
For looking things up, learning and applying
AI TechDoc Press · newsletter on Substack
The analysis that keeps you current
The newsletter follows what changes: new regulation, amended deadlines, standards in progress and what they mean for documentation teams. Every issue is a source-based analysis with a clear argument, delivered to your inbox.
The Press explains what is changing and why it matters; the Blog holds the stable terms, methods and examples you need to act on it. Press articles link to the glossary entries that define their terms, and glossary pages point back to the analyses that put those terms in context.
Our policies
The policies published on my Substack apply to this website as well.