[the_cramer]

Could be, yes, but how to find out? The users won't read it, and the only reason i get for that is "I don't have time for this, just tell/show me how it's done".

My user documentation is usually hand written and in a rather linear style, split by tasks. "You want to reach this goal, do the folling". On the other hand i am aware that as a developer, our style of submitting information to peers is sometimes different. Non-developers have a hard time to follow and sometimes a few explanation attempts are needed to get the information over the river (both ways).

This would tell me that an in-between person should create documentation. This person does not exist in my vicinity...

I will however take the feedback from this thread into account and point at documentations more often. Maybe it has an effect.