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.

1. 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.

2. “You
want
it
when?!?”
Flickr: ken_from_md
Sarah O’Keefe
@sarahokeefe
Scriptorium Publishing

3. 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

4. Flickr: mytmossWe
need
velocity.

5. Content
strategy
Support
the
organization’s
business
goals
using
information
and
information
products.

6. Flickr: grendelkhan
Velocity
and
content
strategy…

7. Know
the
business

8. !
Align
with
business
goals

9. !
!
Style
guides
and
terminology

10. !
!
!
Voice
and
tone

11. !
!
!
!
Production
systems

12. Flickr: brittanyg
!
!
!
!
!
Intelligent
content

13. Flickr: brittanyg
!
!
!
!
!
!
Integration

14. Know
the
business
Align
with
business
goals
Style
guides
and
terminology
Voice
and
tone
Production
systems
Intelligent
content
Integration

15. How
do
we
make
it
happen?

16. Flickr: kirinqueen
Operations
need
to
be
impeccable.

17. Authoring
velocity
Flickr: pedrosz

18. Reduce,
reuse,
recycle

19. Editing
velocity
Flickr: nicokaiser

20. Controlled
language
software

21. Production
velocity
Flickr: dingopup

22. Production
system
must
automate
formatting.

23. Flickr: WI Department of Natural
Resources, mstharpe, daysofthundr46
Distribution
velocity

24. Localization
velocity
Flickr: furphotos

25. Good
source
content
Machine
translation
Automated
formatting
(again)
Flickr: furphotos

26. Global
content
strategy
should
be
redundant.flickr: dtaylorcreative

27. Globalization
drives
content
strategy.
flickr: titushageman

28. flickr: tanyadurrant
Efficient
localization
is
a
basic
prerequisite.

29. flickr: tanyadurrant
What
drives
efficient
localization?

30. flickr: tambako
HINT:
It’s
not
the
service
provider.

31. flickr: tanyadurrant
It’s
the
quality
of
the
input.

32. Localization:
just
along
for
the
ride.
flickr: pmarkham

33. A
computer
can
do
more
than
a
typewriter.

34. Low-quality
source
content
=
inefficient
localization
flickr: dominicspic

35. Image: NASA
In
a
multilingual
workflow,
inefficiency
=
death.

36. Image: NASA
In
a
monolingual
workflow,
inefficiency
=
slow
death.

37. We
cannot
survive
unless
we
evolve.
Quickly.

38. Content
has
never
been
for
the
faint
of
heart…
Flickr: jlascar

39. We
must
adapt
to
changes…
Flickr: Marie Hale

40. Prioritize
Flickr: beleaveme

41. The
old
way
is
not
going
to
work.
Flickr: nostri-imago

42. Flickr: ullisandersson
One
last
thing…

43. Questions?