Skip to main content

11 posts tagged with "Documentation"

View All Tags

Customer Survey Results: NPS 94 and Real Productivity Gains for Technical Writers

· 3 min read
Mattias Sander
Mattias Sander

We recently asked Improvementsoft users a simple question:

"How likely are you to recommend Improvementsoft to a peer?"

The result: Net Promoter Score: 94

For context, an NPS above 70 is considered world-class. A score of 94 means that nearly every customer who responded would actively recommend Improvementsoft tools to their peers.

But numbers are only part of the story. The most interesting part of the survey was how customers described the impact on their work.

RAG Pipelines and Documentation: Why the Content Layer Is Your Biggest Risk

· 6 min read
Mattias Sander
Mattias Sander

Your RAG pipeline is only as good as the content it retrieves. Teams spend months tuning embeddings, chunking strategies, and prompt templates — then feed the system documentation that was never designed for machine consumption. The result is confident, well-formatted answers built on garbage retrieval. The content layer is where most RAG implementations silently fail.

Quality Drift in Documentation: How It Starts, How It Compounds, How to Stop It

· 6 min read
Mattias Sander
Mattias Sander

Nobody ships a documentation project with the intention of letting quality degrade. It happens anyway. Not in a single event, but through hundreds of small decisions — a shortcut here, an exception there, a new writer who follows the patterns they see instead of the patterns you intended. This is quality drift, and by the time it becomes visible, the cost of fixing it has multiplied.

DITA to MadCap Flare: A Practical Conversion Guide

· 7 min read
Mattias Sander
Mattias Sander

Moving from DITA to MadCap Flare is not a simple file conversion. It is an architecture change — from a topic-based XML standard with maps and specializations to a topic-based XML editor with its own structural model. Getting the files across is the easy part. Getting the architecture right is what determines whether the migration succeeds or creates a new set of problems.

Why Your Documentation Will Break Your AI Implementation

· 6 min read
Mattias Sander
Mattias Sander

Enterprise AI projects are failing at a remarkable rate, and the usual suspects — model selection, prompt engineering, integration complexity — get all the attention. But there is a quieter, more fundamental problem that undermines AI initiatives before they produce a single useful answer: the documentation that AI is supposed to learn from is not structured well enough for AI to use.