How to Write a Target Audience Questionnaire

Creating a training plan? Before you do this, you need to step a step back and work out what your colleagues need to learn.

Why?

Well, otherwise, you risk developing a training plan that overlooks the areas where people really need to skill up.

The advantage of a well-developed training is that it lets you focus your skills, as a trainer, and match the training course to the audience.

One way I do this is to develop a Target Audience Questionnaire.

Download: Free Target Audience Questionnaire

What is a Target Audience Questionnaire?

Audience Analysis is used to profile, i.e. learn about, your target audience, so that you can then offer better products, services, training, books or whatever… that match their specific requirements. This is different than gathering requirements, which is more a wish list, of what people want.

Audience Analysis is a snapshot of what your users/readers/viewers etc are doing here and now. Marketing plans also use these to get an better understanding of how to segment their audiences.

For technical writers and trainers, you can use this Target Audience Questionnaire when developing your next set of documents or training plan.

What’s important is that you see the value in this activity.

The more you know about your target audience, the more likely your material will suits their needs.

So, let’s get started.

What goes into a Target Audience Questionnaire?

You need to cover four sections in your questionnaire: document details, objective, experience, tasks.

1. Document Details

The first page of the questionnaire—usually near the header—captures information related to the actual document, for example, the name of the course, the individual, date, and department. Depending on your project, you may want to adjust this to suit your needs.

Some technical writers use version controls on their documents, as well as the document’s status, for example, Draft, Revised, Final or Approved.

Course:

Name:

Date:

Department:

2.Objectives

In the objective section, describe the goal of this questionnaire.

  • Who are the project stakeholders for this project?
  • Who is been asked to complete this questionnaire?
  • What is your motive for doing this?
  • What is the benefit to the reader?
  • When does this questionnaire need to be completed by?
  • Where will the information be kept, share, distributed, and archived?
  • Why should the reader/user/employee complete this questionnaire? Is it compulsory? Is there a date by when this must be completed?
  • How does this questionnaire fit into the company’s overall strategy?

Sample text:

“To help us provide the most appropriate the training to our employees—so you have the necessary skills, knowledge and confidence in your own abilities—please study the following questions and answer them to the best of your abilities.”

The questionnaire must be completed by [date].

The questionnaire is approved by the [project board].

Contact [identify the person] if you have any queries about this questionnaire.

3. Level of Experience

Identify your level of expertise with these tools based on a scale of 1 to 5.

(1=No Experience; 5=Extremely Experienced).

1.         Adobe Acrobat (not Acrobat Reader)

2.         Adobe FrameMaker

3.         AuthorIT

4.         DocBook

5.         DocToHelp

6.         DreamWeaver

7.         Epic Editor

8.         ForeHelp

9.         Interleaf

10.       MadCap Blaze

11.       Madcap Flare

12.       Microsoft Excel

13.       Microsoft Visio

14.       Microsoft Visio

15.       Microsoft Word

16.       RoboHelp

17.       Techsmith Camtasia

18.       Techsmith Snagit

19.       WebWorks

20.       XML editor

4. Tasks & Activities

Please indicate all answers that are applicable to your role.

1. How often are you asked to provide [technical documents/status reports/management reports etc]?

(a) Several times a day

(b) Several times a week

(c) Several times a month

2. What format (s) do you provide the information in?

Charts

Diagrams

Documents

Maps

Pivots tables

PowerPoint

Verbal

3. What is the nature of these requests?  (If possible, please provide examples of each item indicated)

(a) Summary (e.g. totals, averages, status etc.)

(b) Detailed (specific lists, inquiries regarding specific projects, documents, releases etc.)

(c) Operational

(d) Analytical

(e) Other (this may include revisions, merging, editing, publishing, translating, re-formatting, printing etc)

Once you have these in place, you can then begin to write your documents or start developing that training plan.

Does that make sense?

What do you think?

How can I improve this plan and make it better?

Downloads

Business Requirements Template

Functional Requirements Specification Template

Download these templates to start

Acceptance Test Plan

Contingency Plan

Software Development Templates

Acquisition Plan

Conversion Plan

Software Requirements Specification

Action Plan

Cost Benefit Analysis

Software Testing

API Documentation

Database Design

Standard Operating Procedures (SOP)

Audience Analysis

Datasheet

Statement of Work

Availability Plan

Deployment Plan

System Administration Guide

Bill of Materials

Design Document

System Boundary

Business Case

Disaster Recovery Plan

System Design Document

Business Continuity

Disposition Plan

System Specifications

Business Plan

Documentation Plan

Technical Writing Templates

Business Process

Employee Handbook

Test Plan

Business Requirements

Error Message Guide

Training Plan

Business Rules

Expression of Interest

Transition Plan

Capacity Plan

Fact Sheet

Troubleshooting Guide

Case Study

Feasibility Study

Use Case

Change Management Plan

Functional Requirements

User Guide

Communication Plan

Grant Proposal

Verification and Validation Plan

Concept of Operations

Implementation Plan

White Papers

Concept Proposal

Installation Plan

Work Instructions

Configuration Management Plan

Interface Control Document

Software Development Templates

Acceptance Test Plan

Maintenance Plan

Software Requirements Specification

Acquisition Plan

Market Research

Software Testing

Action Plan

Marketing Plan

Standard Operating Procedures (SOP)

API Documentation

Needs Statement

Statement of Work

Audience Analysis

Operations Guide

System Administration Guide

Availability Plan

Policy Manual

System Boundary

Bill of Materials

Project Plan

System Design Document

Business Case

Proposal Manager Templates

System Specifications

Business Continuity

Proposal Template

Technical Writing Templates

Business Plan

Quality Assurance Plan

Test Plan

Business Process

Release Notes

Training Plan

Business Requirements

Request for Proposal

Transition Plan

Business Rules

Risk Management Plan

Troubleshooting Guide

Capacity Plan

Scope of Work

Use Case

Case Study

Security Plan

User Guide

Change Management Plan

Service Level Agreement (SLA)

Verification and Validation Plan

Communication Plan

Setup Guide

White Papers

Concept of Operations

Social Media Policy

Work Instructions

Concept Proposal

Contingency Plan

 

Configuration Management Plan

Conversion Plan