2. Design output to fit the user - design for the person, not the position; remember human information processing differences; issue of detail versus summary
3. Delivering the appropriate quantity of output - don't create overload, create enough to perform business tactics and make anything else optional
4. Making sure the output is where it is needed - right person at the right place; consider discontinuing printed output and see if anyone asks for it
5. Providing the output on time (and for the right time period)
6. Choosing the right output method- consider all senses (sound, smell, touch?)
Internal outputs can include detail, summary, exception reports. Should only negative exceptions be included? Why or why not?
Technology can include printers, specialty printers, screens, projectors, audio, microform, CD-ROM, electronic forms (including the WWW). E-mail, Faxback, or WWW can be used to reach customers both pre-sale and post-sale.
Don't ignore output to reprographic equipment such as high speed copiers.
Considerations when choosing a technology include who, how many users, where, speed, changeability, permanence, storage, cost, and needed environment.
2. Bias when limits are set, especially for exception reports.
3. Bias through graphics due to scales, size, color, or type of graphic. Viewing position also can introduce bias.
User/developer interaction and testing is the best way to avoid bias. Validity should be tested to assure that what you attempt to shown is what is perceived. Iteration is key since you won't get it right the first time.
Use care with headings, titles, page numbers, dates, time periods, and control/summary breaks. Reports are read top to bottom and left to right in our culture. Space separates items. Test to see where the user looks and what he/she sees.
With any output, the users may not see what you intend them to see. Thus, the users must be trained to use the output and relate the output to business tactics.
You must be sure that the output communicates what you intend to communicate, that the message will support business tactics, and that the user knows what to do once a message is received.
Friendly Graphics include:
To see an actual case study regarding output design, see Consulting Opportunity 15.3.