SlideShare a Scribd company logo
Sarah O’Keefe, Scriptorium Publishing




                                          background image
                                        flickr: thelastminute
!   Founder and president, Scriptorium
    Publishing
!   Content strategy for
    tech comm
!   Interested in collision of
    content, publishing, and
    technology
!   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 webcast interface
!   The presentation is being recorded;
    attendees do not appear in the
    recording
!   Business case examples (with numbers)
    !   YMMV
    !   IANAL
    !   WYSIOO
!   Big-picture musings on other issues
    (without numbers)
Flickr: iancarroll
!   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
Flickr: a-m-photo
!   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)
!   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
!   Training
!   Tech support
!   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
!   Cooperate on assignments
Photo: www.christianholmer.com
!   Multiple conditional dimensions
    (platform, customer, audience, product)
!   Huge number of possible variations
!   Dynamic versioning instead of static
    publishing of a limited number of
    variations
!   Eliminate redundancy
!   More targeted information
!   Meet customer requirement for
    personalized documentation
!   Enable more versioning than supported
    in current toolset
!   Enable dynamic publishing
!   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
!   Tagging work does not change for static
    versus dynamic publishing
!   Programming effort to enable dynamic
    publishing included in implementation
    cost
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.
!   Accelerate delivery of first language
!   Reduce delays in shipping localized
    versions
Flickr: ccharmon
David Kelly
                                         Senior Technical Consultant




www.scriptorium.com/blog/2010/09/the-promise-of-xml-publishing.html
!   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 deliveries decoupled from
    software deliveries
!   Measure how topics are used
!   Act on information about:
    !   Popular topics
    !   Unpopular topics
    !   Unsuccessful searches
    !   Topics with lots of comments
!   Source: “The state of structure in
    technical communication,” 2009.
    www.scriptorium.com/blog/2010/05/
    the-state-of-structure-in-technical-
    communication.html
!   Localization
!   Increased reuse
!   Support for complex conditionality
!   Faster time to market
!   Support for new publishing architecture
!   Software integration issues
!   Complex output/formatting requirements
!   Inconsistent source files
!   Source files that are not topic-based
!   Content management system
!   People
Webcast: Calculating the ROI for XML and DITA topic-based authoring
!   Dysfunctional teams
!   Information hoarding during
    implementation
!   Tool-specific blinders
!   Using XML/DITA to clone an existing,
    problematic workflow
!   Improve communication
!   Improve collaboration
!   Build trust
!   Provide project roadmap early
!   Do not reward this behavior
    !   Implicitly
    !   Explicitly
!   Avoid communication bottlenecks
!   Document project decisions
!   Distribute project information
!   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 current workflow
!   Understand how new workflow affects
    authors
Topics                2,000+
Writers                  10+
Supported languages       3+
Deliverable formats       2+




                               flickr: booleansplit
!   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!
!   February 8: Attractive DITA output (it IS
    possible)!
!   March: Trends in technical
    communication, 2011
!   April: Structured authoring survey
    results
Webcast: Calculating the ROI for XML and DITA topic-based authoring
!   Sarah O’Keefe
!   www.scriptorium.com
!   okeefe@scriptorium.com
!   @sarahokeefe

More Related Content

PDF
Calculating the ROI for XML and DITA topic-based authoring
PDF
Back to Basics: Getting the Content Essentials Right
PDF
Designing Narrative Content Workshop
PPT
Painless XML Authoring?: How DITA Simplifies XML
PPTX
Need to reboot your content creation strategy? Start with "No"
PDF
Crossmedia Workflows
PDF
Partner Day at DrupalCon Sydney
Calculating the ROI for XML and DITA topic-based authoring
Back to Basics: Getting the Content Essentials Right
Designing Narrative Content Workshop
Painless XML Authoring?: How DITA Simplifies XML
Need to reboot your content creation strategy? Start with "No"
Crossmedia Workflows
Partner Day at DrupalCon Sydney

Similar to Webcast: Calculating the ROI for XML and DITA topic-based authoring (20)

PPTX
Wicentowski - XML for the Rest of Us
KEY
Practical Microformats - Voices That Matter
PPTX
01 mad cap_software
PDF
Organisational Wiki Adoption
PPT
HATs Today and Tomorrow - STCTC Meeting December 2014
PDF
Citizen Developer Tools (session at SharePoint Saturday Twin Cities 4/14/2018...
PPTX
Implementing a Multi-Device Approach to E-learning Design (US Session)
PDF
Olf2016
PPTX
Help Content Strategy presentation, iDW Oct 2014
PPTX
Navigating the Mess of a Shared drive Migration to SharePoint
PDF
Integrating Alfresco with SharePoint & Drupal Using CMIS
PPT
TechComm 2.0: What You Need To Know
PDF
Yahoo Help Content Strategy - Chris Todd
PDF
A Young Lady's Illustrated Primer to Architecture and Technical Decision-Maki...
PDF
Krellenstein lucene revolution_2011_keynote_once_future_history_enterprise se...
PPT
Planning and Managing Digital Library & Archive Projects
PDF
Flow: A living full-stack framework for the web
PDF
The New Publishing Skillset: Change Management in a Creative Industry - Tech ...
PPT
Web 2.0, Hip or Hype - A Library Perspective
PDF
Getting The Most Out of Open Source and Drupal (Michael Meyers, Acquia)
Wicentowski - XML for the Rest of Us
Practical Microformats - Voices That Matter
01 mad cap_software
Organisational Wiki Adoption
HATs Today and Tomorrow - STCTC Meeting December 2014
Citizen Developer Tools (session at SharePoint Saturday Twin Cities 4/14/2018...
Implementing a Multi-Device Approach to E-learning Design (US Session)
Olf2016
Help Content Strategy presentation, iDW Oct 2014
Navigating the Mess of a Shared drive Migration to SharePoint
Integrating Alfresco with SharePoint & Drupal Using CMIS
TechComm 2.0: What You Need To Know
Yahoo Help Content Strategy - Chris Todd
A Young Lady's Illustrated Primer to Architecture and Technical Decision-Maki...
Krellenstein lucene revolution_2011_keynote_once_future_history_enterprise se...
Planning and Managing Digital Library & Archive Projects
Flow: A living full-stack framework for the web
The New Publishing Skillset: Change Management in a Creative Industry - Tech ...
Web 2.0, Hip or Hype - A Library Perspective
Getting The Most Out of Open Source and Drupal (Michael Meyers, Acquia)
Ad

More from Scriptorium Publishing (20)

PDF
Think global, act global, go global
PDF
Future-proofing your content
PDF
Future-proofing your career
PDF
Developing training websites in multiple languages with (mostly) open-source ...
PDF
Webcast: Balancing standardization against the need for creativity
PDF
The Rocky Road to DITA
PDF
LavaCon keynote: But Father, I'm Goldleafing as Fast as I Can!
PDF
2016 content trends
PDF
Unified Content Development: Integrating Tech Comm, Marcom, and Technical Sup...
PDF
Content Strategy Triage: Who lives? Who dies? Who do you fight to save?
PDF
Content Strategy Triage: Extended Edition
PDF
The Content Strategy of Things
PDF
Localization strategy and the customer journey
PDF
Webinar content strategy_vs_the_undead
PDF
Content strategy triage intro for Lavacon 2015
PDF
2015 content trends
PDF
Adapting content for the US market
PDF
Content strategy vs. The Undead
PDF
The many facets of content strategy
PDF
The Bottom Line: Globalization and the Dependence on Intelligent Content
Think global, act global, go global
Future-proofing your content
Future-proofing your career
Developing training websites in multiple languages with (mostly) open-source ...
Webcast: Balancing standardization against the need for creativity
The Rocky Road to DITA
LavaCon keynote: But Father, I'm Goldleafing as Fast as I Can!
2016 content trends
Unified Content Development: Integrating Tech Comm, Marcom, and Technical Sup...
Content Strategy Triage: Who lives? Who dies? Who do you fight to save?
Content Strategy Triage: Extended Edition
The Content Strategy of Things
Localization strategy and the customer journey
Webinar content strategy_vs_the_undead
Content strategy triage intro for Lavacon 2015
2015 content trends
Adapting content for the US market
Content strategy vs. The Undead
The many facets of content strategy
The Bottom Line: Globalization and the Dependence on Intelligent Content
Ad

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

  • 1. Sarah O’Keefe, Scriptorium Publishing background image flickr: thelastminute
  • 2. ! Founder and president, Scriptorium Publishing ! Content strategy for tech comm ! Interested in collision of content, publishing, and technology
  • 3. ! My ID: @sarahokeefe ! Scriptorium: @ScriptoriumTech ! #techcomm or #dita may be appropriate
  • 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. ! Business case examples (with numbers) ! YMMV ! IANAL ! WYSIOO ! Big-picture musings on other issues (without numbers)
  • 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
  • 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. ! Calculate cost of updates in multiple documents ! Consider error rates ! Don’t forget the mental health toll
  • 11. ! Software error messages ! Product specifications in product database and datasheets ! Product descriptions ! Training ! Tech support
  • 12. ! Improve collaboration among writers ! Develop and enforce consistent style standards
  • 13. “You should not implement XML as a substitute for creating a style guide.”
  • 14. “Structure is no substitute for management.”
  • 16. ! Share topics ! Communicate updates ! Minimize content “ownership” issues ! Smooth out inevitable conflicts ! Cooperate on assignments
  • 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. ! Eliminate redundancy ! More targeted information ! Meet customer requirement for personalized documentation ! Enable more versioning than supported in current toolset ! Enable dynamic publishing
  • 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. ! Tagging work does not change for static versus dynamic publishing ! Programming effort to enable dynamic publishing included in implementation cost
  • 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
  • 27. David Kelly Senior Technical Consultant www.scriptorium.com/blog/2010/09/the-promise-of-xml-publishing.html
  • 28. ! Source content in XML ! Transform to accommodate user-generated content ! Use metadata to support unified search
  • 29. ! Topic-based rather than deliverable- based publishing ! Incremental deliveries for localization ! Content deliveries decoupled from software deliveries
  • 30. ! Measure how topics are used ! Act on information about: ! Popular topics ! Unpopular topics ! Unsuccessful searches ! Topics with lots of comments
  • 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. ! Localization ! Increased reuse ! Support for complex conditionality ! Faster time to market ! Support for new publishing architecture
  • 33. ! Software integration issues ! Complex output/formatting requirements ! Inconsistent source files ! Source files that are not topic-based ! Content management system ! People
  • 35. ! Dysfunctional teams ! Information hoarding during implementation ! Tool-specific blinders ! Using XML/DITA to clone an existing, problematic workflow
  • 36. ! Improve communication ! Improve collaboration ! Build trust ! Provide project roadmap early
  • 37. ! Do not reward this behavior ! Implicitly ! Explicitly ! Avoid communication bottlenecks ! Document project decisions ! Distribute project information
  • 38. ! Ask for open minds ! Consider new features, not just cloning old features ! Try out a variety of XML tools
  • 39. ! 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
  • 40. Topics 2,000+ Writers 10+ Supported languages 3+ Deliverable formats 2+ flickr: booleansplit
  • 41. ! 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!
  • 42. ! February 8: Attractive DITA output (it IS possible)! ! March: Trends in technical communication, 2011 ! April: Structured authoring survey results
  • 44. ! Sarah O’Keefe ! www.scriptorium.com ! okeefe@scriptorium.com ! @sarahokeefe