andrew thomas: frankenstein's monster

27
1 Frankenstein’s Monster: Why You Need to Create Content Mashups

Upload: jack-molisani

Post on 12-Jan-2017

32 views

Category:

Leadership & Management


0 download

TRANSCRIPT

Page 1: Andrew Thomas: Frankenstein's Monster

1

Frankenstein’s Monster:Why You Need to Create Content Mashups

Page 2: Andrew Thomas: Frankenstein's Monster

2

Nobody is reading your technical manuals …

Page 3: Andrew Thomas: Frankenstein's Monster

3

Finding answers in your support knowledgebase is nearly impossible

Page 4: Andrew Thomas: Frankenstein's Monster

4

Customers are beginning to pick up torches and pitchforks ...

Page 5: Andrew Thomas: Frankenstein's Monster

5

How will you defend yourself from the angry mob?

Page 6: Andrew Thomas: Frankenstein's Monster

6

Effective content re-use: not just within your docs but across your organization

You need:• Structure• Shared taxonomies

& terminology• Advanced delivery

methods

Page 7: Andrew Thomas: Frankenstein's Monster

7

You need monstrouscontent mashups …

Page 8: Andrew Thomas: Frankenstein's Monster

8

… that will reanimate dead publications into …

Page 9: Andrew Thomas: Frankenstein's Monster

9

… support experiences that will shock and delight your customers

Page 10: Andrew Thomas: Frankenstein's Monster

10

Some background …

Page 11: Andrew Thomas: Frankenstein's Monster

11

Does your tech doc and marketing look remotely similar?

Page 12: Andrew Thomas: Frankenstein's Monster

12

Content that is useful anywhere in the company should be available throughout the company

Why Content Mashups?

Page 13: Andrew Thomas: Frankenstein's Monster

13

Potential Roadblocks

○ Many company teams still use copy/paste actions, with non-connected content that is not updated during updates or rebranding

○ May end up with parts that don’t respond when content is refreshed

Page 14: Andrew Thomas: Frankenstein's Monster

14

Content in the backend should have as much structure as possible

○ Technical documentation should be XML / DITA

○ Marketing materials should use standard templates

○ Both should have consistent terminology and metadata

Page 15: Andrew Thomas: Frankenstein's Monster

15

Sophisticated dynamic delivery

• Access to entire content repository

• Metadata in intelligent content

• Taxonomy across content repositories for intelligent delivery

Central Nervous system needed

So how do we make this monster mash?

Page 16: Andrew Thomas: Frankenstein's Monster

16

Intelligent delivery (IT’S ALIVE!)

○ In moment of delivery, ideal systems discern key factors about the customer:• Location & language• Platform in use• Low to High past spending

○ Matches between parameters about customer and intelligent metadata within content can ensure appropriate delivery

Page 17: Andrew Thomas: Frankenstein's Monster

17

Customer may be holding data that should initiate an action

Page 18: Andrew Thomas: Frankenstein's Monster

18

Customers may want an encounter with a product that seems like a “regular guy” or that wolf thing

Let customer input and your metadata determine what kind of “monster” to present

Control the phases of the moon? Dynamic content mashup “monster”

Page 19: Andrew Thomas: Frankenstein's Monster

19

A disconnect between your content repositories and other systems can lead to undesired consequences

Page 20: Andrew Thomas: Frankenstein's Monster

20

Lack of (or poor) design can also lead to a scalding customer delivery

BAD WORSE

Page 21: Andrew Thomas: Frankenstein's Monster

21

Appropriate delivery leads to engaged customers who become our advocates

Page 22: Andrew Thomas: Frankenstein's Monster

22

You can make previously “scary” content seem totally unthreatening

Page 23: Andrew Thomas: Frankenstein's Monster

But what about….

The “undead” … stale or lifeless content that has a life of its own, which can animate your customer experience in undesired ways

Page 24: Andrew Thomas: Frankenstein's Monster

24

Identify and remove “undead” content

Page 25: Andrew Thomas: Frankenstein's Monster

25

So in conclusion…

○ Use structure!○ Standardize terminology &

metadata○ Integrate with taxonomies○ Provide a platform for

intelligent delivery

Page 26: Andrew Thomas: Frankenstein's Monster

26

Structured Content

Management

Collaborative Review

Dynamic Delivery

SDL Knowledge Center

And if you’d like to know more…

Page 27: Andrew Thomas: Frankenstein's Monster

Copyright © 2008-2016 SDL plc. All rights reserved. All company names, brand names, trademarks, service marks, images and logos are the property of their respective owners.

This presentation and its content are SDL confidential unless otherwise specified, and may not be copied, used or distributed except as authorised by SDL.