I’m a business experience consultant for Kontent<\/a>, so although this topic may have been covered from a business strategy, content strategy, or other points of view, it’s possible that my exposure to:<\/p>\n\n\n\n \u2026might bring unique insights.<\/p>\n\n\n\n Wikipedia: \u2026 a set of data that describes and gives information<\/strong> about other data<\/strong>.<\/p>\n\n\n\n Examples (values):<\/strong><\/p>\n\n\n\n I’m in development<\/em>:<\/p>\n\n\n\n External ID (GUID), Theme (light, dark), Layout (right aligned, left aligned, 3 columns\u2026), User agent (Mozilla\/5.0, Opera\/9.80\u2026)<\/p>\n<\/blockquote>\n\n\n\n I’m in SEO<\/em>:<\/p>\n\n\n\n Keywords (comma separated values), Description (text), Title (text)<\/p>\n<\/blockquote>\n\n\n\n I’m in marketing<\/em>:<\/p>\n\n\n\n Persona (Technical, Business)<\/p>\n<\/blockquote>\n\n\n\n I’m in UX<\/em>:<\/p>\n\n\n\n Customer journey stage (Awareness, Consideration, Acquisition, Service, Loyalty)<\/p>\n<\/blockquote>\n\n\n\n I’m in sales<\/em>:<\/p>\n\n\n\n Market segment (Enterprise, Mid, Consumer-market)<\/p>\n<\/blockquote>\n\n\n\n Everyone cares in one form or another about metadata. Yes, it’s a different set of metadata, but it’s used throughout a business, supporting its business goals.<\/p>\n\n\n\n The business always has an end goal. And every business needs to have access to channels (market places, audiences, consumers) to get to its goal. The universally targeted channel is the web. A simplified view could be:<\/p>\n\n\n\n As you might expect, it’s not as straightforward as this. Highly successful companies have a framework for success and are investing their resources in a targeted fashion to support their goals. To illustrate different layers of support, the result of such a framework could look the following way.<\/p>\n\n\n\n This framework has multiple layers, but there is common metadata that can bind these layers together. More on that in a bit, but let’s map the metadata examples I’ve listed at the beginning to this framework.<\/p>\n\n\n\n Metadata needs are sprinkled throughout the layers supporting your goals and thus business. On the surface of it, these metadata needs are very different.<\/p>\n\n\n\n I want to propose this doesn’t have to be the case. It might be only about naming and comprehension.<\/p>\n\n\n\n There are only two hard things in Computer Science: cache invalidation and <\/em>naming things<\/em><\/strong>.<\/em><\/p>\n\n\n\n \u2014 Phil Karlton<\/em><\/p>\n\n\n\n Yes, there will be specific metadata requirements for each layer. Still, with education, cross-team communication, and key stakeholder buy-in, many of these can be simplified, removed, unified, auto-generated, or left in the competency of pre-defined rules.<\/p>\n\n\n\n This is, of course, not trivial.<\/p>\n\n\n\n I’ll assume you agree that metadata is needed in one form or another. If a business sees value in this approach, it’s wise to invest in the more stable parts of this framework. This way, the work it does on metadata discovery is more lasting.<\/p>\n\n\n\n As you proceed down through the layers, the framework becomes more stable. So, let’s invest where there is a high return on investment. Let’s invest in the bottom layers and what connects these layers. Let’s invest in useful metadata<\/strong>.<\/p>\n\n\n\n What’s useful?<\/p>\n\n\n\n \u2026it\u2019s able to be used for a practical purpose<\/strong> or in several ways<\/strong>.<\/p>\n<\/blockquote>\n\n\n\n Everyone will argue their metadata category is the most useful one, but how about unifying different metadata categories. If you unify the understanding of what these categories mean, you get one or only a few important metadata categories. So, in the end, everyone agrees that the one (or few) categories are the most useful ones.<\/p>\n\n\n\n In an ideal scenario, you’d have one metadata category, maybe a global taxonomy, driving all needed use cases where metadata is needed. That would be one infinitely useful metadata category.<\/p>\n\n\n\n This taxonomy, classification, or metadata definition will be business-specific, so this concept might not resonate with you yet. Let me try an example, even though it might not fit your business. Any example is better than no example at all.<\/p>\n\n\n\n Thank you for reading this far. A quick check-in: I’m trying to find some stable metadata that can be used across all support layers. From my previously proposed layers, I should focus on Personas<\/strong>, Goals<\/strong>, Tasks<\/strong>.<\/p>\n\n\n\n My fake business, Healthscious<\/strong>, sells health insurance. Let the metadata categories be:<\/p>\n\n\n\n \ud83d\ude4e\u200d\u2640Personas<\/strong>: Heather \u2014 Health conscious, Justin \u2014 Just enjoying life<\/p>\n\n\n\n \ud83c\udfafCustomer goals<\/strong>: Get the best coverage, Get the best value coverage<\/p>\n\n\n\n \u2705Tasks<\/strong>: Redeem a claim, Find my coverage, Add new family member<\/p>\n\n\n\n \ud83d\udcb5Business goals<\/strong>: Sell top tier coverage to low-risk individuals, Retain existing business<\/p>\n\n\n\n \ud83c\udfa2Customer journey<\/strong>: Awareness, Consideration, Acquisition, Service, Loyalty<\/p>\n<\/blockquote>\n\n\n\n You can create separate categories for each above line, but there is more. You can already think about the second level of metadata, connecting these categories together.<\/p>\n\n\n\n These could be:<\/p>\n\n\n\n Lifestyle<\/strong>: Healthy, Fun, Laid-back<\/p>\n\n\n\n Mood<\/strong>: Joyful, Optimistic, Reflective, Annoyed, Distressed<\/p>\n<\/blockquote>\n\n\n\n So now, instead of thinking about \ud83d\ude4e\u200d\u2640\ufe0f Personas <\/strong>as a separate, assignable taxonomy, you can craft a persona based on this second-level metadata:<\/p>\n\n\n\n Heather<\/strong>: Healthy, Reflective, Optimistic<\/p>\n<\/blockquote>\n\n\n\n A similar exercise can be done with the \u2705Task <\/strong>category:<\/p>\n\n\n\n Add a new family member<\/strong>: Joyful, Optimistic<\/p>\n<\/blockquote>\n\n\n\n By continuing with this exercise, you are creating meaningful metadata. It\u2019s meaningful because it’s applicable in a range of use-cases. You are also creating meaningful semantic relationships between data, documents, and content in general.<\/p>\n\n\n\n This will help you personalize customer experiences independently on the presentation channel.<\/p>\n\n\n\n For developers, it will be easy to retrieve all relevant data tagged with the appropriate \ud83c\udfa2Customer journey<\/strong> phase for a customer looking to Add a new family member<\/em>. But this data has to be tagged with the relevant taxonomy term during the content crafting process.<\/p>\n\n\n\n You may think, that’s great, but what about all the other metadata my stakeholders need. My marketer wants to change the background color to \ud83d\udd35blue.<\/p>\n\n\n\n Nothing is easier if there is sufficient context.<\/p>\n\n\n\n You need to explain what your taxonomies are, what they represent, and how they empower everyone in everyday decisions. This is the only way to empower all your stakeholders.<\/p>\n\n\n\n You have to explain things first.<\/p>\n\n\n\n That includes internally evangelizing the benefits of focusing on more stable metadata categories how they connect to the business and customer needs.<\/p>\n\n\n\n The next step is to connect these useful metadata terms to each stakeholder’s work tasks. This could mean that if the marketer selects the tag Joyful<\/em>, the theme (maybe even mood board) used across your channels changes to \ud83d\udd35blue for that particular piece of content.\ud83d\udfe1Yellow would be used if the \u2705Task <\/strong>falls into the Annoyed <\/em>category.<\/p>\n\n\n\n Voila, you’ve empowered your marketer to be able to change the button color to blue without over-engineering of your upper support layers.<\/p>\n\n\n\n Developers will love this as well, as you’ll end up with a library of reusable components with identical or similar behavior without the need to deal with inconsistencies or stylesheet overriding exceptions.<\/p>\n\n\n\n What is, however, very much needed is content crafting and behavior guidelines. The term Joyful<\/em> needs to be associated with the color blue; otherwise, this setup won’t work.<\/p>\n\n\n\n Continuous internal evangelization, explanation, and onboarding onto these concepts is key.<\/p>\n\n\n\n Investing in useful metadata pays off in several ways for a business. You may think this example is irrelevant, and you are happy for each stakeholder to make their own siloed decisions. This will lead to inconsistencies without a business-wide agreed-upon taxonomy helping to drive decisions.<\/p>\n\n\n\n This article covers a tiny slice of a broad subject. Other things which I could have touched on are:<\/p>\n\n\n\n This illustrates the ability of stable metadata definitions to drive less obvious parts of the business. I may have committed logical fallacies, oversimplification, and the like, which I’d love to improve on, so please leave a comment below.<\/p>\n\n\n\n You can also dive deeper into how exactly a global taxonomy helps deliver business and customer value in day-to-day tasks<\/a>.<\/p>\n\n\n\n Happy to chat, connect or discuss use cases on Twitter<\/a> or LinkedIn<\/a> as well!<\/p>\n","protected":false},"excerpt":{"rendered":" Investing in metadata has a high return on investment. You can use it to drive a range of decisions, from high-value business decisions to high fidelity personalized design rules. It\u2019s easy to lose sight of what\u2019s important if it isn\u2019t always in front of you, your employees, and your colleagues. People\u2019s minds are fallible in […]<\/p>\n","protected":false},"author":1,"featured_media":46,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[16,23,22],"class_list":["post-45","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-taxonomies","tag-business-and-customer-goals","tag-metadata","tag-taxonomy"],"_links":{"self":[{"href":"https:\/\/contentmodeling.com\/index.php\/wp-json\/wp\/v2\/posts\/45","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/contentmodeling.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/contentmodeling.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/contentmodeling.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/contentmodeling.com\/index.php\/wp-json\/wp\/v2\/comments?post=45"}],"version-history":[{"count":2,"href":"https:\/\/contentmodeling.com\/index.php\/wp-json\/wp\/v2\/posts\/45\/revisions"}],"predecessor-version":[{"id":60,"href":"https:\/\/contentmodeling.com\/index.php\/wp-json\/wp\/v2\/posts\/45\/revisions\/60"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/contentmodeling.com\/index.php\/wp-json\/wp\/v2\/media\/46"}],"wp:attachment":[{"href":"https:\/\/contentmodeling.com\/index.php\/wp-json\/wp\/v2\/media?parent=45"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/contentmodeling.com\/index.php\/wp-json\/wp\/v2\/categories?post=45"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/contentmodeling.com\/index.php\/wp-json\/wp\/v2\/tags?post=45"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
What is metadata?<\/h1>\n\n\n\n
\n
\n
\n
\n
\n
How does a business work?<\/h1>\n\n\n\n
![\"\"\/](\"https:\/\/miro.medium.com\/max\/700\/1*ILvk5xwCmBoTBXeLUBSILQ.png\")
![\"\"\/](\"https:\/\/miro.medium.com\/max\/675\/1*2LvrazjGUOHUAamQksVn8w.png\")
Metadata needs of individual layers<\/h1>\n\n\n\n
![\"\"\/](\"https:\/\/miro.medium.com\/max\/700\/1*6v1-9dz4QByFph7QNNAnJA.png\")
![\"\"\/](\"https:\/\/miro.medium.com\/max\/700\/1*5UKDyFi3grTyB_GN5IdR0g.png\")
Useful metadata<\/h1>\n\n\n\n
\n
Useful metadata example<\/h1>\n\n\n\n
![\"\"\/](\"https:\/\/miro.medium.com\/max\/652\/1*lWY8xBNkkVtaqezCf40OxQ.png\")
\n
\n
\n
\n
Giving context<\/h1>\n\n\n\n
![\"\"\/](\"https:\/\/miro.medium.com\/max\/700\/1*VPiOc53sJ0OuFnHbb5AWLg.png\")
Summary<\/h1>\n\n\n\n
\n