STC Logo
MTC Logo
 
transparent-Home Home                    
transparent-sightsearch Site Search         
transparent-Calendar Calendar              
transparent-Chapter Our Chapter        
transparent-comp Competitions
transparent-Notes Meeting Notes    
transparent-newsletters Newsletters        
transparent-newsletters Employment        
transparent-email Email List             
transparent-links Links                     
transparent-join Join STC             
transparent-feedback Feedback            
transparent-nashville Nashville              

 

MTC Logo
 

 

Meeting Notes

June 2001
Reviewing 2001 in Chicago, previewing 2002 in Nashville

With the next STC annual conference headed into Nashville next May, interest was high at the May chapter meeting.

About 30 chapter members and visitors—a large crowd in the memory of many in attendance—heard Chapter President Rita Johnson and members Holly Quick and Laura Liles review their favorite seminars from the 48th Annual Conference of the Society for Technical Communication in Chicago.

It was our first meeting with Rita as chapter president and Pat Cosky as program coordinator.

After networking and fellowship that were aided by deli treats, soda, wine, and beer (everybody behaved), the crowd settled in to hear Rita, Holly, and Laura recount their most memorable seminars and conference sessions. (See the notes from Holly and Laura notes below.)

Rita gave highlights of briefings she attended with national officials (including both encouragement for and restrictions on what we can do to promote the conference). She also described meetings with representatives of the Chicago chapter in which she gained some insights into the amount of work required of the chapter.

With most of the conference planning handled at the national level, our chapter will primarily be involved in hospitality issues.

 

(Posted June 28, 2001)

48th Annual STC Conference 2001

Highlights

Holly Quick
Tanner Corporate Services

Session: William Horton: Say It in Pictures: Visual Literacy for Business and Technical Communication

Recommended reference: Designing Web-Based Training by William Horton

Key points:

  • Visuals should make words more understandable; this is their purpose in technical and business documentation.
  • To strengthen visual ability
         - practice thinking visually; for example, practice converting words to pictures
         - find examples of good and bad visual design. The library is a good place for reference books
         - take up a visual hobby like photography
         - if you happen upon or think of a good graphic idea, sketch it to help yourself remember
         - practice critiquing graphics - what works, what doesn't. How would you fix it, on budget and on deadline
  • Clichés work great in graphics.
  • Color a very important element. Our eyes are not color-corrected, and as a result red seems closer; blue farther away - use red in foreground, blue in background
  • Don't ever use red or human beings as background; the brain says, these are important, pay attention, so they fight with foreground images.
  • People identify with cartoon characters. When pictures of real people are used, an individual tends to notice what makes the subject of the picture or photograph different from him or her.
  • Think in terms of using telling, not distracting, details.
  • Keep the following in mind:
         - Associations with color; for example, red equals heat, financial loss, blood
         - Red-green color blindness
         - Visual acuity declines with age.
         - We live in a multicultural world. Be sensitive to all cultures; consider what will communicate your ideas to people of different cultures.


Session: Dewitt Jones, Photographer - Opening Session Speaker
Vision

When you have vision and passion, commitment and discipline are non-issues.

Nature has been his greatest teacher.

Five key points:

1. Focus your vision-for example, National Geographic - their mission is to show what's right with the world. A focused vision is where the energy for transformation resides.

2. Get training and develop technique: vision without technique is blind

3. Put yourself in the place of most potential.

4. Be open to possibilities.

5. Lose the fear of making mistakes, and don't stop with the "right" answer-find the next right answer. Showed us several examples of good photographs that led to great photographs because he didn't stop, and instead remained open to the flow, to the movement.

His motto: What will I be given today? Will I be open enough to see it?

Laura Liles
HCAHealthcare Corp.

Session: When Users Hate Help - What to Do

Overview

  • Generate awareness that the help is there.
  • Don't let the tool's bells and whistles overwhelm or take over the content and design of your information.
  • Training is invaluable in teaching users how to use the documentation resources.
  • Make sure the information you deliver is the right content for the audience.
  • Give customers content and don't spend too much time with the sharp look and
    dazzling features.

The Information

  • The information in the help system should match the user's workflow and not necessarily the screens.
  • Information needs are different as different points in the workflow.
  • Different users need different types of information.
  • Present the best information for what they are doing and not just what they are seeing on the screen.
  • Don't overlook embedded help on the user interface. Encourage more information in the interface.

Context-Sensitive

  • Context-sensitive does not mean what's on the screen.
  • Workflow is often the context. For example: Create a folder, Add a folder, Delete a folder.

Integrated Learning Points

  • The topics should address common learning questions such as What is?, When?, How?, What way?, etc.
  • Look at the workflow and the roles and responsibilities of the users. At what point do people need to learn the answers to the basic questions? Where is the user in the workflow? What information do they need at that point?
  • Consider what cognitive processes are going on. What decisions are they having to make?

Example to remember: A help system anticipated the users workflow to the point that it provided the checklists and forms that they would need to complete their job. The help system completely integrated the information into their workflow.

Getting Started on a New Project

  • Think from the user's point of view
  • Ask the basic questions
  • Start with the workflow
  • Work with the interface designers

Session: Strategies for Condensing Online Text

Notes

  • Write concisely
  • Write in the inverted pyramid style
  • Make the text scannable
  • Use more heads, tables, and lists
  • Delete introductory text that repeats content in the heads
  • Don't begin heads with articles
  • Keep overviews brief
  • Link to nonessential information
  • Don't repeat overview information in step-by-step instructions
  • Consider publishing overview information in print only
  • Edit your text online
  • Break up solid blocks of text into shorter topics, shorter paragraphs, or lists. Make the topics self-contained.
  • Each topic should answer one question about one subject
  • Plan for white space

Session: Building an EPSS on a Small Budget

What is an EPSS?

  • Electronic environment that provides information, guidance, tools, and more during a task.
  • Used on the job.
  • Provides information on different levels
  • Allows for different learning styles.
  • Integrates information, advice, and learning experiences.
Answers these questions or needs:
  • Why do this?
  • What is it?
  • How do I do it?
  • What's related to it?
  • How/why did this work?
  • Show me an example
  • Teach me
  • Assist me
  • Advise me
  • Let me try
  • Where am I?
  • What's next?

 

 

 


 

 

 

  

©1998-2003 - Society for Technical Communication, Middle Tennessee Chapter