The business case for technical documentation is a topic that is on the agenda in many technical writing departments right now. Here is what really matters in practice, beyond marketing claims and tool promises.
The typical pattern in technical documentation
When it comes to larger investments in systems, I am asked again and again: „How many staff will we save with this?“
Whether it is about introducing a Component Content Management System (CCMS), a Translation Management System (TMS), or other information-management solutions, the business-case discussion lands on staff costs astonishingly quickly.
The problem: in practice this calculation almost never works out. I do not know a single robust case in which such a system in technical documentation actually caused a real and lasting reduction in headcount — at least not without clear negative side effects on quality, motivation, and project success.
My experience: 0. Not a single case.
And one more thing I keep having to say in leadership rounds: a project’s success is highly questionable when the very same colleagues are expected to introduce and establish a system that supposedly makes their own jobs redundant afterwards. That sounds self-evident, and yet I regularly see exactly this scenario being planned. With predictable results.
Time, then, to shift the view: away from job cuts, towards the value that such systems actually deliver.
The classic ROI mistake: focusing on staff costs
Why is the focus on saving staff so problematic?
It is professionally incomplete. The biggest effects of modern systems lie not in „fewer heads“ but in better processes, lower risk, and scalable work. Anyone who models only the staff costs blots out the genuinely interesting arguments.
It is organisationally dangerous. When a project is perceived as a rationalisation measure, acceptance drops massively. The best systems then fail because of a lack of cooperation and hidden resistance. Not because of the system itself, but because of the way it was communicated.
It is usually unrealistic. In practice it quickly becomes clear: content has to be created and maintained in more languages, for more target audiences, and in more channels. PDF, online help, portal, app — ten years ago that was still manageable. Today it is standard. With fewer staff, that is rarely seriously possible.
In short: the business case „we save staff by introducing new systems“ is rarely sustainable in technical documentation, and it blocks more than it helps.
Bear in mind, too: one day you may have to justify your investment. What if the savings sketched out at the time never materialised? Most companies are geared towards growth, a few percent every year. How do you intend to do „ever more“ with fewer people, while formal requirements and the number of use cases rise at the same time?
The bottleneck logic that gets overlooked
There is a connection I keep having to explain in everyday consulting, and which is almost entirely absent from these ROI discussions: the bottleneck logic.
If the technical writing department is the bottleneck in the process today — the point that delays orders because it cannot keep up with creating documentation — then a CCMS eases this bottleneck. Up to that point the calculation holds. But what happens when staff are cut at the same time as the system is introduced? Then the bottleneck shifts. Instead of too-slow information creation, you suddenly have too few people who can introduce, maintain, and develop the new system. The bottleneck is now the team — but with a more expensive system in the background that cannot realise its potential.
Managers are very quick to call for more resources, meaning people who do the work — internal or external. It is always worth looking closely and identifying whether the staffing level really is the bottleneck, or whether it is the processes, systems, or other circumstances in which these people have to work. If your technical writing department creates 300 documents with three staff, the unit could on average create 400 with four. In theory. But I cannot recommend looking at your metrics that superficially.
The real investment drivers: value instead of staff savings
Instead of eyeing job cuts, managers should justify investments in a CCMS, TMS & Co. through the value that acts directly on risk, quality, and scalability.
1. Data quality: from the document to a reliable body of information
A CCMS brings structure, modularisation, and consistent terminology into the documentation. That sounds technical, but it has very concrete effects: fewer contradictions between variants, product types, and versions; fewer errors with product changes; faster onboarding of new staff, because they can access structured, findable knowledge.
For management, that translates into fewer complaints and support efforts as well as a more professional external impression, because the documentation comes across as reliable and consistent.
2. Legal certainty: documentation as risk insurance
Technical documentation is often a legally relevant product feature. Many forget that until it is too late. A professional system supports versioning — which content applied to which product version — and traceability: who released what, and when? And it ensures availability: how quickly can relevant information be proven in a dispute?
I expressly recommend using legal certainty as a central argument for the investment. Liability risks can be reduced, and in product-liability cases or disputes, audit-proof documentation is the decisive basis. Management can then say: „We can prove what we communicated.“ That is an argument that is understood, even without a technical background.
3. Auditability and compliance: robust evidence instead of file chaos
In many companies, documentation is still organised with Office files and file servers — grown historically, opaque, barely audit-proof. I have seen companies where an audit caused serious stress because nobody could say for certain which document version was valid at the time of delivery. That is not a marginal problem.
A dedicated system offers defined review and release workflows, a complete history and change tracking, as well as clearly defined roles and responsibilities. The value: audit certainty towards customers, certifiers, and authorities, and significantly less effort in audits, because information is structured and findable.
4. Reuse: create content once, use it many times
An essential lever is the modular reuse of content. Standard blocks for safety instructions, function descriptions, product families — created once, deployed everywhere. Automated document assembly from blocks, reduction of redundant text maintenance in dozens of places.
The value: less maintenance effort with product changes, higher consistency across products, variants, and languages, and time gained for the writing department to attend to complex content and better user guidance.
Important: in reality, the capacity thus freed up is rarely used to cut positions. It is used instead to finally do what was left undone before. Closing compliance gaps, improving reuse, building new processes.
5. Translation costs: structure beats per-word price
A TMS and integrated translation processes unfold their greatest effect when structure and reuse are implemented consistently. Reused modules lead to fewer new translation segments — directly measurable in euros per year. Terminology management reduces rework and misunderstandings. Translation processes are standardised, non-value-adding activities automated or technically supported.
Anyone delivering products into several markets will find the most concrete savings here — not through job cuts, but through reduced translation costs over several years, less coordination effort with providers, and faster international product launches, because the documentation is able to grow in parallel.
6. Connectivity and integration: documentation as part of an information ecosystem
Modern systems are not an isolated tool but nodes in the flow of information. A connection to PLM, ERP, PIM, or service systems; use of the content in service portals, e-learning, knowledge databases; provision of information for after-sales, service, and sales.
The value: documentation changes from a mandatory burden into an active value-creating factor. Information is available where it is needed — for technicians, customers, and partners. Intelligent information can fulfil new tasks, and this value can also be monetised.
Why staff savings still rarely materialise
Despite all efficiency gains, practice shows: the volume of variants, languages, and media keeps increasing. Products become more complex, updates more frequent. Documentation is increasingly perceived as a strategic asset. And with the new possibilities of the systems come new use cases; the variety grows.
The systems therefore help, first and foremost, to make a growing workload manageable without immediately having to hire more staff — not to dismantle existing teams.
Freed-up capacity is used for better visualisations (graphics, animation, video), a uniform information architecture across product lines, and new formats such as online help, portals, and self-service offerings.
In other words: the systems prevent the collapse of teams; they do not make them redundant.
Change management: who voluntarily works on their own job cut?
An often underestimated aspect is the psychological effect of the argument.
When staff perceive that a new system is being introduced primarily to cut their jobs, the following happens: acceptance collapses, knowledge is withheld, problems are sat out instead of solved, the system is used as a token but not lived. The consequence: the system’s potential goes unused, shadow processes in Excel and Word persist, and the expected ROI fails to appear.
When I write about change management, I do not mean guru workshops along the lines of „you can achieve anything if you just want it!“. I think little of such approaches. What I mean is normal leadership behaviour: informing staff transparently about what the goals are and how they are to be achieved, and showing the development prospects that come with the tool. Staff can open up new fields of work for themselves and grow through the change itself.
A successful project therefore needs a clear message to management: „We are investing in professional systems so that our good people can work more efficiently, in order to improve quality, safety, and future viability — not to replace people.“
That is the prerequisite for the system to be able to realise its potential at all. Be consistent. Don’t let pseudo-arguments spook you — neither from those who want to keep walking the old path, nor from those who argue with job cuts to push the investment through.
You will not make friends in this phase. But your job is not to find friends, it is to position the department for the future.
How you, as a leader, can argue
Instead of calculating the business case in FTEs, the argument should aim at value contributions and risk reduction:
Risk perspective: which liability risks are reduced? Which standards, directives, and audit requirements can be demonstrated more easily?
Quality and efficiency: how do error rates, correction loops, and rework drop? How quickly can product changes be reflected in the documentation?
Scalability: how many additional products, variants, and languages can the existing team handle in future? Which markets only become sensibly addressable as a result?
Cost effects without job cuts: a reduction in translation costs over 3–5 years, less time lost in audits and customer enquiries, less internal searching and coordination effort.
Employee retention and employer attractiveness: modern tools signal that you take your staff’s work seriously and professionalise it. Skilled people are more likely to stay when they work with sensible tools rather than copy-paste routines. In times of a skills shortage in particular, that is no minor point.
Invest in value, not in job cuts
Introducing a CCMS, TMS, or other systems for technical documentation is a strategic investment: in data quality and legal certainty, in auditability and compliance, in reuse and translation economics, in the scalability of your information processes.
Anyone who tries to justify this investment primarily through supposed staff savings falls short, and jeopardises the acceptance of the project.
Argue with ISO 9001 conformity, audit security, and reuse, with cost effects in localisation and the professionalisation of the information-creation process. But beware of wasting even a single thought on how much staff you will save with such a system. The calculation does not work out, and it breaks the project before it has properly begun.
Developing the argument and business case together
If you are currently facing the decision to invest in a CCMS, TMS, or related solutions, or to modernise your existing documentation landscape, I am glad to support you: in developing a robust business case, in translating professional value into management metrics, and in designing processes and roles so that your investment really pays off.
Would you like to sharpen your argument for management? Then get in touch with me — and together we will develop an investment story that bets on value, security, and future viability, not on unrealistic headcount cuts.
Further standards and industry information are available from tekom — the German professional association for technical communication.