Technical writers are often the last people added to a release sprint and the first cut when timelines compress. They work from engineering specs that were written for engineers, marketing briefs that were written for sales, and product notes that were written for no one in particular.
The result is documentation that is technically defensible but practically unreliable. It covers the feature. It does not always explain the feature. It tells users what a thing does. It does not always tell them when to use it, what to watch out for, or how it connects to the three other things they already use.
This is not a writing problem. It is a workflow problem.
The inputs are incomplete. The review cycle is compressed. The feedback loop between documentation and actual user behaviour is long and indirect. By the time anyone notices the documentation was wrong, the writer is four releases ahead.