Hello from the Summit!

Written by Tom Glennan

Hello from soggy Atlanta, Georgia! Daily highs in the mid-40s to low 50s, rain, wind, and morning fog – it must be STC Summit time in Georgia. In spite of the weather, this year’s Summit program has really been outstanding, and the learning and networking opportunities so far have really made this trip worthwhile. So I thought I’d drop a quick note about my thoughts and experiences before starting my Tuesday afternoon sessions.

Sunday I attended my first Leadership Day, and it was definitely an eye-opening experience. As the STC-SM chapter’s incoming president, I’ve been anxious to learn everything I can about the duties and responsibilities of my new office, and compare notes and experiences with the leadership from other communities who attended the event. While it’s apparent to me after hearing some of the speakers and discussion leaders on Sunday (and yesterday afternoon at the business meeting) that the Society and many other communities are facing many of the same challenges and difficulties that we are at STC-SM, it’s also very clear that the leaders I’ve met are up to the task. I was really encouraged by the sense of togetherness that I felt when speaking with others, and the resources that are available to us. Maryann Bowen and I have already talked several times with each other and with other chapter leaders and members. (For example, I had lunch with the Southeast Ohio chapter yesterday, of which I am also a member.) We’ve been putting together our lists of things to tackle and the options available to us as we work to build upon and expand the recent successes of our chapter, while also preparing for the future with new ideas and approaches. We’ll be sharing these ideas with you and with the Leadership Council over the coming weeks and months.

Of course, I’ve also been focused on using my participation at the Summit as an excellent opportunity to learn and apply many ideas for adding new or improved skills and abilities to my technical communicator toolbox, as well as my personal branding and career development. The Summit has been very beneficial and informative, beginning with an excellent case study yesterday on single-source collaboration for developing a training program materials, and subsequent sessions on using content management systems and sharpening my subject matter expert interviewing skills, as well as some sessions with vendors to better understand how to apply their products, And a free newly published book on how to use Adobe® FrameMaker® 11 was the icing on the cake (so far).

Well, I need to catch the progression session on writing and editing, but I’ll send an additional blog posting at the Summit’s conclusion. In the meantime, send me an email (tglennan@twsinfo.com, and no, I don’t do Facebook® or Twitter®) if you have any comments or questions, and I’ll get back to you as soon as I can.

Tom Glennan
Incoming STC-SM president

An evening about e-learning

Written by Elizabeth Donoghue Colvin

smaller Articulate photoOn the evening of March 26, 2013, STC-SM program attendees were treated to demonstrations of Articulate® Storyline, a software that lets you “create polished interactive courses” and that’s “simple enough for beginners, powerful enough for experts” (Articulate website). At one of the Ann Arbor, MI, Thomson-Reuters offices, individuals representing a wide range of professions – including technical communicators and e-learning specialists and other educators – not only received instructions in how Articulate works but were invited to develop a basic e-learning storyline using the software as part of a hands-on experience while seated at computers.

Leading the program for the evening were Megan Torrance, the Chief Energy Officer of TorranceLearning, an e-learning design and development company located in Chelsea, MI; Matt Kliewer, a TorranceLearning designer who handles special technology projects; and Jeanette Brooks, who spent four years as Articulate Storyline’s e-learning community manager and who is now the Manager of Member Services at the Dexter Wellness Center in Dexter, MI.

Participants either worked on a prepared storyline about how to make candied bacon or chose their own storyline. Either way, they learned the basics about how the software works and heard opinions on how it compares to other e-learning options such as Adobe® Captivate® and Lectora®. They took their presentations home with them on their USB flash drives.

The presenters showed that Articulate Storyline has some easy-to-use features in common with Microsoft® PowerPoint®, including a design tab with pre-made templates and an ease in moving things around on the screen. In addition, one of Articulate Storyline’s strengths is that it allows the user to synchronize the progression of the visual storyline with the audio attached to it by moving things around – including the audio waves – on the screen. In addition, Articulate Storyline e-learning products can be translated into other languages after the entire e-learning course has been built; everything except the images gets translated, even the buttons. Typically, though, the product will need tweaking after translation, because other languages generally take up more space than English does. E-learning products can also be made 508 compliant (accessible to individuals with disabilities).

Program participants also learned that Articulate Storyline outputs can be published to Adobe Flash® or as HTML5. The Articulate Storyline website has information about what to consider when publishing as HTML5, as publishing that way can present some challenges to the user. Articulate can also function as a learning management system: It can host your content and track and report on its use.

The presenters praised Articulate Storyline for the energy it puts into its online community, which includes blogs, forums and the opportunity for peer-to-peer connections with others users. Even when using the free-trial download, users who ask questions get prompt answers. (Click on the Free Trials button on the Articulate home page). Users are also invited to suggest enhancements to features for inclusion in the next version of the software.

At closing, the presenters had some words of advice: One way to learn how to build an e-learning product is to deconstruct one built by someone else. Also, one of the most useful things you can do as an Articulate Storyline learner is to subscribe to the word-of-mouth blog on the Articulate website.

STC-SM appreciates the time the presenters contributed in hosting one of the most well-attended programs in recent memory. We are also grateful to Thomson-Reuters staff, who lent the use of their computer lab and made sure several computers were ready for use that evening.

Content Management Systems (CMS) and their Application in Creating Documentation

Written by Tom Glennan

CMS program room shot According to a recent study by Information Mapping Inc. (2012), an organization of 1000 employees spends 2500 hours per week searching for information in their documentation. They waste up to $2.5 million per year on employees searching for information they cannot find, and up to $5 million per year recreating information that already exists. And because most organizations typically have only centralized 50% or less of their critical information, there are many harder to quantify costs incurred by the organization relating to poor decisions, poor quality, employee frustration, and lost sales. Furthermore, according to Forbes magazine (1/4/2013), the “creative employees” in an organization (like technical communicators) waste 30% or more of their time looking for, re-creating, or unnecessarily moving content within their organization.
Sound familiar? For situations like these and others, a content management system (CMS) may be the solution you and your customers or employers need. To help understand the issues and solutions with managing and retrieving information, Patrick Becker, president of Asyling Digital Media Solutions of Ann Arbor, discussed the topic, “Content Management Systems (CMS) and their Application in Creating Documentation”, in the February 27th STC-SM program meeting. The program was held at the offices of Thomson Reuters in Dexter, Michigan, and refreshments and door prizes were sponsored by the communications department at Lawrence Technological University in Southfield.

LTU's table at Feb 23, 2013 meeting
What is a Content Management System?
A content management system is a computer program that allows publishing, editing and modifying content, as well as maintenance, from a central interface. These systems can be either manual or automatic in executions, manage workflow among many authors or documents in a collaborative environment. Originally designed in the 1990s to simplify the task of writing multiple versions of code and make the website development process more flexible, CMS now enables the centralization of data editing, publishing, and modification. (Wikipedia, retrieved 2-10-13 from http://en.wikipedia.org/wiki/Content-management_system).
So How Can a CMS Help Me?
According to Patrick and his team of presenters, a properly-designed CMS consists of three subsystems: the production content component, the web component, and the digital asset management component (think of iTunes or your DVR at home). These three components make up the CMS “eco-system” which creates, manages and distributes the content information. By employing “templates”, the CMS is able to improve the speed, accuracy and control when managing the content information throughout the organization. Furthermore, you can also have multiple working on the same document (although not the same particular article or paragraph) simultaneously, which improves the ability to share ideas and collaborate on the document.
In addition, David Rheault reviewed the concept of “brands” (think a publication title like Time or Sports Illustrated), which are specific to a particular genre within the publication industry and can be used as labels for organizing, managing and distributing the content within specific modules or chunks.
So What’s the Bottom Line?
CMS is both a strategy and a tool for effectively and efficiently managing and distributing reusable content within an organization. Although it may be difficult at first and requires taking more of a “topic-based” approach to content creation as opposed to the narrative method you may be familiar with, the ease of accessing information and distributing it throughout the organization may make it worth the effort.

Member Spotlight: Pat Gómez Martz

P Martz Feb 2013What is your educational background? How long have you been a member of  STC? In what STC positions have you served? 
I have a Bachelor of Science in Botany and a Bachelor of Forestry from SUNY College of Environmental Science and Forestry, and a Master of Science in Technical and Professional Communication, completed in May 2012, at Lawrence Tech. I have been an STC member since 2009, and I took over as webmaster in late May 2012.

Why did you decide to pursue technical communication as a career?
It pursued me!

My undergraduate education was extremely heavy in science, math, and technology. When I was offered a contract position as an indexing editor for UMI, I took it and started my professional life indexing biology, chemistry, engineering, and math dissertation abstracts.

Most of my working life I have been a self-taught graphic designer who also edits, writes copy, and illustrates. “Self-taught” is a secret code for “I read a lot about what I do, about the things that influence how I do what I do, and I look at a lot of different types of communication and talk to people to see what works and what doesn’t.”

My daughter pointed out that I was a technical communicator after she did a multiyear time audit of my project work. Boy, was I surprised. There’s a name for it.

Why did you decide to join STC?
Having learned that I had been in technical communication for all these years, I wanted to learn more about the possibilities, so I joined STC.

Where are you currently employed?
I run my own business, Inkberry Solutions, and I am an adjunct professor at Lawrence Tech.

What are your job activities? What do you find most interesting and/or satisfying about your job?
Currently, the focus is on proposals—consulting on process, developmental and technical editing, and building a custom database system to manage content for future proposals. I do a lot of other things as well: graphic design, illustration, simple websites, and teaching the “why” and “how” to clients—a lot of “why,” but not as much “how.” The best part of my work life is the wide variety of projects.

What are some examples of projects you are particularly proud of?
I built a database system that tackles the administrative end of a five-year federal project to produce thousands of fixed-priced environmental reports about parcels of land. The database allows my client to handle heavy bouts of report-writing while keeping track of where each one is in the process, and maintaining profitability.

How has being an STC member helped you with your career?
It has exposed me to some new ideas, and it has given me some exposure.

What advice do you have for students as they are entering the field of technical communication?
Keep learning. Read, including about things outside your particular area. Talk to people. Write. Draw. Paint. Learn a craft. Keep looking at the rhetorical bent and the design of communications, especially when you are the end user. How does it affect you? How would you improve it?

What else would you like our readers to know about you?
The joke is on me. I spent my undergraduate college career studiously avoiding anything and everything having to do with English, and now I work predominantly with words.

Usability Testing Reveals Two Audiences and an Approach to Both

On Saturday, February 2, participants from the September 2012 card-sorting activity reconvened at Lawrence Tech with Pam Finger, MS-TPC candidate at Lawrence Tech, to learn about her analysis, to verify or correct her interpretations, and to discuss how to implement some of these changes.


Everyone agreed we need good navigation and easy-to-scan pages. Everyone wanted information about STC/SM and our activities and programs, a members’ area, contact information, and resources.


Students are looking outward for resources including social networking, professional development opportunities, and program calendars, but had no interest in archives. They are interested in multimedia.

Council members on the other hand, are looking inward for a repository of archived newsletters and program information in the process of developing new programs and other activities.


These groups represent two different audiences. Everyone concurred that a major purpose of the website was to attract new members, so the information that our students gave us was very valuable, and may be representative of what potential new members are looking for. On the other hand, Council needs to be able to find the information they need.

In the course of her research, Finger met with Dave Mitropoulus-Rundus, who had analyzed the previous website and reviewed the current interim website. One thing stuck out as a shortcoming on both: we need a tagline at the top of the page to the right of the logo.

When Pat Martz took over as STC/SM webmaster last June, she felt that the volunteers who work with the website, including blog editors and writers and the webmaster, need a standards-based, easy-to-maintain site.

Recommendations and Next Steps

Finger took all this into account when she prepared wireframes, which we discussed. We realized that we can move archived files into Resources, as that is what they are for Council members. One person pointed out that archives would also serve as resources for students, if they were to write articles or give presentations that they would later like to refer to in a portfolio.

The Council will discuss the mission statement and a better tagline at the next Council meeting.

A new information architecture will be worked up and implemented over the next few months; the resulting website will evolve from the current one, rather than being another complete change.

Ann Arbor to Host a WIAD 2013 Conference

What is WIAD? It’s World Information Architecture Day, February 9. The Student Organization for Computer-Human Interaction (SOCHI) at the UM School of Information is coordinating this free Information Architecture Institute conference, one of 15 conferences worldwide.

The focus will be on clarifying what we mean when we say “architecture” and when we say “design” in research and practice; the differences implied by these terms are frequently lost in translation. Peter Morville, Malcolm McCullough, Daniel Eizans, and Andrew Hinton are scheduled to speak.

More information, including the agenda and a registration link, is available at Ann Arbor WIAD 2013 Conference. You may also register in person from 8:30–9:30 a.m.

Where: University of Michigan, Modern Languages Building, Auditorium 3, 812 E Washington Street, Ann Arbor, Michigan (one block east of State Street)

When: February 9, 9:30 a.m.–5:10 p.m., with a reception following from 5:10–7 p.m.

Cost: Free

November Program Meeting: “Agile Technical Writing”

Jack DeLand explains Agile

Written by Susan Fisher

Agile is not your father’s (or mother’s) tech writing. It’s all about working with small chunks of content, being continually iterative, and understanding that it’s never really “done.”

STC-SM member Jack DeLand, a Certified Scrum Master and Agile practitioner, led the audience on a tour of the Agile development process and explained how technical writing fits into it. Most commonly used in computer software and systems development, Agile can be used with other types of development as well.

Traditional Development vs. Agile Development

In the traditional development process, comprehensive requirements and design specifications are created at the front end of a project. The entire product is then built and finally tested — followed by product-wide bug diagnosis and repair.

The Agile methodology is essentially about iterative, incremental development. Small functional chunks of the product are defined, designed, developed, tested, revised, and tested again until they are working properly. Then, these small chunks are combined into larger functional pieces using the same approach, until the product is complete. Development is a collaborative effort by cross-functional teams.

Flexible design, rapid prototyping, and quick adaptation to changing needs are hallmarks of the methodology. User input and usability testing are woven throughout the process.

What Does It Mean for the Tech Writer?

Instead of joining the project near the end, as is typical with traditional development, the tech writer on an Agile project is a member of the cross-functional team from the beginning. As such, the writer can play a key role in user needs analysis, design, usability testing, and the continual improvement of the product.

On the other side of the coin, the writer has to be comfortable with ambiguity, writing in fragments, innumerable versions of the documentation, and the reality that the product will continue to change until the end of the project.

It’s not for the faint of heart, but the rewards are worth the effort — and best practices have been, and continue to be, identified.

More Information

To learn more, Jack recommended starting with “Agile Technical Documentation” by Jean-Luc Mazet (http://writersua.com/articles/Agile_doc/index.html).

He also suggested visiting these LinkedIn groups:

  • ŸAgile Technical Writers
  • ŸTechnical Writers in an Agile Environment