Learn about how overcoming content strategy silos can impact your brand and revenues.
This presentation will look at how trends in modern purchasing habits and content consumption are driving more holistic content strategies. Today's content must be more agile, and there is more pressure for portable, multi-purpose content assets.
The case study portion will look at a manufacturer of medical devices that developed a global CS to bring benefits to both brand equity and bottom line. In it, users are able to access and contribute to content from any device or platform, and build up their own content stories from reusable modules, deliverable to any format. This case study is also contained in Ann Rockley's new book: Managing Enterprise Content - An Unified Content Strategy.
Supporting the brand with reusable content - CSA12
1. Supporting the brand with reusable
content
Supporting the brand with technical
content
How to get happier customers by overcoming
content silos
Noz Urbina – Principal Consultant
Mekon Ltd.
noz.urbina@mekon.com
lessworkmoreflow.blogspot.com // @nozurbina
@nozurbina
#CSA12
2. Me
~ Consultant/Trainer for Mekon Ltd.
– Content strategy, Technical Communications focus
– Mekon 20 years, me 10 years in content and mark-up
– Small-to-medium-to-huge enterprises
~ Chairperson for Congility Events (congility.com)
– Today’s Content Needs Agility
@nozurbina
#CSA12
3. The World of Content
Semantics (XML)
Nothing has changed...
Standards Speed
Metadata
...and everything has changed.
Efficiency
Strategy &
Single ROI
Sourcing
@nozurbina
#CSA12
4. We’re going to...
~ Look at trends that are forcing changes to
content strategy
~ Learn from “non-publishers” about publishing
~ How structured content standards (DITA XML)
can be applied (outside of tech comms) to create
new stories from your content assets
@nozurbina
#CSA12
12. Take-Aways
~ Reviews and manuals are the most frequently
searches by far
~ Manuals are by far the most sought-after item
actually produced by the brand
@nozurbina
#CSA12
16. Fantasy! Never in Our Lifetime!
@nozurbina
http://www.mediadecor.com/
#CSA12
17. Take-Aways
~ Smart phones and tablets are the tip of
the iceberg
– Need to migrate to a presentation-neutral
format (Like Scott said...)
– Converting and building our content into
deliverables is not scalable
@nozurbina
#CSA12
19. Components
build up a
unified story
Metadata driven
relationships
@nozurbina
#CSA12
20. Cloud computing - SaaS
Cloud computing is the delivery
of computing as a service rather than
a product
... shared resources, software, and
information are provided to computers and
other devices as a utility (like the electricity
grid)
http://en.wikipedia.org/wiki/Cloud_computing
@nozurbina
#CSA12
21. CaaS: Content as a Service
~ Content can be conceived of and delivered
as a service (CaaS)
– Content gets encapsulated in deliverables
– Each deliverable is one view for one context, at
one time.
~ One issue or update of a “Journal”, “Microsite”,
“Magazine”, etc..
~ Need to move away from project/deadline/campaign
focus to repeatable, holistic CS
@nozurbina
#CSA12
22. CaaS requires
~ Metadata-rich content, cross-silo terms/taxonomy
~ Format neutral, not proprietary content (DITA, XML)
~ Repository of reusable, structured content modules
~ Repository/Delivery platforms that support content
queries via metadata
~ Ability to re-cast content for a new context to create
new value (Content Curation)
~ Metric and analytics reporting
– To help you decide what to reuse and pipe where
@nozurbina
#CSA12
23. Content curation and reuse
~ Content curation is reusing content for new
aims
~ Sometimes it can be automated, sometimes
can be hand-curated
~ If your content is intelligent, you can use
existing assets to tell new stories, anywhere
@nozurbina
#CSA12
24. Content curation issues
~ Is it modular? (References to old context,
links, etc.)
~ Metadata - Is it findable by the appropriate
metadata in the new context?
~ Is it still current/accurate at the point of
reuse?
~ Is it editorially, stylistically, etc. appropriate in
its new reuse context?
@nozurbina
#CSA12
25. Can you pull it apart, and rebuild it?
Original Flow New New New
Scenario Audience Platform
@nozurbina
#CSA12
26. Case study in MEC Second Edition
FOR EXAMPLE
@nozurbina
#CSA12
27. Medical Devices Manufacturer
~ Content from various sources in page-based deliverables.
Coming from:
– Partners
– Official technical communications
– User-generated content
– Product management updates and customer notices
~ Going to various audiences and scenarios:
– Planned and corrective maintenance
– End Customers, Field Engineers, Support Engineers
~ Want a way to relate and recombine content for various
needs/scenarios/devices
@nozurbina
#CSA12
28. The brand wanted...
Cheaper Brand Auditable /
Impression Compliant
Lower More
More
Support “One Voice” Money
Calls
Knowledge
Faster Sharing
@nozurbina
#CSA12
29. The users wanted...
My custom tags
Up to date
Not a
Consistent website or
PDF: Both!
And more!
Simpler
My content,
in context,
Relevant
acted on
@nozurbina
Visual
#CSA12
http://upload.wikimedia.org/wikipedia/commons/7/77/Nanobay_workstation.jpg
31. Socially Enabled Across Silos Community
and Personal
Bookmark/Download data
Let users build and
share their own
In-line discussion stories, for any
format
Page discussion
Comments
@nozurbina
#CSA12
35. Initial Returns - 2011
• “Our research showed that organizations that move to [a
DITA-XML-based system] can reduce translation costs by 30%
to 50%.
• Our own examples showed 40% to 75% savings.
• Over the next few years, we anticipate savings in the region
of £193.49k, £425.68k, £468.25k, and £515.07k, which is an
average saving of £400k per year.
• Note that this ROI assumes all content is in XML, which is not the case
just yet.”
@nozurbina
#CSA12
36. XML: components and maps
Original Flow New New New
Scenario Audience Platform
@nozurbina
#CSA12
38. XML – The standards-based enabler
~ CMS form functionality in a real authoring tool
– Insert ‘keyword’ instead of ‘bold’
~ Reusable components
– Note: needs good content and metadata design
~ Standard enforcement across tools
~ Semantics/metadata
– Detailed content profiling at any level of granularity
~ Taxonomy-based relationships
~ Common processing architecture for all content
@nozurbina
#CSA12
39. Map
~ XML standard for stitching
bits back together
– Defines a complete, but
presentation-agnostic,
content story
~ Components
~ Hierarchy
~ Linking/Navigation
~ Medatata
~ Many maps can share
components
– HTML, PDF, media, XML
~ Specifically DITA XML
@nozurbina
#CSA12
40. Take-aways
~ The approach (and standards) apply outside of tech
comm
– Early (non-tech comm) take-up in
~ Publishing and catalogues
~ Reports and analyst content
~ Policies and government
~ Learning materials
~ The content strategist helps align the planets
so magic can happen
Tweetme
@nozurbina
#CSA12