I had the same bump of excitement when I read the description of StackOverflow Documentation, but was saddened quickly when I looked at what they produced and h

I had the same bump of excitement when I read the description of StackOverflow Documentation, but was saddened quickly when I looked at what they produced and how they were producing it. If you want to create bad documentation, here is how you do it: Hire an intern and have them describe each element, function, screen, button, etc of a program. If you want to create good documentation, here is how you do it: Hire an instructional designer to define the audience, their objectives, the common tasks, and then build your documentation around this information. This effort seems to be taking the first approach, and might end up producing documentation, but it won't be very good.