Focus on Audience-centred writing

What’s your purpose?

What's your purpose?

What’s your purpose?

– or –

What’s the difference between a purpose and an objective?

Sometimes these terms seem synonymous, and often the term purpose is used solely to mean both, but the distinction between them in a document or training plan is key. The purpose is about the document and the objective is about the audience. In other words, “purpose” is what the document sets out to teach and “objective” is what the reader will be able to do as a result of that teaching.

Purpose

Example:

“The purpose of this guide is to describe how to complete a customer claim.”

I once saw a purpose statement at the front of a guide that stated, “The purpose of this guide is to be a user manual.” The circular reasoning is obvious, and it’s easy to see how feature-focused this kind of planning is. The purpose is the story the document is telling; or put another way, it’s the point of this guide.

Objective

Example:

“As a result of reading this guide, the reader will be able to complete
a customer claim accurately to company standards.”

Writing an objective in technical writing is a thornier issue and unless you’re writing training materials, it’s something quite foreign. The reason for this is simply that the objective describes something about the consumer of the information. Often, technical writers are removed from their readers. Technical writers don’t have to stand up in front of a room of readers, but trainers do, so instructional designers (those who write training materials) are more familiar with writing objectives.

In a technical document, I’m one for a blended approach and stating both, even if it means that the objective is buried in a purpose statement.

Purpose + Objective = Purpose

The result is something like this:

“The purpose of this guide is to enable readers to complete
a customer claim accurately to company standards.”

Big whoop—I know—it’s not all that different, but by taking in both the document and its reader, the purpose statement becomes much more meaningful (it’s not filler at the beginning of a guide), and the reader can go back to the beginning and assess if that objective was fulfilled (or not).

Testimonial – Words of wisdom on proposal writing

I appreciate the words of wisdom Jason shared in class about persevering and being open to all kinds of writing as a technical writer. Those words were valuable when I began my technical writing role as part of a sales team. It involves a lot of proposal writing, which walks a nice line between informative and persuasive writing. I’m using my strengths, but expanding the scope of my writing skills as well.

—Deborah Hazebroek,Technical Writing Student, BCIT
(now Technical Writer at ENBALA Power Networks Inc.)

Writing for the Web: Clarity 1/7

Clarity

Futurama - Stuff n' Junk (or whatever)Using concrete specific words won’t necessarily make your writing shorter, but it will make it more interesting to read. Consider the following:

“A number of factors must be addressed to ensure this effort meets its objectives within the proposed time frame.”

Avoid:

  • Several – how many?
  • Numerous – What number?
  • Various – Which?
  • Very – use your imagination!

And of course:

  • Stuff
  • Junk
  • Whatever!

Rule: Use Concrete Specific Words

Testimonial – Combining profound technical knowledge with creative flair

Jason combines profound technical knowledge with creative flair that makes him the Michelangelo of training/user manuals. He upgraded our training materials to a world-class level and streamlined the production process.

—Michael Kano, Training Operations Manager, ACL Software