Stop Trying to Prove Documentation Saved Money
How to handle the question every documentation leader eventually gets asked
A reader of The Content Wrangler recently sent me a question that will sound familiar to many tech writers, content strategists, knowledge managers, and knowledge engineers.
Their manager had asked them to measure the effectiveness of their team’s content.
They were looking at support ticket trends and website analytics, hoping to find a way to demonstrate business value. The challenge, they explained, was that every path seemed to lead to the same frustrating conclusion. There was no definitive way to say, “Our content saved the company money.” Too many variables were involved. Too many things were changing at the same time.
It’s a good question. It’s also a question that sends a lot of documentation teams down the wrong path.
The assumption hiding inside the question is that documentation should be able to prove its value with the same certainty that an accountant can prove an expense or a revenue number. Once you start looking closely, that expectation falls apart pretty quickly.
Marketing can’t prove that a particular webinar generated a precise amount of revenue. Human Resources can’t isolate the exact value of a leadership development program. IT departments typically can’t demonstrate that a server upgrade produced a specific percentage increase in profit.
Yet documentation teams are often asked to do exactly that.
The problem isn’t that documentation lacks value. The problem is that value and proof are different things.
The Attribution Trap
Many of us would love to run documentation experiments the way pharmaceutical companies run clinical trials. Give one group of customers excellent documentation. Give another group none. Compare the results and calculate the difference.
Real organizations don’t cooperate with that kind of experiment.
Customers become more experienced. Products change. User interfaces improve. Training programs evolve. Support teams launch new initiatives. Search tools get better. AI systems arrive and introduce an entirely new set of variables.
Now imagine support tickets decline after your team publishes a new set of troubleshooting topics.
What happened?
👉🏾 Maybe customers found the answers they needed in the documentation.
👉🏾 Maybe the product became easier to use. Perhaps.
👉🏾 Maybe support agents started proactively sharing information. Maybe customers simply became more familiar with the workflow.
🤔 Maybe. Maybe not. The honest answer is usually some combination of all of those things.
This is where many content teams get stuck. They spend months trying to isolate documentation’s contribution inside a system where dozens of factors influence the same outcome. The search for certainty becomes the project.
Unfortunately, certainty rarely shows up.
Organizations Run On Evidence, Not Certainty
One of the odd things about this conversation is that organizations make important decisions every day without proof. Every quarterly forecast, sales projection, hiring plan, and budget request is based on evidence rather than certainty.
Leaders review available information, assess risks, make assumptions, and decide what to do next. Documentation should be evaluated the same way.
Instead of asking whether content can be proven to have created a particular outcome, ask whether outcomes improved after content improvements were made.
Suppose your team rewrites a collection of troubleshooting articles associated with frequent support requests. Three months later, support tickets related to those issues decline.
Have you proven that documentation caused the reduction?
Nope.
Have you gathered evidence that the documentation contributed to a positive outcome?
Probably.
That’s often enough.
Most executives are not looking for courtroom-level proof. They’re trying to determine whether investments appear to be producing useful results. Documentation teams sometimes forget that and hold themselves to a standard that nobody else in the organization is expected to meet.
When Activity Masquerades As Value
Part of the challenge comes from the metrics we choose to report.
