TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Can someone learn to be detail-oriented? From:Chris Kowalchuk <chris -at- BDK -dot- NET> Date:Tue, 17 Aug 1999 13:32:13 +0000
Speaking strictly anecdotally, I think you can learn to respect the
details. I'm very much a big-picture person and do not enjoy "sweating
the small stuff", BUT it is necessary in our line of work to do so. In
my own case, I simply recognize that paying attention to details
requires a greater level of concentration and effort for me than it does
for some others, so I know that I'm only good for a few hours a day of
proofreading or what have you. On the other hand, being constantly aware
of the context in which the details fit is a great help in arranging or
working with those details more intelligently. I think it can be
learned. One might never become "detail oriented" ("orientation" sounds
like a personality trait to me), but that is no excuse for doing sloppy
work. Those who are not detail oriented simply have to use more
organizational tools, checklists, etc. to help remind them to check the
details they might otherwise overlook. Also, in cases of subject matter,
it may be a question of reframing. If a detail (such as, you press the
*red* button to shut off the boiler before it explodes) is important, as
they often are in tech writing, then even a generalist thinker, if
behaving conscientiously, will be aware that without the detail, there
will be serious gaps in the information. Suddenly the particular is a
critical component of the overall system. You can't talk about the
system without it. So the generalist will understand (and deal with) the
details in the context of the overall system or process. If not, what
the heck is he or she writing about?