![]() |
| Main Entrance to the Convention Centre |
| Entrance to the Vendor Showcase |
![]() |
| Tribute to the Pony Express in Old Sacramento |
![]() |
| State Building |
![]() |
| The Peace Garden, full of roses and writings from children about peace |
![]() |
| Convention Centre Ceiling |
![]() |
| Main Entrance to the Convention Centre |
| Entrance to the Vendor Showcase |
![]() |
| Tribute to the Pony Express in Old Sacramento |
![]() |
| State Building |
![]() |
| The Peace Garden, full of roses and writings from children about peace |
![]() |
| Convention Centre Ceiling |
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:
On May 4, I attended the following sessions:
On May 5, I attended the following sessions:
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.
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 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.
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.
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):
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.