is desktop publishing really for every desktop?  because of the proliferation of new hardware and software products aimed at turning all microcomputer users into publishers, editors of newsletters, user documentation, and training materials need to carefully consider the many options available for producing the highest quality product to meet the stated goals of their publications. while there are several distinct advantages to desktop publishing, such as permitting the quick turnaround of near-typeset quality publications, there are many additional considerations required to evaluate and decide what level of desktop publishing (dtp) best fits your needs and the capabilities of your staff.  as users contemplate the move to dtp products, it is critical that their expectations are realistic and acceptable. essential to the success of any dtp implementation is the recognition of the "hidden" responsibilities placed on the user. there must be a realization, for example, that there is a significant amount of individual expertise required to go from word processing to desktop publishing, and the dtp practitioner will be making the same design decisions as those made by highly trained graphic artists and typographers. within most organizations it is difficult to find one person who can write, edit, do page layout, and produce graphics for a publication. each publication, be it system or user documentation, newsletter, system notice, workshop and lecture schedule, brochure, or flyer, has its own set of design and publishing requirements. in spite of what the salesperson may tell you, dtp may not be the greatest invention since the light bulb. you can guarantee, however, that they will keep you in the dark about more appropriate products, simply because they may not be able to demonstrate them effectively. depending on the type of publication you prepare, dtp may not answer all your publishing needs. yet, there are practical steps you can follow to see if dtp is the appropriate choice to enhance and improve your publications.  the information services group at the center for computing and information technology at the university of arizona uses both dos-based and macintosh desktop publishing workstations to produce all user documents. our group is responsible for all external publications for both administrative and academic users.  certainly the arrival of desktop publishing in our department represented the potential for increased services to our audience, but it also brought the realization that we needed to revisit existing publications. just as we analyze a new publication, we examined each document for its stated purpose, audience, content, and design, in order to effectively integrate the new technology into established production methods.  over the past eighteen months we have been evaluating and choosing appropriate products suited for the varied types and requirements of the publications we produce. to effectively incorporate desktop publishing we felt we had to address the impact in five critical areas: hardware requirements for both macintosh and dos-based systems, output devices, software options, system compatibility, and system implementation timelines and training requirements.  paul christian