Already on ArticleSlash?

Forgot your password? Sign Up

Technical Writing - What is "Variance" and How Can a Technical Writer Eliminate it in Documents?

Ugur Akinci

Visitors: 304

"Variance" is an important term in statistics and plays a crucial role in technical documentation as well. Without getting too technical about it: “variance" denotes the way the values of a set of elements vary around a central mean value.

Imagine you weighing a hundred marbles. Let's say the arithmetic-mean weight of an “average" marble is 10 ounces. But some weigh 10.1 ounces, some 9.8, some others 9.5 and 11.3, etc. You get the picture.

The “average degree" to which any given marble differs from that central value of “10 ounces" is called “variance" and is closely related to the statistical concept of “standard deviation. " In short, “variance" is a measure of the extent to which the individual elements of a set are identical. “Zero variance" means all elements in a group are exactly alike.

In manufacturing, “zero variance" is a highly coveted but impossible goal because it means there are no manufacturing defects.

In technical documentation “zero variance" is equally desirable in this sense: there should be no syntax, vocabulary and style “variations" in your manuals. Why? Because a technical text that varies in syntax, vocabulary and style from page to page confuses the readers and fails to instill confidence.

You should have “zero variance" in your vocabulary. If you have used the term “LAN" on the first page, you should not switch to “local network" on page 10.

If you have used a Figure Caption AFTER Figure 1, you should not use it BEFORE Figures 2, 3 and 4.

If you have used “Arial 14 Points" for Header 1 on page 1, the Header 1 on page 56 should not have “Times New Roman 18 Points" font.

If the First Page template in Chapter 1 has a 1.5 inch left margin, every Chapter First Page should also have a 1.5 inch left margin.

You should aim for “zero variance" in your icons, table formatting, bullets, they way you use active and passive voice, and other style elements. “Zero variance" is one of the important features that make technical writing predictable, trustworthy and easy to follow. That should be a goal in every technical documentation project you tackle.

If you are interested to read more about technical writing as a career and how it can help you earn a steady living, visit . You might be pleasantly surprised with what you'll find out. Join the thousands who are already helped and inspired by this information provided by a Fortune 500 Senior Technical Writer. Visit today and claim your free report “How Much Do Technical Writers Make?"


Article Source:

Rate this Article: 
New Technical Writer: First Things to Do on the Project
Rated 4 / 5
based on 5 votes

Related Articles:

ZTweet Announces Real Time Technical Writing Jobs Including Free Training for ..

by: Lewis Shawz (November 29, 2010) 
(Business/Career Advice)

New Technical Writer - Have No Fear of Writing

by: Barry Millman (August 22, 2007) 
(Writing and Speaking/Writing)

Technical Writing Tech Writer Salaries in the US

by: Bryan S. Adar (July 14, 2008) 
(Writing and Speaking/Writing)

New Technical Writer - Avoiding the Interview-Writing Disconnect

by: Barry Millman (April 15, 2007) 
(Writing and Speaking)

Learn Technical Writing - The Difference Between Technical Writing and ..

by: Bryan S. Adar (September 07, 2008) 
(Writing and Speaking/Writing)

Great Technical Writing: How Small Companies Can Create Great User Documents

by: Barry Millman (February 14, 2007) 
(Writing and Speaking)

Learn Technical Writing - The Case For Technical Writing

by: Bryan S. Adar (September 07, 2008) 
(Writing and Speaking/Writing)

Sbcglobal email Technical support is Helpful for fixing technical issues

by: Prashant Mishra (November 12, 2014) 
(Computers and Technology/Data Recovery)

Technical Support Companies-Quick Solution To Your Technical Problems

by: Graig Scott (August 17, 2011) 
(Computers and Technology/Hardware)

New Technical Writer: First Things to Do on the Project

by: Barry Millman (February 12, 2007) 
(Writing and Speaking)