Friday, May 14, 2010
A Monumental Day Dawns for Technical Communicators: Certification!
The Society for Technical Communication (STC) announced today that certification for the technical communication field has been approved. Within the next year, technical communicators will be able to attain certification in their profession.
Certification creates two enormous benefits for our profession and for practitioners. First, certification establishes a solid foundation for the legitimacy and economic contribution of technical communication. Second, certified practitioners can clearly demonstrate their expertise as technical communicators, greatly enhancing their value in the marketplace.
Practitioners will become certified in six core competency areas:
• User analysis
• Document design
• Project management
• Authoring (content creation)
• Delivery
• Quality assurance
As a result, employers and clients alike will now have a concrete idea of the expertise, contribution, and value that technical communicators bring to the marketplace. STC is developing a page on its website dedicated to promoting certification and explaining the value of certified technical communicators.
Two days ago, on 30 April, the STC Board of Directors accepted a business case from its Certification Task Force. This historic event occurred after 35 years of ongoing and difficult discussion. The Society has embraced the idea of certification for technical communicators, and in the coming months will be developing a certification program.
Certification will be based on assessing portfolios and work artifacts, not examinations. (In other words, there are no tests.) This method takes advantage of the existing methodology and infrastructure of both the publications competitions and the Associate Fellow and Fellow process. To implement the program, STC is defining assessment criteria for each of these six competency areas, then recruiting a network of examiners to review applications. In the future, as the Body of Knowledge is fleshed out, STC will look at adding an exam-based assessment as another certification method.
Once conferred, certification will be valid for three years. To ensure that competencies are kept relevant, certified professionals must become recertified for another three years. As with many other professions, recertification involves completing and participating in educational and professional activities. STC currently has a number of these opportunities available, and will be creating more in the upcoming year.
Member and nonmember certification and recertification fess are still being developed; however, these fees will be comparable to certification programs of similar associations.
To learn more, attend the “Status of Certification for Technical Communicators” session Wednesday morning, 5 May, at 11:30 AM in Cumberland KL during STC’s Summit in Dallas, Texas. The Certification Task Force will report on its process, progress, and future. You can also expect to hear much more about certification in the coming weeks!
Saturday, May 8, 2010
STC Summit - Topic Trends
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.
Thursday, May 6, 2010
STC Summit - Tourist Tidbits
On 4.2 acres of downtown Dallas, there is Pioneer Plaza, which contains approximately 40 statues of longhorn steer, complete with cowboys. These larger than life statues show a typical cattle drive. My husband found out about this site when he talked to Manny, who worked at the hotel. Manny turned out to be a wealth of information.
Tuesday, May 4, 2010
The Summit 2010, Keynote Speaker and Education Sessions Begin
For most of the conference attendees, this was the day when the bulk of us started learning. The Leadership Day enabled me to learn from one perspective, the remaining days were opportunities for me to learn from another perspective.
The first stage of learning was from the keynote speaker. Erin McKean—Chief Consulting Editor, American Dictionaries for Oxford University Press, as well as founder and CEO of Wordnik —showed us how words, especially when considered as part of the history of the dictionary, are as much fun as we expected. She talked about the first issue of the dictionary and how there were instructions on how to look up things in alphabetical order. There was even a description of what alphabetical meant! To top this off, it was written in an older form of English (looketh up writing from the 1600s and you will knoweth what I mean). :-)
She poked fun at the dictionary itself because it describes a dictionary has having one-sentence descriptions of words that are captured in a book. If you have ever looked at a dictionary, you know that there is far more content than one sentence and it no longer needs to be in a book.
She also talked about dictionaries defining what without capturing, who, how, where and when. Her example was the word "tuxedo". Without context, how would you know if the person wearing the tuxedo was a waiter or James Bond? To give you an example of Erin's sense of humour, this was conveyed with pictures of Lego figures, where only one was carrying a gun and an attache case.
She also gave an example of a definition of a feather that went on for about five lines, which left us more confused than ever before. Talk about poor choices of words and the passive voice!
All in all, the topic struck a chord with the audience, and it became quite clear why she had just been made an Honorary Fellow of the Society.
After the keynote speaker, the more intense learning began. Because of the keynote speaker, the education sessions did not start until 1:30 pm, but they continued throughout the day until 6:15 pm. During that time I attended the following sessions (each of which is about 1.5 hours long):
- Assessing/Increasing Your Corporate Value
- Using Stories for More Effective Usability
- Content Management as a Practice
The last session hit home with me because it related to some projects that I have been working on lately. It emphasized the importance of putting processes in place even before selecting a tool, and even deciding if a tool is needed. Ironically, the speaker is from Toronto. It was particularly funny (for me) when she mentioned Canada's win over the U.S. team in the Olympics. Things went uphill after that. :-)
After these learning sessions, I attended a Community Reception. It's at events like this that you get a good sense of just how international the organization is. As a member in your own town or city, you don't really think about India, France, Israel, Australia or even the vastness of the United States, and just how many states there really are. After a short time at a networking event—not to mention Leadership Day, and talking to the person beside you at one of the education sessions—you have a real eye-opening experience. You start to recognize the vastness of the technical communication profession, of which you are an important part.
I am writing this blog entry between learning sessions, which is when I am supposed to be eating; however, to get free Internet access, which is set up in the Exhibitition Hall, I have to use the terminals a little off hours, although, as you can see from the picture, there really is no down time.
My head is getting ready to burst with all the new information. It helps to write about it and share it with others. Stayed tuned for more details about some great sessions that I have attended so far today.
The Summit 2010, Leadership Day
Leadership Day started at 7:30 am Sunday morning. Perhaps it was a test of leadership to be on time for this event and still follow the great presentations going on. Not all people are morning people.
The day started with Cindy Currie, STC President, providing a summary of the financial crisis and how the Society survived and even made a small profit after taking many actions to deal with a projected deficit.
In an effort to let chapters participate in how we move forward, the Society asked for volunteers to be on a task force -- Community Funding and Support. One of the members of that task force is from the West Coast Chapter in British Columbia. Four members of the task force gave a presentation, which was really well received. In fact, their observations and recommendations were one of the highlights of the morning as the leaders (both Chapters and Society) recognized the validity and value of the information.
In the afternoon, there were various progressions to attend. I participated in the following:
- Re-engineering Your Community
- How to Create Webinars
- Community Funding and Support
- Developing Educational Programs
Everyone had some great ideas. The day was full of a lot of questions and answers -- so many that one of the items on the agenda had to be dropped. Some of the suggestions require more research at the Society level. I look forward to seeing the end result.
Look for my next post about the keynote speaker and my first education seminars.
Monday, May 3, 2010
The Summit 2010, Travelling to Dallas
I am the Immediate Past President of the chapter. In a draw that the chapter held to see which council member would attend this conference, my name was selected. The last conference did not go well for me -- my appendix ruptured and I spent my time in Las Vegas, the place of the conference, in a hospital room. The standard bon voyage message as I left for the conference had something to do with returning and having all my organs intact.
In an effort to keep costs down, I decided to fly out of Detroit. Although the drive was a long one, the weather was good and I saved about $400 in the process.
While the drive was long, the sleep was limited. I got up at 3:30 am to make sure I caught my 6:45 am plane. The lineups at the airport were like those at Wonderland. I couldn't believe that there would be so many people at the airport at that awful hour. The plane out of Detroit was delayed because of a storm (lightning, high winds, and heavy rains). I was glad that it started before takeoff rather than after. Although there was some turbulence, I arrived in one piece.
My husband came with me on the trip, so in an effort to do something together before all the meetings and education sessions started, we tried out Dallas's transportation system and went to the Dallas Zoo. The zoo in Toronto is a lot bigger, but from the walking we did and the pain in our feet, my husband and I were glad that the zoo wasn't any bigger.
Bedtime was early because, between the 3:30 am start and the amount of walking, we were exhausted. Our last bit of exercise was trying to climb up into bed. The top of the mattresses was about 3 feet off the floor, which meant that neither my husband or I could touch the floor when we were sitting on the mattress.
The Leadership Day started at 7:30 am the next day, so I wanted to be wide awake for the discussions.
Look for my next blog entry about Leadership Day. I am off to my first education session.