Having written lots of software documentation in the 90s and developed numerous UIs since then, I've come to use a balance of UX and documentation. My strategy is to build into the UI simple instructions for operating each set of controls encountered by the user. Often these instructions appear in info panels that the user can dismiss when they no longer need/want to see them. The documentation then becomes little more than an outline of common and advanced procedures the users may perform within the app with short instructions of where to begin the procedure within the UI. So essentially, the documentation acts as an easily navigable directory of procedures, and the UI provides the step by step documentation within info panels.
Slashdot Mirror
Having written lots of software documentation in the 90s and developed numerous UIs since then, I've come to use a balance of UX and documentation. My strategy is to build into the UI simple instructions for operating each set of controls encountered by the user. Often these instructions appear in info panels that the user can dismiss when they no longer need/want to see them. The documentation then becomes little more than an outline of common and advanced procedures the users may perform within the app with short instructions of where to begin the procedure within the UI. So essentially, the documentation acts as an easily navigable directory of procedures, and the UI provides the step by step documentation within info panels.