Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
BetterCross-ChannelExperiencesWithMetadata        @AdamUngstad                #XChannelMetadata
Metadata enables...
consistency
context
interoperability
incross-channel experiences
by facilitating
structuredinformation exchanges.
what is metadata?
information       aboutinformation objects
the content
the containers
of information objects
what is aninformation object?
Document
3 Types of Metadata
DescriptiveAdministrative  Structural
Descriptive
discover & identify
DateColourVersionCategoryMakeOrigin
When used with UXtechniques such as
Faceted Search
Descriptive metadata...
...enables context.
Administrative
manage
StatusExpiry DateContent OwnerAccess RightsIntellectual Property
Right content  Right timeRight channel  Right user
When used with UXtechniques such as
Content Strategy
Administrative metadata…
…enables consistency.
Structural
compositionof compound objects
Name
First NameMiddle InitialLast Name
First Name        Other Given Names       cv                 cvSurnameSurname (Birth)                  cvSurname (Previous...
When used with UXtechniques such as
Form Design
Structural metadataenables interoperability.
Channels
Multi-Channel
Website   SMS   Mail   In-Store   Phone
Website   SMS   Mail   In-Store   Phone
Website   SMS   Mail   In-Store   Phone
Cross-Channel
Website   SMS   Mail   In-Store   Phone
Website   SMS   Mail   In-Store   Phone
Moving between channels
requiresinformation exchanges.
So how do weexchange information?
3 Sides ofInformation Architecture
Presentation
Storage
Exchanges
Exchanges
each side has aunique structure
exchanges
X
X   Y
X       Y    Z
Z
ZOrg 1                            Org 4        Org 2       Org 3
What is ‘Z’?
Metadata Standards
RDF                 ZOrg 1                          Org 4        Org 2     Org 3
Z                NIEMOrg 1                           Org 4        Org 2      Org 3
DUBLIN                  Z                 COREOrg 1                              Org 4        Org 2         Org 3
Good                   Z                RelationsOrg 1                                Org 4        Org 2           Org 3
Z                OASISOrg 1                            Org 4        Org 2       Org 3
XML                 ZOrg 1                          Org 4        Org 2     Org 3
standardsenable exchanges
exchangesenable data linking
what is defined by ametadata standard?
Semantics
meaning
“bench”
Syntax
expression
capsicum
pepper
Name
3ric?
St. Germaine?
Lexical Rules
words
Name
The Cookie Monster?
Talula Does The Hula From         Hawaii?
Experiences
If a pepper is aninformation object...
...a user is one too.
Website   SMS   Mail   In-Store   Phone
is an experience‘one size fits all’?
experiences must be personalized
previous experiences
memories
expectations
wants
interests
aspirations
behaviours
each channel
must know the user
users are not anexchange mechanism!
X       Y    Z
never ask forsomething twice
you only getone first chance
What to do on Monday:
1. make metadata a priority
link metadata to ROI
reduce inefficiencies
create loyalty
2. define your data
information objects
content assets
users
relationships
1:1 1 : manymany : many
1:1 1 : manymany : many
is part ofis delivered by  is used with
Ontology
Mental Models
@indiyoung @rosenfeldmedia
Contextual Inquiries
Diary Studies
discoverwhat needs to be defined
specify
semantics   syntaxlexical rules
start with acontrolled vocabulary
3. identify exchanges
internal & external
Journey Map
@uxjam
Business Origami
@jessmcmullin
happy paths
unplanned paths
4. build the infrastructure
start small
build on what exists
borrow & reuse
you have to start  somewhere
build bettercross-channel experiences
with metadata
Thank You!@AdamUngstad
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Upcoming SlideShare
Loading in …5
×

Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012

25,509 views

Published on

Metadata provides a foundation for the cross-channel experiences we consume in the dawn of the 21st century by enabling consistency, context and interoperability.

While Metadata is key to many of the User Experience methods we use – from triggering Content Strategy workflows to enabling faceted search through groups, sorts and filters, it remains a mystery to many of us. This session is a crash course on Metadata in the 21st century for UX Designers.

We'll look at recent developments in the field, and build an understanding of how Metadata enables the exchange of information between parties, channels, systems and platforms through semantic, syntax and lexical specifications.

Attendees will understand how Metadata fits into UX methods and tools they already know – using an ontology to support a mental model for example. This session is a must for all UX Designers looking to build meaningful cross-channel experiences in an increasingly interlinked world.

Published in: Technology, Education

Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012

  1. BetterCross-ChannelExperiencesWithMetadata @AdamUngstad #XChannelMetadata
  2. Metadata enables...
  3. consistency
  4. context
  5. interoperability
  6. incross-channel experiences
  7. by facilitating
  8. structuredinformation exchanges.
  9. what is metadata?
  10. information aboutinformation objects
  11. the content
  12. the containers
  13. of information objects
  14. what is aninformation object?
  15. Document
  16. 3 Types of Metadata
  17. DescriptiveAdministrative Structural
  18. Descriptive
  19. discover & identify
  20. DateColourVersionCategoryMakeOrigin
  21. When used with UXtechniques such as
  22. Faceted Search
  23. Descriptive metadata...
  24. ...enables context.
  25. Administrative
  26. manage
  27. StatusExpiry DateContent OwnerAccess RightsIntellectual Property
  28. Right content Right timeRight channel Right user
  29. When used with UXtechniques such as
  30. Content Strategy
  31. Administrative metadata…
  32. …enables consistency.
  33. Structural
  34. compositionof compound objects
  35. Name
  36. First NameMiddle InitialLast Name
  37. First Name Other Given Names cv cvSurnameSurname (Birth) cvSurname (Previous) cv
  38. When used with UXtechniques such as
  39. Form Design
  40. Structural metadataenables interoperability.
  41. Channels
  42. Multi-Channel
  43. Website SMS Mail In-Store Phone
  44. Website SMS Mail In-Store Phone
  45. Website SMS Mail In-Store Phone
  46. Cross-Channel
  47. Website SMS Mail In-Store Phone
  48. Website SMS Mail In-Store Phone
  49. Moving between channels
  50. requiresinformation exchanges.
  51. So how do weexchange information?
  52. 3 Sides ofInformation Architecture
  53. Presentation
  54. Storage
  55. Exchanges
  56. Exchanges
  57. each side has aunique structure
  58. exchanges
  59. X
  60. X Y
  61. X Y Z
  62. Z
  63. ZOrg 1 Org 4 Org 2 Org 3
  64. What is ‘Z’?
  65. Metadata Standards
  66. RDF ZOrg 1 Org 4 Org 2 Org 3
  67. Z NIEMOrg 1 Org 4 Org 2 Org 3
  68. DUBLIN Z COREOrg 1 Org 4 Org 2 Org 3
  69. Good Z RelationsOrg 1 Org 4 Org 2 Org 3
  70. Z OASISOrg 1 Org 4 Org 2 Org 3
  71. XML ZOrg 1 Org 4 Org 2 Org 3
  72. standardsenable exchanges
  73. exchangesenable data linking
  74. what is defined by ametadata standard?
  75. Semantics
  76. meaning
  77. “bench”
  78. Syntax
  79. expression
  80. capsicum
  81. pepper
  82. Name
  83. 3ric?
  84. St. Germaine?
  85. Lexical Rules
  86. words
  87. Name
  88. The Cookie Monster?
  89. Talula Does The Hula From Hawaii?
  90. Experiences
  91. If a pepper is aninformation object...
  92. ...a user is one too.
  93. Website SMS Mail In-Store Phone
  94. is an experience‘one size fits all’?
  95. experiences must be personalized
  96. previous experiences
  97. memories
  98. expectations
  99. wants
  100. interests
  101. aspirations
  102. behaviours
  103. each channel
  104. must know the user
  105. users are not anexchange mechanism!
  106. X Y Z
  107. never ask forsomething twice
  108. you only getone first chance
  109. What to do on Monday:
  110. 1. make metadata a priority
  111. link metadata to ROI
  112. reduce inefficiencies
  113. create loyalty
  114. 2. define your data
  115. information objects
  116. content assets
  117. users
  118. relationships
  119. 1:1 1 : manymany : many
  120. 1:1 1 : manymany : many
  121. is part ofis delivered by is used with
  122. Ontology
  123. Mental Models
  124. @indiyoung @rosenfeldmedia
  125. Contextual Inquiries
  126. Diary Studies
  127. discoverwhat needs to be defined
  128. specify
  129. semantics syntaxlexical rules
  130. start with acontrolled vocabulary
  131. 3. identify exchanges
  132. internal & external
  133. Journey Map
  134. @uxjam
  135. Business Origami
  136. @jessmcmullin
  137. happy paths
  138. unplanned paths
  139. 4. build the infrastructure
  140. start small
  141. build on what exists
  142. borrow & reuse
  143. you have to start somewhere
  144. build bettercross-channel experiences
  145. with metadata
  146. Thank You!@AdamUngstad

×