End User Support – User Training

Slides:



Advertisements
Similar presentations
Module 2 Sessions 10 & 11 Report Writing.
Advertisements

Copyright © 2010 Pearson Education InternationalChapter Completing Business Messages.
© Prentice Hall, 2008 Business Communication Today, 9eChapter Completing Business Messages.
CO1010 IT Skills in Science Lecture 3: Good Practice in Report Writing.
At the end of this lesson you will be able to:
Chapter 12 Chapter 12: Writing for End Users A Guide to Computer User Support for Help Desk and Support Specialists second edition by Fred Beisse.
Chapter 2: The Communication Process
Chapter 12 Writing for End Users
Revising and Editing Your Research Paper. Self-Revision In the revision step, focus on the following questions and strategies:  Assignment requirements:
Chapter 12 Writing for End Users
1 Business Writing in a Technical Environment Prepared by Graham Associates copyright 2002 copyright © 2002.
“Put It in Writing” Adding Value to Company Knowledge.
© Prentice Hall, 2007 Business Communication Essentials, 3eChapter Completing Business Messages.
CTS 217: Computer Training & Support
CSC135 Review A Slide to a week review of the material covered 1.
The Writing Process and 6 Plus 1 Traits “Writing allows you to penetrate your life and learn to trust your own mind.” Natalie Goldberg By Kathy Mraz.
Writing for Business Collaborative Reports Collaborative Writing 87% of all business writing is done in a group or team. The average business document.
EE LECTURE 4 REPORT STRUCTURE AND COMPONENTS Electrical Engineering Dept King Saud University.
© 2010 Pearson Education, Inc., publishing as Longman Publishers. 1 Chapter 13 Instructions and Procedures Strategies for Technical Communication in the.
Key Skills: Communications Presented by Bill Haining.
A Guide to Computer User Support for Help Desk & Support Specialists Fourth Edition by Fred Beisse Chapter 11 Writing for End Users.
Training Computer Users Writing For End Users. What is Training? Focus on performing activities building expertise that will be immediately useful.
© 2008 Pearson Education, Inc., publishing as Longman Publishers. 1 Chapter 22 Instructions and Procedures Technical Communication, 11 th Edition John.
© Prentice Hall, 2008 Excellence in Business Communication, 8eChapter Completing Business Messages.
Unit 1 Activity 2B Communication Barriers Report
Chapter 3 Writing for End Users
Revise Five Times (then proofread) Pointers on written assignments when you lack time The Five Revisions.
Writing Workshop Priscilla L. Griffith, Ph.D. University of Oklahoma Slide 1.
© Prentice Hall, 2003 Business Communication TodayChapter Completing Business Messages.
©2011 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
Document Review for Reviewers and Writers. Topics Readability Document Review Structured Reading.
CERTIFICATE IV IN BUSINESS JULY 2015 BSBWRT401A - Write Complex Documents.
What are the characteristics of “good writing”? What are the characteristics of “good writing”?
The Writing Process. What makes a sentence? A sentence is a complete thought Sentence must have a subject A sentence must have a verb.
© Prentice Hall, 2005 Business Communication Today 8eChapter Completing Business Messages.
ENGR 1181 College of Engineering Engineering Education Innovation Center Introduction to Technical Communication.
Panayiotis Christodoulou
© Prentice Hall, 2007 Excellence in Business Communication, 7eChapter Completing Business Messages.
Chapter 6 Writing Reports: A Complex Process Made Easy.
ENG 113: INTRODUCTION TO COMPOSITION THE ART OF COMPOSITION.
Chapter 6 Completing Business Messages Copyright © 2014 Pearson Education, Inc. publishing as Prentice Hall 1Chapter 6 -
Chapter 5 Copyright © 2014 Pearson Education, Inc.Chapter Completing Business Messages.
© Prentice Hall, 2004 Excellence in Business CommunicationChapter Completing Business Messages.
BUSINESS CORRESPONDENCE BUSINESS CORRESPONDENCE. INTRODUCTION INTRODUCTION  Why is it important for business people to develop business correspondence.
B200- TMA Requirements 1. Page Layout A cover page must contain the following: the name of university, name and title of the course, TMA number and title,
Copyright © 2010 Pearson Education, Inc. publishing as Prentice HallChapter Completing Business Messages.
Copyright © 2011 Pearson Education, Inc. publishing as Prentice HallChapter Completing Business Messages.
1 January 31, Documenting Software William Cohen NCSU CSC 591W January 31, 2008.
Handout 2: Written communications
Handout 2: Written communications
Instructions and Procedures
Document Development Cycle
Year 6 Objectives: Writing
Chapter 3 Writing for End Users
Chapter 03: Basic Application Software
Chapter 4 Preparing Spoken and Written Messages
Writing Effective Abstracts
An Introduction to the 6+1 Traits of Writing
The Five Paragraph Essay
Unit 13 Internal and External Business Communication – Writing Business Reports.
To support your understanding of the Literacy and Numeracy demands in your workplace and how they relate to the ability and efficiency of your employees.
Possible texts for writing
Revising and editing Week 3.
WRITE TO COMMUNICATE.
FOCUS: IDEAS, ORGANIZATION
Research Report Writing and Presentation
Editing vs Proofreading
Business Communication
Completing Business Messages
The Technical Writing Process
Presentation transcript:

End User Support – User Training Documentation for End Users

Objectives Types of Documentation Technical Writing Organisation of Technical Documents Document Planning Process and Strategies Problems with Technical Writing Tools Evaluation Criteria

Documentation for End Users Training can be a once-off session These sessions can be split over a number of days or weeks It is therefore important that the trainee can take something back to the work place in order to remind themselves of their training.

Types of Documentation Brochures and Flyers Proposals, Letters and Memos Newsletters Handouts and Training Aids E-mail Messages Procedural Documentation Web Pages User Guides and Manuals On-line Help Troubleshooting Guides

Technical Writing Technical writing differs from other types of writing because of the following factors: Style Information Goals Uses short phrases, short sentences, lists

Technical Writing Communicates a step-by-step sequence of events or tasks Important points should remain at the beginning It should be brief but not lacking information essential to understanding Uses an economical writing style to present information

Organisation of Technical Documents Introduction Purpose Who is it for Why read it Body Explain the Tasks and Steps Common problems users encounter More detailed information Summary Pointers to additional information

Document Planning Who is it for? What do they already know? What do they need to know? How will they use the documentation? What do you want them to be able to do when they have finished reading the document?

The Process Generate a List of Ideas or features to be covered Organise the list into a logical sequence to form an outline Expand the outline into a first draft Edit as required Review Externally Revise into Final form Proof-read the Document

Strategies Analogies Repetition Consistent Word Use Parallel Structure Similar items are handled consistently Consistent verb tense

Problems with Technical Writing Clutter Nominalisation (use of –tion and –ing endings to create nouns; verbs are easier to understand) Inappropriate Typefaces Wordiness Gender References

Problems with Technical Writing Jargon / undefined acronyms Passive Voice Unclear References Dangling Phrases A few words (or single word) at the beginning or end of a sentence that add little to the meaning of the sentence other than making it longer

Technical Writing Tools Word processing functions technical writers can use: Outliner Spell Checker Grammar Checker Thesaurus Readability Index Desktop Publishing Specialist tools (include programming capability)

Evaluation Criteria Content Organisation Is it accurate? Is the coverage of the topic complete? Organisation Is the information easy to locate? Are the transitions between topics identifiable? Can the user get in and out quickly with the right answer?

Evaluation Criteria Format Mechanics Does the layout help the reader? Is the format consistent? Mechanics Are the words spelled correctly? Is the grammar correct? (incl. correct homophones used) Is the writing style effective?

In Conclusion Types of Documentation Technical Writing Organisation of Technical Documents Document Planning Process and Strategies Problems with Technical Writing Tools Evaluation Criteria