STC Summit - Topic Trends

By Debbie Kerr

Prior to coming to the conference, I tried to plan which education sessions I wanted to attend. Since I was going to a conference for technical communicator, nearly every session seemed to apply to me. I took my best guess at what I thought would be the best for me. However, once I got to Dallas and started looking again, I started to develop stronger feelings about some sessions over others. The name of the speaker made the difference. In other cases, I noticed something in the session descriptions that I hadn't notice it before. It was like being told you could only have one piece of candy when all of them looked good. With this in mind, I spent every night reviewing the next day's sessions to make sure that what I thought were my best selections before I arrived at the Summit were still my best choices.

When I was planning for the conference, Fei Min Lorente (your fearless president) and Carol Lawless (your chapter secretary) suggested that I select two sessions for each time slot so that if one session wasn't providing me with the information that I wanted I could go to my second choice. I am happy to report, in all cases, that I was satisfied with my first choice.

On May 3, I attended the following sessions:

• Assessing Your Corporate Value - Jack Molisani


• Using Stories for More Effective Usability - Whitney Quesenbery


• Content Management as a Practice - Pamela Kostur (my favourite for the day)

On May 4, I attended the following sessions:

• How to Edit Online Like a Pro! - Linda Oestreich and Michelle Corbin


• Creating Visual Help and Training Using Adobe Acrobat - Neil Perlin


• Managing Documentation Projects in a Collaborative World - Larry Kunz (one of my favourites for the day)


• Content Strategy SIG Progression - too many presenters to mention


• Building Visual Explanations: Practical Advice for Writers - Don Moyer (my favourite of the Summit)

On May 5, I attended the following sessions:

• Results of Interviewing Editors: Best Practices, Challenges, Insights - Angela Eaton, Liz Pohland, Cynthia McPherson


• Thriving in an Agile Environment - Kathryn Poe


• Enhance Your Writing Career with Improved Speaking Skills - Barrie Byron

While the topics may seemed varied, there were two hot topics for the Summit: Content Strategy and Agile. Some of these topics you can see in the title of the sessions and others were embedded in the topic descriptions.

Social Media

With changes in the way that information can be presented to users, a content strategy is becoming more accurate than preparing a documentation plan. With the various social media options available (e.g. forums, wikis, Twitter, and blogs), many organizations are looking toward using these resources in addition to traditional documentation. In some cases, these other methods of communication will replace all or some of the more traditional methods. For this reason, the method for planning how to provide users with information must be an entire content strategy, and not merely focused on documentation.

For example, in one education session, the presenter talked about how someone had used Twitter to learn when users were having trouble with a product. Since the success of a company is often based on customer service, being proactive in providing information is an excellent place to start. Imagine being on Twitter and complaining to someone that a particular feature doesn't work. Wouldn't be great if someone from that company contacted you and provided you with an answer without you even having to contact them? In many cases, users don't even ask for assistance from the company. They often complain about the company/product without trying to get an answer to their questions. Using Twitter helps to eliminate this step.

Another interesting way to use Twitter is to get sales leads and to obtain feedback about what features users would like to see in a product. Another way that companies are using social media is to use wikis for Help and forums for customers to obtain support from either the company or fellow users. Social media seems to have more uses than just being sociable.

Agile

Agile is a new way of planning and completing a project. This methodology replaces the traditional waterfall and iterative waterfall that is usually used for the software development life cycle. With Agile, requirements, development, documentation, and testing, take place over and over in iterations that build on the previous iteration. One iteration might include A, B, and C. The second iteration will include any necessary changes to A, B, and C, and new items D and E. This process will continue until everything is complete -- development, documentation, and testing.

The major change for technical communicators is that everyone involved in the design and development cycles are part of the project right from the beginning. This means moving from the end of the development cycle to being involved right from the beginning. As you can imagine, for many technical communicators, this is a big and welcome change.

Some people enter into the Agile world for the wrong reasons, for example, they believe that it will eliminate the need for documentation and that everything will get done faster. The truth is that documentation will still be needed; it just might be created using different timelines, which will necessitate writing and reviewing documentation in a different way. As for getting work done faster, this will only be true if the people involved in the process have the discipline needed to complete their work on time and in the way that is needed. Without this discipline, companies can end up with more chaos than they may have had before.

Conclusion

It seems like there is a lot of potential changes to the role of technical communicator. It also emphasizes that the term technical writer does not accurately reflect our changing role.