Embed Size (px)
DESCRIPTION
In this webcast recording, Sarah O'Keefe discusses how content initiatives are putting new demands on technical communication—improving customer experience, building interactive documents, including advanced visualizations, integrated translations, and more. To meet these requirements, we must increase the velocity of technical communication. That means stripping out inefficiency and creating content development workflows that eliminate wasted time. Most publishing systems are ill-equipped for flexible, fast, and changeable production. Instead, they are intended to support a manufacturing process, in which the result is static (like print or PDF). For today's workflows, this approach is not good enough. We must increase our velocity so that we can support the requirements that are coming.
Citation preview
Before we begin…
❖ Everyone is muted except for the presenter and the moderator.
❖ Please ask your questions through the Questions area in the webcast interface.
❖ The presentation is being recorded.
“You want it when?!?”
Flickr: ken_from_md
Sarah O’Keefe @sarahokeefe
Scriptorium Publishing
Sarah O’Keefe, @sarahokeefe
❖ Founder and president, Scriptorium Publishing, www.scriptorium.com, North Carolina
❖ Coauthor with Alan Pringle of Content Strategy 101
❖ Interested in intersection of content, publishing, and technology
Flickr: mytmossWe need velocity.
Content strategy Support the
organization’s business goals using information
and information products.
Flickr: grendelkhan
Velocity and content strategy…
Know the business
!
Align with business goals
!
!
Style guides and terminology
!
!
!
Voice and tone
!
!
!
!
Production systems
Flickr: brittanyg
!
!
!
!
!
Intelligent content
Flickr: brittanyg
!
!
!
!
!
!
Integration
Know the business Align with business goals Style guides and terminology Voice and tone Production systems Intelligent content Integration
How do we make it happen?
Flickr: kirinqueen
Operations need to be impeccable.
Authoring velocityFlickr: pedrosz
Reduce, reuse, recycle
Editing velocity
Flickr: nicokaiser
Controlled language software
Production velocity
Flickr: dingopup
Production system must automate formatting.
Flickr: WI Department of Natural Resources, mstharpe, daysofthundr46
Distribution velocity
Localization velocity
Flickr: furphotos
Good source content Machine translation Automated formatting (again)
Flickr: furphotos
Global content strategy
should be redundant.
flickr: dtaylorcreative
Globalization drives content strategy.
flickr: titushageman
flickr: tanyadurrant
Efficient localization is a basic prerequisite.
flickr: tanyadurrant
What drives efficient localization?
flickr: tambako
HINT: It’s not the service provider.
flickr: tanyadurrant
It’s the quality of the input.
Localization: just along for the ride.
flickr: pmarkham
A computer can do morethan a typewriter.
Low-quality source content = inefficient localization
flickr: dominicspic
Image: NASA
In a multilingual workflow, inefficiency = death.
Image: NASA
In a monolingual workflow, inefficiency = slow death.
We cannot survive unless we evolve. Quickly.
Content has never been for the faint of heart…
Flickr: jlascar
We must adapt to changes…
Flickr: Marie Hale
Prioritize
Flickr: beleaveme
The old way is not going to work.
Flickr: nostri-imago
Flickr: ullisandersson
One last thing…
Questions?
