This month, I was fortunate to attend the Adobe Tech Comm Enterprise Summit, a free conference on the latest trends in technical communication, held at the Adobe facility, in Boston, MA. It was a full and lively day, complete with informative presentations on trends in technical communication, from various thought leaders on structured authoring, including Scott Abel, CEO, from The Content Wrangler, Inc., and Max Hoffman, from Globalization Partners International, Inc. Others presenters included Adobe’s own Kapil Verma, Ankur Jain, and Tom Aldous, followed by a detailed case-study on how to leverage Adobe’s Technical Communication Suite 3.5 , from Accenture’s Rick Thompson.
Technical Communicators, as Content Management Consultants
As described in my earlier post, Scott Abel’s keynote suggested that technical communicators are now more management consultants for content, as opposed to creators of content. Working alongside product management, Abel called upon technical communicators to continue breaking down the cylos within their respective organizations, with the objective of optimizing every part of the content delivery process. The end result, according to Abel, is re-usable content, developed for multiple delivery channels, audiences, formats, and languages.
Key Trends in Technical Communication Today
Adobe’s Kapil Verma described key trends in technical communication
today, driving the evolution of Adobe’s Technical Communication Suite 3.5:
- Globalization, opening up new markets, in
- Multiple devices, requiring multi-screen, multi-channel
- User-generated content & democratization of
- Increasing demand for rich media
- Increasing demand for highly personalized content
Later that day, Thomas Aldous made a strong case that the
Adobe Tech Comm Suite, which includes both unstructured and structured
authoring versions of FrameMaker 10.0, sets technical communicators up for long-term success, as market requirements continue to evolve.
Structured Authoring: Reasons for Making the Change
Verma provided helpful guidelines, for when making the
change to structured authoring may make the most sense. Structured authoring
may be suitable for your organization, Verma advised, when you’ll be…
- Translating doc into multiple languages
- Transfering documentation, between systems
- Managing dispersed content production
- Creating and maintaining a large volume of
- Making frequent documentation updates
- Supporting multiple production variants
- Publishing multiple formats
- Following a standard documentation structure
Verma followed up these recommendation, with a meaty analysis, on how to derive the highest ROI from your migration to structured authoring.
In my next post, be on the lookout for highlights, from Ankur Jain’s presentation, on developing an enterprise social collaboration strategy.
I haven’t used the structured version of FrameMaker, or Robohelp in a few help authoring assignments, so in the comments, please feel free to add your experiences with these tools, or comparisons with other authoring tools. Past versions of FrameMaker (up thru version 9.0) have spoiled me for all other desktop publishing tools. How has making the transition to version 10.0 been for you?
And oh, before I sign off, a very Happy 25th Birthday, FrameMaker. Thanks to Adobe and all the presenters for their time and for the generous knowledge share.