Posted in Uncategorized

If Tech Comm had its own Coachella, how would it be done?

coachella[WARNING: this is a long post, but jam-packed with information!]

Every industry has its own rock stars. Those are the people who have lived, spoken, and written about topics in a particular field. The information and perspective they provide are considered out of this world.

As technical communicators, we are fortunate that we have lots of tech comm rock stars among us.  There are several events that happen over the course of a year that allow several of those rock stars to come to one place to dazzle us with their brilliance, and we are the better for it.

Among the ultimate organizers for such events is Adobe. For the 2013 STC Summit’s “Adobe Day,” they put together a lineup that would make any tech comm groupie squeal with joy to be able to hear some of the leading minds and pacesetters in technical communications. The best part is that, as always, the events are not product sales pitches, but truly a compilation of thought leadership.

The speakers included headliner Charles Corfield, the inventor and “father” of Framemaker, content strategist Rahel Anne Baillie, online learning educator John Daigle and content strategist Mark Lewis. I’ll be writing more about each of their talks soon.

For this post, I’m going to start with the panel discussion that was at the end of the event first. The panel discussion wrapped up Adobe Day well,  and I’m using it first as I think it will to help set the tone for the next blog posts about the event.

ScottAbel
Scott Abel, “The Content Wrangler” asks the panel a question.

Scott Abel, “The Content Wrangler,” served as our trusty moderator for the discussion titled, “The Changing Role of Technical Communication Professionals–Looking at the Decade Ahead.” This was a similar theme to the Lavacon Adobe Day, but with a different set of panelists, the attendees were sure to get a different perspective this time around.

The panelists for this talk included:

panel
L to R: Joe Welinske, Ray Gallon, Sarah O’Keefe,
Bernard Aschwanden and Kevin Siegel

Scott started the panel out with the questions, “What do you think will be going on in technical communication in the next 10 years? What are the necessary things for tech comm going forward?”

Kevin Siegel replied first, saying that technical communicators need to learn how to write content so that content can be consumed quickly, as the average attention span of online consumers is about fifteen seconds, and the mobile is the most viable means of getting content out, so think mobile!

Bernard Aschwanden felt that networking was most important going forward. Face-to-face discussions–not social media discussions–with subject matter experts, your audience, and anyone else who is going to consume your content will help you learn what is required for your content. He stressed that ideas and tools are constantly changing, and technical communicators need to be able to adapt. Bernard continued by saying, “No one wants to read what you write.” He emphasized that readers read the output of tech writers because they have to, so tech writers should making information easier to find and easier to read.

Sarah O’Keefe emphasized that the biggest skill gap in technical communication is how content and information is relevant to business. Business needs content because of…why? The most important skills required in Sarah’s eyes bring relevance–like ROI (return on investment)–so technical communicators need to learn how to write business cases for tools and other resources to be able to deliver effective products and outputs.

Ray Gallon agreed with Sarah’s point of view, and also emphasized Bernard’s point about adaptability.  Ray stressed that technical communicators have a unique view, so using that special view plus being adaptable will help technical communications go forward. He believes that software is driving content and making decisions, so we must create it on how software creates things today.

The second question that Scott posed asked, “What is the global impact with tech comm?”

Ray responded first by declaring that all technical communicators should have an understanding of at least three languages, as knowing three languages lends to their global credibility.  Since I know that localization is a big emphasis these days in technical communications, Ray’s comment made a lot of sense to me.

Joe felt that in ten years, technical communicators will still be the same people, but traditional tech comm documentation will be less relevant, and QA (quality assurance testing) of documentation will be more prevalent. He emphasized that by testing the documentation, it allows us to truly understand what part of content is not being used, and what part really matters.  He also agreed with Charles Corfield (more on his talk in a future post) that voice and multi-screen publishing will be important going forward. He stressed that access to multiple devices are needed as you write, especially to test usability and “Google-ability.” He felt that a technical publications department needed at least three smart phones and three tablets for testing content on commonly used mobile devices as emulators don’t work as well. Real devices, including the ones you don’t like, are needed to see how well your content works.

The next question posed was, “Have you had an ‘ah-hah’ moment with things going forward?”

Scott chimed in his own response, saying that he thinks looking at internationalized English is important going forward. He felt that having a controlled vocabulary and other English language standardization will allow content to be created in form of English that machines can understand.

Kevin thinks localization is highly important, backing this claim up with the fact that the most popular article in his company’s weekly newsletter is about localization. He felt that soon enough, we’ll be converting books to other languages more quickly and easily.

Bernard’s “ah-hah” moment was when he realized that people are the key, not products or tools. He felt that typing was dying, and that technology is leap-frogging. He talked about how younger people today commonly connect and communicate without face-to-face person contact, not caring about political correctness and preferring to connect with those who are like-minded. He said, “Teens have few barriers with race, gender or sexual orientation. We must get over our own barriers to address needs of future consumers.” He emphasized that people are needed in order to work collectively, we need to be able to connect effectively with people.

Sarah’s “ah-hah” realization involves the “rise of the machine” and the machine integration of content.

Ray concurred with Sarah, pointing to Google Glass as an example, declaring that Google Glass is the “caveman” version of the next generation of machines that technical communicators with encounter.

Joe’s “ah-hah” was understanding that mobile apps are not interested in being help documentation. Instead, mobile apps involve how to have product integrated in everyday use.

At this point, the floor was opened to attendees who had questions. The first audience question asked if technical communicators need to be the drivers of change and adaptability. Ray answered for the entire panel with a resounding, “YES!”

The next question asked if there was any empirical data to back up the statements made in this panel discussion. Sarah answered that that her responses were derived from the anecdotal data from client requests. Joe said he based his responses on the QA testing done  he’s done over time, and stressed knowing one’s audience. Bernard agreed with both these responses.

The last question asked about relevance–is this a PR problem for technical communication, or is this more of a marketing communication issue? Scott piped in that marketing communication is meant to dazzles customers, but technical communication provides the real customer experience, so in essense, tech comm IS marketing!  Customer service is central.

Ray felt that content is permeable and will get more so over time. Various departments will disappear due to unified content strategy; things will get blurred and content will get unified, so tech comm will be an integral part of teams.

Bernard reminded us that, “We must get to know the ‘language’ of our audience in order to stay relevant.” Scott reiterated that idea, stating that globalization is going to be really key going forward, which will affect ROI.

Joe had the last word, stressing that how we present what we do is going to make a difference!

As you can see, it was quite the lively conversation, and the ideas presented here were more concentrated on localization, technology and networking with people going forward. It’s amazing to me to hear a different perspective to the similar questions asked at the Lavacon Adobe Day panel just seven months ago! It does prove to me that adaptability and understanding the bottom line of what content is needed, and how to disseminate content with ever-changing technology is key going forward.

Thanks to all the panel participants for your insights! (Also thanks to Maxwell Hoffman, as I used both my notes and his notes on Twitter to recall this panel discussion.)

To any of the panel participants–if I misquoted or mis-paraphrased you, please feel free to comment below to correct me!

So, this was the closing act of our tech comm “Coachella?” Impressive! Stay tuned to learn more about the main acts of this gig!

Posted in Uncategorized

Adobe Day at LavaCon 2012 Roundup!

This post is just a quick summary of the Adobe Day at LavaCon 2012 series from this past week. As you see, there was so much information that it took six posts to try to summarize the event!

Being in Portland, Oregon was great. It was my first trip there, and being a native Easterner, my thoughts pushed me to that pioneer spirit of moving westward in this country. Once there, I saw a hip, young, modern city, continuing to look towards the future.  The information I gathered at Adobe Day was general information that was endorsement-free, and practical information that I can use going forward as a technical communicator, and that by sharing it, I hope that others in the field will equally take on that pioneering spirit to advance what technical communications is all about, and bring the field to the next level.

To roundup the series, please go to these posts to get the full story of this great event. I hope to go to more events like this in the future!

As I said, I really enjoyed the event, and learned so much, and enjoyed not only listening to all the speakers, but also enjoyed so many people who are renowned enthusiasts and specialists in the technical communications field and talking “shop”. I rarely get to do that at home (although it does help to have an e-learning developer in the house who understands me), so this was a chance for me to learn from those who have been doing this for a while and not only have seen the changes, but are part of the movement to make changes going forward.

I hope you’ve enjoyed this series of blog posts. I still have many more to come–at least one more that is inspired by my trip out to Portland, and I look forward to bringing more curated content and commentary to you!

The autograph from my copy of
Sarah O’Keefe’s book,
Content Strategy 101.
Awesome!
Posted in Uncategorized

Adobe Day Presentations: Part III – Joe Welinske and Multi-Screen Help Authoring

Joe Welinske
President of Writers UA

Joe Welinske of Writers UA followed Sarah O’Keefe’s presentation on Adobe Day. I was especially interested in hearing what he had to say, because the topic of his presentation was  about “Multi-screen Help Authoring–How to Deal With the Explosion in Device Sizes.” Anyone who’s read this blog before knows that I’m very much into the mobile revolution, and while I’m usually talking about m-learning more specifically, mobile goes beyond learning, and using mobile in technical communications is connected to m-learning in many ways.

Joe explained that the device population keeps growing! Smartphones and desktops are changing; the sizes between smartphone and tablet devices, whether they be iOS, Windows or Android devices truly vary. The same content needs to be displayed on everything from large monitors to laptops to tablets to GPS to small phones–there are dozens of choices! How do you design a UI (user interface) for all these variations?

Joe explained that different devices have different dimensions, different operating systems, different user interfaces elements…lots of variations to contend with when creating content. He suggested that a “graceful, efficient adjustment is needed,” namely matching the amount of content and the type of content with a device without crafting solutions for each.  He contended that responsive design the key as it allowed for adaptive content. Responsive design would allow flexibility for different environments.

Joe mentioned that Scott Abel has touched upon this during his presentation, but Scott later clarified for me on Twitter, by saying, “That’s one way, although I question whether it is the best way…Lesson: Adapt content first, design second. Wrong content, right design = #fail.”

Joe continued by pointing out that one way to accomplish this objective included using HTML5/CSS3, tagging all objects in source code, create device-type style sheets, and including media queries in source. The end result would be a single-source content file that looks and works well on different devices. To prove his point,  Joe demonstrated how same source content looked on different devices, specifically the iPad versus iPhone in this example. Joe also showed an example of how he divides the devices by “buckets” when creating his style sheets into categories such as 10″ tablets, desktops, phones, etc. He recommended using a “parent” style sheet, then fine tuning with a device style sheet for each device type. This would help create a graceful adaptation using HTML/CSS and query to allow your content to flow automatically and intelligently. From that point going forward, a technical communicator can consider making mobile the starting point and expanding from there. Joe’s last point was that a small percentage of people from traditional technical communications are involved in mobile projects but the user experience and design skills are actually similar.

I agree with Joe that designing for mobile really does use many of the same skills as traditional design methods, but it does take a little extra time to lay out the thought process and structure needed to make the content be delivered from a single-source to multiple types of mobile devices. It’s a little tricky, but with some careful thought, it’s not really as complicated as it could be. By using single-sourcing and customizing style sheets, multiple output of content can easily be attained.  I strongly agree as well that this is the mentality that people need to adopt, whether involved in technical communications or e-learning/m-learning now.  I think this opened the eyes of many attendees in the room. Mobile really is an important consideration now in content output!

Next: Adobe Day Presentations – Part IV: Val Swisher asks, “Are You Global Ready?”