Every software team knows about technical debt. Code that works but was written fast, under pressure, with the intention of cleaning it up later. It accumulates quietly until it becomes expensive to ignore.
Documentation debt works the same way. It just takes longer to feel.
A release goes out. The documentation is close enough. The product manager signs off. The writer moves to the next sprint. Six months later, a support ticket arrives about a feature that was documented incorrectly from day one. One user has been working around it. Another has left. A third never adopted the feature at all because the documentation made it sound more complicated than it was.
Nobody connected those dots to the documentation. They rarely do.
The teams that take documentation seriously are not doing it because they love documentation. They are doing it because they have done the maths.