Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Why do many manuals and technical documents seem to prefer passive voice?

+0
−0

It seems like many manuals and technical documents prefer passive voice over active voice. Is this true, or is it just my perception? If so, why?

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

This post was sourced from https://writers.stackexchange.com/q/33467. It is licensed under CC BY-SA 3.0.

0 comment threads

2 answers

+1
−0

Speaking only from my own experience, passive voice is often a last resort. I write a lot of user guide material, and my company's style guide discourages using passive phrasing, but even more strongly discourages using second-person pronouns. So while it may feel more natural for me to write "You can access the setting in the widget," I may have to use "The setting can be accessed in the widget" instead, assuming I can't figure out another way around it.

I suspect this is true of other widely-used style guides as well.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

This post was sourced from https://writers.stackexchange.com/a/33469. It is licensed under CC BY-SA 3.0.

0 comment threads

+0
−0

Well, there is no good practical reason for it. In other words, there are no studies showing that passive voice is more effective in communicating technical information. That leaves us with social reasons, which are necessarily a little more speculative and anecdotal. There is history to suggest that the following may be factors:

  • People often feel that because documentation is a "business document" it must be formal, and they often feel that the passive voice sounds more formal than the active voice. Neither of these propositions is true but they seem to be frequently held by people whose training and experience is not in communications.

  • The passive voice can be used to conceal the actor. "John hit Frank" becomes "Frank got hit" with the accusatory "by John" elided out. Thus it absolves the speaker either of taking responsibility or of assigning it. Communicators who seem unsure of themselves or who don't really want to communicate at all often take refuge in the passive to avoid taking or assigning responsibility.

  • If people are in a field where passive documentation is common, they may simply copy that style. It is remarkable the extent to which people will produce information designs that they would never use or like themselves just because they think those designs are conventional. People choose the conventional over the useful all the time.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »