To be quite frank, I'm really puzzled by this. For software projects, many times the documentation is the only record of how the application works outside of the code. So it seems pretty important to have good documentation to train end users and train new developers.
When I got my BlackBerry Storm, however, there was only a little four page pamphlet in the box. It explained the most basic parts of the system which I aready knew intuitively. Getting my corporate and personal email to the BlackBerry took me days of research in online forums -- so little information was available from the company.
So in our fast paced, technical world, we've come to have a love-hate relationship with documentation. We know it should be there and follow standards, but it is also outdated so quickly and often poorly written.
I know this doesn't directly answer the question, but it should give you some things to think over.