No, the problem is that while you are writing documentation you are not making money for the company. I remember when I and Dave as the senior tech told our boss that we should put the most common repairs into a database so new hires would not have to ask us questions all the time.

He asked how long the job would take, and we answered about a week for all the common stuff. And his answer was, "That is a week you will not be making the company any money.".

We tried to explain the long term savings, but he was not interested.

I think the best way to think of this part of a wiki is as a cache for everybody's help. No need to pre-populate the cache, just start using it, and the most frequently used information will tend to be there.

Definitely, not perfect readme or documentation but at least that covers 70% of cases.