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!
As I had mentioned in my first post about Adobe Day, there were several well-known tech comm authorities presenting, and Scott Abel was the first presenter. Scott is the founder and CEO of The Content Wrangler, Inc., and he has a great Twitter feed and blog, if you haven’t read them. Scott’s presentation was called, “More than Ever, Why We Need to Create Structured Content.” If you’ve never read Scott or seen Scott speak, he is a force to be reckoned with, as he’s definitely got strong opinions from his experiences, and he’s not afraid of letting you know what he thinks.
Scott explained that structure is in everything we do–including in nature–so it would make sense that content needs to be structured as well. Structure formalizes a content model and provides authoring guidance. It can enhance the usability of content, providing visual cues and is the foundation for automatic delivery of content through syndication. Structure makes it possible to efficiently publish to multiple channels, outputs and devices from a single source, making it a critical component of transactional content and making business automation process possible. By providing structure, it is possible to adapt content and leverage responsive design techniques. Structure also allows us to leverage the power of content management systems to deliver content dynamically and increasingly in real time. By creating structured content, it is possible for us to move past “persona-ized content” and facilitate innovative reuse of content in known sets of related information as well as in the unknown needs as well.
Scott quoted author and technologist Guy Kawasaki by saying that innovators must allow time for the majority to catch up; new ideas take time to filter through. He followed up with the question, “How much time does it take to adopt?” He answered his question by explaining that technological innovation is getting faster, and the technological adoption rate is becoming shorter, which is good news. However, how long to adopt structured content? He explained that it’s actually not a new idea–the idea started in 1963! It started with the Sequential Thematic Organization of Publications created in the airline industry to standardize airline manuals.
With that in mind, Scott presented that the question now is to figure out where are we today with structured content. Scott concluded that right now, one of the major challenges is that old ideas are getting in the way because many technical communicators are still stuck with design concepts created in the print paradigm. Other major challenges include the lack of knowledge and experiences, writers making manual updates, the lack of human resource support, and making tools work with configurable content. He did point out that lots of reuse content is going on! His point was that the tools work, but it’s the people and processes are the problem, as Sarah O’Keefe paraphrased him on Twitter.
So when asked why we should be technical communicators, Scott’s response was that as technical communicators, we know how to create structured content. Knowing how to create structured content increases our value and makes us marketable. “Our professional needs to change whether we like it or not,” he concluded, to keep up with these technological changes.
Much of what Scott talked about in his presentation was echoed again in the panel discussion later in the morning. Scott had provided a few examples during the presentation which showed what unstructured content versus structured content looked like, and it was very clear what the differences were. As technical writers, as Scott said, we understand the importance of structured content and how reused content can be used effectively. Those who don’t have that mindset tend to repeat the same processes and make more work for themselves, wasting time and money for a company. We have value, and we need to promote our skills in creating this kind of content organization. I think technical communicators take this ability for granted, and by being proactive in showing how we can help create efficient and structured content, we can add value not only to ourselves, but also provide on a larger scale a true cost-saving service to our respective companies and clients.
(Scott–if you are reading this, please feel free to clarify anything that I’ve written if I didn’t interpret it quite correctly in the comments.)
You must be logged in to post a comment.