Posted in Uncategorized

Adobe Day@STC Summit 2014 – We Went Back to The Future

We definitely didn't hear this panel say to any of us, "I'm afraid you're just too darn loud!"
We definitely didn’t hear this panel say to any of us, “I’m afraid you’re just too darn loud!”

I apologize for my blog coverage of the 2014 STC Summit edition of Adobe Day being delayed–it’s been a busy month! But hopefully, you’ll feel it’s been worth the wait, and you had a chance to see my live Twitter feed as it happened.

The STC’14 Adobe Day felt a little bit different this year. One of the things I noticed was that as much as Adobe says that these Adobe Day events are Adobe-product free, lately, they haven’t been. HOWEVER, they are still not one big, in-person infomercial either. Adobe products are not brought up much, but if they are, it’s to show that they can be tools to use to create solutions to common tech comm issues. So, it might be an inadvertant infomercial in that respect, but it’s not done in a blatant way that screams, “YOU NEED TO BUY ME!!!!!! PLEASE BUY OUR PRODUCTS!!!” Adobe continues to do a good job in showing what tech comm issues are out there, and as leaders in the software field, they are tuned into these issues and are creating products that benefit the technical communicator. I think that’s fair enough. The talks, overall, were broader topics that in some instances used Adobe Tech Comm Suite tools to provide solutions. And you have to remember, while these talks are aimed to be product-free for the most part, it’d probably look pretty bad if you had someone declaring all the glories of a competitive product when Adobe is hosting the event. Y’know?

With that out of the way, I observed some other things that made this a little bit different. First, there were fewer speakers this year. I felt that was a good thing, because in the past with more speakers, each speaker would be racing to get his/her presentation completed in a very short amount of time, and there would be little time for questions or discussion. Since there were fewer speakers this year, each one could elaborate more on their topic, which allowed for more time for questions and discussion. More networking time during the breaks was also a benefit from having less speakers.

The other difference I saw dealt with the speakers themselves. While they were all familiar, established voices in the tech comm world, it wasn’t the same crowd that one usually sees at Adobe Day events. All of them have participated in Adobe events or other tech comm events before, but in the past, it usually is most of the same speakers up on the podium. While I like all the “usual suspects” very much, and consider them my mentors and have become friends with several of them, seeing these new “players” was actually refreshing to me. I hope that Adobe continues to change up the speaker lineups with future Adobe Days, as all the speakers I’ve heard have a clear voice that’s worth listening to, and hearing as many of those voices as possible provides both variety and fresh perspectives going forward. As I go through each presentation in forthcoming blog posts, hopefully you’ll see what I mean.

But as tradition in this blog dictates, I always start with the panel that capped off the Adobe Day event. I find that these panel talks bring an umbrella perspective to where we are as a profession through several points of view, and seeing where there are agreements and disagreements in the issues at hand.

This year, the panel was moderated by Matt Sullivan, who has been an Adobe Day speaker in the past. He did a great job, as this was the first time I’d seen him as the moderator of an Adobe Day panel. The panel consisted of Adobe Day speakers Marcia Riefer Johnston, Bernard Aschwanden, Kevin Siegel, and past Adobe Day speaker, Joe Welinske. The theme for the panel was looking ahead to the future of where tech comm seems to be going.

The Adobe Day Panel L to R: Matt Sullivan, Bernard Aschwanden, Joe Welinske, Marcia Riefer Johnston, and Kevin Siegel
The Adobe Day Panel
L to R: Matt Sullivan, Bernard Aschwanden, Joe Welinske, Marcia Riefer Johnston, and Kevin Siegel

Matt started with the point that tech comm is more than tech writing now, so what do we need to improve short-term and long-term? Kevin responded first, saying that we need to do more with less on smaller displays and adapting the content appropriately for mobile. Marcia added to that, saying that using less can mean writing tighter as well. (She has a technique she taught during the STC Summit, in fact!) Joe agreed with Marcia, adding that technical communicators need to put in the time to make concise content meaningful, and to look at simplified English as part of that objective. Bernard felt that attending workshops and demonstrations were important, because technical communicators need to continually learn and adapt in this industry! He added that SMEs (Subject Matter Experts) should contribute to content, but technical communicators should control it. Kevin also agreed with Bernard, saying that SMEs are writing content more often now, so teaching them to write tighter will help. Marcia chimed in that many people are now being required to write, but don’t have the skills. We need to help with that.

Moving onto topics about how technology affects technical communication, Kevin said that new technology, like Google Glass and other wearables, is emerging, and we need to understand how these work. Joe pointed out that the Pebble watch now is starting to have user docs now, and more will be emerging. Bernard added that gesture based technology similar to the Xbox Kinect will need documentation.

Matt then asked, “What should we look forward to in the next five years?” Bernard felt that less specialization will be needed so that the right people write the right content, such as an engineer who can write. Specialized writing will be very important. Joe added that we need to agree on taxonomy and terminology, and use style sheets more often for consistency. Marcia believed that topic-based writing will be emerging more as a growth area. Kevin explained that in e-learning, there is a need to develop learning for new devices that responds to user displays, thus accomodating multiple screens.

The next question asked about how to help educate and help with adapting certain generations adjust between print and digital writing/designing. The consenus was that we just need to adapt. The panel encouraged the audience to get to know your UX/UI people, as they will help you learn to adapt, especially if you aren’t as tech-adaptive.

The last question centered on customers customizing their content–is this a trend? Bernard leapt into a response with, “GOOD! DO IT!” He encouraged us to help customers to start doing personalized help, or personalizing any information, for that matter! Moderator Matt closed by saying that rich media that engages users is going to be about content strategy, but it will also be about content marketing. The group agreed that personalized, concise information going forward will be best!

"I guess you guys aren't ready for that yet--but your kids are going to love it!"
“I guess you guys aren’t ready for that yet–but your kids are going to love it!”

And that was it! The session went by quickly, but as you can see, there was a lot of great information that many technical communicators can take and use going forward in their own work.  While it might take some time to adapt, sure enough, it will bring the field forward as technology and the way we access it moves ahead.

Coming soon: The individual presentations at Adobe Day #STC14 Edition!

Posted in Uncategorized

Adobe Day at #STC14 Will Be Looking Towards the Future!

Doc and Marty McFly can't believe the fabulous information they are getting at Adobe Day @STC Summit 2014 . (They already went, and said it was fantastic--not to be missed!)
Doc Brown and Marty McFly can’t believe the fabulous information they got at Adobe Day at the STC Summit 2014. (They already went, and said it was fantastic–not to be missed!)

With each big conference that I attend, I always look forward to Adobe Day, and Adobe Day at the 2014 STC Summit is no exception.  You’ve probably read my past posts about Adobe Day from other conferences, so you know how rich in information they are. I’ve learned an enormous amount of information FOR FREE that would otherwise cost thousands of dollars from the leading experts in the field. It’s hard to find that anywhere else.

On Sunday morning, May 18th, 2014, Adobe is once again putting together a stellar group of technical communications luminaries to set our imaginations on fire! This year’s theme appears to be, “Vision 2020: The Demanding Job of a Technical Communicator.”  Based on the descriptions of each speaker’s talk during this morning session, each will be providing advice and tools–free of any product promotion–that can help make our demanding jobs easier and more productive.  I’ve heard all the speakers before in one way or another, and I can tell you that all of them are top rate. Most of them have spoken at previous Adobe Day events, and they are invited back time and time again because they have valuable information to share.

Kapil Verma of Adobe will be speaking about who he thinks are today’s technical communicators (hint: there’s more than one type!). Marcia Riefer Johnston will be talking about single-sourcing techniques she used to save her company USD$16,000! I’ve taken Marcia’s writing workshop and read her book, so I can tell you she have some marvelous tips. Kevin Siegel will be talking about how to combine something I love–e-learning–with technical documentation to make the documentation more dynamic and valuable! I’m looking forward to that.  Bernard Aschwanden–the STC’s newly elected vice-president–will be speaking about using content strategy to help promote revenue growth. And last, but not least, a panel including all the speakers plus Tom Aldous of Acrolinx, moderated by Matt Sullivan, looks like it will be quite the lively talk.

Did I mention that breakfast, snacks, and lunch are included, too? And it’s FREE?

I know–you are saying, “Great! I want to go! I don’t want to miss out on this!” Great! But you do have to register so that Adobe knows you are coming! Make sure you register by 11:59 PM PDT on May 16th, because you don’t want to miss out!

Register for Adobe Day @ STC Summit 2014

I will be covering the event LIVE on Twitter from my @techcommgeekmom account, so make sure to follow along, even if you are attending!

See you there!

Posted in Uncategorized

Adobe Day @ Lavacon 2013: Scott Abel’s 5 Technologies Tech Comm Can’t Ignore

voodoodonutsignI realized as I was writing this post that this would be my 500th post on TechCommGeekMom. Who knew that so much information and thought could accumulate through original posts and curated content?  I’m also very close to my all-time 15,000 hits mark (only a few hits away at this writing). I wouldn’t have believed you if you told me that I’d hit these benchmarks when I started this blog, but of course, I’m going to keep going! I debated about what I should write for my 500th post–whether to finish my Adobe Day coverage or do something else, and in the end, it seems fitting to finish my Adobe Day coverage, because in many respects, knowing and writing about the presentation of Scott Abel, aka “The Content Wrangler”, shows how far I’ve come already in my tech comm journey from beginner to covering internationally known presenters.

Scott is one of the most prolific and vocal speakers out there on the conference circuit speaking about content–whether it be content management or other technical communication topics.  It also seems like he has written the forewords of many of the best tech comm books out there. He’s everywhere! To boot, he’s an accomplished DJ, and I found myself “bonding” with him over dance remixes and mash-ups while at Lavacon, because I always enjoy when he posts either his mash-ups or his favorite mash-ups on Facebook. (I’ll be writing a post about the relationship between tech comm and dance mash-ups in the near future.)  He is a person who is full of so much kinetic energy that you wonder when he’s going to explode, but he doesn’t. Even the time I saw him at the STC Summit last spring with a bad cold, he was still more on top of his game than a lot of people would be on a good day.  Much like Val Swisher, my love for all things Scott Abel also knows no bounds.  He knows how to stir things up at times, but there is no denying that in his frenetic pace of delivering a presentation, you learn SO much. I’m lucky that he’s so kind to be one of my cheerleaders!

ScottAbel
Scott Abel checking his files before his presentation

So when it came to thinking of a garden in Portland to use as an analogy to Scott, I had to deviate. In my mind, he’s the Voodoo Doughnuts shop located about four or five blocks away from the Chinese Garden. Scott’s talks always have lines going out the door, and like many of the Voodoo Doughnuts themselves, the unique flavors dispensed open your mind up to new and delicious possibilities and ideas, and you come back wanting more (hence, more long lines!).  They are both crazy and sweet at the same time. You can’t beat that combination.

Scott was the keynote speaker for Adobe Day as well as the moderator of the discussion panel later in the event. Scott’s topic for his talk was called, “Five Revolutionary Technologies Technical Communicators Can’t Afford To Ignore.”  If Joe Gollner went fast during his presentation, then Scott went at lightning speed, so my notes below are the highlights.

Scott started by telling us that translation is going to be an important part of automated content going forward. It’s important to understand that for the web, the World Wide Web (WWW) is equal to the “land of opportunity.” The WWW can reach a global market reaching new consumers. As American users, we forget that 96% of web users are not in the US. We don’t all speak English globally. In fact, less than 6% of the global population speaks English well, but don’t necessarily read or write it well.

Scott’s list of the five technologies the Tech Comm can’t ignore were as follows:

1) Automated Translation
Why would be need automated translation? We write for the *worldwide* web.  There are over 6000 languages in the world, so translation is a big deal for a global reach and global connection. We need to recognize that content is written for both machines and humans. Even though we write for both machines and humans, we need to write for machines first, as they are the “gatekeepers” of content, such as for searches. Everything goes through the machine first. We need to recognize that writing rules learned in elementary school are no longer sufficient for a world in which language science is needed.  We need to examine our content from the vantage point of a rules-processing engine and ensure it’s optimized for machine translation.

2) Automated Transcription
Automated transcription involves software that translates speech to text for machine use. Without transcription, content is locked and hidden from view. Transcription allows for better searchability of content.  Scott recommended Koemei as a good transcription software tool for video and general transcription, as it can help transform editable content into other languages.

3) Terminology Management
Terminology management controls words in a central place, namely the words used the most and used consistently for branding, products, etc. Terminology management is important for consistency as well as for regulatory reasons. This is an instance where seeking a global content strategist is needed to help standardize processes.  It’s best to adopt a terminology management system, such as Adobe partner and Scott’s suggestion, Acrolinx.

4) Adaptive content
Adaptive content is content that is structured and designed to adapt to the needs of your customer; it’s about substance of the content. Adaptive content adapts to the devices, e.g. laptops, GPS, and smartphones.  Customers are demanding exceptional experiences, so we need to meet their expectations, so it’s up to responsive designers to meet that challenge. Adaptive content makes it possible to publish to multiple platforms and devices.  It is content separated from formatting information. By allowing authors to focus on what they do best, adaptive content makes content findable and reuseable by others who need it. We need to rethink content, as the move to adaptive content involves work, but the ROI (return on investment) can be realized in months instead of years.

5) Component Content Management
Component content management systems are needed. They focus on the storing of content components that are used to assemble documents. Components can be in all sizes, and can be photos, video, and text. It’s about managing CONTENT not FILES.

Scott provided these slides as his example to show this:

ScottAbel_ExampleA ScottAbel_ExampleB

Structured content, combined with a component content management system, supports personalized content and  targeted marketing, which in turn increases response rates. In this end, this process can save money! The key is to remember that all customers are not the same! Reusing content without the “copy and paste” methods produce the best results. You can ensure that content is consistent by seeking a content strategist who understands content and is a technologist. Implement a component management system. Scott suggested checking out Astoria Software for a good component content management system. 

At this point, Scott’s talk had pretty much finished, but in answering audience questions, he pointed out that there’s a lot more than just these five technologies to watch. He suggested that we should look out for wireless electricity, flexible surfaces, more wireless devices, wearable computing, and augmented reality as well. He also said that in order to mature as a discipline, we need to be content craftspeople, content designers and content engineers. We need to leverage using content and code. We need to think more like engineers, and less like writers and editors. Even websites that are very localized still need to be written for global purposes to improve the English used for the native speakers as well. Controlled vocabulary helps all end users!

Scott covered a LOT of information in a short amount of time, and he set the tone for the rest of the session, as the presentations that followed repeated much of the same information. (This is a good thing, because then we know that the information is valid, coming from several experienced technical communicators!)

Scott posted on Twitter than his presentation was available on SlideShare, but I have it below.

And as always–Scott, if I misinterpreted or misquoted any of the information I summarized above, please let us know in the comments!

Posted in Uncategorized

Adobe Day @ Lavacon 2013 – Joe Gollner: The Changing Role of the Technical Communicator

The Flat Garden in the Japanese Garden, Portland Photo from the Portland Japanese Garden website.
The Flat Garden in the Japanese Garden, Portland
Photo from http://japanesegarden.com/learn-more/gardens/flat/

As I’m going backwards in my Adobe Day reviews, the second presentation of the day was by Joe Gollner. Joe is another prolific speaker in the world of technical communications, but I really hadn’t even heard him do a presentation before. I had seen him in last year’s Adobe Day at Lavacon on the panel discussion, but he was one of many voices in that discussion, so it was hard to determine what his presentations would be like.  I was pleased to find that his talk was as top caliber as the other presenters (which was no surprise, really).

It is fairly well known that Joe earned a degree in philosophy, and he’s known to be quite thoughtful in his presentations. I had the chance to chit chat with him after his talk, and found that his quiet demeanor was rather enjoyable–although in my “fangirl” moment, I don’t remember a thing we talked about. (Ha ha on me!)  So when I looked at the various gardens in Portland that I could use to describe Joe, I chose the Japanese Garden. On the Japanese Garden’s website, it describes the garden as a place in which “…the desired effect is to realize a sense of peace, harmony, and tranquility and to experience the feeling of being a part of nature. In a deep sense, the Japanese garden is a living reflection of the long history and traditional culture of Japan.” Similarly, Joe talked about technical communication in a zen-like way that the evolution of technical communication was a natural one that continues worldwide.

Joe’s presentation was about the changing role of the technical communicator within the integrated product lifecycle. He started the talk by asking the question of how do we deploy content to help with other aspects of business, and reach out to customers? His answer was that we need to adapt our conclusions. Joe mentioned Peter Drucker‘s book, The Practice of Management from 1954, in which Drucker spoke of  the drive towards specialized components with variety as the order of the day at that time. Drucker understood in 1954 that the global economy would require standardized parts with flexible and dynamic assembly. The global economy calls for continuous process improvement that is maximized, automated, and makes dynamically tailored products. Joe emphasized that there’s no escape from the need to standardize and automate content.

In today’s market, portability and processability is key.  Using XML to distribute content is central to the way business is conducted. It’s influential in technical interoperability, electronic data exchanges, social media integration, responsible web design, internet commerce, and supply chain automation. Thomas Friedman‘s book, The World is Flat, specifically focused on the levelling effects of XML. XML enabled supply chain automation, so it drove the ability to massively distribute manufacturing  and distribution of products.

XML changed the way world works. XML is not a secret!  To prove his point, Joe posted the following slide:

Gollner_example1Around those spokes, any business will go through the activities of governance, acquisition, delivery, and operation. We need to understand this applies to consumer products, complex systems, or data systems/big data. No trade-offs are allowed! Efficiency is measured as quality, cost, and speed. What this means for knowledge workers is that specialization is in order, and it does pose challenges in how we communicate. There are new and more challenging communication problems to be solved. Not only do we need to make technology understandable to users, but we need to make technology understandable at all in the first place.

Many companies need to understand for themselves what their own products do  so they understand what they truly are. But many companies use the “silo” model of creating content, and the problem with the silo model is that it’s old, tired and broken, and can’t keep up with modern issues. Joe showed us this chart:

Gollner_example2Joe pointed out that the details in this chart show that sometimes content “silos” and customer experience don’t align correctly. What can we, as content professionals, do to help fix this?

Joe Gollner taking notes during Val Swisher's talk.
Joe Gollner taking notes during Val Swisher’s talk.

Joe cited a case study that was done using Massively Integrated Systems (MSI), a market leading software company. It compared Agile versus Lean practices of MSI. Agile success led to general failure, because if Agile was embraced, then the company embarked on aggressive innovation, thus it ran straight into the complexity of their own product and of their customers’ environments . The company developed specialist departments, but these types of teams find it harder to communicate with each other. The groups didn’t understand each other’s language, goals, constraints, and approaches, and it showed. The roots of the Lean process were in Training within Industry (TWI), a World War II initiative to mobilize US industry. It was all about communication during Cold War engineering that were powered by these practices, but it dissipated in the 1980s. The Lean process worked better.

Joe’s conclusion was that current practices aren’t sustainable. Content is placed in the center of the integrated product lifecycle (see spoke diagram above).  Content is potential information, and is needed for effective information, processes, and products. There are many specializations to choose from as technical communication specialists. Joe asked the question, “Is adaption an option?”  His response was a definitive NO. He believes that competitive pressures make reintegrating the product lifecycle mandatory.  He gave the example of his daughter becoming a “cyberian” rather than a librarian, and she has a new job title of “meta-dor” due to this quickly changing world. Technical communicators will make themselves a visible part of the solution.

While I found Joe’s presentation informative, I actually have to disagree slightly with what he’s saying about becoming a specialist.  Because I’ve been in the job market fairly recently (and might be again soon due to my contract ending), I feel that while you can have a main specialty in tech comm, it’s better to be a multi-specialist. Joe had spoken about how the “silo” groups couldn’t speak each others’ language, and that’s because of specialization. By being a multi-specialist, this allows a technical communicator to be multi-lingual, in a manner of speaking.  Because I understand the nature of social media, content management, user interface design, and technical writing, I can fit into any of those positions as needed. Even in my current job as a “web publisher”, having those multiple “languages” and abilities served me well beyond knowing only content management. Understanding the other “languages” of those specialties–provided more technical communicators are also multi-specialists–will help to bring about that standardization of language needed between the groups. Perhaps it’s a more diplomatic or ambassadorial viewpoint on my part.

Still, I do agree with him that there is a need for standardization of language that needs to come about, and XML can be an important part of making that happen for better customer experience.

(Joe, if you are reading this, please feel free to correct or comment on my notes here in the comments below.)

Posted in Uncategorized

Adobe Day @Lavacon 2013 – Val Swisher Says It Starts With The Source

Ladds_1
Ladd’s Addition Rose Garden
Photo from http://www.rosegardenstore.org

Val Swisher was the next to last individual to speak at the Adobe Day at Lavacon 2013 event. For those who are regular readers of this blog, you know that my love for all things Val Swisher has no bounds. I’ve always been able to take her easy-to-digest information, and absorb it quickly into my brain, as well as relay her knowledge to others.  When I looked at Portland Gardens to compare her to, I chose Ladd’s Addition Rose Garden.  While it’s not as well-known (unlike Val, who is very well-known), this particular park, according to The Rose Garden Store,  was one of four rose gardens especially built from the Ladd estate, in which the design included these gardens coming together to form the points of a compass. I often think of Val as my compass, as she has never steered me wrong with her information or with the wisdom and fun that she’s shared with me one-on-one.

Val’s Adobe Day presentation centered on talking about source English terminology in a multi-channelled, global world, and how terminology affects structured authoring, translation and global mobile content. She started the talk by reminding us that historically, we’ve always created content, whether it’s been on cave walls, through stenography, through typewriters or eventually on word processors. In every instance, consistent terminology has been essential for structured authoring and content. Managing terminology is also essential for translation and for reuse.  She stated that prior attitudes used to be that the more complicated the writing was, the more “fancy” the product was. Today, that’s definitely not true.  She used the example that I’ve heard her use before, but it’s so simple itself that it’s a classic. Her example involves writing for a pet website. If multiple words meaning dog are used, there can be problem with reuse, because you can’t reuse content if you use different words.

Val_example_dog
Here’s the example Val showed.

Val pointed out that it would be an even worse situation if technological or medical terminology was used instead.

Val continued by saying that when it comes to  XML, reuse , and terminology, you cannot realize the gains of structured authoring if you’re not efficient with your words. Terminology is critically important to gain more opportunities.

ValSwisher
Val Swisher explaining how to approach content from a translation perspective.

Translation comes down to three elements– we’re trying to get better, cheaper, and faster translation output. We MUST use technology to push terminology and style/usage rules to content developers. In order to make it cheaper, we need fewer words, reused words, and reused sentences. It’s impossible for writers to know or even know to look up all term and usage rules. We MUST automate with technology. For example, “Hitting the button” is not translatable, but “Select OK” is fine!  She said, “Say the same thing the same way every time you say it.”

For better translation, translation quality needs to improve and meanings need to match in order for better machine translation to be a possibility. Bad translation comes from the source itself.  If the source information is problematic, then the translation will be problematic.  The best way to save money and time is to say the same thing, every time, using the same words, and use shorter sentences. For machine translation, don’t go over 24 words in a sentence.

Faster translation is seen as content that takes less time to translate, needs fewer in-country reviews, and gets to market more quickly. The key to delivering global mobile content is responsive design, global mobile apps, text selection is key, and terminology is the most important element. Val showed this example of how translation in responsive design isn’t working, where the Bosch websites are not exactly in synchronization:

The mobile website on the left looks nothing like the English language version on the right.
The mobile website on the left looks nothing like the English language version on the right.

The simpler the design is for the website–especially in mobile, the less you have to tweak it. This is especially true where consistent terminology is important, because consistency is needed for structured authoring. Creating truly faster, cheaper, and better translation enables a true global responsive design. This is not a simple task, as there is no such thing as simple, even when writing about complex concepts. Even if you think you’re not translating, your customers are, so the content needs to be very clear. The scary part of this is that some companies use Google Translate as their translation strategy, which is risky at best. To use something like Google Translate as the translation software, the content had better be tight, clear, and consistent.

One of the things I enjoy with Val Swisher’s presentations is that it all comes down to common sense, and she breaks it down into easy manageable parts for those of us–like me–who might not have thought about the context of language for structured authoring, and the consequences for not strategizing content to include translation considerations.

I highly recommend checking out Val’s blog for other great insights.

(As always, Val–if you’d like to add or correct anything here, please do in the comments below!)