> If the individual steps are complex, I feel that > scrunching them into small flowchart boxes or making > the flowchart boxes large would not help. If the steps are > numerous but the complexity of each step is small, then a > flowchart really shouldn't be used in place of the procedure, > but rather alongside it. Some learn visually, and some > learn by reading. I imagine that you would frustrate at least > 1/4th of the audience by removing the text entirely.
One is not the other. You don't have to have the text that you'd have in your document crammed into a flowchart box and you don't have to have a one-to-one relationship between a written step and a box. In fact, in the example I gave earlier, there were probably three flowchart elements for each written documentation step. John Posada Senior Technical Writer "I think the problem, to be quite honest with you, is that you've never actually known what the question is." _______________________________________________ Are you a Help Authoring Trainer or Consultant? Let clients find you at www.HAT.Matrix.com, the searchable HAT database based on Char James-Tanny's HAT Comparison Matrix. Contact [EMAIL PROTECTED] for details. Interested in Interactive 3D Documentation? Get the scoop at http://www.doc-u-motion.com -- your 3D documentation community. _______________________________________________ Technical Communication Professionals To post a message to the list, send an email to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://techcommpros.com/mailman/listinfo/tcp_techcommpros.com or, via email, send a blank message [EMAIL PROTECTED] Visit the TCP site at http://www.techcommpros.com To find out more about the list, including archives and your account options, visit http://techcommpros.com/mailman/listinfo/tcp_techcommpros.com If you need assistance with the list, write to [EMAIL PROTECTED]
