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

Post History

60%
+1 −0
Q&A How should I respond to a supervisor/editor who thinks my technical writing is "too conversational?"

There have been significant changes in technical communication style over the last 20 years, and particularly in the last five years as increasing volumes of evidence have shown that simple friendl...

posted 6y ago by Mark Baker‭  ·  last activity 5y ago by System‭

Answer
#4: Attribution notice removed by user avatar System‭ · 2020-01-03T20:41:57Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/34596
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#3: Attribution notice added by user avatar System‭ · 2019-12-08T08:24:36Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/34596
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by user avatar System‭ · 2019-12-08T08:24:36Z (almost 5 years ago)
There have been significant changes in technical communication style over the last 20 years, and particularly in the last five years as increasing volumes of evidence have shown that simple friendly language is both easier to understand and more respected by users.

But it sounds like your supervisor is a stickler and the way you convince a stickler is by citing an authoritative source. So here is that source. There are few works on technical communication style that are better established or more respected than the Microsoft Manual of Style. That manual has recently undergone a major update to bring it into line with modern practice and research. You can find it on line here: [Microsoft Writing Style Guide](https://docs.microsoft.com/en-us/style-guide/welcome/)

Here are the top ten tips from that guide (see the guide for details and examples of each tip):

> Use bigger ideas, fewer words: Our modern design hinges on crisp minimalism. Shorter is always better.
> 
> Write like you speak: Read your text aloud. Does it sound like something a real person would say? Be friendly and conversational.
> 
> Project friendliness: Use contractions: it’s, you’ll, you’re, we’re, let’s.
> 
> Get to the point fast: Lead with what’s most important. Front-load keywords for scanning. Make customer choices and next steps obvious.
> 
> Be brief: Give customers just enough information to make decisions confidently.
> 
> When in doubt, don’t capitalize: Default to sentence-style capitalization—capitalize only the first word of a heading or phrase and any proper nouns or names.
> 
> Skip periods (and : ! ?): Skip end punctuation on titles, headings, subheads, UI titles, and items in a list that are three or fewer words. Save the periods for paragraphs and body copy.
> 
> Remember the last comma: In a list of three or more items, include a comma before the conjunction.
> 
> Don’t be spacey: Use only one space after periods, question marks, and colons—and no spaces around dashes.
> 
> Revise weak writing: Most of the time, start each statement with a verb. Edit out you can and there is, there are, there were.

#1: Imported from external source by user avatar System‭ · 2018-03-26T10:27:36Z (over 6 years ago)
Original score: 9