Sarah O’Keefe, Scriptorium Publishing




                                          background image
                     ...
!   Founder and president, Scriptorium
    Publishing
!   Content strategy for
    tech comm
!   Interested in collision o...
!   My ID: @sarahokeefe
!   Scriptorium: @ScriptoriumTech
!   #techcomm or #dita may be appropriate
!   Everyone is muted except for the
    presenter
!   Please ask your questions through the
    Questions area in the web...
!   Business case examples (with numbers)
    !   YMMV
    !   IANAL
    !   WYSIOO
!   Big-picture musings on other issue...
Flickr: iancarroll
!   Estimate 30–50 percent of total
    localization cost is desktop publishing
!   With XML-based publishing, you can
   ...
Flickr: a-m-photo
!   Baseline assumption:
    !   DITA = increased content reuse!
!   10,000 topics
!   Development cost: $200 per topic
  ...
!   Calculate cost of updates in multiple
    documents
!   Consider error rates
!   Don’t forget the mental health toll
!   Software error messages
!   Product specifications in product
    database and datasheets
!   Product descriptions
!   ...
!   Improve collaboration among writers
!   Develop and enforce consistent style
    standards
“You should not implement XML as a
substitute for creating a style guide.”
“Structure is no substitute for
management.”
Flickr: kevenlaw
!   Share topics
!   Communicate updates
!   Minimize content “ownership” issues
!   Smooth out inevitable conflicts
!   Co...
Photo: www.christianholmer.com
!   Multiple conditional dimensions
    (platform, customer, audience, product)
!   Huge number of possible variations
!  ...
!   Eliminate redundancy
!   More targeted information
!   Meet customer requirement for
    personalized documentation
! ...
!   40 variations of a deliverable
!   Configure and publish one at a time:
    !   1 hour per variant
    !   40 hours of ...
!   Tagging work does not change for static
    versus dynamic publishing
!   Programming effort to enable dynamic
    pub...
Photo: Rachel Houghton
flickr: uhop
Flickr: chris_radcliff
!   If product revenue is $1M per year, then
    each week of availability is worth about
    $20K in revenue.
!   Acceler...
Flickr: ccharmon
David Kelly
                                         Senior Technical Consultant




www.scriptorium.com/blog/2010/09/the-...
!   Source content in XML
!   Transform to accommodate
    user-generated content
!   Use metadata to support unified search
!   Topic-based rather than deliverable-
    based publishing
!   Incremental deliveries for localization
!   Content deli...
!   Measure how topics are used
!   Act on information about:
    !   Popular topics
    !   Unpopular topics
    !   Unsu...
!   Source: “The state of structure in
    technical communication,” 2009.
    www.scriptorium.com/blog/2010/05/
    the-s...
!   Localization
!   Increased reuse
!   Support for complex conditionality
!   Faster time to market
!   Support for new ...
!   Software integration issues
!   Complex output/formatting requirements
!   Inconsistent source files
!   Source files th...
!   Dysfunctional teams
!   Information hoarding during
    implementation
!   Tool-specific blinders
!   Using XML/DITA to...
!   Improve communication
!   Improve collaboration
!   Build trust
!   Provide project roadmap early
!   Do not reward this behavior
    !   Implicitly
    !   Explicitly
!   Avoid communication bottlenecks
!   Document pro...
!   Ask for open minds
!   Consider new features, not just cloning
    old features
!   Try out a variety of XML tools
!   Identify best and worst features of
    current workflow
!   Identify new requirements that can’t be
    met with curre...
Topics                2,000+
Writers                  10+
Supported languages       3+
Deliverable formats       2+




  ...
!   Researching adoption rates, issues, tools
!   Open until March 1
!   Participants get free results
!   http://www.surv...
!   February 8: Attractive DITA output (it IS
    possible)!
!   March: Trends in technical
    communication, 2011
!   Ap...
!   Sarah O’Keefe
!   www.scriptorium.com
!   okeefe@scriptorium.com
!   @sarahokeefe
Webcast: Calculating the ROI for XML and DITA topic-based authoring
Webcast: Calculating the ROI for XML and DITA topic-based authoring
Upcoming SlideShare
Loading in …5
×

Webcast: Calculating the ROI for XML and DITA topic-based authoring

1,741 views

Published on

n this webcast, Sarah O'Keefe discusses how to calculate the return on investment of an XML/DITA implementation for technical content.

If you are considering XML and DITA, but are trying to figure out whether you can justify the cost and effort, this session is for you. You'll learn how to communicate the rationale for XML in terms that management understands.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,741
On SlideShare
0
From Embeds
0
Number of Embeds
260
Actions
Shares
0
Downloads
15
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Webcast: Calculating the ROI for XML and DITA topic-based authoring

  1. 1. Sarah O’Keefe, Scriptorium Publishing background image flickr: thelastminute
  2. 2. ! Founder and president, Scriptorium Publishing ! Content strategy for tech comm ! Interested in collision of content, publishing, and technology
  3. 3. ! My ID: @sarahokeefe ! Scriptorium: @ScriptoriumTech ! #techcomm or #dita may be appropriate
  4. 4. ! Everyone is muted except for the presenter ! Please ask your questions through the Questions area in the webcast interface ! The presentation is being recorded; attendees do not appear in the recording
  5. 5. ! Business case examples (with numbers) ! YMMV ! IANAL ! WYSIOO ! Big-picture musings on other issues (without numbers)
  6. 6. Flickr: iancarroll
  7. 7. ! Estimate 30–50 percent of total localization cost is desktop publishing ! With XML-based publishing, you can squeeze that cost to under 10 percent ! Cost savings: $20K–$40K per $100K in localization cost
  8. 8. Flickr: a-m-photo
  9. 9. ! Baseline assumption: ! DITA = increased content reuse! ! 10,000 topics ! Development cost: $200 per topic (4!hours x $50) ! 5% more content reuse = $100,000 in savings (and additional savings in localization)
  10. 10. ! Calculate cost of updates in multiple documents ! Consider error rates ! Don’t forget the mental health toll
  11. 11. ! Software error messages ! Product specifications in product database and datasheets ! Product descriptions ! Training ! Tech support
  12. 12. ! Improve collaboration among writers ! Develop and enforce consistent style standards
  13. 13. “You should not implement XML as a substitute for creating a style guide.”
  14. 14. “Structure is no substitute for management.”
  15. 15. Flickr: kevenlaw
  16. 16. ! Share topics ! Communicate updates ! Minimize content “ownership” issues ! Smooth out inevitable conflicts ! Cooperate on assignments
  17. 17. Photo: www.christianholmer.com
  18. 18. ! Multiple conditional dimensions (platform, customer, audience, product) ! Huge number of possible variations ! Dynamic versioning instead of static publishing of a limited number of variations
  19. 19. ! Eliminate redundancy ! More targeted information ! Meet customer requirement for personalized documentation ! Enable more versioning than supported in current toolset ! Enable dynamic publishing
  20. 20. ! 40 variations of a deliverable ! Configure and publish one at a time: ! 1 hour per variant ! 40 hours of work per deliverable, per release ($2,000) ! Dynamic publishing: publish once
  21. 21. ! Tagging work does not change for static versus dynamic publishing ! Programming effort to enable dynamic publishing included in implementation cost
  22. 22. Photo: Rachel Houghton
  23. 23. flickr: uhop
  24. 24. Flickr: chris_radcliff
  25. 25. ! If product revenue is $1M per year, then each week of availability is worth about $20K in revenue. ! Accelerate delivery of first language ! Reduce delays in shipping localized versions
  26. 26. Flickr: ccharmon
  27. 27. David Kelly Senior Technical Consultant www.scriptorium.com/blog/2010/09/the-promise-of-xml-publishing.html
  28. 28. ! Source content in XML ! Transform to accommodate user-generated content ! Use metadata to support unified search
  29. 29. ! Topic-based rather than deliverable- based publishing ! Incremental deliveries for localization ! Content deliveries decoupled from software deliveries
  30. 30. ! Measure how topics are used ! Act on information about: ! Popular topics ! Unpopular topics ! Unsuccessful searches ! Topics with lots of comments
  31. 31. ! Source: “The state of structure in technical communication,” 2009. www.scriptorium.com/blog/2010/05/ the-state-of-structure-in-technical- communication.html
  32. 32. ! Localization ! Increased reuse ! Support for complex conditionality ! Faster time to market ! Support for new publishing architecture
  33. 33. ! Software integration issues ! Complex output/formatting requirements ! Inconsistent source files ! Source files that are not topic-based ! Content management system ! People
  34. 34. ! Dysfunctional teams ! Information hoarding during implementation ! Tool-specific blinders ! Using XML/DITA to clone an existing, problematic workflow
  35. 35. ! Improve communication ! Improve collaboration ! Build trust ! Provide project roadmap early
  36. 36. ! Do not reward this behavior ! Implicitly ! Explicitly ! Avoid communication bottlenecks ! Document project decisions ! Distribute project information
  37. 37. ! Ask for open minds ! Consider new features, not just cloning old features ! Try out a variety of XML tools
  38. 38. ! Identify best and worst features of current workflow ! Identify new requirements that can’t be met with current workflow ! Understand how new workflow affects authors
  39. 39. Topics 2,000+ Writers 10+ Supported languages 3+ Deliverable formats 2+ flickr: booleansplit
  40. 40. ! Researching adoption rates, issues, tools ! Open until March 1 ! Participants get free results ! http://www.surveymonkey.com/s/ structure ! Please participate, and tell your friends!
  41. 41. ! February 8: Attractive DITA output (it IS possible)! ! March: Trends in technical communication, 2011 ! April: Structured authoring survey results
  42. 42. ! Sarah O’Keefe ! www.scriptorium.com ! okeefe@scriptorium.com ! @sarahokeefe

×