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.
I use future tense only in functional specs--"this is what the software will
do". I avoid it in user doc, because it seems overly formal and aggressive
(it's a completely subjective reason) However, that's just me, so I look
forward to seeing other responses.
"Tell me and I'll forget. Show me, and I may not remember. Involve me,
and I'll understand." - Native American Proverb
-----Original Message-----
From: Hager, Harry (US - East Brunswick) [mailto:hhager -at- dc -dot- com]
Sent: Thursday, November 16, 2000 9:14 AM
To: TECHWR-L
Subject: Future Tense in Tech Writing
Hi,
In the thread "display vs. appears" there were a few responses suggesting
the use of future tense, as in the following:
1. Click ABC. The ABC window will (your word of choice).
Forget about the "display" part. We've successfully beaten that dead horse
to a pulp; at least until the next time. I want to talk about the "will"
part.
How many of you use future tense in your technical writing?
I've always avoided using future tense in technical writing. I've been
taught and have taught others that future tense in technical writing is a
big no no.
The only reason I'm writing this is that nobody else has mentioned it so
far. This surprises me.
I alway use present tense when I document procedures. (In rare cases, I'll
use future tense if the action I'm talking about produces several results or
leads to several possibilities and some are discussed somewhere else in the
book. I might use future tense when it's clear that the result of the action
occurs in a different timeframe, such as what might happen when I'm
documenting procedures for our operations group [submit a form online at
noon and the night shift operations group performs certain actions at
midnight.] Even then I generally opt to exclude future tense.)
Why use present tense only? When a user is reading a set of instructions and
performing a set of instructions, each step is occurring in the present
tense as related to the user. Click ABC. ABC window opens. Click Close. ABC
window closes. Each action leads to a reaction and as the user goes through
the actions, everything happens in the present tense, as related to the
user.
Another reason is that is is easier to read, easier to scan the steps
(MS-MOS book).
I've always considered this (using present tense) as one of the basic rules
of technical writing.
Am I wrong?
I get the digest, so I will not be able to reply interactively to any
queries or comments directed my way until tomorrow.
H. Jim Hager
hhager -at- dc -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-based Help with Macromedia Dreamweaver! (STC Discount.)
**NEW DATE/LOCATION!** January 16-17, 2001, New York, NY. http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.
Sponsored by SOLUTIONS, Conferences and Seminars for Communicators
Publications Management Clinic, TECH*COMM 2001 Conference, and more http://www.SolutionsEvents.com or 800-448-4230
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
