<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;DUUHQH04eSp7ImA9WhRUGUs.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414</id><updated>2012-01-31T00:47:11.331+01:00</updated><category term="simplified english" /><category term="DITA" /><category term="inaugural" /><category term="technical simplified english" /><category term="NF3" /><category term="content reuse" /><category term="workflow" /><category term="webinar" /><category term="NF1" /><category term="congility 2011" /><category term="doc_train_west" /><category term="technical communications" /><category term="conference" /><category term="mekon" /><category term="user assistance" /><category term="help" /><category term="USA" /><category term="content strategy audit" /><category term="content agility" /><category term="announcement" /><category term="techcomm" /><category term="xmetal" /><category term="trade articles" /><category term="content management" /><category term="modular writing" /><category term="NF4" /><category term="web 2.0" /><category term="writing for reuse" /><category term="darwin information typing architecture" /><category term="NF2" /><category term="technical documentation" /><category term="fun" /><category term="congility" /><category term="social media" /><category term="localisation" /><category term="tech docs" /><category term="metadata" /><category term="training" /><category term="content strategy" /><category term="NF0" /><title>Less Work, More Flow</title><subtitle type="html">Content Strategy and Component Content Management</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://lessworkmoreflow.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>33</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/LessWorkMoreFlow" /><feedburner:info uri="lessworkmoreflow" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>LessWorkMoreFlow</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><entry gd:etag="W/&quot;DUAAQXwzcSp7ImA9WhRWFkU.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-7006108836969129398</id><published>2012-01-04T15:34:00.001+01:00</published><updated>2012-01-04T15:35:40.289+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-04T15:35:40.289+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conference" /><category scheme="http://www.blogger.com/atom/ns#" term="content agility" /><category scheme="http://www.blogger.com/atom/ns#" term="NF0" /><category scheme="http://www.blogger.com/atom/ns#" term="announcement" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><category scheme="http://www.blogger.com/atom/ns#" term="mekon" /><category scheme="http://www.blogger.com/atom/ns#" term="congility" /><title>Speaking at Publishing Expo 2012 [NF0]</title><content type="html">&lt;p&gt;&lt;a title="Publishing Expo Logo" href="http://publishing-expo.co.uk/content-agility-theatre" target="_blank"&gt;&lt;img style="border-bottom: 0px; border-left: 0px; margin: 0px 10px 10px 0px; display: inline; border-top: 0px; border-right: 0px" title="pubsexpo" border="0" alt="pubsexpo" align="left" src="http://lh5.ggpht.com/-X--s6Yx3rgA/TwRji9pNuEI/AAAAAAAAAH0/whJSzIDQ1Rc/pubsexpo%25255B5%25255D.jpg?imgmax=800" width="172" height="172" /&gt;&lt;/a&gt; For those considering the &lt;a href="http://publishing-expo.co.uk/" target="_blank"&gt;Publishing Expo Conference&lt;/a&gt; Feb 28-29 – I’ll be there with some favourite &lt;a href="http://www.congility.com" target="_blank"&gt;Congility&lt;/a&gt; speakers. We’re still accepting last-minute submissions for remaining speaking slots too.&lt;/p&gt;  &lt;p&gt;&lt;b&gt;Presentations should be educational, conceptual or &amp;quot;thought-leading&amp;quot; oriented presentations, i.e., not a commercial sales pitch.&lt;/b&gt;&lt;/p&gt;  &lt;p&gt;They can sent by email to georgina.johnson@mekon.com.&lt;/p&gt;  &lt;p&gt;Here’s a bit of background on the event:&lt;/p&gt;  &lt;h2&gt;Publishing Expo 2012 – Content Agility Theatre&lt;/h2&gt;  &lt;p&gt;The Content Agility Theatre is back at Publishing Expo 2012. It will focus on core challenges facing the modern publisher in today’s user-led publishing landscape, and educate and inform visitors on the processes, strategies and technologies required to overcome them.&lt;/p&gt;  &lt;p&gt;&lt;b&gt;Content Agility means making information agile, portable and reusable – abilities made ever more critical by eBooks, ePub 3.0, mobile web. &lt;/b&gt;&lt;/p&gt;  &lt;p&gt;These tools are faster and more powerful than anything we’ve had before, but how do you leverage them without increasing complexity and risk?&lt;/p&gt;  &lt;p&gt;The Theatre will feature key presentations from internationally recognised consultants, thought-leaders, and content strategists. They work with organisations the world over, helping them make relevant, excellent content available in the context and format of the consumer’s choosing.&lt;/p&gt;  &lt;h3&gt;Publishing Expo 2012 – CA Theatre Featured speakers:&lt;/h3&gt;  &lt;ul&gt;   &lt;li&gt;&lt;b&gt;Rahel Anne Bailie, Senior Consultant and Content Strategist, Intentional Design,&lt;/b&gt; will discuss making e-Pubs relevant to the audience as well as the business. &lt;/li&gt;    &lt;li&gt;&lt;b&gt;Noz Urbina, Senior Consultant and Content Strategist, Mekon Ltd., &lt;/b&gt;will discuss updating your content strategy for a community-driven world. &lt;/li&gt;    &lt;li&gt;&lt;b&gt;Brett Freeman, Content Publishing Specialist, Aptara,&lt;/b&gt; will address publishing content to digital platforms. &lt;/li&gt;    &lt;li&gt;&lt;b&gt;Anne Caborn, Co-founder and Content Development Specialist, CDA,&lt;/b&gt; will take you through governing digital content to achieve agility while avoiding risk.&lt;b&gt;&lt;/b&gt; &lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;&lt;a href="http://publishing-expo.co.uk/content-agility-theatre"&gt;http://publishing-expo.co.uk/content-agility-theatre&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-7006108836969129398?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=7nPRbCxjqt0:wN4HPT_ncY8:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=7nPRbCxjqt0:wN4HPT_ncY8:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=7nPRbCxjqt0:wN4HPT_ncY8:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=7nPRbCxjqt0:wN4HPT_ncY8:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=7nPRbCxjqt0:wN4HPT_ncY8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=7nPRbCxjqt0:wN4HPT_ncY8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=7nPRbCxjqt0:wN4HPT_ncY8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=7nPRbCxjqt0:wN4HPT_ncY8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=7nPRbCxjqt0:wN4HPT_ncY8:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=7nPRbCxjqt0:wN4HPT_ncY8:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=7nPRbCxjqt0:wN4HPT_ncY8:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=7nPRbCxjqt0:wN4HPT_ncY8:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/7nPRbCxjqt0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/7006108836969129398/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2012/01/speaking-at-publishing-expo-2012-nf0.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/7006108836969129398?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/7006108836969129398?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/7nPRbCxjqt0/speaking-at-publishing-expo-2012-nf0.html" title="Speaking at Publishing Expo 2012 [NF0]" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh5.ggpht.com/-X--s6Yx3rgA/TwRji9pNuEI/AAAAAAAAAH0/whJSzIDQ1Rc/s72-c/pubsexpo%25255B5%25255D.jpg?imgmax=800" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2012/01/speaking-at-publishing-expo-2012-nf0.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEANR34-fip7ImA9WhRWGEg.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-4425601882398858036</id><published>2011-12-08T12:34:00.003+01:00</published><updated>2012-01-06T14:33:16.056+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-06T14:33:16.056+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="NF0" /><category scheme="http://www.blogger.com/atom/ns#" term="technical communications" /><category scheme="http://www.blogger.com/atom/ns#" term="techcomm" /><category scheme="http://www.blogger.com/atom/ns#" term="NF1" /><category scheme="http://www.blogger.com/atom/ns#" term="content management" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><title>Musings On Choosing a CMS: Feature Overload [NF0]</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
﻿ &lt;br /&gt;
&lt;table cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: left; margin-right: 1em; text-align: left;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://upload.wikimedia.org/wikipedia/commons/5/53/The_giant_wenger.jpg" imageanchor="1" style="clear: left; cssfloat: left; margin-bottom: 1em; margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="168" src="http://upload.wikimedia.org/wikipedia/commons/5/53/The_giant_wenger.jpg" width="240" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Missing the point completely...&lt;br /&gt;
&lt;sup&gt;&lt;a href="http://commons.wikimedia.org/wiki/File:The_giant_wenger.jpg"&gt;&lt;/a&gt;&lt;/sup&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
﻿ I’m working with a major client choosing a CMS.&lt;br /&gt;
&lt;br /&gt;
In this particular choice, it’s a multi-year, multi-million dollar choice. &lt;br /&gt;
&lt;br /&gt;
If all goes well, it will eventually be a system that touches from at least 1000, to many thousands&lt;em&gt; &lt;/em&gt;of staff.&lt;br /&gt;
&lt;br /&gt;
Their demanding business context has quickly filtered the market from literally thousands to only a handful of systems. We’re now down to two major vendors. The first of these vendors is demonstrating their extremely powerful system.&lt;br /&gt;
&lt;br /&gt;
Problem: it’s too powerful, and too customisable.&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;
Spoiled for Choice&lt;/h2&gt;
&lt;br /&gt;
The system is positively bristling with functions, but as a result, it looks unusable. By the end of this week we’ll have spent 4 straight days digging through this thing.&amp;nbsp; As the product selection team, we’re looking at as many aspects as humanly possible before the selection process itself stops being cost effective.&lt;br /&gt;
What’s happening is that with too many ways to do something and too many options, the whole thing seems daunting.&amp;nbsp; If you’ve not used a CMS before, or used only lightweight or simplistic ones (you know who you are, Vendors!) then a big customisable beastie can start to look like something you’d dread putting your users in front of, then having to train on and support.&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;
Metrics vs Feelings [NF1]*&lt;/h2&gt;
&lt;br /&gt;
As scientific and unbiased as we try to make software decisions, there’s a very real and human component. And it’s an important one. When I talk about brand I talk a lot about the brand “experience”.&lt;br /&gt;
&lt;br /&gt;
The whole “holistic content strategy” thing is about looking at all aspects of how content affects the experience of the brand.&amp;nbsp; It’s crucial to whether we’ll move from one phase of a relationship to another.&lt;br /&gt;
For this project we’ve defined 31 high-level use cases which between them have nearly 350 specific points of evaluation. Each evaluation point is then given a score and weighting multiplier, resulting in lots of juicy math and pretty pie-charts to make everyone feel confident and rest easy.&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;But do you go with the system that’s better on paper, or the one that feels like you could live with it?&lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;
Take Aways&lt;/h2&gt;
&lt;br /&gt;
What I’d like to put forward here is two musings from my experience with buying CMSs:&lt;br /&gt;
&lt;br /&gt;
&lt;h3&gt;
Not Just a Pretty Face&lt;/h3&gt;
Don’t dismiss UI discussions as a software ‘beauty pageant’.&amp;nbsp; UI discussions are important.&amp;nbsp; Bad UI in your internal systems is damaging to performance in the same way as bad&amp;nbsp;design of the content you’re managing in it.&amp;nbsp; The message gets lost, and you’re slowed, if not prevented, from realising your goals.&amp;nbsp; &lt;br /&gt;
The fact that staff can be “told” to do their jobs but users can’t be “told” to engage with your content has some effect, but don’t rely on this factor. This is especially true for those looking at buying XML/DITA-capable CMSs.&lt;br /&gt;
&lt;br /&gt;
&lt;h3&gt;
It’s Not About You&lt;/h3&gt;
That said, remember that this is technology we’re talking about.&amp;nbsp; Configuration options can be overwhelming, but especially with big systems, they’re there for a reason. &lt;br /&gt;
&lt;br /&gt;
You want something that can grow with your business.&amp;nbsp; As the stakeholders in the system decision it’s your responsibility to understand how the system could look different to different user roles in your organisation.&amp;nbsp; &lt;br /&gt;
The fact you’ve got to sit through ALL those options, doesn’t mean they do. You’ve got to sit through 20 examples of how the interface &lt;em&gt;could &lt;/em&gt;look, but they’ll only get one or two.&amp;nbsp; As with all decisions in business, we must step outside of our emotional reactions and think on behalf of others.&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&lt;h3&gt;
Use the Math&lt;/h3&gt;
The Use Cases and formal points of evaluation are your sanity check. As much as I think that people should weigh subjective user experience into the decision matrix, it is one – albeit important – factor among many. &lt;br /&gt;
Develop your use cases well, validate them with your users, then make your vendors go through them, ideally, with your content.&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Investing in your use cases is vital.&amp;nbsp; Then you’ve got to&amp;nbsp;brief the vendors to make sure they walk through them properly.&amp;nbsp; It’s easy to&amp;nbsp;squander huge amounts of time, and eventually not be comparing apples to apples in&amp;nbsp;the&amp;nbsp;flow of canned demos.&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
If you don’t structure your evaluation, you’re only left with “I liked that one better, and I’m pretty sure they ticked all our boxes”. That’s not a reason to invest in any key system, and not a defensible position if anyone asks in 6 months time what you did with all that budget.&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;Any one else have CMS selection tips they can share?&lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* This is an &lt;a href="http://lessworkmoreflow.blogspot.com/2011/12/nerd-factor-4-mr-sulu-revising-my.html" target="_blank"&gt;NF (Nerd Factor) Rating&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-4425601882398858036?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=nXLAf9yG-XQ:sCmumKjuX0Q:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=nXLAf9yG-XQ:sCmumKjuX0Q:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=nXLAf9yG-XQ:sCmumKjuX0Q:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=nXLAf9yG-XQ:sCmumKjuX0Q:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=nXLAf9yG-XQ:sCmumKjuX0Q:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=nXLAf9yG-XQ:sCmumKjuX0Q:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=nXLAf9yG-XQ:sCmumKjuX0Q:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=nXLAf9yG-XQ:sCmumKjuX0Q:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=nXLAf9yG-XQ:sCmumKjuX0Q:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=nXLAf9yG-XQ:sCmumKjuX0Q:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=nXLAf9yG-XQ:sCmumKjuX0Q:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=nXLAf9yG-XQ:sCmumKjuX0Q:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/nXLAf9yG-XQ" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/4425601882398858036/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/12/musings-on-choosing-cms-feature.html#comment-form" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/4425601882398858036?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/4425601882398858036?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/nXLAf9yG-XQ/musings-on-choosing-cms-feature.html" title="Musings On Choosing a CMS: Feature Overload [NF0]" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><thr:total>3</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/12/musings-on-choosing-cms-feature.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkIARHw_cSp7ImA9WhRRF04.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-5495267129151711568</id><published>2011-12-01T12:19:00.001+01:00</published><updated>2011-12-01T12:22:25.249+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-01T12:22:25.249+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="NF0" /><category scheme="http://www.blogger.com/atom/ns#" term="NF3" /><category scheme="http://www.blogger.com/atom/ns#" term="NF1" /><category scheme="http://www.blogger.com/atom/ns#" term="NF2" /><category scheme="http://www.blogger.com/atom/ns#" term="NF4" /><title>Nerd Factor 4, Mr Sulu: Revising My Posting Metadata</title><content type="html">&lt;p&gt;Hello Readerinos,&lt;/p&gt;  &lt;p&gt;I love to talk brand, and customer experience and ROI impact until I’m blue in the face. I also get lots of people asking me about some seriously hardcore stuff, and work on some of the world’s largest and meanest content munching machines.&amp;#160; &lt;/p&gt;  &lt;p&gt;As a result, I’ve gotten myself blog readers at both ends of the content strategy technical interest spectrum.&amp;#160; &lt;/p&gt;  &lt;p&gt;I need to help readers find the stuff that’s going to add value to &lt;em&gt;them&lt;/em&gt;, and pass over (for now) the stuff replete with language and acronyms that to everyone else is gibberish.&amp;#160; &lt;/p&gt;  &lt;br /&gt;  &lt;h2&gt;Presenting the Nerd Factor Ratings System&lt;/h2&gt;  &lt;p&gt;&lt;a href="http://lh3.ggpht.com/-WrTlsU8YtZQ/Ttdiys6diLI/AAAAAAAAAHk/vp4z4y1xXCY/s1600-h/nerd-http-commons.wikimedia.org.wiki.File.NERD%25255B2%25255D.png"&gt;&lt;img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="nerd-http-commons.wikimedia.org.wiki.File.NERD" border="0" alt="nerd-http-commons.wikimedia.org.wiki.File.NERD" src="http://lh3.ggpht.com/-9XkoY3YTvMo/TtdizCOfTfI/AAAAAAAAAHs/auPOEMktKfg/nerd-http-commons.wikimedia.org.wiki.File.NERD_thumb.png?imgmax=800" width="244" height="196" /&gt;&lt;/a&gt; &lt;/p&gt;  &lt;p&gt;Photo: &lt;a title="http://commons.wikimedia.org/wiki/File:NERD.png" href="http://commons.wikimedia.org/wiki/File:NERD.png"&gt;&lt;font face="Arial Narrow"&gt;http://commons.wikimedia.org/wiki/File:NERD.png&lt;/font&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;So, from now on, I’m going to try rank and tag the technie-ness of my posts from 0 (General) to 4 (Gandalf the White Ninja of Content Coding). So watch for [NF0],[NF2], etc. tags in blog and section titles.&lt;/p&gt;  &lt;p&gt;This extra metadata should help you find the content that’s appropriate for your interests. &lt;/p&gt;  &lt;p&gt;I hope my readers take the opportunity to push themselves a bit, but I also want you to spare your time for the posts that are going to help you in your work!&lt;/p&gt;  &lt;p&gt;Now that I’ve got the levels, I’ll try to make sure I’m blogging at each one with some regularity.&lt;/p&gt;  &lt;p&gt;Enjoy!&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;Here’s some examples of questions I might answer or things I might talk about in each level: &lt;/strong&gt;    &lt;br /&gt;&lt;/p&gt;  &lt;h2&gt;General Audience Stuff [NF0] &lt;/h2&gt;  &lt;br /&gt;  &lt;ul&gt;   &lt;li&gt;Content affects the customer experience!&amp;#160; &lt;/li&gt;    &lt;li&gt;Brand management and content management are kindred fields! &lt;/li&gt;    &lt;li&gt;Here's some tips on selling content value to managers. &lt;/li&gt;    &lt;li&gt;It’s about knowledge, communication, collaboration and money. &lt;/li&gt; &lt;/ul&gt;  &lt;br /&gt;  &lt;h2&gt;Somewhat Nerdy Stuff [NF1] &lt;/h2&gt;  &lt;br /&gt;  &lt;ul&gt;   &lt;li&gt;Here's some tips on building a content inventory. &lt;/li&gt;    &lt;li&gt;Look what I found out by analysing the SEO of this content. &lt;/li&gt;    &lt;li&gt;Change management and process factors to think about before integrating CMSs between departments. &lt;/li&gt;    &lt;li&gt;How does terminology management affect content reuse and readability? &lt;/li&gt; &lt;/ul&gt;  &lt;br /&gt;  &lt;h2&gt;Definitively Nerdy Stuff [NF2] &lt;/h2&gt;  &lt;br /&gt;  &lt;ul&gt;   &lt;li&gt;What metrics should I report on in an XML system to prove to management we're performing? &lt;/li&gt;    &lt;li&gt;How should I evaluate a DITA CMS before buying one? &lt;/li&gt; &lt;/ul&gt;  &lt;br /&gt;  &lt;h2&gt;Very Nerdy Stuff [NF3] &lt;/h2&gt;  &lt;br /&gt;  &lt;ul&gt;   &lt;li&gt;What’s new in DITA 1.2? What is editor support like? &lt;/li&gt;    &lt;li&gt;Here’s a &lt;a href="http://www.youtube.com/watch?v=Ajp_ggtSxMk" target="_blank"&gt;new webinar on DITA 1.2 keys&lt;/a&gt;!&lt;/li&gt;    &lt;li&gt;What’s the best way the set up my DITA metadata and folder taxonomy for organising my @conref targets? &lt;/li&gt; &lt;/ul&gt;  &lt;br /&gt;  &lt;h2&gt;About as Nerdy as I Ever Get [NF4] &lt;/h2&gt;  &lt;br /&gt;  &lt;ul&gt;   &lt;li&gt;When should I use @conkeyref and when should I use @ttr conditions? &lt;/li&gt;    &lt;li&gt;Is it ANT scripts or XSLTs that you need to customise to get your DOT output ready for processing to XSL:FO/PDF and CHM deliverables? &lt;/li&gt; &lt;/ul&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-5495267129151711568?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=SdJ24-Ng4W8:-fTcD0VQ0MY:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=SdJ24-Ng4W8:-fTcD0VQ0MY:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=SdJ24-Ng4W8:-fTcD0VQ0MY:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=SdJ24-Ng4W8:-fTcD0VQ0MY:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=SdJ24-Ng4W8:-fTcD0VQ0MY:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=SdJ24-Ng4W8:-fTcD0VQ0MY:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=SdJ24-Ng4W8:-fTcD0VQ0MY:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=SdJ24-Ng4W8:-fTcD0VQ0MY:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=SdJ24-Ng4W8:-fTcD0VQ0MY:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=SdJ24-Ng4W8:-fTcD0VQ0MY:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=SdJ24-Ng4W8:-fTcD0VQ0MY:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=SdJ24-Ng4W8:-fTcD0VQ0MY:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/SdJ24-Ng4W8" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/5495267129151711568/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/12/nerd-factor-4-mr-sulu-revising-my.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/5495267129151711568?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/5495267129151711568?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/SdJ24-Ng4W8/nerd-factor-4-mr-sulu-revising-my.html" title="Nerd Factor 4, Mr Sulu: Revising My Posting Metadata" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh3.ggpht.com/-9XkoY3YTvMo/TtdizCOfTfI/AAAAAAAAAHs/auPOEMktKfg/s72-c/nerd-http-commons.wikimedia.org.wiki.File.NERD_thumb.png?imgmax=800" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/12/nerd-factor-4-mr-sulu-revising-my.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE4FSXo4fSp7ImA9WhRRFEQ.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-4786086229477066148</id><published>2011-11-28T12:17:00.001+01:00</published><updated>2011-11-28T17:15:18.435+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-28T17:15:18.435+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="DITA" /><category scheme="http://www.blogger.com/atom/ns#" term="tech docs" /><category scheme="http://www.blogger.com/atom/ns#" term="webinar" /><category scheme="http://www.blogger.com/atom/ns#" term="technical communications" /><category scheme="http://www.blogger.com/atom/ns#" term="techcomm" /><category scheme="http://www.blogger.com/atom/ns#" term="social media" /><category scheme="http://www.blogger.com/atom/ns#" term="content reuse" /><category scheme="http://www.blogger.com/atom/ns#" term="announcement" /><category scheme="http://www.blogger.com/atom/ns#" term="content management" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="darwin information typing architecture" /><title>2 New Webinars: Socially Enabled Help, DITA 1.2</title><content type="html">&lt;p&gt;Some new webinars coming at you! Both delivered in partnership &lt;a href="http://www.dclab.com" target="_blank"&gt;DCL&lt;/a&gt; and their &lt;a href="http://www.dclab.com/learning_series/" target="_blank"&gt;DCL Learning Series&lt;/a&gt;.&lt;/p&gt;  &lt;p&gt;Upcoming next week and beyond, I’ve got some DITA 1.2 &lt;/p&gt;  &lt;h2&gt;DITA 1.2 Interactive Tutorial: Three Part Online Mini-Series&lt;/h2&gt;  &lt;br /&gt;  &lt;h3&gt;&lt;a href="http://www.mekon.com/index.php/pages/company/mekon-and-data-conversion-laboratory-present/news/news" target="_blank"&gt;Register/Learn more »&lt;/a&gt;&lt;/h3&gt;  &lt;p&gt;On-demand you’ve got: &lt;/p&gt;  &lt;h2&gt;Socially Enabling Documentation in the Cloud&lt;/h2&gt;  &lt;h3&gt;   &lt;br /&gt;“Social” isn’t limited to WIKIs, Forums, Facebook, and Twitter.&lt;/h3&gt;  &lt;p&gt;More and more organisations are looking at how community content can complement (and in some cases replace) their formal product content. Also, many are noticing how much overlap there is with social content platforms and their own intranets, internal business collaboration and knowledge sharing platforms.&lt;/p&gt;  &lt;p&gt;For most, putting documentation fully in the hands of the users – even internal subject matter experts – isn’t an option, 1or is simply not desirable. Also, creating yet another silo of social content isn’t helpful for users trying to find answers.&lt;/p&gt;  &lt;p&gt;&lt;b&gt;So, how can community and formally created content play nicely together?&lt;/b&gt;&lt;/p&gt;  &lt;p&gt;On this session see best practice concepts and case study examples demonstrating:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;The pitfalls of poorly implemented social functions &lt;/li&gt;    &lt;li&gt;How the DITA platform can form the core of a socially-enabled documentation platform &lt;/li&gt;    &lt;li&gt;The key social features that organisations are implementing – and the back-end processes required to prevent chaos &lt;/li&gt;    &lt;li&gt;How internal SME and external customer communities can be leveraged for maximum benefit to both &lt;/li&gt;    &lt;li&gt;The impact on: editorial process, metrics and measurement, version management, content models, workflow, and metadata strategies      &lt;br /&gt;&lt;/li&gt; &lt;/ul&gt;  &lt;h3&gt;&lt;a href="http://www.youtube.com/watch?v=fizWmOJQkFQ"&gt;View Online »&lt;/a&gt;&lt;/h3&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-4786086229477066148?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=X12ovwJxycU:llNTTZfI94o:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=X12ovwJxycU:llNTTZfI94o:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=X12ovwJxycU:llNTTZfI94o:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=X12ovwJxycU:llNTTZfI94o:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=X12ovwJxycU:llNTTZfI94o:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=X12ovwJxycU:llNTTZfI94o:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=X12ovwJxycU:llNTTZfI94o:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=X12ovwJxycU:llNTTZfI94o:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=X12ovwJxycU:llNTTZfI94o:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=X12ovwJxycU:llNTTZfI94o:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=X12ovwJxycU:llNTTZfI94o:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=X12ovwJxycU:llNTTZfI94o:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/X12ovwJxycU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/4786086229477066148/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/11/2-new-webinars-socially-enabled-help.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/4786086229477066148?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/4786086229477066148?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/X12ovwJxycU/2-new-webinars-socially-enabled-help.html" title="2 New Webinars: Socially Enabled Help, DITA 1.2" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/11/2-new-webinars-socially-enabled-help.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkQDQXs8eyp7ImA9WhdbE0w.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-8226893506498454804</id><published>2011-10-10T17:25:00.001+02:00</published><updated>2011-10-11T09:32:50.573+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-10-11T09:32:50.573+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conference" /><category scheme="http://www.blogger.com/atom/ns#" term="tech docs" /><category scheme="http://www.blogger.com/atom/ns#" term="technical communications" /><category scheme="http://www.blogger.com/atom/ns#" term="techcomm" /><category scheme="http://www.blogger.com/atom/ns#" term="announcement" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><title>Content Strategy Day @ Tekom / TCWorld Oct 19, 2011</title><content type="html">&lt;p&gt;Hello!&lt;/p&gt;  &lt;p&gt;In a big rush but just wanted to let everyone know about the Content &lt;a title="http://bit.ly/tcw11cs" href="http://bit.ly/tcw11cs"&gt;&lt;img style="border-bottom: 0px; border-left: 0px; display: inline; margin-left: 0px; border-top: 0px; margin-right: 0px; border-right: 0px" title="tcworld" border="0" alt="tcworld" align="right" src="http://lh6.ggpht.com/-BbicYqVXkZk/TpPxIVZlohI/AAAAAAAAAHc/1iXnVtJhDt4/tcworld.jpg?imgmax=800" width="194" height="159" /&gt;&lt;/a&gt;Strategy Day at TCWorld in Germany next week. &lt;/p&gt;  &lt;p&gt;Led by Scott Abel, &lt;a href="http://thecontentwrangler.com"&gt;TheContentWrangler&lt;/a&gt;, this should be a great event within a great event!&lt;/p&gt;  &lt;p&gt;Here are two links to more complete and tantalising blog posts:&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;Interview with the &lt;/strong&gt;&lt;a href="http://de.linkedin.com/in/michaelfritz"&gt;&lt;strong&gt;Michael Fritz&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;, Executive Director of tekom:&lt;/strong&gt;&lt;/p&gt;  &lt;p&gt;&lt;a title="http://bit.ly/tcw11cs" href="http://bit.ly/tcw11cs"&gt;http://bit.ly/tcw11cs&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;An overview of Content Strategy day by Scott Abel:&lt;/strong&gt;&lt;/p&gt;  &lt;p&gt;&lt;a title="http://bit.ly/tcw11cs2" href="http://bit.ly/tcw11cs2"&gt;http://bit.ly/tcw11cs2&lt;/a&gt;&amp;#160;&lt;/p&gt;  &lt;h2&gt;Content Strategy Day Speakers and Topics&lt;/h2&gt;  &lt;p&gt;&amp;#160;&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;&lt;a href="http://www.linkedin.com/in/scottabel"&gt;Scott Abel&lt;/a&gt;, &lt;a href="http://www.thecontentwrangler.com"&gt;The Content Wrangler&lt;/a&gt; – Introduction to Content Strategy: Why do we need a content strategy, anyway? &lt;/li&gt;    &lt;li&gt;&lt;a href="http://www.gollner.ca/"&gt;Joe Gollner&lt;/a&gt;, &lt;a href="http://gnostyx.com/"&gt;Gnostyx Research&lt;/a&gt; – An Introduction to Intelligent Content Strategies &lt;/li&gt;    &lt;li&gt;&lt;a href="http://en.wikipedia.org/wiki/Ann_Rockley"&gt;Ann Rockley&lt;/a&gt;, &lt;a href="http://www.rockley.com"&gt;The Rockley Group&lt;/a&gt; – eBooks 101: Developing a unified digital content strategy for eBooks and apps &lt;/li&gt;    &lt;li&gt;&lt;a href="http://aaronfulkerson.com/"&gt;Aaron Fulkerson&lt;/a&gt;, &lt;a href="http://www.mindtouch.com/products/mindtouch_tcs"&gt;MindTouch&lt;/a&gt; – Thinking differently about customer support content: Designing a Help 2.0 strategy &lt;/li&gt;    &lt;li&gt;&lt;a href="http://intentionaldesign.ca/profile/"&gt;Rahel Anne Bailie&lt;/a&gt;, &lt;a href="http://intentionaldesign.ca/"&gt;Intentional Design&lt;/a&gt; and &lt;a href="http://www.linkedin.com/pub/geoffrey-roberts/1/313/7b4"&gt;Geoffrey Roberts&lt;/a&gt;, &lt;a href="http://mekon.com/"&gt;Nokia&lt;/a&gt; – Adventures in Localization: The oft forgotten stepchild of content strategy &lt;/li&gt;    &lt;li&gt;&lt;a href="http://es.linkedin.com/in/bnozurbina"&gt;B. Noz Urbina&lt;/a&gt;, &lt;a href="http://mekon.com/"&gt;Mekon&lt;/a&gt; – Content Strategy is a many-splendored thing: Breaking down technical communication silos &lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;Hope to see you there!&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-8226893506498454804?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=TptRPcA44AE:v5Gws2hX4Ws:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=TptRPcA44AE:v5Gws2hX4Ws:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=TptRPcA44AE:v5Gws2hX4Ws:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=TptRPcA44AE:v5Gws2hX4Ws:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=TptRPcA44AE:v5Gws2hX4Ws:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=TptRPcA44AE:v5Gws2hX4Ws:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=TptRPcA44AE:v5Gws2hX4Ws:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=TptRPcA44AE:v5Gws2hX4Ws:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=TptRPcA44AE:v5Gws2hX4Ws:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=TptRPcA44AE:v5Gws2hX4Ws:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=TptRPcA44AE:v5Gws2hX4Ws:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=TptRPcA44AE:v5Gws2hX4Ws:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/TptRPcA44AE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/8226893506498454804/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/10/content-strategy-day-tekom-tcworld-oct.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/8226893506498454804?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/8226893506498454804?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/TptRPcA44AE/content-strategy-day-tekom-tcworld-oct.html" title="Content Strategy Day @ Tekom / TCWorld Oct 19, 2011" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh6.ggpht.com/-BbicYqVXkZk/TpPxIVZlohI/AAAAAAAAAHc/1iXnVtJhDt4/s72-c/tcworld.jpg?imgmax=800" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/10/content-strategy-day-tekom-tcworld-oct.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE4GRXg_fip7ImA9WhdUGUw.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-7827471791615340520</id><published>2011-10-06T18:02:00.001+02:00</published><updated>2011-10-06T18:02:04.646+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-10-06T18:02:04.646+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="DITA" /><category scheme="http://www.blogger.com/atom/ns#" term="tech docs" /><category scheme="http://www.blogger.com/atom/ns#" term="webinar" /><category scheme="http://www.blogger.com/atom/ns#" term="techcomm" /><category scheme="http://www.blogger.com/atom/ns#" term="social media" /><category scheme="http://www.blogger.com/atom/ns#" term="announcement" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><category scheme="http://www.blogger.com/atom/ns#" term="darwin information typing architecture" /><title>Socially Enabled Documentation in the Cloud: Dangerous, Benefits, Getting There</title><content type="html">&lt;p&gt;Hiddly-ho, Readerinos!&lt;a href="http://lh3.ggpht.com/-IptIZzXYf20/To3Q-dP8juI/AAAAAAAAAHQ/TM06Hlw54m4/s1600-h/community_copyright_free%25255B4%25255D.jpg"&gt;&lt;img style="border-bottom: 0px; border-left: 0px; display: inline; margin-left: 0px; border-top: 0px; margin-right: 0px; border-right: 0px" title="community_copyright_free" border="0" alt="community_copyright_free" align="right" src="http://lh6.ggpht.com/-P8FiIVJg6Cs/To3Q--GR7PI/AAAAAAAAAHU/qJ5CQ-tBMTw/community_copyright_free_thumb%25255B2%25255D.jpg?imgmax=800" width="166" height="163" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;FYI - I'll be doing a webinar on one of my favourite topics Oct 12th: Social enablement of technical communications.&lt;/p&gt;  &lt;h2&gt;Socially Enabled Content…?&lt;/h2&gt;  &lt;p&gt;Social Enablement…? Socially Enabled Technical Communication?&amp;#160; &lt;/p&gt;  &lt;p&gt;What on earth is that? Glad you asked! &lt;/p&gt; “Social” isn’t limited to WIKIs, Forums, Facebook, and Twitter, and &amp;quot;Communities&amp;quot; doesn't just mean external customers, they're you and your colleagues as well.  &lt;p&gt;Social enablement basically means taking traditional content, and complementing (not necessarily replacing) it with community-driven social functionality like:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;user contributions and conversations &lt;/li&gt;    &lt;li&gt;community activity monitoring &lt;/li&gt;    &lt;li&gt;tagging &lt;/li&gt;    &lt;li&gt;ranking and metrics &lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;All for the good of the users and the enterprise. And in the Cloud, and using DITA XML, so that it's easy to roll out and access from smartphones, tablets, PCs and (gasp!) print.&lt;/p&gt;  &lt;p&gt;I'll be going over some of the content strategy pitfalls, issues, and gotchas as well as walking through an example where we're prototyping social features in what was, 18 months ago, a traditional unstructured manufacturing tech docs environment&lt;/p&gt;  &lt;p&gt;Hope we see you there!&lt;/p&gt;  &lt;p&gt;Register: &lt;a href="http://bit.ly/qmeeXQ"&gt;http://bit.ly/qmeeXQ&lt;/a&gt; or read more: &lt;a href="http://bit.ly/qA1n0N"&gt;http://bit.ly/qA1n0N&lt;/a&gt; &lt;/p&gt;  &lt;p&gt;Noz&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-7827471791615340520?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=04_8ySkjg3I:TSnBjB2Rglg:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=04_8ySkjg3I:TSnBjB2Rglg:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=04_8ySkjg3I:TSnBjB2Rglg:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=04_8ySkjg3I:TSnBjB2Rglg:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=04_8ySkjg3I:TSnBjB2Rglg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=04_8ySkjg3I:TSnBjB2Rglg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=04_8ySkjg3I:TSnBjB2Rglg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=04_8ySkjg3I:TSnBjB2Rglg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=04_8ySkjg3I:TSnBjB2Rglg:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=04_8ySkjg3I:TSnBjB2Rglg:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=04_8ySkjg3I:TSnBjB2Rglg:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=04_8ySkjg3I:TSnBjB2Rglg:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/04_8ySkjg3I" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/7827471791615340520/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/10/socially-enabled-documentation-in-cloud.html#comment-form" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/7827471791615340520?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/7827471791615340520?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/04_8ySkjg3I/socially-enabled-documentation-in-cloud.html" title="Socially Enabled Documentation in the Cloud: Dangerous, Benefits, Getting There" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh6.ggpht.com/-P8FiIVJg6Cs/To3Q--GR7PI/AAAAAAAAAHU/qJ5CQ-tBMTw/s72-c/community_copyright_free_thumb%25255B2%25255D.jpg?imgmax=800" height="72" width="72" /><thr:total>2</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/10/socially-enabled-documentation-in-cloud.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEMAQno5fip7ImA9WhdVGUg.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-2405055656844848058</id><published>2011-09-24T12:38:00.002+02:00</published><updated>2011-09-25T15:14:03.426+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-09-25T15:14:03.426+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conference" /><category scheme="http://www.blogger.com/atom/ns#" term="content agility" /><category scheme="http://www.blogger.com/atom/ns#" term="technical communications" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><title>Mobile Content Busts Industry Silos</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
For me &lt;a href="http://lessworkmoreflow.blogspot.com/2011/09/cs-forum-2011-afterthoughts.html"&gt;CS Forum&lt;/a&gt; made the penny drop for the “Why now?” question.&lt;br /&gt;
&lt;br /&gt;
We’ve been harping on about the importance of product information and separating content from format for years. Why is everyone listening all of a sudden? Methinks it’s mobile.&lt;br /&gt;
&lt;br /&gt;
When the web and CD-roms hit the documentation community we suddenly had a second format to which all our content just&amp;nbsp;&lt;em&gt;had&lt;/em&gt;&amp;nbsp;to go.&lt;br /&gt;
&lt;br /&gt;
Print content was not good enough anymore.&amp;nbsp; Content needed to be single-source, multiple output. Heads and tears rolled aplenty. It was an agonizing and painful lesson that some companies are still grappling with today, some two decades later.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://commons.wikimedia.org/wiki/File:Mobile_phone_evolution.jpg" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;" title="By Anders (Own work) [Public domain], via Wikimedia Commons"&gt;&lt;img alt="Mobile phone evolution" height="400" src="//upload.wikimedia.org/wikipedia/commons/thumb/d/d6/Mobile_phone_evolution.jpg/240px-Mobile_phone_evolution.jpg" width="266" /&gt;&lt;/a&gt;&lt;br /&gt;
Since then we’ve had a whole generation of professionals who grew up fully on the web, considering the browser and the personal computer to be&amp;nbsp;&lt;u&gt;the&lt;/u&gt;&amp;nbsp;way to access information. A new monotheism for content.&amp;nbsp; Progress was over and nothing could ever be cooler than accessing content on your computer, it was just matter of refining how.&lt;br /&gt;
&lt;br /&gt;
Until mobile.&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;
Thank you Apple for the iPhone&lt;/h2&gt;
&lt;br /&gt;
&lt;br /&gt;
As much as I am not a fan of Apple or their products, they have lots of things for which I respect them. High on the list is that they seriously took mobile devices mainstream. There’s a whole ecosystem of Android based devices (currently whipping their asses – burn!) specifically because Apple took smart phones from “nerd toy” territory to “normal phone”. Then they had the brainwave to say: “Tablets aren’t skinny crippled laptops, they’re big (crippled) phones!”&lt;br /&gt;
&lt;br /&gt;
Now we all know how to use tablets, even if we’ve never picked one up.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;
    We Are Not Alone&lt;/h2&gt;
&lt;br /&gt;
&lt;br /&gt;
Mobile internet access is overtaking desktop-based access as our primary way of getting information (&lt;a href="http://bit.ly/mobvsdesk"&gt;http://bit.ly/mobvsdesk&lt;/a&gt;).&lt;br /&gt;
&lt;br /&gt;
Mobile and its nasty combination of “little website” and “web app” modalities has given the web community a running kick to the tenders, just like the internet gave us way back when.&lt;br /&gt;
&lt;br /&gt;
Suddenly, single source, multiple output and separation of form and content look really interesting.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://twitter.com/nozurbina"&gt;&lt;img alt="By: TwitterButtons.com" border="0" height="22" src="http://www.twitterbuttons.com/upload/images/6a2fe834b0twitter-wb-fm.png" title="Follow Noz Urbina on Twitter" width="72.25" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-2405055656844848058?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=9DtLM9rMzb8:wH3BgaNrauk:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=9DtLM9rMzb8:wH3BgaNrauk:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=9DtLM9rMzb8:wH3BgaNrauk:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=9DtLM9rMzb8:wH3BgaNrauk:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=9DtLM9rMzb8:wH3BgaNrauk:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=9DtLM9rMzb8:wH3BgaNrauk:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=9DtLM9rMzb8:wH3BgaNrauk:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=9DtLM9rMzb8:wH3BgaNrauk:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=9DtLM9rMzb8:wH3BgaNrauk:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=9DtLM9rMzb8:wH3BgaNrauk:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=9DtLM9rMzb8:wH3BgaNrauk:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=9DtLM9rMzb8:wH3BgaNrauk:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/9DtLM9rMzb8" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/2405055656844848058/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/09/mobile-content-busts-industry-silos.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/2405055656844848058?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/2405055656844848058?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/9DtLM9rMzb8/mobile-content-busts-industry-silos.html" title="Mobile Content Busts Industry Silos" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/09/mobile-content-busts-industry-silos.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkMMQHo9eip7ImA9WhdVGEs.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-1465643482241038042</id><published>2011-09-24T01:27:00.001+02:00</published><updated>2011-09-24T12:34:41.462+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-09-24T12:34:41.462+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conference" /><category scheme="http://www.blogger.com/atom/ns#" term="technical communications" /><category scheme="http://www.blogger.com/atom/ns#" term="techcomm" /><category scheme="http://www.blogger.com/atom/ns#" term="content management" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><title>Information Beats Persuasion: CS Forum 2011 Afterthoughts</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
&lt;br /&gt;
&lt;img align="left" border="0" height="134" src="http://1.bp.blogspot.com/-076O4QAEphA/Tn0VMATUYeI/AAAAAAAAAHM/pBYNQkopS_M/s200/csf.JPG" style="display: inline; margin-bottom: 10px; margin-left: 10px; margin-right: 10px; margin-top: 0px;" width="200" /&gt;I spoke at CS Forum earlier this month on Content Strategy.&lt;br /&gt;
&lt;br /&gt;
My presentation title (suck as it did) was "B2B Content Strategy: &lt;a href="http://2011.csforum.eu/topics/technology#urbina"&gt;How to create company- and customer-focused content&lt;/a&gt;".&amp;nbsp; Terrible.&amp;nbsp; But still, people seemed to see through that and show up.&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Here's my feelings on, and inspired by, the event:&lt;br /&gt;
&lt;br /&gt;
I liked &lt;a href="http://2011.csforum.eu/"&gt;CS Forum&lt;/a&gt; a lot. Like, a &lt;i&gt;lot&lt;/i&gt;.&amp;nbsp; It was definitely eye opening!&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;

People Are Getting Enable vs. Persuade&lt;/h2&gt;
&lt;br /&gt;
My most epic of blog of all time addressed the landmark case of &lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-4.html"&gt;Enable vs. Persuade&lt;/a&gt;, aka &lt;a href="file:///C:/Users/Noz/AppData/Roaming/Microsoft/Word/lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide.html"&gt;MarComm vs TechComm&lt;/a&gt;. Summarising 3000+ words into much fewer: &lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;Focus first on helping people do what &lt;i&gt;they&lt;/i&gt; want, and they’ll do what &lt;i&gt;you&lt;/i&gt; want.&lt;/strong&gt;&lt;br /&gt;
&lt;strong&gt;&lt;br /&gt;&lt;/strong&gt;&lt;br /&gt;
Check this post from just today on the CS Google Group by Ian Waugh entitled, “Product 'support' content as marketing/sales”:&lt;br /&gt;
&lt;br /&gt;
“Wonder if you can help me? I've heard and read a couple of things recently about the benefits of providing support content like a PDF manual as part of a product description page in an ecommerce site, and the effect that it can have on sales.&lt;br /&gt;
&lt;br /&gt;
I agree with this intuitively, I know I have bought products after looking at the user manual before purchase.     &lt;br /&gt;
Guess it fits in with the whole "information beats persuasion" kind of approach.”&lt;br /&gt;
&lt;br /&gt;
"Information beats persuasion" Wow. So, 3000+ words down to 3. Good ratio. &lt;br /&gt;
&lt;br /&gt;
For me reading emails like this is like being handed water after running a marathon that lasted 11 years.&lt;br /&gt;
&lt;br /&gt;
Now, there are many more people than I’d have imagined in the web content strategy community who are thinking about this stuff. They’re considering the overlap and touch-points between web/marketing content strategy and, for lack of a better description the "format agnostic" and “product content-centric” content strategy on which I focus. &lt;br /&gt;
&lt;br /&gt;
If they weren't thinking about it before CS Forum, they were thinking about it after.&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;

  Killer Keynotes&lt;/h2&gt;
&lt;br /&gt;
Both of the first keynote talks - &lt;a href="http://2011.csforum.eu/speakers/mcgovern"&gt;Gerry McGovern&lt;/a&gt; and &lt;a href="http://2011.csforum.eu/speakers/mcgrane"&gt;Karen McGrane&lt;/a&gt; - were dead on.&amp;nbsp; They talked about task orientation, technical information and its role in the (modern, online) sales cycle. My favourite quote of the conference was Gerry's: &lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;
"The content that use to come after the sale, is now driving the sale".&amp;nbsp;&lt;/blockquote&gt;
Karen even specifically did us a shout-out by name: &lt;br /&gt;
&lt;blockquote&gt;
"The Techcomm folks have been doing this stuff [that we in the rest of the CS world need to do] for years. We need to engage with them."&amp;nbsp; &lt;/blockquote&gt;
She talked about a "Content API" which was like a CMS which can content to any format you want, even ones that have not been invented yet, and allow mash-ups of content to any device easily and quickly.&amp;nbsp; &lt;br /&gt;
I realised that that was not a normal thing at this event.&amp;nbsp; This was a conference where CMSs publish to one format/channel: the web.&amp;nbsp; The extra fancy super-duper ones will do multi-language and serve up your mobile site.&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
The stuff our customers bang on us for, was a bridge way too far. Stuf like: &lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Generating content that goes to offline-capable mobile apps&lt;/li&gt;
&lt;li&gt;Delivering dynamically to user-driven, nicely formatted print-ready PDF&lt;/li&gt;
&lt;li&gt;Serving up content as a service to multiple internal and external websites&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
Just today I have a conf call about a customer who wants to move to publishing knowledge base content from one repository (authored by various flavours of support and service engineer) and standard content (written by technical authors and trainers) from another repository &lt;i&gt;inside &lt;/i&gt;their product itself.&amp;nbsp; &lt;br /&gt;
The products have sometimes PCs attached, and sometimes they have data screens (like the data dashboard console in newer cars).&amp;nbsp; Why not get some real, dynamic content in there?&amp;nbsp; &lt;a href="http://lessworkmoreflow.blogspot.com/2011/07/making-socially-enabled-help-better.html"&gt;Embedded, integrated, social content&lt;/a&gt;. &lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;

  Content Drives the Customer Experience&lt;/h2&gt;
&lt;br /&gt;
People are starting to realise that when you buy a TV for $800, you go online first - a lot - and when you do so, being told that it's "elegantly designed" and "sleek" is not compelling.&amp;nbsp; Being told it's got a USB port that can open those movies oh-so-legally downloaded is.&lt;br /&gt;
&lt;br /&gt;
You may not know what your TV being 100 megahertz or 50 megahertz means, but if you asked anyone (and you probably did) then you at least have a feeling of whether it’s a good thing or not. &lt;br /&gt;
&lt;br /&gt;
When it’s time to shop, it’s facts and product, not concepts or “brand messages” that you are seeking.&amp;nbsp; Brand messages aren’t dead, but everyone has to add “We’re here to enable you, not seduce you” to their core messages. &lt;br /&gt;
&lt;br /&gt;
To quote &lt;a href="http://www.fergusson.net/"&gt;a wise friend&lt;/a&gt;: &lt;br /&gt;
&lt;blockquote&gt;
“Content drives the customer experience”. &lt;/blockquote&gt;
To read more about how the web has had some fundamental flaws in how it evaluated itself, I suggest reading more on &lt;a href="http://www.gerrymcgovern.com/nt/2011/nt-2011-09-19-Help-people.htm"&gt;Gerry’s blog&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
So after my CS Forum experience, I repeat my call for collaboration to web CSs, UX people, and IAs. We’re here to help and learn from each other. You do things we don’t, and vice versa. Let’s chat and build some content applications that drive customer experiences.&lt;br /&gt;
&lt;br /&gt;
Has anyone other in the web community be thrust into a web project that’s pushed you out of your comfort zone? “After sales” material mixing in with your copy?&amp;nbsp; Apps? Print?&amp;nbsp; If so: &lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;How did it go?&lt;/li&gt;
&lt;li&gt;How did you handle keeping that all in sync with other deliverables? &lt;/li&gt;
&lt;li&gt;How did workflows, process and roles have to change vs. what you’re used to?&lt;/li&gt;
&lt;li&gt;How did management envision all this and what drove the new approach?&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
I’m been hearing experiences from the other side of the fence and I’m looking forward to more stories!&lt;/div&gt;
&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-1465643482241038042?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=qR3aVz8Fp2c:cqwzaAVioYQ:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=qR3aVz8Fp2c:cqwzaAVioYQ:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=qR3aVz8Fp2c:cqwzaAVioYQ:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=qR3aVz8Fp2c:cqwzaAVioYQ:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=qR3aVz8Fp2c:cqwzaAVioYQ:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=qR3aVz8Fp2c:cqwzaAVioYQ:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=qR3aVz8Fp2c:cqwzaAVioYQ:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=qR3aVz8Fp2c:cqwzaAVioYQ:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=qR3aVz8Fp2c:cqwzaAVioYQ:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=qR3aVz8Fp2c:cqwzaAVioYQ:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=qR3aVz8Fp2c:cqwzaAVioYQ:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=qR3aVz8Fp2c:cqwzaAVioYQ:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/qR3aVz8Fp2c" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/1465643482241038042/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/09/cs-forum-2011-afterthoughts.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/1465643482241038042?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/1465643482241038042?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/qR3aVz8Fp2c/cs-forum-2011-afterthoughts.html" title="Information Beats Persuasion: CS Forum 2011 Afterthoughts" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-076O4QAEphA/Tn0VMATUYeI/AAAAAAAAAHM/pBYNQkopS_M/s72-c/csf.JPG" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/09/cs-forum-2011-afterthoughts.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ak8GRn4zeCp7ImA9WhdSE0w.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-97825175696802141</id><published>2011-07-20T11:23:00.011+02:00</published><updated>2011-07-22T09:13:47.080+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-22T09:13:47.080+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="tech docs" /><category scheme="http://www.blogger.com/atom/ns#" term="help" /><category scheme="http://www.blogger.com/atom/ns#" term="technical communications" /><category scheme="http://www.blogger.com/atom/ns#" term="user assistance" /><category scheme="http://www.blogger.com/atom/ns#" term="techcomm" /><category scheme="http://www.blogger.com/atom/ns#" term="social media" /><category scheme="http://www.blogger.com/atom/ns#" term="content reuse" /><category scheme="http://www.blogger.com/atom/ns#" term="metadata" /><category scheme="http://www.blogger.com/atom/ns#" term="content management" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><title>Making Socially Enabled User Assistance Better– “Help” vs. ”HEEELP!”</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
Someone posted to the Content Strategy Google Group asking about Help content.&amp;nbsp; I didn’t have a lot of time so I pinged over my fav article going on Help these days: &lt;a href="http://thecontentwrangler.com/" target="_blank"&gt;Scott Abel&lt;/a&gt;’s &lt;a href="http://intercom.stc.org/2011/04/the-future-of-technical-communication-is-socially-enabled-understanding-the-help-2-0-revolution/" target="_blank"&gt;The Future of Technical Communication Is Socially Enabled: Understanding the Help 2.0 Revolution&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
Then I did a runner… &lt;br /&gt;
&lt;br /&gt;
Since, &lt;a href="http://usabilitytestinghowto.blogspot.com/" target="_blank"&gt;Dana Chisnell&lt;/a&gt; then challenged me: &lt;br /&gt;
&lt;quote&gt; &lt;/quote&gt;&lt;br /&gt;
&lt;blockquote&gt;
Why are you providing help? Any time you have a separate system for the help, you're in trouble. Embedding the assistance in the UI and surfacing it when the user needs it will work much, much better.&lt;/blockquote&gt;
&lt;br /&gt;
Which is of course, preaching to the choir.&amp;nbsp; I couldn't be more in agreement.&amp;nbsp;&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Socially enabled&lt;i&gt; &lt;/i&gt;help almost immediately begets socially enabled &lt;i&gt;embedded&lt;/i&gt; help.&amp;nbsp; It's only logical, and it’s not even my idea, it’s already happening.&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Smart companies generally (regardless of social enablement) are bringing user assistance (the posh word for Help these days) into the UX and the UI, not making it retrospective.&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
On demand is good, but you want to assist users before they ‘demand’ it. In other words: Help should &lt;em&gt;help&lt;/em&gt;, not wait&amp;nbsp;until&amp;nbsp;the user needs&amp;nbsp;'HEEELLP!' (Tweet that, I dares ya!)&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;
















The Problem With The World Today&lt;/h2&gt;
&lt;br /&gt;
&lt;strong&gt;Today the user assistance UX story is:&lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
“What's that?&amp;nbsp; I can't figure out this UI! Now my User Experience is broken and I &lt;em&gt;hate&lt;/em&gt; this company! HEEELP!&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;It &lt;i&gt;should&lt;/i&gt; be:&lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
'What's that?' &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;em&gt;Helpful bit of content appears to the rescue!&lt;/em&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'Oh. Ok. Now back to what I was doing'&lt;br /&gt;
&lt;br /&gt;
I’m sure Scott’s probably got this in mind too as our brain children go to the same school of thought. It’s nice.&amp;nbsp; Lovely play areas and recess is 9 times a day.&amp;nbsp; And they serve the kids wine…&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;
















What you need to do&lt;/h2&gt;
&lt;br /&gt;
Anyway! If it wasn’t explicit enough, I’ll provide some detail (in my own words, so I don’t want anyone to think I’m speaking for Scott without permission).&amp;nbsp; Here’s Noz’s official to-do list for the Help World:&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Help needs to be socially enabled (Scott’s &lt;a href="http://intercom.stc.org/2011/04/the-future-of-technical-communication-is-socially-enabled-understanding-the-help-2-0-revolution/" target="_blank"&gt;already broke it down for you&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Help content needs to be brought into devices and UIs (hardware, software, website - whatever!) so that those with content skills work in harmonious partnership with those that have UI, UX and development skills.&amp;nbsp; &lt;/li&gt;
&lt;li&gt;The application assistance architecture should be socially extensible so that the social components of help integrate nicely with the brand-generated components&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
Here’s some examples of companies that have it part right:&lt;br /&gt;
&lt;h3&gt;
















&amp;nbsp;&lt;/h3&gt;
&lt;h3&gt;
















Adobe Photoshop Help Offline&lt;/h3&gt;
&lt;a href="http://lh3.ggpht.com/-CLlPdC_ZzWY/Tiaei3fdjfI/AAAAAAAAAGs/kslYidLLpHg/s1600-h/image%25255B8%25255D.png"&gt;&lt;img alt="image" border="0" height="227" src="http://lh5.ggpht.com/-kNURkGYZf1E/Tiaejcd5KDI/AAAAAAAAAGw/LG58lGcfUZA/image_thumb%25255B4%25255D.png?imgmax=800" style="background-image: none; border: 0px currentColor; display: inline; padding-left: 0px; padding-right: 0px; padding-top: 0px;" title="image" width="418" /&gt;&lt;/a&gt;&lt;br /&gt;
&lt;strong&gt;&lt;em&gt;Right-click and view/open in a new window to enlarge.&lt;/em&gt;&lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you’re offline, hit F1 in &lt;a href="http://www.adobe.com/products/photoshop.html" target="_blank"&gt;PS&lt;/a&gt; and you go to a html-based help file (html, running offline&amp;nbsp;from a folder on your computer).&amp;nbsp; Note the PDF link on top right!&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Defaultpagesayswhat? Community help!&amp;nbsp; In other words, to REALLY get the full experience, go online and join the party, silly!&lt;br /&gt;
&lt;h3&gt;
















Adobe Photoshop Help Online&lt;/h3&gt;
&lt;br /&gt;
Turn ye ol’ Net back on and Adobe takes you straight to a website that looks exactly the same, but new features abound!&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Feedback&lt;/li&gt;
&lt;li&gt;Options to search through help for other applications&lt;/li&gt;
&lt;li&gt;Still available as PDF! &lt;/li&gt;
&lt;li&gt;Community intro link available (blue, bottom left)&lt;/li&gt;
&lt;li&gt;Commenting&lt;/li&gt;
&lt;li&gt;Comments RSS feed (subscribe to this piece of content!)&lt;/li&gt;
&lt;li&gt;And so on… &lt;a href="http://help.adobe.com/en_US/Photoshop/11.0/index.html?trackingid=DYNQE" target="_blank"&gt;explore it&amp;nbsp;yourself&lt;/a&gt; for fun.&lt;/li&gt;
&lt;/ul&gt;
&lt;a href="http://lh5.ggpht.com/-zlHAx5UYLjs/TiaekEj2MZI/AAAAAAAAAG0/3338hiO4qmI/s1600-h/image%25255B14%25255D.png"&gt;&lt;img alt="image" border="0" height="570" src="http://lh3.ggpht.com/-7rm9Q-2bivU/TiaekpTuiMI/AAAAAAAAAG4/yND8X23z_mo/image_thumb%25255B8%25255D.png?imgmax=800" style="background-image: none; border: 0px currentColor; display: inline; padding-left: 0px; padding-right: 0px; padding-top: 0px;" title="image" width="419" /&gt;&lt;/a&gt;&lt;br /&gt;
&lt;strong&gt;&lt;em&gt;Right-click and view/open in a new window to enlarge.&lt;/em&gt;&lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Good, but could be better.&lt;br /&gt;
&lt;br /&gt;
Let’s compare with one of my favourite apps, &lt;a href="http://www.ableton.com/" target="_blank"&gt;Ableton Live&lt;/a&gt;:&lt;br /&gt;
&lt;h3&gt;
















&amp;nbsp;&lt;/h3&gt;
&lt;h3&gt;
















Ableton Live Context &lt;u&gt;Ultra-sensitive&lt;/u&gt; Help&lt;/h3&gt;
&lt;a href="http://lh3.ggpht.com/-v7qHzuGipXg/TiaelO7Eg4I/AAAAAAAAAG8/tFzVAD_37bQ/s1600-h/ableton%25255B4%25255D.jpg"&gt;&lt;img alt="ableton" border="0" height="222" src="http://lh5.ggpht.com/-LA8J7-cpwPA/TiaemABGybI/AAAAAAAAAHA/JBQXuXw2a7Q/ableton_thumb%25255B2%25255D.jpg?imgmax=800" style="background-image: none; border: 0px currentColor; display: inline; padding-left: 0px; padding-right: 0px; padding-top: 0px;" title="ableton" width="411" /&gt;&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;&lt;em&gt;Right-click and view/open in a new window to enlarge.&lt;/em&gt;&lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In Ableton, help is in panes &lt;em&gt;within&lt;/em&gt; the UI.&amp;nbsp; Once you’re experienced user, you hide them both away and only bring them back as needed.  &lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Big stuff like tutorials, walkthroughs, set-up instructions, is on the right in the main help pane (F1).&lt;/li&gt;
&lt;li&gt;Bottom left we have a little hide-able pane that constantly pops helpful information and short-cuts for ANYTHING I hover my mouse over (the 'Live Device Browser' in this case).&amp;nbsp; That is to say, new users just leave that baby open, and you instantly know what every UI item works, and the short-cut for triggering it:&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;/ul&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;img border="0" height="518" src="http://2.bp.blogspot.com/-M5RdHuoWXhc/TigxjFIJ44I/AAAAAAAAAHE/yCYclhLNPNI/s1600/ableton-hover-pane.JPG" width="352" /&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Compare this to user's alternative workflow: &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'What's this? How do I use it?'&lt;br /&gt;
&lt;br /&gt;
&lt;em&gt;Learns how to use it is somehow. By looking it up?  Probably not...&lt;/em&gt;
&lt;br /&gt;
&lt;em&gt;Starts getting into productive work...&lt;/em&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'Showing and hiding this thing is annoying....&lt;br /&gt;
Hmmm...maybe there's a short-cut...?&lt;br /&gt;
Do I want to stop what I'm doing and look it up?&lt;br /&gt;
No.&lt;br /&gt;
Actually, yes... this &lt;u&gt;is&lt;/u&gt; annoying...I'll go look it up!'&lt;br /&gt;
&lt;br /&gt;
...and how mad are they going to be&amp;nbsp;if it turns out there is no short-cut after all?&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;
















The Promised Land&lt;/h2&gt;
&lt;br /&gt;
Of course, we should bring the two together, so that the web snazzies of Adobe’s help appear in the UI like Ableton.&amp;nbsp; In time dear friends, but fear not, that &lt;u&gt;is&lt;/u&gt; where we’re heading!&lt;br /&gt;
&lt;br /&gt;
Agree? Disagree?&amp;nbsp; Let me have it in the &lt;em&gt;socially-enabled&lt;/em&gt; comments!&lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-size: large;"&gt;UPDATE!&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
Dana pointed out I forgot to mention mobile devices and hit me with this great soundbite: &lt;br /&gt;
&lt;br /&gt;
"...we should all be thinking about what will work on the tiny screen that will scale up, not the other way around."&lt;br /&gt;
&lt;br /&gt;
I also forgot to mention: &lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Great help doesn't mean UI/UX designers can all start leaving work at 3pm! The idea is to avoid needing to get help in the first place, no matter how nicely it's delivered.&lt;/li&gt;
&lt;li&gt;Those implementing DITA or any other Component CMS platform should be thinking about how this social content gets round-tripped back into source so that the brand-sourced content, service desk knowledge-bases, intranets,&amp;nbsp;and the &lt;em&gt;product itself &lt;/em&gt;are all improved by leveraging the crowd's contributions.&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-97825175696802141?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=kyBzk4Yy0MY:oX8hH3niieM:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=kyBzk4Yy0MY:oX8hH3niieM:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=kyBzk4Yy0MY:oX8hH3niieM:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=kyBzk4Yy0MY:oX8hH3niieM:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=kyBzk4Yy0MY:oX8hH3niieM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=kyBzk4Yy0MY:oX8hH3niieM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=kyBzk4Yy0MY:oX8hH3niieM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=kyBzk4Yy0MY:oX8hH3niieM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=kyBzk4Yy0MY:oX8hH3niieM:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=kyBzk4Yy0MY:oX8hH3niieM:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=kyBzk4Yy0MY:oX8hH3niieM:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=kyBzk4Yy0MY:oX8hH3niieM:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/kyBzk4Yy0MY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/97825175696802141/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/07/making-socially-enabled-help-better.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/97825175696802141?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/97825175696802141?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/kyBzk4Yy0MY/making-socially-enabled-help-better.html" title="Making Socially Enabled User Assistance Better– “Help” vs. ”HEEELP!”" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh5.ggpht.com/-kNURkGYZf1E/Tiaejcd5KDI/AAAAAAAAAGw/LG58lGcfUZA/s72-c/image_thumb%25255B4%25255D.png?imgmax=800" height="72" width="72" /><thr:total>1</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/07/making-socially-enabled-help-better.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUcARXs9fSp7ImA9WhdSGUk.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-373324598169821616</id><published>2011-07-19T09:18:00.002+02:00</published><updated>2011-07-29T15:44:04.565+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-29T15:44:04.565+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="DITA" /><category scheme="http://www.blogger.com/atom/ns#" term="writing for reuse" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy audit" /><category scheme="http://www.blogger.com/atom/ns#" term="tech docs" /><category scheme="http://www.blogger.com/atom/ns#" term="technical communications" /><category scheme="http://www.blogger.com/atom/ns#" term="modular writing" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="congility 2011" /><category scheme="http://www.blogger.com/atom/ns#" term="darwin information typing architecture" /><category scheme="http://www.blogger.com/atom/ns#" term="congility" /><title>Time Go Bye Bye, DITA Training, Largest DITA Project Ever</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
Wow...&lt;br /&gt;
&lt;br /&gt;
&lt;div&gt;
&lt;/div&gt;
Time has just... &lt;em&gt;gone&lt;/em&gt;! &lt;br /&gt;
&lt;br /&gt;
&lt;div&gt;
&lt;/div&gt;
It seems like last week I was delivering my opening address, somewhat exhausted, at &lt;a href="http://www.congility.com/2011"&gt;Congility 2011&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;div&gt;
&lt;/div&gt;
The event wasn't even over and we were letting people know about the DITA Training courses on offer at &lt;a href="http://www.congility.com/south"&gt;Congility South&lt;/a&gt;.&amp;nbsp; Not to mention my having to prepare the course itself.&lt;br /&gt;
&lt;br /&gt;
&lt;div&gt;
&lt;/div&gt;
A heartbeat after I was whisked away to begin work&amp;nbsp;on what is one of the largest DITA Content Management projects of my career, and the biggest Content Technology Audit (CTA, similar to a Content Strategy Audit but systems-focussed) I've ever done.&amp;nbsp; They have&amp;nbsp;1000 (one THOUSAND) dedicated technical authors worldwide with 10,000 (you heard me) engineers looking to contribute natively into DITA topics.&amp;nbsp;&amp;nbsp; They said full roll-out numbers might be 30,000 users globally. If we opt to go for direct Engineer contributions, they will&amp;nbsp;have more DITA authors than most companies have staff!&lt;br /&gt;
&lt;br /&gt;
&lt;div&gt;
&lt;/div&gt;
Oh, and they're working off the file system - no CMS support.&lt;br /&gt;
&lt;br /&gt;
&lt;div&gt;
&lt;/div&gt;
&lt;h2&gt;




DITA Gone Wild&lt;/h2&gt;
&lt;br /&gt;
&lt;div&gt;
&lt;/div&gt;
It's been a fascinating example of DITA pushed to the limits.&amp;nbsp; They products are&amp;nbsp;set up in a 'platform&amp;gt;product' way where specific&amp;nbsp;products are built off the&amp;nbsp;platforms, so there is&amp;nbsp;extensive reuse.&amp;nbsp; But:&lt;br /&gt;
&lt;br /&gt;
&lt;div&gt;
&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;They various builds of the software run in parallel, meaning there's reuse from platforms but also any number of parallel builds of the software&lt;/li&gt;
&lt;li&gt;The need to keep maintaining all the various versions - current, plus 2 versions back&lt;/li&gt;
&lt;li&gt;They have to reuse extensively into training materials &lt;/li&gt;
&lt;li&gt;There's hardware too...&lt;/li&gt;
&lt;li&gt;Oh... and just for fun, it's full of client-specific stuff&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
They're handling this all with extensive branching and merging, and more conditions than I've ever seen.&amp;nbsp; They're conditionalising content by: &lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Version - because of all the branching and parallel development, different versions are considered different &lt;em&gt;products&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Audience - Including the employees, the public, and customers &lt;/li&gt;
&lt;li&gt;Outputclass: e.g., chm and pdf &lt;/li&gt;
&lt;li&gt;Platform - what base platform is the product derived from&lt;/li&gt;
&lt;/ul&gt;
&lt;div&gt;
&lt;br /&gt;
Single lines like 'The XYZ product can boil a chicken in 5 minutes if you press the "boil" button' might be conditionalised to the point where it can say:&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;The XYZ23 product can boil, or broil&amp;nbsp;a chicken in 5-10 minutes if you press the "cook" button&lt;/li&gt;
&lt;li&gt;The XYZ27 product can&amp;nbsp;cook a chicken in&amp;nbsp;15 minutes automatically&lt;/li&gt;
&lt;li&gt;The ABC123 product can boil a turkey in&amp;nbsp;20 minutes if you press the "boil" button&lt;/li&gt;
&lt;li&gt;The 321CBA product can nuke a turkey, squab or chicken if you press the "Angry birds" button&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
And so on, and so on and so on aaand so on...&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Imagine working on the sentences while looking at a document module (DITA Topic) where all that&amp;nbsp;is&amp;nbsp;being expressed &lt;em&gt;&lt;u&gt;simultaneously.&lt;/u&gt;&lt;/em&gt;&amp;nbsp;and then sharing modules like that that were created by other people for use in &lt;em&gt;your&lt;/em&gt; documents.&amp;nbsp; Without a database...&lt;br /&gt;
&lt;br /&gt;
What is amazing is how well they're managing.&amp;nbsp; I have amazing respect for what they've already accomplished.&amp;nbsp; Now they've asked for help to go from managing to optimising and really tuning for the customer's interests.&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
I'll let you know how we get on.&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Overall I'm really enthused by seeing such a huge DITA project be a success, and now, having the opportunity to help take it to the next level.&amp;nbsp; Lame, but that gives me the warm and squishies inside.&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;


Geek corner&lt;/h2&gt;
&lt;br /&gt;
For the nerds out there,&amp;nbsp;I'm seeing now just how interesting DITA Keys and Conkeyref are to the scalability of reuse, especially combined with Conditions.&amp;nbsp; I'm upping the focus on them significantly at Congility South.&lt;br /&gt;
&lt;br /&gt;
Also, I've finally got a little workshop together on Context-sensitive help in DITA.&amp;nbsp; I had a real developer build me an actual application that I can use to demonstrate the concepts and make new context sensitive help on the fly for various formats from DITA source&lt;br /&gt;
&lt;br /&gt;
Now I just need to work out how to use it to teach conditions as well... and make it call a website instead of a local help file...&lt;br /&gt;
&lt;br /&gt;
&lt;div&gt;
&amp;nbsp;&amp;nbsp;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;
&lt;/div&gt;
&lt;a href="http://twitter.com/nozurbina"&gt;&lt;img alt="By: TwitterButtons.com" border="0" height="22" src="http://www.twitterbuttons.com/upload/images/6a2fe834b0twitter-wb-fm.png" title="Follow Noz Urbina on Twitter" width="72" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-373324598169821616?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=01SWO8N3Oq0:M1E42_qvun4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=01SWO8N3Oq0:M1E42_qvun4:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=01SWO8N3Oq0:M1E42_qvun4:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=01SWO8N3Oq0:M1E42_qvun4:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=01SWO8N3Oq0:M1E42_qvun4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=01SWO8N3Oq0:M1E42_qvun4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=01SWO8N3Oq0:M1E42_qvun4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=01SWO8N3Oq0:M1E42_qvun4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=01SWO8N3Oq0:M1E42_qvun4:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=01SWO8N3Oq0:M1E42_qvun4:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=01SWO8N3Oq0:M1E42_qvun4:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=01SWO8N3Oq0:M1E42_qvun4:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/01SWO8N3Oq0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/373324598169821616/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/07/time-go-bye-bye-dita-training-largest.html#comment-form" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/373324598169821616?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/373324598169821616?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/01SWO8N3Oq0/time-go-bye-bye-dita-training-largest.html" title="Time Go Bye Bye, DITA Training, Largest DITA Project Ever" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><thr:total>4</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/07/time-go-bye-bye-dita-training-largest.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEQMRHk9eip7ImA9WhdWEk4.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-2456199676243378915</id><published>2011-05-14T11:56:00.004+02:00</published><updated>2011-09-05T17:26:25.762+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-09-05T17:26:25.762+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="tech docs" /><category scheme="http://www.blogger.com/atom/ns#" term="technical communications" /><category scheme="http://www.blogger.com/atom/ns#" term="techcomm" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><category scheme="http://www.blogger.com/atom/ns#" term="congility 2011" /><category scheme="http://www.blogger.com/atom/ns#" term="congility" /><title>When Content Strategies Collide Pt 6: Conclusion, Unification</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
&lt;i&gt;(Reposting this after it was deleted by Blogger’s maintenance update)&lt;/i&gt;&lt;br /&gt;
&lt;br /&gt;
I’ve harped about Marketing vs. Technical Communication Content Strategy in this wacky &lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide.html"&gt;World of Content&lt;/a&gt; for a while now.&amp;nbsp; The thesis in short is that we can and must integrate content strategy across these divisions for the sake of competitiveness and customer experience in the modern global market. &lt;br /&gt;
&lt;br /&gt;
Now here’s the wrap-up and what I think we should really be doing about it. Your comments have indicated that there are some glowing exceptions to the trend of separation, but that others feel the challenge is hopeless.&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
My final thoughts below, but here’s some links to the other posts: &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide.html"&gt;When Content Strategies Collide: Marketing versus Technical Communication&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-2.html"&gt;When Content Strategies Collide Pt 2: Customer Impact&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-3.html"&gt;When Content Strategies Collide Pt 3: War. Huh! What is it Good For?&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-4.html"&gt;When Content Strategies Collide Pt 4: Enabling vs. Persuasive Content&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-5-is.html"&gt;When Content Strategies Collide Pt 5: Is Communication Mired in the Past?&lt;/a&gt; &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;h2&gt;



Conclusion&lt;/h2&gt;
&lt;br /&gt;
Content Strategy is at the centre of debate right now, not only because it’s a buzzy term, but because it brings together content together with the bigger picture issues of planning and accountability.&amp;nbsp; It links in with the overarching business goals that will take content to its rightful place as a strategic asset in any organisation. &lt;br /&gt;
&lt;br /&gt;
Content Strategy unification, integration and sharing of standards.&amp;nbsp; Is it hopeless? No. Difficult? Yes. &lt;br /&gt;
Companies don’t get far in a globalising marketplace when we don’t even make strategic efforts to do things because they’re "hard".&amp;nbsp; We should be reassured more by our similarities than bothered by our differences. &lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Our customers will benefit most when we federate into a United Nations of Content, with common governance, standards, and practices which are tailored, as needed, for the business context.&lt;/b&gt;&lt;br /&gt;
&lt;b&gt;&amp;nbsp;&lt;/b&gt; &lt;br /&gt;
&lt;a href="http://lh6.ggpht.com/_nJ8XHcWrG0A/Tcuq3Gvm7yI/AAAAAAAAAGk/LkMPE76hjFw/s1600-h/2003-05-10%20Geneva%20Switzerland%200014%5B4%5D.jpg"&gt;&lt;img alt="2003-05-10 Geneva Switzerland 0014" border="0" height="422" src="http://lh6.ggpht.com/_nJ8XHcWrG0A/Tcuq3paUTgI/AAAAAAAAAGo/TzX_b5hoEbQ/2003-05-10%20Geneva%20Switzerland%200014_thumb%5B1%5D.jpg?imgmax=800" title="2003-05-10 Geneva Switzerland 0014" width="417" /&gt;&lt;/a&gt; &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We have much common ground to build on. In discussing this post with &lt;a href="http://thecontentwrangler.com/"&gt;Scott Abel&lt;/a&gt; he articulated quite nicely that content professionals share a baseline of skill-sets like: &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;analytical and structural thinking &lt;/li&gt;
&lt;li&gt;empathy for the user and usability sensibilities &lt;/li&gt;
&lt;li&gt;the ability to express oneself in words. &lt;/li&gt;
&lt;/ul&gt;
Everyone in this world of communications and content rallies behind (or should?) certain battles cries: &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Content is king &lt;/li&gt;
&lt;li&gt;Content is a strategic (critical) business asset &lt;/li&gt;
&lt;li&gt;Consistency helps us and helps customers understand and engage with us &lt;/li&gt;
&lt;li&gt;Business needs first, technology second &lt;/li&gt;
&lt;/ul&gt;
&lt;div align="left"&gt;
&lt;br /&gt;
&lt;a href="http://www.gollner.ca/" target="_blank"&gt;Joe Gollner&lt;/a&gt; wrote &lt;a href="http://thecontentwrangler.com/2011/01/15/the-emergence-of-intelligent-content/"&gt;on this blog&lt;/a&gt; recently and defined content quite nicely: that which goes in a container. This is most apt. If you’ve been following this series you know I am organising &lt;a href="http://www.congility.com/2011"&gt;Congility 2011&lt;/a&gt;. The "unwritten theme" is recognising that all content professionals are, in the end, concerned with how to best move those containers around amongst different formats, audiences and channels to best serve our customers and business goals. When it can, you can say your content has agility. &lt;/div&gt;
Once you are integrated and agile, we can break down silos in delivery as well as silos in the business, and that is really when the customer and therefore the revenue stream will see some effect.&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;



Giving the Customer What They Want&lt;/h2&gt;
&lt;br /&gt;
&lt;b&gt;The wisdom that content is king is second (in my mind) to the older wisdom: the customer’s always right. &lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
We’re designing customer experiences; not web pages, not manuals, not help files. &lt;br /&gt;
It’s about the customers and what they want to do, how they want to do it; not your content nor what you want them to do. They (may) want to buy your product, &lt;i&gt;if&lt;/i&gt; you show them properly why they should.&amp;nbsp; Especially true in the B2B space – putting meat behind the sizzle of communication is vital to engaging the modern mind. &lt;br /&gt;
&lt;br /&gt;
Users want answers to their product and technical questions fast and easily in the format that’s most convenient for &lt;i&gt;them&lt;/i&gt;.&amp;nbsp; Not just support post-sales questions, but presales curiosities and decision-making questions. Persuasion loses its effect if it is not backed up with enablement. &lt;br /&gt;
&lt;br /&gt;
I’ll dust off this same “&lt;i&gt;The Oatmeal&lt;/i&gt;” cartoon from a previous post: &lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://theoatmeal.com/comics/sell_generation"&gt;http://theoatmeal.com/comics/sell_generation&lt;/a&gt; &lt;br /&gt;
&lt;br /&gt;
It talks about how to sell to the new generation (but I don’t think that is generation just in age, this applies to the new generation of consumers). He pulls out three keywords; we must be: &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Sincere &lt;/li&gt;
&lt;li&gt;Helpful &lt;/li&gt;
&lt;li&gt;Knowledgeable &lt;/li&gt;
&lt;/ul&gt;
How are you &lt;i&gt;really&lt;/i&gt; going to be helpful and knowledgeable without closing the communications loop? &lt;br /&gt;
&lt;h3&gt;



Final thoughts for Web Content folk:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;You are less persuasive when you spend too much time focussed on persuading. &lt;/li&gt;
&lt;li&gt;When you’re selling technology products, the stuff that might bore you – like tables, specs, details, trouble-shooting, how-tos, and so forth – is often make or break to your customers. &lt;/li&gt;
&lt;li&gt;There are all sorts of skills and technologies already developed for technical content that do the things you want to do like control language, metadata style, presentation, and structure across multiple formats. Some may already be in your company. Go learn about them! &lt;/li&gt;
&lt;li&gt;There is a lot of process management experience and integration experience in the more forward thinking TechComms world. Each organisation moves at its own speed. Think of every organisation as being somewhere on a "Content Maturity Model" and check out the &lt;a href="http://www.x-pubs.com/site/dita_whitepaper_mm1-download/"&gt;DITA Maturity Model&lt;/a&gt;, or JoAnn Hackos’ &lt;a href="http://www.comtech-serv.com/pdfs/IPMM.pdf"&gt;Information Process Maturity Model&lt;/a&gt; as examples looking at how a large business can develop its content smarts. &lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;


&amp;nbsp;&lt;/h3&gt;
&lt;h3&gt;


Final thoughts for TCs:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;No matter how good your information is, if it’s still “the documentation”, then you will struggle to get it considered as a first port of call for users in trouble. Diversify your delivery methods to engage people across different media and models. &lt;/li&gt;
&lt;li&gt;You have so much more to offer the business than you may realise. Your skills are applicable to many business critical operations on both sides of the sales / pre-sales cycle. You know how to deal with ugly, complex content. Teach your colleagues and they will thank you. &lt;/li&gt;
&lt;li&gt;Social media a) has already impacted your career and your customer’s preferred way of ingesting information b) is your pipeline to the user feedback you’ve been denied all these years c) is more trusted than you are by an order of magnitude – you &lt;u&gt;can’t&lt;/u&gt; beat ‘em. Join ‘em. &lt;/li&gt;
&lt;li&gt;Search has changed everything. &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;h2&gt;



Your turn&lt;/h2&gt;
&lt;br /&gt;
I’m really interested in hearing the from “the exceptions” – people in the collaborative, integrated, standardised teams out there.&amp;nbsp; There’s been a few comments from those in shining star organisations, and some saying it’s hopeless and that the populations of these worlds could never produce ‘viable offspring’. &lt;br /&gt;
&lt;br /&gt;
Can we do it?&amp;nbsp; What are the half-measures in your opinion that get us at least on the road from point A to B?&amp;nbsp; Where does technology fit into all this?&lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-size: small;"&gt;See also:&lt;/span&gt; &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide.html"&gt;When Content Strategies Collide: Marketing versus Technical Communication&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-2.html"&gt;When Content Strategies Collide Pt 2: Customer Impact&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-3.html"&gt;When Content Strategies Collide Pt 3: War. Huh! What is it Good For?&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-4.html"&gt;When Content Strategies Collide Pt 4: Enabling vs. Persuasive Content&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-5-is.html"&gt;When Content Strategies Collide Pt 5: Is Communication Mired in the Past?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/05/when-content-strategies-collide-pt-6.html"&gt;When Content Strategies Collide Pt 6: Conclusion, Unification&lt;/a&gt;&amp;nbsp; &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-2456199676243378915?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=IBg3CTbXQbc:DkZl6Bi3JSY:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=IBg3CTbXQbc:DkZl6Bi3JSY:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=IBg3CTbXQbc:DkZl6Bi3JSY:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=IBg3CTbXQbc:DkZl6Bi3JSY:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=IBg3CTbXQbc:DkZl6Bi3JSY:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=IBg3CTbXQbc:DkZl6Bi3JSY:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=IBg3CTbXQbc:DkZl6Bi3JSY:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=IBg3CTbXQbc:DkZl6Bi3JSY:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=IBg3CTbXQbc:DkZl6Bi3JSY:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=IBg3CTbXQbc:DkZl6Bi3JSY:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=IBg3CTbXQbc:DkZl6Bi3JSY:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=IBg3CTbXQbc:DkZl6Bi3JSY:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/IBg3CTbXQbc" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/2456199676243378915/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/05/when-content-strategies-collide-pt-6.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/2456199676243378915?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/2456199676243378915?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/IBg3CTbXQbc/when-content-strategies-collide-pt-6.html" title="When Content Strategies Collide Pt 6: Conclusion, Unification" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh6.ggpht.com/_nJ8XHcWrG0A/Tcuq3paUTgI/AAAAAAAAAGo/TzX_b5hoEbQ/s72-c/2003-05-10%20Geneva%20Switzerland%200014_thumb%5B1%5D.jpg?imgmax=800" height="72" width="72" /><thr:total>1</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/05/when-content-strategies-collide-pt-6.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEcDRnkyeip7ImA9WhdWEk4.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-6595512861562380647</id><published>2011-04-27T19:13:00.001+02:00</published><updated>2011-09-05T17:21:17.792+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-09-05T17:21:17.792+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="tech docs" /><category scheme="http://www.blogger.com/atom/ns#" term="technical communications" /><category scheme="http://www.blogger.com/atom/ns#" term="techcomm" /><category scheme="http://www.blogger.com/atom/ns#" term="content reuse" /><category scheme="http://www.blogger.com/atom/ns#" term="content management" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><title>When Content Strategies Collide Pt 5: Is Communication Mired in the Past?</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
&lt;img align="left" height="185" src="http://farm4.static.flickr.com/3448/3289017683_3e636acf3a.jpg" style="display: inline; float: left; margin: 0px 10px 10px 0px;" width="188" /&gt;My biggest, and possibly most controversial, post to-date continues with responding to and extending the question – is TechComms mired in the past?&amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Yes. But we’re not alone.&amp;nbsp; Those of us in MarComms are at the beginning of a new dawn too.&amp;nbsp; If we’re in the the past, what does the future hold?&amp;nbsp; I take a little look at some cutting edge thinking… &lt;br /&gt;
&lt;a href="http://www.flickr.com/photos/craftydame/3289017683/#" target="_blank"&gt;&lt;sup&gt;&lt;/sup&gt;&lt;/a&gt;&lt;a href="http://www.flickr.com/photos/craftydame/3289017683/#" target="_blank"&gt;Typewriter image used under Creative Commons License&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-size: small;"&gt;See also:&lt;/span&gt; &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide.html"&gt;When Content Strategies Collide: Marketing versus Technical Communication&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-2.html"&gt;When Content Strategies Collide Pt 2: Customer Impact&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-3.html"&gt;When Content Strategies Collide Pt 3: War. Huh! What is it Good For?&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-4.html"&gt;When Content Strategies Collide Pt 4: Enabling vs. Persuasive Content&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-5-is.html"&gt;When Content Strategies Collide Pt 5: Is Communication Mired in the Past?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/05/when-content-strategies-collide-pt-6.html"&gt;When Content Strategies Collide Pt 6: Conclusion, Unification&lt;/a&gt;&amp;nbsp; &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;h2&gt;
Is TechComms mired in the past? Hell Yeah.&lt;/h2&gt;
&lt;br /&gt;
In &lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-2.html" target="_blank"&gt;Pt 2 of this series&lt;/a&gt;, we talked about Julie Norris’ mildly infamous comment about TechComms being mired in the past, and the voracious sh**storm that hit her after, causing her to erase the whole debacle from her blog (sadly). &lt;br /&gt;
&lt;br /&gt;
The only quote I managed to save from Julie’s blog was:&lt;br /&gt;
&lt;blockquote&gt;
“In any case, by “mired in the past” I mean a mindset that’s opposed to change, or trying new things. It’s not something new. I’ve seen it with every advance that’s come along in this industry, with every new method I’ve tried to help move along. I’m burned out with trying to explain to people the benefits of whatever is new, up-and-coming, or important to watch at the time.””&lt;/blockquote&gt;
&lt;br /&gt;
Hear, hear, Julie. There are loads of us behind you. Thought-leaders, consultants, leading bloggers and TechComms practitioners have felt the frustration of trying to move their peers in the TC community forward. &lt;br /&gt;
&lt;br /&gt;
I was on a call with &lt;a href="http://www.rockley.com/"&gt;Ann Rockley&lt;/a&gt; moments after reading the firestorm about Julie’s original post, so I raised the issues with her. We’re both agreed that it’s always been this way since we started in Technical Communications – back when it was called ‘Technical Documentation’.&lt;br /&gt;
&lt;br /&gt;
Ann noted that herself, Scott Abel, Rahel Bailie, and myself are all people who have, in her words, “Let but not left” – bridging the gap between the “world of TC” and the wider content community. TechComms is not to be left behind if you’re really promoting an integrated approach to content and customer experience. &lt;br /&gt;
&lt;h4&gt;
---------------------------&lt;/h4&gt;
&lt;h4&gt;
UPDATE (18:19 18/05/2011):&lt;/h4&gt;
Julie has commented on this post and &lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-2.html" target="_blank"&gt;part 2&lt;/a&gt; to point out an error.&amp;nbsp; Because I was not able to access her blog directly, I was left with the misinterpretation that she had in fact ‘left’ TechComms for pastures new.&amp;nbsp; The truth was that was refocusing her blog away from TechComms, but she is today and will continue to be a Technical Communications practitioner.&amp;nbsp; I have left the rest of the blog as was, because the key point is the reaction that the mere idea caused.&amp;nbsp; At Julie’s request I have included this point of fact that she has not ‘left’ at all.&amp;nbsp; Any words not quoted directly from her blog were my interpretation based on Tom Johnson’s post and the contents are not to be attributed to Julie herself.&lt;br /&gt;
&lt;h4&gt;
---------------------------&lt;/h4&gt;
&lt;br /&gt;
Scott pointed out a word of wisdom to me: “TechComms professionals should consider how having real-time analytics and unique IDs on every piece of content they create affects their process and measurements.” Seeing how content is used, shared, and consumed can help optimise and prioritise content and tasks. Why was this procedure shared or “favourited” fifty times, and this one twice?&lt;br /&gt;
&lt;br /&gt;
What does that say about the content, or even the product and its design?&lt;br /&gt;
&lt;br /&gt;
&lt;sup&gt;For more, see: &lt;a href="http://lessworkmoreflow.blogspot.com/2011/01/social-media-and-super-role-of.html"&gt;http://lessworkmoreflow.blogspot.com/2011/01/social-media-and-super-role-of.html&lt;/a&gt;&lt;/sup&gt;&lt;br /&gt;
&lt;br /&gt;
If you don’t have public facing documentation, what about socially enabling the intranet or secure customer extranet so that key clients, or your hundreds of support, services and engineering colleagues can give you feedback after the content goes live? Imagine. Well, we have the technology! These are the same SMEs who are always ignoring your requests for feedback and reviews before content release. Post-launch is not too late to fix things in the socially enabled web world.&lt;sup&gt;&lt;/sup&gt;&lt;br /&gt;
&lt;br /&gt;
But, TechComms aren’t the only group of Communications and Content folks mired in the past. We all are. If we’re only on the edge of major change with a clearly visible future, then we are all, ipso facto, living the past.&lt;br /&gt;
&lt;h2&gt;
Is MarComms Mired in the Past? Hell Yeah.&lt;/h2&gt;
&lt;br /&gt;
But I’d say less so.&lt;br /&gt;
&lt;br /&gt;
The web is fast and fickle.&lt;br /&gt;
&lt;br /&gt;
Web-oriented, and Marketing-oriented folks are ok with that. They’re ready to adopt whatever’s hot, leave behind what is not, and are generally vision-oriented, not detail oriented. In the Archipelago of Internet Marketing*, they quite enjoy the fluid flux and flow of web work and the instant gratification of metrics and analytics. It’s all a bit more easy-going on Ze Islands! Basically, they are committed to brand and see it as their responsibility to root out all threats to its global domination. If that includes support and technical content, so be it.&lt;br /&gt;
&lt;br /&gt;
&lt;sup&gt;*See &lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide.html" target="_blank"&gt;the first post in the series&lt;/a&gt;.&lt;/sup&gt;&lt;br /&gt;
&lt;br /&gt;
That said, there’s definitively lots of ‘mired in the past’ thinking. Often an Internet Marketing consultant comes in, maybe with their freshly minted Content Strategist passport, and is asked to look at a business problem. This involves the audiences, the workflows and of course the content. What &lt;i&gt;are&lt;/i&gt; we giving these people? Too often we’ll consider these issues with a marketing or brand bias, because of our backgrounds.&lt;br /&gt;
&lt;br /&gt;
Content can get neglected, or it’s assumed that needed content can come from the ‘usual’ content sources. Content that comes from deeper in the organisation (for example, technical content) is the harder content to get, and therefore the easiest content to neglect.&lt;br /&gt;
&lt;br /&gt;
If the content the people want is coming from technical communicators, then we have to find a way to deliver that isn’t shoving up a forum and a bunch of hard-to-index, hard-to-share PDFs on the site and calling it a ‘Knowledge and Support Centre’.&lt;br /&gt;
&lt;br /&gt;
I am still hearing a lot of agencies and consultants on the web-focussed side saying “My customer just wants to launch a website. They don’t want me complicating their lives”. Why should they change when the market is not asking for change?&amp;nbsp; How can you know how much &lt;i&gt;more &lt;/i&gt;effective you can be if you don’t have other companies to benchmark yourself against?&lt;br /&gt;
&lt;br /&gt;
Each consultant or software vendor is being engaged by one contact, with his or her own agenda, for his or her own department within the enterprise. Those individuals or teams are not pushing for integration the way they should be.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;The true work of Content Strategy – as a field – is not done until that market mentality changes, and organisations are &lt;i&gt;asking &lt;/i&gt;for unified, integrated content experiences for their customers. &lt;/b&gt;&lt;br /&gt;
&lt;h2&gt;
A Glimpse at the Future&lt;/h2&gt;
&lt;br /&gt;
So, what does it look like when marketing and technical mentalities collaborate? Here’s just &lt;i&gt;one&lt;/i&gt; example (I’d like to see more in the comments from all of you).&lt;br /&gt;
&lt;br /&gt;
Firefox has overtaken Internet Explorer as &lt;a href="http://mashable.com/2009/12/20/firefox-popular-browser/"&gt;the world’s leading Internet Browser&lt;/a&gt;. Look at the help content on their Sumo (&lt;u&gt;Su&lt;/u&gt;pport &lt;u&gt;Mo&lt;/u&gt;zilla) site. It’s something any communicator could love. It’s engaging, aesthetic, re-enforces brand values and is tuned for the audience.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://lh4.ggpht.com/_nJ8XHcWrG0A/TbhPVMp7DTI/AAAAAAAAAGc/l9YWnNnZV3A/s1600-h/clip_image002_thumb1%5B2%5D.jpg"&gt;&lt;img alt="clip_image002_thumb1" border="0" height="316" src="http://lh6.ggpht.com/_nJ8XHcWrG0A/TbhPVnJnkjI/AAAAAAAAAGg/tCENGEggE5E/clip_image002_thumb1_thumb.jpg?imgmax=800" style="background-image: none; border-bottom-width: 0px; border-left-width: 0px; border-right-width: 0px; border-top-width: 0px; display: inline; padding-left: 0px; padding-right: 0px; padding-top: 0px;" title="clip_image002_thumb1" width="420" /&gt;&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Note the stark contrast with a traditional manual or online help layout and feel. &lt;br /&gt;
Take this example of their help text (from the first link “How to set the home page”): &lt;br /&gt;
&lt;blockquote&gt;
&lt;b&gt;“Setting your home page in Firefox is easy.&lt;/b&gt; Can't decide on just one page? No problem. Firefox lets you set a group of websites as your home page.”&lt;/blockquote&gt;
Friendly, chatty, and although it’s direct and to the point, has some “unnecessary” words like “Can’t decide on just one page?” that are there to connect to the user. This combination of community forum, support, and technical documentation into a single platform has enabled technical content to be tracked and measured &lt;a href="http://support.mozilla.com/en-US/kb/Measuring%20knowledge%20base%20success"&gt;en masse&lt;/a&gt;, but also by the &lt;a href="http://support.mozilla.com/en-US/kb/Using%20poll%20data%20to%20judge%20your%20edits"&gt;individual author&lt;/a&gt; on their specific contributions. This is truly the best of all worlds.&lt;br /&gt;
&lt;br /&gt;
All this content is volunteer generated. Content professionals spend so long talking about how we should speak to users, this is an example of the users showing us exactly how they want to be spoken to. &lt;br /&gt;
&lt;br /&gt;
Part of what motivated this revolution in approach was: “Firefox quickly went from an early-adopters’ browser for the tech savvy (not because Firefox was hard to use, but because early adopters tend to have an affinity with technology) to a mainstream browser used by everyone.” They weren’t appealing to geeks anymore, and had to take on some slick marketing-esque techniques to make things work for the mainstream.&lt;br /&gt;
&lt;br /&gt;
This line from their “Scope” topic &lt;a href="http://dev.tiki.org/SUMO+Tiki+differences+and+similarities"&gt;discussing Sumo&lt;/a&gt; sums up the connection between content of this type, and revenue nicely:&lt;br /&gt;
&lt;blockquote&gt;
“Firefox is one of the rare and probably the only open source project of this magnitude that has a business model. More Firefox users = More money for Firefox.”&lt;/blockquote&gt;
&lt;br /&gt;
They’ve embraced social technical content, with an aim to improve experience and revenues, and they have the metrics to prove it was a success.&lt;br /&gt;
&lt;br /&gt;
To some extent, this is like &lt;a href="http://en.wikipedia.org/wiki/Gamification" target="_blank"&gt;gamification&lt;/a&gt; - i.e. rewarding positive acts with "points", levels and social recognition among peers.&lt;br /&gt;
&lt;br /&gt;
Firefox are &lt;i&gt;of course&lt;/i&gt; piping their support out through &lt;a href="http://blog.mozilla.com/sumo/2010/04/19/beyond-sumo-reaching-out-to-twitter-users/"&gt;Twitter&lt;/a&gt; and &lt;a href="http://blog.mozilla.com/sumo/2010/11/09/beyond-the-ordinary-reaching-out-to-facebook-users/"&gt;Facebook&lt;/a&gt; as well.&lt;br /&gt;
&lt;br /&gt;
&lt;sup&gt;For more see: &lt;a href="http://blog.mozilla.com/sumo/2009/03/30/the-road-to-sumo-in-retrospect/"&gt;http://blog.mozilla.com/sumo/2009/03/30/the-road-to-sumo-in-retrospect/&lt;/a&gt;&lt;/sup&gt;&lt;br /&gt;
&lt;br /&gt;
People today (ask everyone you know who doesn’t know you’re a tech author) want to type a few words into a web page and be gratified ASAP. But, can every product be supported by online social platforms, or Twitter and Facebook &lt;i&gt;specifically&lt;/i&gt;? No. Heck, some products still need printed manuals, because that’s the nature of their business context. Every communicator needs to explore how some new interaction models apply to their users and context, and assess if they’re still delivering the best possible communication service.&lt;br /&gt;
&lt;br /&gt;
Do all products even need “technical content”? No. I’ve never read a manual for a piece of clothing, or a hotel package, but some of the websites that sold them to me might need some good guidance information to make the usable. Technical Communications aren’t just the failure of good design. Don’t think of them as a recourse, but as an asset.&lt;br /&gt;
&lt;br /&gt;
&lt;span style="background-color: yellow;"&gt;&lt;b&gt;&lt;/b&gt;&lt;/span&gt;&lt;b&gt;In the next and final chapter, we wrap up and I solicit those exceptions that prove the rule*.&amp;nbsp;&amp;nbsp;&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
*Don’t you just love that expression?&amp;nbsp; So delightfully nonsensical…&lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-size: small;"&gt;See also:&lt;/span&gt; &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide.html"&gt;When Content Strategies Collide: Marketing versus Technical Communication&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-2.html"&gt;When Content Strategies Collide Pt 2: Customer Impact&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-3.html"&gt;When Content Strategies Collide Pt 3: War. Huh! What is it Good For?&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-4.html"&gt;When Content Strategies Collide Pt 4: Enabling vs. Persuasive Content&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-5-is.html"&gt;When Content Strategies Collide Pt 5: Is Communication Mired in the Past?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/05/when-content-strategies-collide-pt-6.html"&gt;When Content Strategies Collide Pt 6: Conclusion, Unification&lt;/a&gt;&amp;nbsp; &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;span style="background-color: yellow;"&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-6595512861562380647?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=KrU25JGUK4A:p1YZ-3uGj7Y:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=KrU25JGUK4A:p1YZ-3uGj7Y:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=KrU25JGUK4A:p1YZ-3uGj7Y:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=KrU25JGUK4A:p1YZ-3uGj7Y:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=KrU25JGUK4A:p1YZ-3uGj7Y:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=KrU25JGUK4A:p1YZ-3uGj7Y:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=KrU25JGUK4A:p1YZ-3uGj7Y:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=KrU25JGUK4A:p1YZ-3uGj7Y:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=KrU25JGUK4A:p1YZ-3uGj7Y:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=KrU25JGUK4A:p1YZ-3uGj7Y:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=KrU25JGUK4A:p1YZ-3uGj7Y:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=KrU25JGUK4A:p1YZ-3uGj7Y:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/KrU25JGUK4A" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/6595512861562380647/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-5-is.html#comment-form" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/6595512861562380647?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/6595512861562380647?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/KrU25JGUK4A/when-content-strategies-collide-pt-5-is.html" title="When Content Strategies Collide Pt 5: Is Communication Mired in the Past?" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://farm4.static.flickr.com/3448/3289017683_3e636acf3a_t.jpg" height="72" width="72" /><thr:total>3</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-5-is.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEAHR3w7fyp7ImA9WhZQFEg.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-730364320566608678</id><published>2011-04-21T09:18:00.000+02:00</published><updated>2011-04-22T09:18:56.207+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-04-22T09:18:56.207+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="DITA" /><category scheme="http://www.blogger.com/atom/ns#" term="tech docs" /><category scheme="http://www.blogger.com/atom/ns#" term="technical communications" /><category scheme="http://www.blogger.com/atom/ns#" term="localisation" /><category scheme="http://www.blogger.com/atom/ns#" term="techcomm" /><category scheme="http://www.blogger.com/atom/ns#" term="social media" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><title>When Content Strategies Collide Pt 4: Enabling vs. Persuasive Content</title><content type="html">&lt;p&gt;&lt;font style="background-color: #ffffff"&gt;&lt;/font&gt;Part 4 of my post comparing Marketing Content Strategy vs. Technical Communication Content Strategy.&amp;#160; A love letter to the community and a petition that yes, we can all just get along… even if we have several valid and deeply rooted differences.&amp;#160; &lt;/p&gt;  &lt;p&gt;We’ve started with the World of Content: the virtual geographic landscape where content flows like water through various channels and lines, digital and otherwise.&amp;#160; Then the customer – the one who suffers our divide, and then looked at the nature of what separates us.&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide.html"&gt;When Content Strategies Collide: Marketing versus Technical Communication&lt;/a&gt; &lt;/li&gt;    &lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-2.html"&gt;When Content Strategies Collide Pt 2: Customer Impact&lt;/a&gt; &lt;/li&gt;    &lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-3.html"&gt;When Content Strategies Collide Pt 3: War. Huh! What is it Good For?&lt;/a&gt; &lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;Now going into the cultural differences and ‘geographic’ differences between marketing and technical content strategy.&lt;/p&gt;  &lt;h2&gt;Cultural Divide&lt;/h2&gt;  &lt;p&gt;Supporting vs. Leading, Proven and Familiar vs. New and Sexy…&lt;/p&gt;  &lt;p&gt;As far as I’m concerned, the most powerful thing that divides the content world is simple: “persuasive” vs. “enabling” content. Everything from the most technical – technical data specifications – to the most persuasive – ad copy, is all content that touches the customer. So you have:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;Persuasive – Content that leads the customer to &lt;i&gt;your&lt;/i&gt; goals – the usual goal is that they buy stuff, or, promote your brand so that their peers buy stuff. When planning and creating this content there’s lots of talk of brand messages, engaging with the brand, calls to action, conversion rates, and so on. It’s front-line web pages, mailer content, ad copy, brochure copy, and the like. &lt;/li&gt;    &lt;li&gt;Enabling – Content that supports the customer in &lt;i&gt;their&lt;/i&gt; goals. Here we’ve got manuals, tech specs, help, forums, self-serve support materials. &lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;&lt;sup&gt;I also discuss this on a &lt;a href="http://idratherbewriting.com/2011/04/05/podcast-content-strategy-and-agility-with-noz-urbina/" target="_blank"&gt;podcast&lt;/a&gt; on &lt;a href="http://idratherbewriting.com/" target="_blank"&gt;Idwratherbewriting.com&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;  &lt;p&gt;Again, when these two content areas aren’t in synch, you get negatively impacted customer experience. No one in the World of Content wants the content consumers to have a bad experience.&lt;/p&gt;  &lt;p&gt;&lt;a href="http://lh3.ggpht.com/_nJ8XHcWrG0A/Ta_3Pbv6goI/AAAAAAAAAGU/1TRmHPaoYP4/s1600-h/cherry-layer-cake%5B3%5D.jpg"&gt;&lt;img style="background-image: none; border-right-width: 0px; margin: 0px 10px 10px 0px; padding-left: 0px; padding-right: 0px; display: inline; float: left; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px; padding-top: 0px" title="cherry-layer-cake" border="0" alt="cherry-layer-cake" align="left" src="http://lh5.ggpht.com/_nJ8XHcWrG0A/Ta_3QH9VFKI/AAAAAAAAAGY/01dJGiwjALs/cherry-layer-cake_thumb%5B1%5D.jpg?imgmax=800" width="182" height="181" /&gt;&lt;/a&gt;Rahel put it very well on &lt;a href="http://intentionaldesign.ca/page/4/"&gt;her blog&lt;/a&gt;:&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;I would argue that, despite the perception that websites consist of marketing content, for many sites, the marketing content is only the top layer – the icing on the cake, and what supports that top layer is a substantial amount of technical content – the cake itself. &lt;/p&gt; &lt;/blockquote&gt;  &lt;br /&gt;  &lt;p&gt;&lt;sup&gt;&lt;a href="http://www.freedigitalphotos.net/images/view_photog.php?photogid=151"&gt;Image: Suat Eman / FreeDigitalPhotos.net&lt;/a&gt; Note: Nerd that I am, I took 45 minutes to choose this cake.&amp;#160; I like it because the icing layer also shares content with the cake layers below, just more pretty and glossy-like.&amp;#160; : D&lt;/sup&gt;&lt;/p&gt;  &lt;p&gt;That technical content is often far more valuable to the corporate or product brand than the persuasive content. In doing user research for one client in particular, a manufacturer of power generators and inverters, I saw how guys used their site. Consistently, they would bypass all of the marketing material and go right for the specs. (Of course, before the site revamp, a lot of the specs were missing or buried in a PDF in some obscure area of the site…)”&lt;/p&gt;  &lt;p&gt;&lt;a href="http://www.congility.com/site/speaker_detail/bredenkamp" target="_blank"&gt;Andrew Bredenkamp&lt;/a&gt;, CEO of &lt;a href="http://www.acrolinx.com" target="_blank"&gt;acrolinx&lt;/a&gt; – a product that has been very successful in major TechComms organisations helping people control their language, keep to a corporate terminology base and monitor style and writing, was &lt;a href="http://blogs.acrolinx.com/andrew/2010/12/13/it_s_all_about_words/"&gt;recently blogging&lt;/a&gt; about how all these things apply to web marketing’s baby: SEO.&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;…what was most interesting talking to people in the Marketing space, and especially SEO, was how familiar the issues were to me. I kept hearing words like “shared vocabulary”, “establishing brand voice and style”, and *everyone* was talking about keywords and keyword research.&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;So, same tools, same drivers, different application and different content professionals benefiting. Web marketing folks: think about it. You might have already bought something in your organisation that helps you automatically police style and word usage on your website, or many other things you’re looking to do but don’t know how.&lt;/p&gt;  &lt;p&gt;Generally, there’s divisive attitudes about new technologies and content channels. For example, XML and DITA are often considered scary, “techie” and complex by the web marketing world, whereas Social Media is often, unfortunately, considered frivolous and irrelevant by the TechComms world.&lt;/p&gt;  &lt;p&gt;&lt;sup&gt;Related article on social media and TechComms &lt;a href="http://lessworkmoreflow.blogspot.com/2011/01/social-media-and-super-role-of.html" target="_blank"&gt;available here&lt;/a&gt;.&lt;/sup&gt;&lt;/p&gt;  &lt;h2&gt;Geography &lt;/h2&gt;  &lt;p&gt;MarComms and TechComms generally exist on different branches of the org chart and generally, in the product life cycle. Marketing kicks into gear mostly late, when there’s something they can start to make noise about. TechComms wants to be integrated as early as possible into the product development cycle. To have the content ready for launch, they need lots of warning and lead time.&lt;/p&gt;  &lt;p&gt;I’m going to stretch my analogy a bit here and include some real geography and another continental crash: the one of east meets west. The western world is hotly debating what will happen when Asia “hits”, and global competition ratchets up several notches. &lt;/p&gt;  &lt;p&gt;For MarComms, we all keep getting reminded that the west will need to compete on service and brand, as price and even product quality can be duplicated more easily. TechComms is an asset here. By integrating processes with the other organisations, you have:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;Keyword rich information (it’s all about the product and related ideas) &lt;/li&gt;    &lt;li&gt;Content that many customers really, really want &lt;/li&gt;    &lt;li&gt;Content that helps do things like seed forums and that can sit side-by-side with user generated content &lt;/li&gt;    &lt;li&gt;A differentiator that supports your after sales experience, and therefore customer experience and brand &lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;If TechComms provides you content that solves users’ problems, and other users can see that, share it, and help their friends solve their problems, then you’re cultivating happier customers.&lt;/p&gt;  &lt;h3&gt;For TechComms, globalisation REALLY matters&lt;/h3&gt;  &lt;p&gt;I live in Spain. I buy far more products than I used to that are made in countries where English isn’t the native language. As globalisation increases, I’m going to get even more clunky and/or badly translated manuals under my nose than before (the current crop are often hilarious). As a result, my inclination to bother even &lt;i&gt;opening&lt;/i&gt; them to check if that &lt;i&gt;particular&lt;/i&gt; company delivers good content is going to get smaller and smaller.&lt;/p&gt;  &lt;p&gt;We’ve been begrudgingly discussing the comment “No one wants to read the manual” for years. Add the content of a new, non-native English, non-EU economy’s to the landscape. Now they REALLY don’t want to! At least not in its traditional manual/help format.&lt;/p&gt;  &lt;p&gt;Is it safe to assume all content created abroad will be poor? Absolutely not, but with the number of companies scrambling to get involved, the chances of content being left behind are high.&lt;/p&gt;  &lt;p&gt;Do any of you have any experience with trying to bridge the timezones and language barriers with content?&amp;#160; I’d be interested in hearing anecdotes and approaches.&amp;#160; Happy to compare notes.&lt;/p&gt;  &lt;p&gt;&lt;font style="background-color: #ffff00"&gt;&lt;/font&gt;&lt;strong&gt;Next post we’ll go into the question: Is TechComms mired in the past?&amp;#160; Is MarComms? And we’ll look at what the future could look like.&lt;/strong&gt; &lt;font style="background-color: #ffff00"&gt;&lt;/font&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-730364320566608678?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=ktDcDN8kz1I:DuZjhqBEbzA:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=ktDcDN8kz1I:DuZjhqBEbzA:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=ktDcDN8kz1I:DuZjhqBEbzA:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=ktDcDN8kz1I:DuZjhqBEbzA:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=ktDcDN8kz1I:DuZjhqBEbzA:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=ktDcDN8kz1I:DuZjhqBEbzA:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=ktDcDN8kz1I:DuZjhqBEbzA:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=ktDcDN8kz1I:DuZjhqBEbzA:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=ktDcDN8kz1I:DuZjhqBEbzA:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=ktDcDN8kz1I:DuZjhqBEbzA:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=ktDcDN8kz1I:DuZjhqBEbzA:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=ktDcDN8kz1I:DuZjhqBEbzA:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/ktDcDN8kz1I" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/730364320566608678/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-4.html#comment-form" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/730364320566608678?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/730364320566608678?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/ktDcDN8kz1I/when-content-strategies-collide-pt-4.html" title="When Content Strategies Collide Pt 4: Enabling vs. Persuasive Content" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh5.ggpht.com/_nJ8XHcWrG0A/Ta_3QH9VFKI/AAAAAAAAAGY/01dJGiwjALs/s72-c/cherry-layer-cake_thumb%5B1%5D.jpg?imgmax=800" height="72" width="72" /><thr:total>4</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-4.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEUFSH4yeSp7ImA9WhdWEk4.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-1446120213636973221</id><published>2011-04-16T18:12:00.001+02:00</published><updated>2011-09-05T17:23:39.091+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-09-05T17:23:39.091+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conference" /><category scheme="http://www.blogger.com/atom/ns#" term="tech docs" /><category scheme="http://www.blogger.com/atom/ns#" term="techcomm" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><category scheme="http://www.blogger.com/atom/ns#" term="congility 2011" /><category scheme="http://www.blogger.com/atom/ns#" term="congility" /><title>When Content Strategies Collide Pt 3: War. Huh! What is it Good For?</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
&lt;a href="http://lh3.ggpht.com/_nJ8XHcWrG0A/TZ8zzlWlHxI/AAAAAAAAAGE/PxsDQeQfFLc/s1600-h/2011-04-08%20002%5B4%5D.jpg"&gt;&lt;img alt="2011-04-08 002" border="0" height="122" src="http://lh5.ggpht.com/_nJ8XHcWrG0A/TZ8z0BBlrAI/AAAAAAAAAGI/c9qfP7xy6Tg/2011-04-08%20002_thumb%5B1%5D.jpg?imgmax=800" style="background-image: none; border-bottom-width: 0px; border-left-width: 0px; border-right-width: 0px; border-top-width: 0px; display: inline; float: left; margin: 0px 10px 10px 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px;" title="2011-04-08 002" width="121" /&gt;&lt;/a&gt;This is Part 3 “When Content Strategies Collide – MarComms vs. TechComms”.&lt;br /&gt;
Today we’ll look at how the gap between communications departments (specifically Technical and Marketing) persists despite the damage to customer experience.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-size: small;"&gt;See also:&lt;/span&gt; &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide.html"&gt;When Content Strategies Collide: Marketing versus Technical Communication&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-2.html"&gt;When Content Strategies Collide Pt 2: Customer Impact&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-3.html"&gt;When Content Strategies Collide Pt 3: War. Huh! What is it Good For?&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-4.html"&gt;When Content Strategies Collide Pt 4: Enabling vs. Persuasive Content&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-5-is.html"&gt;When Content Strategies Collide Pt 5: Is Communication Mired in the Past?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/05/when-content-strategies-collide-pt-6.html"&gt;When Content Strategies Collide Pt 6: Conclusion, Unification&lt;/a&gt;&amp;nbsp; &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;h2&gt;
&lt;span style="font-weight: normal;"&gt;Why Can’t We All Just Get Along?&lt;/span&gt;&lt;/h2&gt;
&lt;br /&gt;
Like many neighbouring nations, we get very excited about our little differences instead of focussing on our big picture commonalities. In my mind, the usual suspects that separate people are: &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Language &lt;/li&gt;
&lt;li&gt;Culture &lt;/li&gt;
&lt;li&gt;Geography &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
Let’s take a look at these areas and the impact they have on the people we’re all in the end working for: the customer aka, the content consumer.&lt;span style="font-weight: normal;"&gt;&amp;nbsp;&lt;/span&gt;&lt;br /&gt;
&lt;span style="font-weight: normal;"&gt; &lt;/span&gt;&lt;br /&gt;
&lt;h2&gt;
&lt;span style="font-weight: normal;"&gt;Language: We’re All “Content Professionals”&lt;/span&gt;&lt;/h2&gt;
&lt;br /&gt;
Whatever it says on your business card – your passport in the world of content – we have many words we share. We all talk about: &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Consistency of…      &lt;ul&gt;
&lt;li&gt;Language &lt;/li&gt;
&lt;li&gt;Style &lt;/li&gt;
&lt;li&gt;Structure &lt;/li&gt;
&lt;li&gt;user-orientation &lt;/li&gt;
&lt;li&gt;taxonomy / metadata &lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Localisation &lt;/li&gt;
&lt;li&gt;Customer-specific content and understanding what the customer wants or needs &lt;/li&gt;
&lt;li&gt;Content management &lt;/li&gt;
&lt;li&gt;Content audits &lt;/li&gt;
&lt;li&gt;and now of course, Content Strategy. &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
Where we differ is in some of the details. MarComs and Tech Comm are the way that the organisation communicates with the outside world. The only other “Communications” group is “Business Communications” Take this list of words and see how many terms hit home with you:&lt;br /&gt;
&lt;br /&gt;
&lt;table border="1" cellpadding="0" cellspacing="0"&gt;&lt;tbody&gt;
&lt;tr&gt;         &lt;td valign="top" width="238"&gt;Brand Values / Brand Management&lt;/td&gt;          &lt;td valign="top" width="234"&gt;XML&lt;/td&gt;          &lt;td valign="top" width="238"&gt;Information Architecture&lt;/td&gt;       &lt;/tr&gt;
&lt;tr&gt;         &lt;td valign="top" width="238"&gt;Social Media&lt;/td&gt;          &lt;td valign="top" width="234"&gt;DITA&lt;/td&gt;          &lt;td valign="top" width="238"&gt;CX&lt;/td&gt;       &lt;/tr&gt;
&lt;tr&gt;         &lt;td valign="top" width="238"&gt;Socially Enabled&lt;/td&gt;          &lt;td valign="top" width="234"&gt;CCMS&lt;/td&gt;          &lt;td valign="top" width="238"&gt;Personas&lt;/td&gt;       &lt;/tr&gt;
&lt;tr&gt;         &lt;td valign="top" width="238"&gt;SEO&lt;/td&gt;          &lt;td valign="top" width="234"&gt;CMS&lt;/td&gt;          &lt;td valign="top" width="238"&gt;UX&lt;/td&gt;       &lt;/tr&gt;
&lt;tr&gt;         &lt;td valign="top" width="238"&gt;Single Sourcing&lt;/td&gt;          &lt;td valign="top" width="234"&gt;Context Sensitive&lt;/td&gt;          &lt;td valign="top" width="238"&gt;Monetised&lt;/td&gt;       &lt;/tr&gt;
&lt;tr&gt;         &lt;td valign="top" width="238"&gt;Syndicated&lt;/td&gt;          &lt;td valign="top" width="234"&gt;Reusable&lt;/td&gt;          &lt;td valign="top" width="238"&gt;Modular&lt;/td&gt;       &lt;/tr&gt;
&lt;tr&gt;         &lt;td valign="top" width="238"&gt;Messaging&lt;/td&gt;          &lt;td valign="top" width="234"&gt;Style guide&lt;/td&gt;          &lt;td valign="top" width="238"&gt;Structural Templates&lt;/td&gt;       &lt;/tr&gt;
&lt;tr&gt;         &lt;td valign="top" width="238"&gt;Analytics / Metrics&lt;/td&gt;          &lt;td valign="top" width="234"&gt;ROI&lt;/td&gt;          &lt;td valign="top" width="238"&gt;Content Modelling&lt;/td&gt;       &lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;br /&gt;
I read &lt;a href="http://twitter.com/halvorson" target="_blank"&gt;Kristina Halvorson&lt;/a&gt;’s “Content Strategy for the Web” and in the margins of each page put little markers about whether the statements and language were applicable and understandable off the web and outside the marketing team. My markers indicated three things: “Yes (this idea is applicable off the web)”, “No”, “Maybe”, and “Not usually, but it should be!”&lt;br /&gt;
&lt;br /&gt;
There were lots of each category, but the “No” items were in the vast minority, i.e., &lt;i&gt;most&lt;/i&gt; content best practices &lt;i&gt;don’t&lt;/i&gt; differ between channels. Let’s take an example which any content professional can immediately understand (or should):&lt;br /&gt;
&lt;br /&gt;
“If your CMS metadata is inconsistent or poorly managed, your content’s going to pile up, and information will be buried. You’ll also end up creating redundant content, waste money on inefficient workflow, and generally rack up unnecessary content-related expenses and headaches.”&lt;br /&gt;
&lt;br /&gt;
And then a bit that would leave other content professionals making a sort of slanty grimace:&lt;br /&gt;
&lt;br /&gt;
“During the analysis phases, you collected all of your messages – the pieces of information you want the user to learn or the user wants to see. In the content strategy phases, you make recommendations about how the messages all work together to form useful, usable, enjoyable web content.”&lt;br /&gt;
&lt;br /&gt;
So, we share some words, but not all, and those we do, we don’t &lt;i&gt;always&lt;/i&gt; mean the same things by them. “Messages”, “Messaging”, “Messaging hierarchy” are all pretty marketing-specific for those in other departments. When defined as “the pieces of information you want the user to learn or the user wants to see”, then it’s more relatable. It’s not that different.&lt;br /&gt;
&lt;br /&gt;
People outside the web team get shocked and offended by quotes like:&lt;br /&gt;
&lt;br /&gt;
“The content strategist may collaborate closely with a web editor or web writer to oversee the creation, revision, and approval of all required content. In the absence of a web editor or writer, the content strategist may also be called upon to create all necessary content.”&lt;br /&gt;
&lt;br /&gt;
... “All”?&lt;br /&gt;
&lt;br /&gt;
Come again?&lt;br /&gt;
&lt;br /&gt;
Naturally anyone in the Land of Tech Comm would be hurt and dismayed to hear that “all” content on the website, which probably includes tens of thousands of their words in HTML Help, How-To, FAQ, Release Note, and downloadable PDF form, and more, was being so totally left out of Content Strategy thinking.&lt;br /&gt;
&lt;br /&gt;
I think it’s obvious, however, that Kristina, or any leading web content strategist saying something like this is talking about the &lt;i&gt;new&lt;/i&gt; and &lt;i&gt;website-specific&lt;/i&gt; words, probably in the context of only the web project in question. There are loads of words which only exist on the web and serve to gel together, relate, enhance, and support all the other content created by other sources that needs to go public via online channels.&lt;br /&gt;
&lt;br /&gt;
So… chill.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;In Part 4 we’ll go on to discuss the Cultural divide – the different way that MarComms and TechComms tick.&amp;nbsp;&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-size: small;"&gt;See also:&lt;/span&gt; &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide.html"&gt;When Content Strategies Collide: Marketing versus Technical Communication&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-2.html"&gt;When Content Strategies Collide Pt 2: Customer Impact&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-3.html"&gt;When Content Strategies Collide Pt 3: War. Huh! What is it Good For?&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-4.html"&gt;When Content Strategies Collide Pt 4: Enabling vs. Persuasive Content&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-5-is.html"&gt;When Content Strategies Collide Pt 5: Is Communication Mired in the Past?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/05/when-content-strategies-collide-pt-6.html"&gt;When Content Strategies Collide Pt 6: Conclusion, Unification&lt;/a&gt;&amp;nbsp; &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;/div&gt;
&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-1446120213636973221?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=t09MJX2Un9Q:QYKB_UYHhzw:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=t09MJX2Un9Q:QYKB_UYHhzw:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=t09MJX2Un9Q:QYKB_UYHhzw:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=t09MJX2Un9Q:QYKB_UYHhzw:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=t09MJX2Un9Q:QYKB_UYHhzw:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=t09MJX2Un9Q:QYKB_UYHhzw:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=t09MJX2Un9Q:QYKB_UYHhzw:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=t09MJX2Un9Q:QYKB_UYHhzw:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=t09MJX2Un9Q:QYKB_UYHhzw:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=t09MJX2Un9Q:QYKB_UYHhzw:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=t09MJX2Un9Q:QYKB_UYHhzw:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=t09MJX2Un9Q:QYKB_UYHhzw:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/t09MJX2Un9Q" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/1446120213636973221/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-3.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/1446120213636973221?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/1446120213636973221?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/t09MJX2Un9Q/when-content-strategies-collide-pt-3.html" title="When Content Strategies Collide Pt 3: War. Huh! What is it Good For?" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh5.ggpht.com/_nJ8XHcWrG0A/TZ8z0BBlrAI/AAAAAAAAAGI/c9qfP7xy6Tg/s72-c/2011-04-08%20002_thumb%5B1%5D.jpg?imgmax=800" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-3.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D08FQHs6cCp7ImA9WhdWEk4.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-4155773837112934799</id><published>2011-04-11T15:15:00.001+02:00</published><updated>2011-09-05T17:16:51.518+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-09-05T17:16:51.518+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conference" /><category scheme="http://www.blogger.com/atom/ns#" term="tech docs" /><category scheme="http://www.blogger.com/atom/ns#" term="techcomm" /><category scheme="http://www.blogger.com/atom/ns#" term="content management" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><category scheme="http://www.blogger.com/atom/ns#" term="congility 2011" /><category scheme="http://www.blogger.com/atom/ns#" term="technical simplified english" /><category scheme="http://www.blogger.com/atom/ns#" term="congility" /><title>When Content Strategies Collide Pt 2: Customer Impact</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
In my last post, I left off with my description of the two major continents in the World of Content: &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;“&lt;b&gt;The Archipelago of Internet Marketing&lt;/b&gt;” &lt;/li&gt;
&lt;li&gt;“&lt;b&gt;The Land of TechComms (and a bit of Training)&lt;/b&gt;” &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;a href="http://lh4.ggpht.com/_nJ8XHcWrG0A/TZ8GguIGa5I/AAAAAAAAAFc/RFPa7K-WgMQ/s1600-h/2004-08-21%20Machu%20Picchu%2CPeru%203793%5B5%5D.jpg"&gt;&lt;img alt="2004-08-21 Machu Picchu,Peru 3793" border="0" height="405" src="http://lh5.ggpht.com/_nJ8XHcWrG0A/TZ8GhQqQdVI/AAAAAAAAAFg/LDJAxMGOJ_4/2004-08-21%20Machu%20Picchu%2CPeru%203793_thumb%5B10%5D.jpg?imgmax=800" style="background-image: none; border-bottom-width: 0px; border-left-width: 0px; border-right-width: 0px; border-top-width: 0px; display: inline; padding-left: 0px; padding-right: 0px; padding-top: 0px;" title="2004-08-21 Machu Picchu,Peru 3793" width="400" /&gt;&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here’s some links to all the posts if you haven't read them: &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide.html"&gt;When Content Strategies Collide: Marketing versus Technical Communication&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-2.html"&gt;When Content Strategies Collide Pt 2: Customer Impact&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-3.html"&gt;When Content Strategies Collide Pt 3: War. Huh! What is it Good For?&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-4.html"&gt;When Content Strategies Collide Pt 4: Enabling vs. Persuasive Content&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-5-is.html"&gt;When Content Strategies Collide Pt 5: Is Communication Mired in the Past?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/05/when-content-strategies-collide-pt-6.html"&gt;When Content Strategies Collide Pt 6: Conclusion, Unification&lt;/a&gt;&amp;nbsp; &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
Today there’s a gap between them, but the two continents are starting to collide and create some topographical ruffles in the process. Here we look a bit more at some names and faces from the populations and why this is an issue for the enterprise.&amp;nbsp; &lt;br /&gt;
This was all born of my thinking when coming up with the theme for the &lt;a href="http://www.congility.com/" target="_blank"&gt;Congility 2011 Conference in the UK this May&lt;/a&gt;. &lt;br /&gt;
&lt;h2&gt;
The Lay of the Land And The Cloud&lt;/h2&gt;
Wherever you picture yourself on this Communications landscape, the word wide web flows around and between us all like water. As they say, “location, location, location”. Everyone – inside and outside any organisation – can see the web and (theoretically) find the information on it.&lt;br /&gt;
On the web you can even package up bits of content and ship them stuck to other bits (related items, banner ads, pop-ups), to make them even more “findable”. Now in the age of social media, every single man, woman, and especially child is throwing their work into the growth of web’s wealth of information and the findability of that information. &lt;br /&gt;
This creates a friction along the coast as the Archipelago of Internet Marketing and Land of TechComms start to merge, pushed on, inexorably, by the underlying market forces. &lt;br /&gt;
Take for example some other posts from both sides of Web Content / Technical Content fence: &lt;br /&gt;
&lt;a href="http://twitter.com/halvorson"&gt;Kristina Havlorson&lt;/a&gt;’s posted “&lt;a href="http://blog.braintraffic.com/2010/11/why-i-wrote-content-strategy-for-the-web/"&gt;Why I Wrote Content Strategy FOR THE WEB&lt;/a&gt;” recently regarding her book and why the title and examples therein focussed on the web. On that post she’s provided further contextual links, and calls it a source of “serious frustration”. In the end, I’d say she’s not as webby as you might think, and she and her book are not to be dismissed by any content professional. &lt;br /&gt;
Kristina links her post to one by &lt;a href="http://twitter.com/rahelab"&gt;Rahel Bailie&lt;/a&gt;. Several conversations with Rahel and Rahel’s blogs regarding Content Strategy were further dominos leading up to this article. &lt;br /&gt;
There was also some feather ruffling in the blogosphere (&lt;b&gt;see 18:19 18/05/2011 Update below for new information and correction on this&lt;/b&gt;) caused by notable blogger and Content Professional &lt;a href="http://twitter.com/2morodocs"&gt;Julie Norris&lt;/a&gt; announcing she was leaving technical communications and transitioning into something more in the UX and social-media related fields (Here’s a post where TechComms blogger &lt;a href="http://twitter.com/tomjohnson"&gt;Tom Johnson&lt;/a&gt; then reacted to that). Almost as an aside in her announcement she was leaving TechComms, she dropped, grenade-like, the comment that TechComms was ‘mired in the past’. &lt;br /&gt;
Bam! &lt;br /&gt;
I, unfortunately, can’t quote directly or even link to it because the original post, its update notes, and even a follow-up post, have all been (tragically) removed from Julie’s blog. The evidence can be now most easily found via &lt;a href="http://twitter.com/tomjohnson"&gt;Tom Johnson&lt;/a&gt;’s blog “&lt;a href="http://idratherbewriting.com/2010/12/30/technical-communication-stuck-in-the-past/"&gt;Technical Communication Stuck in the Past?&lt;/a&gt;” &lt;br /&gt;
&lt;a href="http://lh3.ggpht.com/_nJ8XHcWrG0A/TZ8GhqkhDQI/AAAAAAAAAFk/JhvI4P-EYxA/s1600-h/clip_image002_thumb%5B1%5D%5B2%5D.jpg"&gt;&lt;img alt="clip_image002_thumb[1]" border="0" height="180" src="http://lh3.ggpht.com/_nJ8XHcWrG0A/TZ8GiGQHAkI/AAAAAAAAAFo/v9qyziOK9cU/clip_image002_thumb%5B1%5D_thumb.jpg?imgmax=800" style="background-image: none; border-bottom-width: 0px; border-left-width: 0px; border-right-width: 0px; border-top-width: 0px; display: inline; padding-left: 0px; padding-right: 0px; padding-top: 0px;" title="clip_image002_thumb[1]" width="419" /&gt;&lt;/a&gt; &lt;br /&gt;
So – we can see the wrinkles forming the landscape already. Let’s hope that like when real tectonic plates crash, it forces the horizon skyward, and everyone’s game will be raised. But why is this happening, and possibly more importantly, what is impact? &lt;br /&gt;
&lt;h4&gt;
---------------------------&lt;/h4&gt;
&lt;h4&gt;
UPDATE (18:19 18/05/2011):&lt;/h4&gt;
Julie has commented on this post and &lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-5-is.html#comments" target="_blank"&gt;part 5&lt;/a&gt; to point out an error.&amp;nbsp; Because I was not able to access her blog directly, I was left with the misinterpretation that she had in fact ‘left’ TechComms for pastures new.&amp;nbsp; The truth was that was refocusing her blog away from TechComms, but she is today and will continue to be a Technical Communications practitioner.&amp;nbsp; I have left the rest of the blog as was, because the key point is the reaction that the mere idea caused.&amp;nbsp; At Julie’s request I have included this point of fact that she has NOT ‘left’ at all.&amp;nbsp; Any words not quoted directly from her blog were my interpretation based on Tom Johnson’s post and the contents are not to be attributed to Julie herself.&lt;br /&gt;
&lt;h4&gt;
---------------------------&lt;/h4&gt;
&lt;h2&gt;
The Point of Impact – The Customer’s Doorstep&lt;/h2&gt;
I’m very interested in the rift* between those in the content industry who are generally taking a holistic approach, integrating across the borders, and those who keep to their ‘nationalities’. &lt;br /&gt;
&lt;sup&gt;* For more on TechComms rift see Sarah O’Keefe’s blog on 2011 predictions: http://www.scriptorium.com/2011/01/2011-predictions-for-technical-communication/ &lt;/sup&gt;&lt;br /&gt;
This second rift is more important because of the victims: the customers. Oh please, won’t someone think of the customers! My &lt;a href="http://lessworkmoreflow.blogspot.com/2010/12/drowning-your-audience-in-content.html"&gt;most popular blog post to date&lt;/a&gt; was all about how fragmentation and division inside the organisation create fragmentation in our content and our communications. The result: customer experience suffers. &lt;br /&gt;
&lt;a href="http://www.flickr.com/photos/failpost/3758092256/" title="Customer Service Fail by FailPost, on Flickr"&gt;&lt;img alt="Customer Service Fail" height="304" src="http://farm3.static.flickr.com/2467/3758092256_6f4f36efbf_m.jpg" width="402" /&gt;&lt;/a&gt;&lt;br /&gt;
&lt;sup&gt;Every business is busy, busy, busy, especially successful ones. BUT, when you’re too busy working harder to work smarter, the customer is the one who waits in frustration while you try to get your act together.&lt;/sup&gt;&lt;br /&gt;
&lt;sup&gt;&lt;a href="http://www.flickr.com/photos/failpost/3758092256/" title="http://www.flickr.com/photos/failpost/3758092256/"&gt;http://www.flickr.com/photos/failpost/3758092256/&lt;/a&gt;&lt;/sup&gt;&lt;br /&gt;
I recently had calls with three companies (in one week!) who had: &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;unified their writing style, structural and metadata guidelines &lt;/li&gt;
&lt;li&gt;implemented a content management system &lt;/li&gt;
&lt;li&gt;set up standards and collaboration across business units &lt;/li&gt;
&lt;li&gt;moved to a modular XML-based standard (DITA, for their technical content) &lt;/li&gt;
&lt;/ul&gt;
And by doing so had realised all sorts of great benefits. What were we talking about on the call? The fact that in the end, what they had done was set up a very efficient, collaborative &lt;u&gt;silo&lt;/u&gt; of technical content that was isolated from the rest of the content in training, engineering, presales and marketing. Terminology, Language, Labelling/Taxonomy, Metadata, even things as important as product names, were not supported with the solutions implemented. &lt;br /&gt;
Many of the software vendors and even many consultants and experts only make this worse. Each of these organisations had Web CMS systems in place, but they weren’t integrated neither in process nor in software. Software vendors know that trying to bridge a departmental gap is only going to complicate and therefore lengthen their sales cycle. That ain’t gonna happen. So they “give the people what they want”. &lt;br /&gt;
However, it’s the customers who have navigate through all our output, regardless of source department, so the more rifts there are in our thinking and processes the more rifts they’ll have to traverse to get what they want. That’s annoying!&lt;br /&gt;
Today, the customer wants us to integrate.&amp;nbsp; They want us to work together to deliver the value-added, clear, CONCISE*, factual information about products and services.&amp;nbsp; Most marketers already know that today the more you appear to be trying to sell, the less affective, but haven’t got a plan yet as to how they’re realistically going to keep product information fresh, available and digestible.&lt;br /&gt;
Check out The (ever-brilliant) Oatmeal:&lt;br /&gt;
&lt;a href="http://theoatmeal.com/comics/sell_generation" title="http://theoatmeal.com/comics/sell_generation"&gt;http://theoatmeal.com/comics/sell_generation&lt;/a&gt;&lt;br /&gt;
There you have it.&lt;br /&gt;
&lt;b&gt;In Part 3 we deep-dive into why we can’t get along.&amp;nbsp; Why does the rift persist?&lt;/b&gt;&lt;br /&gt;
&lt;sub&gt;*Unlike my blog posts…&lt;/sub&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-size: small;"&gt;See also:&lt;/span&gt; &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide.html"&gt;When Content Strategies Collide: Marketing versus Technical Communication&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-2.html"&gt;When Content Strategies Collide Pt 2: Customer Impact&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-3.html"&gt;When Content Strategies Collide Pt 3: War. Huh! What is it Good For?&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-4.html"&gt;When Content Strategies Collide Pt 4: Enabling vs. Persuasive Content&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-5-is.html"&gt;When Content Strategies Collide Pt 5: Is Communication Mired in the Past?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/05/when-content-strategies-collide-pt-6.html"&gt;When Content Strategies Collide Pt 6: Conclusion, Unification&lt;/a&gt;&amp;nbsp; &lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-4155773837112934799?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=UKWftd0wJLg:Y4pTVJy39cc:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=UKWftd0wJLg:Y4pTVJy39cc:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=UKWftd0wJLg:Y4pTVJy39cc:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=UKWftd0wJLg:Y4pTVJy39cc:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=UKWftd0wJLg:Y4pTVJy39cc:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=UKWftd0wJLg:Y4pTVJy39cc:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=UKWftd0wJLg:Y4pTVJy39cc:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=UKWftd0wJLg:Y4pTVJy39cc:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=UKWftd0wJLg:Y4pTVJy39cc:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=UKWftd0wJLg:Y4pTVJy39cc:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=UKWftd0wJLg:Y4pTVJy39cc:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=UKWftd0wJLg:Y4pTVJy39cc:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/UKWftd0wJLg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/4155773837112934799/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-2.html#comment-form" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/4155773837112934799?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/4155773837112934799?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/UKWftd0wJLg/when-content-strategies-collide-pt-2.html" title="When Content Strategies Collide Pt 2: Customer Impact" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh5.ggpht.com/_nJ8XHcWrG0A/TZ8GhQqQdVI/AAAAAAAAAFg/LDJAxMGOJ_4/s72-c/2004-08-21%20Machu%20Picchu%2CPeru%203793_thumb%5B10%5D.jpg?imgmax=800" height="72" width="72" /><thr:total>2</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-2.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUcAQHY5eip7ImA9WhZREko.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-2124500506830087983</id><published>2011-04-08T15:57:00.001+02:00</published><updated>2011-04-08T16:30:41.822+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-04-08T16:30:41.822+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="DITA" /><category scheme="http://www.blogger.com/atom/ns#" term="conference" /><category scheme="http://www.blogger.com/atom/ns#" term="tech docs" /><category scheme="http://www.blogger.com/atom/ns#" term="content reuse" /><category scheme="http://www.blogger.com/atom/ns#" term="training" /><category scheme="http://www.blogger.com/atom/ns#" term="content management" /><category scheme="http://www.blogger.com/atom/ns#" term="metadata" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><category scheme="http://www.blogger.com/atom/ns#" term="technical simplified english" /><category scheme="http://www.blogger.com/atom/ns#" term="congility" /><category scheme="http://www.blogger.com/atom/ns#" term="mekon" /><category scheme="http://www.blogger.com/atom/ns#" term="technical communications" /><category scheme="http://www.blogger.com/atom/ns#" term="modular writing" /><category scheme="http://www.blogger.com/atom/ns#" term="techcomm" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="congility 2011" /><category scheme="http://www.blogger.com/atom/ns#" term="darwin information typing architecture" /><category scheme="http://www.blogger.com/atom/ns#" term="workflow" /><title>Ann Rockley and Rahel Bailie Congility 2011 Podcasts</title><content type="html">&lt;p&gt;&lt;a href="http://lh4.ggpht.com/_nJ8XHcWrG0A/TZ8YBQErrcI/AAAAAAAAAF8/qQUEH2UfAEM/s1600-h/ann-rahel-congility%5B2%5D.png"&gt;&lt;img style="border-right-width: 0px; padding-left: 0px; padding-right: 0px; display: block; float: none; border-top-width: 0px; border-bottom-width: 0px; margin-left: auto; border-left-width: 0px; margin-right: auto; padding-top: 0px" title="ann-rahel-congility" border="0" alt="ann-rahel-congility" src="http://lh3.ggpht.com/_nJ8XHcWrG0A/TZ8YCLJvCFI/AAAAAAAAAGA/0ofM2vio92E/ann-rahel-congility_thumb.png?imgmax=800" width="244" height="228" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;As promised – here are the two Featured Speaker podcasts for Congility 2011 where I interview two major players in the content industry.&lt;/p&gt;  &lt;p&gt;Both are delivering &lt;a href="http://www.congility.com/index.php/site/program_by_track/C386/" target="_blank"&gt;workshops&lt;/a&gt; and featured &lt;a href="http://www.congility.com/site/program" target="_blank"&gt;presentations&lt;/a&gt; at &lt;a href="http://www.congility.com/2011" target="_blank"&gt;Congility 2011&lt;/a&gt;.&lt;/p&gt;  &lt;h2&gt;Ann Rockley&lt;/h2&gt;  &lt;p&gt;&lt;a href="http://www.congility.com/index.php/site/speaker_detail/rockley/" target="_blank"&gt;Ann Rockley&lt;/a&gt;, President of The Rockley Group, Inc. is interviewed by Noz Urbina, Mekon Consultant and Congility Conference Chairperson.&lt;/p&gt;  &lt;p&gt;Sometimes known as the &amp;quot;mother&amp;quot; of content strategy, Ann introduced the concept in 2003 with her best-selling book &amp;quot;Managing Enterprise Content: A Unified Content Strategy&amp;quot;.&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;We talk about: &lt;/strong&gt;&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;Unifying content strategies across silos like technical communications, marketing, support and more &lt;/li&gt;    &lt;li&gt;The role of Darwin Information Typing Architecture and content consistency &lt;/li&gt;    &lt;li&gt;How content affects the customer experience &lt;/li&gt;    &lt;li&gt;Speaking with a single voice to multiple audiences. &lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;&lt;a href="http://www.youtube.com/watch?v=gQAj10KGumQ" target="_blank"&gt;Watch Ann Rockley’s video podcast (8 min)&lt;/a&gt;&lt;/p&gt;  &lt;h2&gt;Rahel Anne Bailie&lt;/h2&gt;  &lt;p&gt;&lt;a href="http://www.congility.com/site/speaker_detail/bailie" target="_blank"&gt;Rahel Bailie&lt;/a&gt;, Principal of Intentional Design, has many years of experience in the areas of content development and user experience environments, including environments producing localized and/or internationalized content.&lt;/p&gt;  &lt;p&gt;Rahel has been making waves in the Content Strategy community as of late and in European circles was recently the Keynote speaker of the Content Strategy themed STC France chapter event.&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;We talk about:&lt;/strong&gt;&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;Knowledge vs. Data and Information &lt;/li&gt;    &lt;li&gt;Combining and recombining content to create context (e.g. in a mash-up) &lt;/li&gt;    &lt;li&gt;How all content today - technical, marketing, commercial and user generated - is becoming a unified body of 'presales' content &lt;/li&gt;    &lt;li&gt;How standards help content converge for better experiences for customers &lt;/li&gt;    &lt;li&gt;&amp;quot;Big picture&amp;quot; content strategy &lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;&lt;a href="http://www.youtube.com/watch?v=BRAxQ3eSD-I" target="_blank"&gt;Watch Rahel Anne Bailie’s video podcast (6.5 min)&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-2124500506830087983?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=OKYUb40OklU:SDVS4bxgp0M:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=OKYUb40OklU:SDVS4bxgp0M:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=OKYUb40OklU:SDVS4bxgp0M:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=OKYUb40OklU:SDVS4bxgp0M:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=OKYUb40OklU:SDVS4bxgp0M:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=OKYUb40OklU:SDVS4bxgp0M:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=OKYUb40OklU:SDVS4bxgp0M:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=OKYUb40OklU:SDVS4bxgp0M:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=OKYUb40OklU:SDVS4bxgp0M:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=OKYUb40OklU:SDVS4bxgp0M:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=OKYUb40OklU:SDVS4bxgp0M:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=OKYUb40OklU:SDVS4bxgp0M:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/OKYUb40OklU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/2124500506830087983/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/04/ann-rockley-and-rahel-bailie-congility.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/2124500506830087983?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/2124500506830087983?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/OKYUb40OklU/ann-rockley-and-rahel-bailie-congility.html" title="Ann Rockley and Rahel Bailie Congility 2011 Podcasts" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh3.ggpht.com/_nJ8XHcWrG0A/TZ8YCLJvCFI/AAAAAAAAAGA/0ofM2vio92E/s72-c/ann-rahel-congility_thumb.png?imgmax=800" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/04/ann-rockley-and-rahel-bailie-congility.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEQHSXo_fip7ImA9WhdWEk4.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-7743464104750147986</id><published>2011-04-08T15:15:00.003+02:00</published><updated>2011-09-05T17:25:38.446+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-09-05T17:25:38.446+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conference" /><category scheme="http://www.blogger.com/atom/ns#" term="tech docs" /><category scheme="http://www.blogger.com/atom/ns#" term="technical communications" /><category scheme="http://www.blogger.com/atom/ns#" term="techcomm" /><category scheme="http://www.blogger.com/atom/ns#" term="content management" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><category scheme="http://www.blogger.com/atom/ns#" term="congility 2011" /><category scheme="http://www.blogger.com/atom/ns#" term="darwin information typing architecture" /><category scheme="http://www.blogger.com/atom/ns#" term="congility" /><title>When Content Strategies Collide: Marketing versus Technical Communication</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
We’re in an intensely exciting time now in “the World of Content”.
      Content Strategy and Social Media are the buzzwords on everyone’s lips.
      Like any new and game-changing hot-button, there’s as much debate about
      what we’re even talking about as there is about why it’s important, or
      what we should do about it.&lt;br /&gt;
&lt;br /&gt;
&lt;sub&gt;See a &lt;a href="http://linkd.in/hLYxwp" target="_blank"&gt;discussion on
      what Content Strategy is on the CS Group on LinkedIn&lt;/a&gt;&lt;/sub&gt;
    &lt;br /&gt;
&lt;br /&gt;
This multi-part blog is going to take a look at how Content Strategy is
      affecting the ‘Word of Content’ and the world of the content
      professional.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://lh3.ggpht.com/_nJ8XHcWrG0A/TZ8GoEonUxI/AAAAAAAAAFs/zpkUvViFWrs/s1600-h/image%5B7%5D.png"&gt;
      &lt;img alt="image" border="0" height="388" src="http://lh3.ggpht.com/_nJ8XHcWrG0A/TZ8GpFBjfzI/AAAAAAAAAFw/kG2ykB4EGv4/image_thumb%5B2%5D.png?imgmax=800" style="background-image: none; border-bottom: 0px; border-left: 0px; border-right: 0px; border-top: 0px; display: inline; padding-left: 0px; padding-right: 0px; padding-top: 0px;" title="image" width="406" /&gt;&lt;/a&gt;
    &lt;br /&gt;
&lt;br /&gt;
By the time I’m done I'll have concluded that both Marketing and
      Technical Communication are both mired in the past – and probably annoyed
      and offended some people in the process for which I apologize in
      advance.&amp;nbsp; I won’t be saying that that I’ve got the magic 100% effective
      snake-oil/silver-bullet-salve to fix it all but hopefully I’ll have
      gotten some discussion started about what potential solutions could and
      should be.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Whatever type of content-related work you do, be it Content
      Strategist, Tech Writer, Brand Manager, UX, IA, Web Writer, Content
      Manager, etc., this blog’s for &lt;u&gt;you&lt;/u&gt;.&lt;/b&gt; &lt;br /&gt;
&lt;br /&gt;
Here in part one we look at the fact that we’re seeing the early
      impact-zone wrinkles of a bigger collision to come: I think what we’re
      going to see is a unifying and blurring of the content functions around
      an organisation. There will be increased collaboration, re-titling of
      staff, new services offerings from traditional
      teams/consultancies/agencies aimed towards closing the loops in and
      outside the organisation itself.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;We’ve been talking about content standards unification and
      integration for decades now, but now, with the recognition of Content
      Strategy, we have the catalyst for change.&lt;/b&gt;
    &lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;


      Why? What difference does CS make?
    &lt;/h2&gt;
&lt;br /&gt;
Because once you really start to think of content itself as a strategic
      asset, and put a well conceived strategy together, our artificial
      traditional separations need to come down to support the business’s true
      goals.
    &lt;br /&gt;
&lt;br /&gt;
To put it another way, you can’t serve customers best interests while
      maintaining high walls between the communications and content-centric
      parts of your operation. Ergo, they’re going to start to integrate. This
      will delight some and horrify and confuse others.
    &lt;br /&gt;
&lt;br /&gt;
Content Strategy as a discipline is generally focussed around content
      that is for communicating. There are two main Communications areas in the
      average enterprise. On one side, you’ve got MarComms, where Content
      Strategy concerned mainly with the public web, and websites and closing
      the loop with brand management and the sales cycle. On the other side,
      TechComms is working to close the loop with product development,
      training, the support lifecycle, and training. Traditionally, they’ve
      scuffled over the word “content”, approaching it with different
      personalities, tools, budgets, departments and sometimes perceived goals.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://www.congility.com/" target="_blank"&gt;&lt;img align="left" src="http://www.congility.com/images/mkting_resources/ca_sqr_200x_ad.jpg" style="display: inline; float: left; margin: 0px 10px 10px 0px;" /&gt;&lt;/a&gt;This
      blog addresses major topographic changes coming in the World of Content,
      integration of silos, and the customer experience. The theme of the
      &lt;a href="http://www.congility.com/"&gt;Congility 2011 Conference&lt;/a&gt;, May
      24-26th, is “Content Integration” and its effect on customers. It, and
      this post, will focus on how the work of all of us as content
      professionals is similar in important ways and would benefit from
      increased collaboration. Our efforts should seek to close the loops in
      the customer lifecycle, user experience, user interaction design, and
      often benefit from similar processes, skill-sets and even underlying
      tools and technology.
    &lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;


      The World of Content, Communication and Content Strategy
    &lt;/h2&gt;
&lt;br /&gt;
As fast moving as the details are, ask anyone who’s been specialising
      here in the World of Content for 10 or more years, and they’ll likely
      tell you that in fact, in many ways, it moves at a tectonic pace.
    &lt;br /&gt;
The chasm of time between a methodology or technology’s introduction and
      its going truly mainstream can be huge. There are still jaded old
      &lt;a href="http://en.wikipedia.org/wiki/Standard_Generalized_Markup_Language#History"&gt;
      SGML&lt;/a&gt; folks hollering, “I told you so! In 1970! Without us there’d be
      no web!” from their dusky digital retirement homes. And they’re right
      too. Content Strategy is by no means new. What is new is the recognition
      it’s receiving, and the effect it’s starting to have.
    &lt;br /&gt;
&lt;sub&gt;&lt;a href="http://lh3.ggpht.com/_nJ8XHcWrG0A/TZ8GqNuPLbI/AAAAAAAAAF0/pApi6A0Ng2U/s1600-h/2004-08-21-look-before-you-leap-Machu-Picchu-Peru-3791%5B3%5D.jpg"&gt;
      &lt;img alt="2004-08-21-look-before-you-leap-Machu-Picchu-Peru-3791" border="0" height="215" src="http://lh5.ggpht.com/_nJ8XHcWrG0A/TZ8GqjA_f_I/AAAAAAAAAF4/vYVUGdILkPM/2004-08-21-look-before-you-leap-Machu-Picchu-Peru-3791_thumb%5B1%5D.jpg?imgmax=800" style="background-image: none; border-bottom: 0px; border-left: 0px; border-right: 0px; border-top: 0px; display: inline; padding-left: 0px; padding-right: 0px; padding-top: 0px;" title="2004-08-21-look-before-you-leap-Machu-Picchu-Peru-3791" width="410" /&gt;&lt;/a&gt;&lt;/sub&gt;
    &lt;br /&gt;
&lt;br /&gt;
&lt;sub&gt;Some content professionals really like to think before they cross
      the chasm.&lt;/sub&gt;
    &lt;br /&gt;
&lt;br /&gt;
I see it as two Continents of Content colliding right now, in “the World
      of Content”. I’ve dubbed the continents:
    &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;“&lt;b&gt;The Archipelago of Internet Marketing&lt;/b&gt;”: Not really
      a unified landmass, but more of a well connected set of large islands
      peopled by Web Copy Writers, Web Editors, User Experience Designers,
      Brand Strategists, Marketing Managers, and the rest. It’s enjoyed a rich
      past of big budgets, booms and bubbles (there was a .com burst, but it
      hardly killed the internet, now did it?), its wealth is fed by of the
      most valuable of natural resources in the content world: visibility.
      &lt;/li&gt;
&lt;li&gt;“&lt;b&gt;The Land of TechComms (and a bit of Training)&lt;/b&gt;”:
      Peopled by robust and hearty breed, they’ve put up with neglect,
      starvation, apathy, segregation, misunderstanding, and sometimes
      commoditization to a point that resembles slavery. I picture the land
      without a lot of trees, considering all the printed paper that gets used
      up...
      &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
Along the borders of both nations, there are those that make their living
      crossing back and forth across the gaps – consultants like to live here.
      Generally the disciplines of Information Architecture, Content Modelling,
      Minimalist Writing, Taxonomy, etc. are all on the borders, but generally
      only familiar to the more forward thinking of Tech Communicators.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Inland on each, you have those who are more known for their work in their
      own nations, like &lt;a href="http://www.comtech-serv.com/people.shtml" target="_blank"&gt;JoAnn Hackos&lt;/a&gt; in very forward thinking TechComms,
      Training and Support material, and &lt;a href="http://twitter.com/#%21/halvorson" target="_blank"&gt;Kristina Halvorson&lt;/a&gt;
      for the Web.
    &lt;br /&gt;
&lt;br /&gt;
But… so what?&amp;nbsp; It’s always been this way…
    &lt;br /&gt;
&lt;br /&gt;
Related posts:   &lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;In Part 2, we’ll look at the differences between these worlds and
      why the separation between them is creating problems for even the most
      forward thinking of organisations.&lt;/b&gt;
    &lt;br /&gt;
&lt;ul&gt;&lt;/ul&gt;
&lt;i&gt;Update – since the time of authoring, the recent tragic situation in
      Japan has developed.&amp;nbsp; Of course no insensitivity or relationship to that
      situation is intended or implied.&amp;nbsp; I debated rewriting the entire piece
      to remove the metaphor, but that also seemed inappropriate.&amp;nbsp;&lt;/i&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-size: small;"&gt;See also:&lt;/span&gt; &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide.html"&gt;When Content Strategies Collide: Marketing versus Technical Communication&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-2.html"&gt;When Content Strategies Collide Pt 2: Customer Impact&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-3.html"&gt;When Content Strategies Collide Pt 3: War. Huh! What is it Good For?&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-4.html"&gt;When Content Strategies Collide Pt 4: Enabling vs. Persuasive Content&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide-pt-5-is.html"&gt;When Content Strategies Collide Pt 5: Is Communication Mired in the Past?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://lessworkmoreflow.blogspot.com/2011/05/when-content-strategies-collide-pt-6.html"&gt;When Content Strategies Collide Pt 6: Conclusion, Unification&lt;/a&gt;&amp;nbsp; &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-7743464104750147986?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=D872aeKuYaY:hUA7QW0PZ5o:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=D872aeKuYaY:hUA7QW0PZ5o:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=D872aeKuYaY:hUA7QW0PZ5o:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=D872aeKuYaY:hUA7QW0PZ5o:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=D872aeKuYaY:hUA7QW0PZ5o:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=D872aeKuYaY:hUA7QW0PZ5o:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=D872aeKuYaY:hUA7QW0PZ5o:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=D872aeKuYaY:hUA7QW0PZ5o:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=D872aeKuYaY:hUA7QW0PZ5o:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=D872aeKuYaY:hUA7QW0PZ5o:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=D872aeKuYaY:hUA7QW0PZ5o:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=D872aeKuYaY:hUA7QW0PZ5o:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/D872aeKuYaY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/7743464104750147986/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide.html#comment-form" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/7743464104750147986?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/7743464104750147986?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/D872aeKuYaY/when-content-strategies-collide.html" title="When Content Strategies Collide: Marketing versus Technical Communication" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh3.ggpht.com/_nJ8XHcWrG0A/TZ8GpFBjfzI/AAAAAAAAAFw/kG2ykB4EGv4/s72-c/image_thumb%5B2%5D.png?imgmax=800" height="72" width="72" /><thr:total>3</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/04/when-content-strategies-collide.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkAMR3s4fCp7ImA9WhZREko.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-880296927615145427</id><published>2011-04-07T17:45:00.003+02:00</published><updated>2011-04-08T16:59:46.534+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-04-08T16:59:46.534+02:00</app:edited><title>Congility S1000D – May 24th</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
&lt;img src="http://www.congility.com//images/s1000d/ca-s1000d-banner.jpg" style="float: left; margin: 0px 10px 10px 0px;" /&gt;S1000D is a sufficiently focussed and sufficiently important area of structured content and dynamic publishing that we gave it its own day at Congility 2011.&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
It’s the first dedicated S1000D event to hit the UK since 2003!&lt;br /&gt;
&lt;br /&gt;
If you’re in Aerospace and Defense documentation, Military documentation or various other heavy manufacturing and safety-intensive areas of technical communications, S1000D is the event for you.&lt;br /&gt;
&lt;br /&gt;
It’s in parallel to the &lt;a href="http://www.congility.com/2011" target="_blank"&gt;Congility 2011&lt;/a&gt; &lt;a href="http://www.congility.com/index.php/site/program_by_track/C386/" target="_blank"&gt;workshops&lt;/a&gt;, so you have to choose, but you can get great deals on attending both conferences for one price.&lt;br /&gt;&lt;br /&gt;
&lt;h2&gt;
A Quick Overview &lt;/h2&gt;&lt;br /&gt;
&lt;a href="http://www.congility.com/s1000d" target="_blank"&gt;Congility S1000D&lt;/a&gt;, London May 24, 2011 is the UK event for anyone that is currently needing to produce, evaluate or implement S1000D.&lt;br /&gt;
&lt;br /&gt;
The one day event will cover a broad range of topics appropriate to your objectives and current level of understanding. Topics include S1000D and the ASD suite of specs, Business Rules, the Software Selection process, addressing legacy data, and more.&lt;br /&gt;
&lt;br /&gt;
Fees have been subsidised by our sponsors to encourage easy access and attendance by Aerospace and Defence organisations. Register early to save your spot!&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://www.congility.com/s1000d"&gt;http://www.congility.com/s1000d&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;&lt;h2&gt;
Speaker Highlights&lt;/h2&gt;
Speakers from A&amp;amp;D house-hold names will be there, like:&lt;br /&gt;&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.congility.com/2011/s1000d_speakers2/luetzelberger"&gt;&lt;strong&gt;Horst Luetzelberger&lt;/strong&gt;&lt;/a&gt; from &lt;small&gt;EADS Cassidian&lt;/small&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.congility.com/2011/s1000d_speakers2/proctor"&gt;&lt;strong&gt;Ian Proctor&lt;/strong&gt;&lt;/a&gt; from &lt;small&gt;CDG, a Boeing Company&lt;/small&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.congility.com/2011/s1000d_speakers2/day1"&gt;&lt;strong&gt;Mike Day&lt;/strong&gt;&lt;/a&gt; from &lt;small&gt;Rolls-Royce Defence Aerospace&lt;/small&gt;&lt;/li&gt;
&lt;li&gt;&lt;small&gt;and many more!&lt;/small&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-880296927615145427?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=JnKShPlk3iE:P77Awlt2Xt0:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=JnKShPlk3iE:P77Awlt2Xt0:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=JnKShPlk3iE:P77Awlt2Xt0:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=JnKShPlk3iE:P77Awlt2Xt0:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=JnKShPlk3iE:P77Awlt2Xt0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=JnKShPlk3iE:P77Awlt2Xt0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=JnKShPlk3iE:P77Awlt2Xt0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=JnKShPlk3iE:P77Awlt2Xt0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=JnKShPlk3iE:P77Awlt2Xt0:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=JnKShPlk3iE:P77Awlt2Xt0:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=JnKShPlk3iE:P77Awlt2Xt0:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=JnKShPlk3iE:P77Awlt2Xt0:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/JnKShPlk3iE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/880296927615145427/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/04/congility-s1000dmay-24th.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/880296927615145427?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/880296927615145427?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/JnKShPlk3iE/congility-s1000dmay-24th.html" title="Congility S1000D – May 24th" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/04/congility-s1000dmay-24th.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk8CRn8-cSp7ImA9WhZREko.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-2019440576668798458</id><published>2011-04-07T17:15:00.002+02:00</published><updated>2011-04-08T17:01:07.159+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-04-08T17:01:07.159+02:00</app:edited><title>Pre- Congility Conference Podcast on I’d Rather Be Writing</title><content type="html">&lt;p&gt;&lt;a href="http://idratherbewriting.com/2011/04/05/podcast-content-strategy-and-agility-with-noz-urbina/" target="_blank"&gt;&lt;img style="margin: 10px 10px 10px 0px; float: left" src="http://idratherbewriting.com/wp-content/uploads/2011/04/podcastmicrophone.png" /&gt;&lt;/a&gt;3 podcasts recorded this week: &lt;a href="http://www.congility.com/site/speaker_detail/rockley" target="_blank"&gt;Ann Rockley&lt;/a&gt;, &lt;a href="http://idratherbewriting.com/2011/04/05/podcast-content-strategy-and-agility-with-noz-urbina/" target="_blank"&gt;Rahel Bailie&lt;/a&gt;, and me.&amp;#160; Running an event like &lt;a href="http://www.congility.com/" target="_blank"&gt;Congility&lt;/a&gt; is really fascinating.&amp;#160; Most interesting in the industry buzz has been seeing how we seem to have struck a chord with the ‘&lt;a href="http://www.congility.com/2011/speaker_insights_what_is_content_agility/" target="_blank"&gt;Content Agility&lt;/a&gt;’ concept, and have seen a sudden spike in people referring to content that is ‘agile’ on other events, blogs and websites.&lt;/p&gt;  &lt;p&gt;Check out my podcast here (audio only) and watch this space for quick (&amp;lt;10 min) video podcasts from both Ann and Rahel.&lt;/p&gt;  &lt;p&gt;“&lt;a href="http://idratherbewriting.com/2011/04/05/podcast-content-strategy-and-agility-with-noz-urbina/"&gt;Podcast: Content Strategy and Agility, with Noz Urbina&lt;/a&gt;”&lt;/p&gt;  &lt;p&gt;&lt;a href="http://www.podtrac.com/pts/redirect.mp3?http://idratherbewriting.com/podcasts/nozurbinacongility.mp3" target="_blank"&gt;Download mp3&lt;/a&gt;&lt;/p&gt;  &lt;h2&gt;Congility Speaker Insights – Discuss!&lt;/h2&gt;  &lt;p&gt;To make this year's conference more interactive and try to blunt the ‘cutting edge’ a little, we asked speakers: &lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;&lt;a href="http://www.congility.com/2011/speaker_insights_what_is_content_agility/"&gt;What does &amp;quot;content agility&amp;quot; mean to you? Why does content need agility? &lt;/a&gt;&lt;/li&gt;    &lt;li&gt;&lt;a href="http://www.congility.com/2011/speaker_insights_why_congility/"&gt;Why do you feel Congility 2011 is an event of which you want to be a part?&lt;/a&gt;&lt;/li&gt;    &lt;li&gt;&lt;a href="http://www.congility.com/2011/speaker_insights_content_integration_impact/"&gt;What impact do you feel lack of integration has on customers (i.e., siloed internal processes, or inconsistent and fragmented published content)? &lt;/a&gt;&lt;/li&gt;    &lt;li&gt;&lt;a href="http://www.congility.com/2011/speaker_content_insights/"&gt;Anything else you want to tell us about your talk? For example, who will benefit from it, and what practical things they would learn to take back to their organisations? &lt;/a&gt;&lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;Many of the answers give food for thought and nail this year’s message right on the head.&lt;/p&gt;  &lt;p&gt;Disagree?&amp;#160; Have at them with the feedback features.&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-2019440576668798458?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=oqCr3RzXB8U:ePfvFJfVMdg:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=oqCr3RzXB8U:ePfvFJfVMdg:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=oqCr3RzXB8U:ePfvFJfVMdg:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=oqCr3RzXB8U:ePfvFJfVMdg:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=oqCr3RzXB8U:ePfvFJfVMdg:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=oqCr3RzXB8U:ePfvFJfVMdg:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=oqCr3RzXB8U:ePfvFJfVMdg:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=oqCr3RzXB8U:ePfvFJfVMdg:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=oqCr3RzXB8U:ePfvFJfVMdg:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=oqCr3RzXB8U:ePfvFJfVMdg:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=oqCr3RzXB8U:ePfvFJfVMdg:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=oqCr3RzXB8U:ePfvFJfVMdg:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/oqCr3RzXB8U" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/2019440576668798458/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/04/pre-congility-conference-podcast-on-id.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/2019440576668798458?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/2019440576668798458?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/oqCr3RzXB8U/pre-congility-conference-podcast-on-id.html" title="Pre- Congility Conference Podcast on I’d Rather Be Writing" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/04/pre-congility-conference-podcast-on-id.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE4AR308cCp7ImA9Wx9aEUs.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-3691310486406413588</id><published>2011-03-02T11:46:00.007+01:00</published><updated>2011-03-03T16:42:26.378+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-03T16:42:26.378+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conference" /><category scheme="http://www.blogger.com/atom/ns#" term="content management" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="congility 2011" /><category scheme="http://www.blogger.com/atom/ns#" term="technical simplified english" /><category scheme="http://www.blogger.com/atom/ns#" term="congility" /><title>Andrew Bredenkamp signing up for Congility Talk</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
&lt;a href="https://lh3.googleusercontent.com/-VPSDB30qqCk/TW4q_m72yzI/AAAAAAAAAFY/KUHxpfVTEnw/s1600/brendenkamp_andrew_100x100.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"&gt;&lt;img border="0" src="https://lh3.googleusercontent.com/-VPSDB30qqCk/TW4q_m72yzI/AAAAAAAAAFY/KUHxpfVTEnw/s1600/brendenkamp_andrew_100x100.jpg" /&gt;&lt;/a&gt;I've just been chatting with &lt;a href="http://www.congility.com/site/presenters/bredenkamp"&gt;Andrew Bredenkamp&lt;/a&gt; (CEO, &lt;a href="http://www.acrolinx.com/"&gt;acrolinx&lt;/a&gt;) about &lt;a href="http://www.congility.com/2011"&gt;Congility 2011&lt;/a&gt; and his talk submission. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Of course all the speaker interviews are interesting, but the session with Andrew was particularly so because of how deeply he 'gets' where Congility is trying to go. &lt;br /&gt;
&lt;br /&gt;
If you're going to:&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;reuse&lt;/li&gt;
&lt;li&gt;sell&lt;/li&gt;
&lt;li&gt;be found&lt;/li&gt;
&lt;li&gt;make content consumable and understandable on the first read&lt;/li&gt;
&lt;li&gt;localise/translate&lt;/li&gt;
&lt;li&gt;leverage the crowd and (UGC) user generated content&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
online or offline, then content consistency and the ability to mine large data sets for key patterns is vital. &amp;nbsp;So is attacking the issue across the customer life cycle, and therefore, across the content life cycle. &lt;br /&gt;
&lt;br /&gt;
The content industry is moving so fast that those who can understand where it is are hard to come by. &amp;nbsp;Those that can articulate a clear and well supported vision of where it's going are even rarer. &amp;nbsp;As such, I'm incredibly pleased to have Andrew and so many other top-quality speakers submit, and look forward to having him engage and interact with the Congility audience.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://twitter.com/nozurbina"&gt;&lt;img alt="By: TwitterButtons.com" border="0" height="22" src="http://www.twitterbuttons.com/upload/images/6a2fe834b0twitter-wb-fm.png" title="Follow Noz Urbina on Twitter" width="72.25" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-3691310486406413588?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=9Zqyf-E3mlI:NWRjBG99Rt4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=9Zqyf-E3mlI:NWRjBG99Rt4:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=9Zqyf-E3mlI:NWRjBG99Rt4:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=9Zqyf-E3mlI:NWRjBG99Rt4:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=9Zqyf-E3mlI:NWRjBG99Rt4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=9Zqyf-E3mlI:NWRjBG99Rt4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=9Zqyf-E3mlI:NWRjBG99Rt4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=9Zqyf-E3mlI:NWRjBG99Rt4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=9Zqyf-E3mlI:NWRjBG99Rt4:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=9Zqyf-E3mlI:NWRjBG99Rt4:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=9Zqyf-E3mlI:NWRjBG99Rt4:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=9Zqyf-E3mlI:NWRjBG99Rt4:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/9Zqyf-E3mlI" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/3691310486406413588/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/03/andrew-brendenkamp-signing-up-for.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/3691310486406413588?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/3691310486406413588?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/9Zqyf-E3mlI/andrew-brendenkamp-signing-up-for.html" title="Andrew Bredenkamp signing up for Congility Talk" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://lh3.googleusercontent.com/-VPSDB30qqCk/TW4q_m72yzI/AAAAAAAAAFY/KUHxpfVTEnw/s72-c/brendenkamp_andrew_100x100.jpg" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/03/andrew-brendenkamp-signing-up-for.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUENQ306eCp7ImA9Wx9WFk8.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-7114611755552334781</id><published>2011-01-13T15:52:00.003+01:00</published><updated>2011-01-21T17:34:52.310+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-01-21T17:34:52.310+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="web 2.0" /><category scheme="http://www.blogger.com/atom/ns#" term="tech docs" /><category scheme="http://www.blogger.com/atom/ns#" term="social media" /><category scheme="http://www.blogger.com/atom/ns#" term="trade articles" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><title>Social Media and The Super-Role of the Technical Communicator</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
&lt;div align="left" class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://2.bp.blogspot.com/_nJ8XHcWrG0A/TS8PzSmww3I/AAAAAAAAAE8/HBgRh2k8Xbw/s1600/ISTC_logo_rgb.jpg" imageanchor="1" style="clear: left; cssfloat: left; float: left; margin-bottom: 1em; margin-right: 1em;"&gt;&lt;img border="0" n4="true" src="http://2.bp.blogspot.com/_nJ8XHcWrG0A/TS8PzSmww3I/AAAAAAAAAE8/HBgRh2k8Xbw/s1600/ISTC_logo_rgb.jpg" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;strong&gt;&lt;u&gt;NOTE:&lt;/u&gt;&lt;/strong&gt; &lt;strong&gt;This is a re-publishing of a Social Media and Technical Communcations piece that Adobe requested I put together for a special supplement to the UK's Communicator Magazine (&lt;/strong&gt;&lt;a href="http://www.istc.org.uk/"&gt;&lt;strong&gt;http://www.istc.org.uk/&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;). It was originally released in print only in mid-2010.&amp;nbsp; I was pleased to be selected to introduce the issues in the supplement. &lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;The contributors were &lt;/strong&gt;&lt;strong&gt;&lt;a href="http://twitter.com/dfarb" target="_blank"&gt;David Farbey&lt;/a&gt;, &lt;/strong&gt;&lt;a href="http://twitter.com/onemanwrites"&gt;&lt;strong&gt;Gordon McLean&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt; from Sword Ciboodle, &lt;/strong&gt;&lt;a href="http://twitter.com/rjacquez"&gt;&lt;strong&gt;RJ Jaquez&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt; of Adobe, and &lt;a href="http://twitter.com/nozurbina"&gt;&lt;strong&gt;myself&lt;/strong&gt;&lt;/a&gt;. &lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;Enjoy!&lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
On a recent discussion in the ISTC Yahoo! Group, a Technical Communicator compared Social Media’s significance to his profession as being as useful as a pogo stick or skateboard. In other words, he stated Social Media has no significance to Technical Communications at all. &lt;br /&gt;
&lt;br /&gt;
There is a delicious irony here, in that this particular Technical Communicator posted this theory in an online web forum (a prime example of Social Media) which was created by and for his profession’s community. As evidenced here, it is clear that Social Media can play an extremely important role for technical communicators, enabling them to collaborate on how they guide and direct the strategy of their organisation’s content. &lt;br /&gt;
&lt;br /&gt;
It is a widely-held belief that Social Media is the biggest thing to hit communication since the advent of the internet. Globally, communications are still experiencing the tectonic shifts, but these are only the warnings of the earthquake that is to come. The impact, now and in future, means that users are integrating social media and the ‘old-fashioned’ internet so fast and so deeply that they are starting to blur. Social Media is not just the hot new thing being utilised by the Marketing department to reach audiences; it is bringing back to the fore the forgotten art of conducting business with a two-way conversation between shop and customer. If an organisation isn’t engaging with and guiding this conversation, it will be overwhelmed by it, and most likely, in a negative way. &lt;br /&gt;
&lt;br /&gt;
Let’s tie that into what I’m going to call the ‘super-role’ of the Technical Communicator: to assist the user in getting the best use out of the product or service their company provides. This extends throughout the product lifecycle from pre-sales evaluation content, to repeat business when the client (hopefully) re-invests in a relationship with your organisation because of the great experience they had last time. &lt;br /&gt;
&lt;br /&gt;
Datasheets, manuals, help, knowledge bases and learning/training materials all affect this experience, and to achieve the ‘super-role’, the Technical Communicator attempts to: &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;understand how, where and why different users need content &lt;/li&gt;
&lt;li&gt;become an expert in creating and managing content to meet these needs &lt;/li&gt;
&lt;li&gt;deliver content in the correct context, structure, format and language across all the channels in which the user expects it &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
Like all megatrends, the Social Media explosion is the sum of various trends that have been building for a while, some since the first pre-internet Bulletin Board Systems (BBSs). In 2009, digital marketing intelligence agency Comscore stated that “social networking attracts three quarters of European internet users [15 and over]” – this means that 75% of all people in Europe using the web engage in Social Media. Although teenagers comprise only a small slice of the sample group, as they are tomorrow’s consumers, their impact is still weighted heavily. These results show there has already been a monumental impact on how and why people collectively access online information. &lt;br /&gt;
&lt;br /&gt;
&lt;em&gt;&lt;sup&gt;&lt;em&gt;Comscore report: &lt;/em&gt;&lt;a href="http://www.comscore.com/Press_Events/Press_Releases/2009/2/Social_Networking_Spain/(language)/eng-US"&gt;&lt;em&gt;http://www.comscore.com/Press_Events/Press_Releases/2009/2/Social_Networking_Spain/(language)/eng-US&lt;/em&gt;&lt;/a&gt;&lt;/sup&gt;&lt;/em&gt; &lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://3.bp.blogspot.com/_nJ8XHcWrG0A/TS8QMoOhs9I/AAAAAAAAAFA/h4GHBSNkEz0/s1600/Site-ranks-social-media-content-strategy.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="270" n4="true" src="http://3.bp.blogspot.com/_nJ8XHcWrG0A/TS8QMoOhs9I/AAAAAAAAAFA/h4GHBSNkEz0/s400/Site-ranks-social-media-content-strategy.JPG" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://1.bp.blogspot.com/_nJ8XHcWrG0A/TS8Q8PFPnFI/AAAAAAAAAFM/XKaA7mgo1HQ/s1600/Site-ranks-social-media-content-strategy6-10.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="251" n4="true" src="http://1.bp.blogspot.com/_nJ8XHcWrG0A/TS8Q8PFPnFI/AAAAAAAAAFM/XKaA7mgo1HQ/s400/Site-ranks-social-media-content-strategy6-10.JPG" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;h2&gt;
Social Media Facts &lt;/h2&gt;
&lt;ul&gt;&lt;br /&gt;
&lt;li&gt;Social Media is not just for socialising. A quick internet search shows that most any organisation you can think of has content (video, blog, articles, etc.) posted on the internet from its employees. It is therefore fair to say that the business perspective and presence is now a key part of what we call “Social Media”. &lt;/li&gt;
&lt;li&gt;Marketing departments no longer own web communications. As more documentation and training material is posted online (both in textual and media/video formats), or gets embedded directly into application interfaces, there is a greater need to include technical information within an overall corporate web strategy. I’m sure you’ll have noticed that more often than not, pressing the F1 key takes us to a live, hosted website instead of to an HTML file or CHM file, so even our definition of ‘electronic’ is changing. A corporate web strategy will invariably create a technological requirement for a global web server, which will force the integration of goals and cooperation between Marketing and IT and various content-generating departments. This is no longer the remit for Fortune 5000 organisations only – small to medium-sized businesses are addressing this issue as well. &lt;/li&gt;
&lt;li&gt;Social Media isn’t necessarily “public”. Many Technical Communicators suffer from inconsistent, out-of-date or poor access to product knowledge within their organisation. Social Media can improve this because by its very nature, the organisation is itself a ‘community’. Therefore, the collaborative aspects of Social Media can all apply across teams, geographies or departments. For example, Technical Communicators can engage in the WIKIs and blogs utilised by their Software and R&amp;amp;D Departments. These can be fantastic content lifecycle tools which can be used as a product knowledge source*. Large organisations may even have Subject Matter Expert blogs (public web or internal) to view. From the public space, Technical Communicators can monitor user blogs and Twitter streams to learn the issues which users are having with their product directly. &lt;br /&gt;&lt;br /&gt;&lt;sup&gt;Of course, they can also be badly implemented, poorly organised and a waste of time&lt;/sup&gt; &lt;/li&gt;
&lt;li&gt;Many large organisations are integrating Social Media functions directly into their product help. Microsoft has been at it for nearly a decade with their more technical products, bringing programmer blogs and communities into its help and knowledge base applications. Adobe Creative Suite 3 brought link management and user communications into their online help, and in CS4 and the Technical Communications Suite, they’ve implemented an AIR application which enables Social Media posts to be hosted on an information platform, enabling a community of Adobe users to generate their own media which links directly with the help, and thus forms an extended part of it. &lt;br /&gt;&lt;sup&gt;&lt;a href="http://www.adobe.com/community/publishing/"&gt;http://www.adobe.com/community/publishing/&lt;/a&gt;&lt;/sup&gt; &lt;/li&gt;
&lt;li&gt;People have integrated the concept of Search into their core brain functionality, using Google before thinking. Consider: users who type URLs into Google instead of into their browser’s address bar; users who employ Google as a spell checker; and users who haven’t consulted a paper map in the past 5 years. &lt;/li&gt;
&lt;li&gt;The all-time classic: people don’t want to read manuals. Thanks to Social Media, users can and are viewing video tutorials contributed by other users as another way to avoid picking up the manual. &lt;/li&gt;
&lt;li&gt;Organisations of all kinds are investing heavily in Social Media as a continuing conversation channel with their prospects and customers via different types of this technology (blogging, WIKIs, microblogging, forums, video, etc). The Society for New Communications Research just published a report discussing the incredible success of the by-product of this phenomenon: revenue-rich online advertising. This reinforces just how seriously the market considers these information platforms. &lt;br /&gt;&lt;sup&gt;&lt;a href="http://sncr.org/wp-content/uploads/2008/08/new-influencers-study.pdf"&gt;http://sncr.org/wp-content/uploads/2008/08/new-influencers-study.pdf&lt;/a&gt;&lt;/sup&gt; &lt;/li&gt;
&lt;li&gt;2 of the top 3&lt;sup&gt;[1]&lt;/sup&gt; (Facebook and YouTube, after Google) and 4 out of the top 10 most used sites on the internet are social media/networking sites. Created as recently as July, 2006, Twitter has shot to 14&lt;sup&gt;th&lt;/sup&gt; on the list and continues to rise. Continuously innovative, Google has recently created the ultimate Social Media extension to search, the “SideWiki&lt;sup&gt;[2]&lt;/sup&gt;”, where even after you’ve searched and found a page – any page, anywhere&lt;sup&gt;[3]&lt;/sup&gt; – Google users can comment on and extend the site being viewed. &lt;br /&gt;&lt;sub&gt;&lt;strong&gt;[1] UPDATE&lt;/strong&gt;: As of writing these numbers have changed.&amp;nbsp; Twitter is now in the top 10, as predicted! Ha!&amp;nbsp; The other two social media sites I was talking about were WIKIpedia and Blogger.com: &lt;a href="http://www.alexa.com/topsites"&gt;http://www.alexa.com/topsites&lt;/a&gt; &lt;/sub&gt;&lt;br /&gt;&lt;br /&gt;&lt;sup&gt;&lt;strong&gt;[2]&lt;/strong&gt; &lt;a href="http://googleblog.blogspot.com/2009/09/help-and-learn-from-others-as-you.html"&gt;http://googleblog.blogspot.com/2009/09/help-and-learn-from-others-as-you.html&lt;/a&gt;&lt;/sup&gt; &lt;br /&gt;&lt;br /&gt;&lt;sup&gt;&lt;strong&gt;[3]&lt;/strong&gt; Google has opted to “turn off” SideWiki functions for pornography or otherwise sexually explicit sites, and unfortunately I think, have made it (or have only been able to make it) available only to users of their Google Toolbar for Firefox and Internet Explorer. &lt;/sup&gt;&lt;/li&gt;
&lt;/ul&gt;
If taken individually, these items can seem more or less trivial or arguable, but what we’re seeing is a cumulative phenomenon and it must be interpreted that way. Social Media technologies are a primary connection between the customer and the business. &lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;
The Importance of (and to) Content Strategy&lt;/h2&gt;
&lt;br /&gt;
So, Social Media is big and it’s here to stay. To a market already struggling to deliver to multiple channels, it presents a whole collection of new channels, and worse yet, they’re moving and changing faster than we’ve ever seen publishing channels move. To tackle multiple channels, you have to work smarter, not harder. This means creating content which is flexible in structure so that it can be utilised in multiple contexts; using a format-neutral content storage method to allow for different viewing formats; and leveraging reuse so that your content can be quickly updated when necessary across all channels. All of these factors underline the importance of taking a very strategic approach to content, not a deliverable- or document-based approach. A successful content strategy is something you develop and maintain holistically, above and apart from specific projects and deadlines, and overarches all content processes being delivered to all channels. It should take the following into account: &lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Your content sources: the product, internal and external Subject Matter Experts, end users, yourself and your fellow professional communicators &lt;/li&gt;
&lt;li&gt;Your content consumers: internal and external people who need content to do their jobs &lt;/li&gt;
&lt;li&gt;Your content constraints: localisation/translation, accessibility, usability, industry standards, corporate standards, branding guidelines, etc. &lt;/li&gt;
&lt;li&gt;The product and content lifecycles: all the different touch points between the players listed above across time &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;h2&gt;
Embrace Your Super-Role&lt;/h2&gt;
&lt;br /&gt;
It’s a contradiction to think you can fulfil the role of the Technical Communicator, which includes understanding the user information needs and trends, and yet dismiss Social Media as the latest technological pogo stick going. User expectations have changed, the conversations are raging, and you need to participate to know what’s being said and how you’re going to need to speak in the future if you want to be heard.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-7114611755552334781?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=d4cbswcSW8w:JB1f7LCRR0A:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=d4cbswcSW8w:JB1f7LCRR0A:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=d4cbswcSW8w:JB1f7LCRR0A:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=d4cbswcSW8w:JB1f7LCRR0A:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=d4cbswcSW8w:JB1f7LCRR0A:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=d4cbswcSW8w:JB1f7LCRR0A:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=d4cbswcSW8w:JB1f7LCRR0A:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=d4cbswcSW8w:JB1f7LCRR0A:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=d4cbswcSW8w:JB1f7LCRR0A:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=d4cbswcSW8w:JB1f7LCRR0A:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=d4cbswcSW8w:JB1f7LCRR0A:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=d4cbswcSW8w:JB1f7LCRR0A:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/d4cbswcSW8w" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/7114611755552334781/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2011/01/social-media-and-super-role-of.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/7114611755552334781?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/7114611755552334781?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/d4cbswcSW8w/social-media-and-super-role-of.html" title="Social Media and The Super-Role of the Technical Communicator" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_nJ8XHcWrG0A/TS8PzSmww3I/AAAAAAAAAE8/HBgRh2k8Xbw/s72-c/ISTC_logo_rgb.jpg" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2011/01/social-media-and-super-role-of.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkEESXY9fip7ImA9Wx9WGEU.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-5954597486176943003</id><published>2010-12-09T15:30:00.016+01:00</published><updated>2011-01-24T16:56:48.866+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-01-24T16:56:48.866+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="web 2.0" /><category scheme="http://www.blogger.com/atom/ns#" term="conference" /><category scheme="http://www.blogger.com/atom/ns#" term="content management" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><category scheme="http://www.blogger.com/atom/ns#" term="workflow" /><category scheme="http://www.blogger.com/atom/ns#" term="mekon" /><title>Drowning Your Audience in Content</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
&lt;a href="http://lh4.ggpht.com/_nJ8XHcWrG0A/TQDn9iu9biI/AAAAAAAAADY/c7IOx_hcUSI/s1600-h/ocean-wave-jj-001%5B3%5D.jpg"&gt;&lt;img alt="ocean-wave-jj-001" border="0" height="281" src="http://lh6.ggpht.com/_nJ8XHcWrG0A/TQDn_K0dq9I/AAAAAAAAADc/gTawuglPw3I/ocean-wave-jj-001_thumb%5B1%5D.jpg?imgmax=800" style="background-image: none; border-bottom-width: 0px; border-left-width: 0px; border-right-width: 0px; border-top-width: 0px; display: inline; padding-left: 0px; padding-right: 0px; padding-top: 0px;" title="ocean-wave-jj-001" width="412" /&gt;&lt;/a&gt;&lt;br /&gt;
&lt;sup&gt;Image - treehugger.com&lt;/sup&gt;&lt;br /&gt;
The National Health Service just got caught red-handed doing what way too many companies do every day: &lt;br /&gt;
&lt;blockquote&gt;
“The &lt;a href="http://www.guardian.co.uk/society/nhs" target="_blank"&gt;NHS&lt;/a&gt; spends up to £86m a year on thousands of websites that are difficult to find, badly designed and irrelevant to patient needs, according to a leaked government report.”&lt;/blockquote&gt;
This article made me dust off my biggest jaded, bitter sigh. It’s like a macrocosm example of what happens both in private enterprises and not-for-profit organisations all the time.&lt;br /&gt;
&lt;br /&gt;
With Content Strategy featuring high on the &lt;a href="http://www.congility.com/" target="_blank"&gt;Congility&lt;/a&gt; track-list this year, and this year’s theme of “Content Integration”, I thought that the NHS article was a great example to illustrate what “Content Integration” actually means.&lt;br /&gt;
&lt;br /&gt;
&lt;sup&gt;Full NHS article: &lt;a href="http://www.guardian.co.uk/society/2010/aug/04/nhs-websites-failing-patients" target="_blank"&gt;http://www.guardian.co.uk/society/2010/aug/04/nhs-websites-failing-patients&lt;/a&gt;&lt;/sup&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;
Delivery Overload – Content Flowing All Around but Nary a Drop to Drink&lt;/h2&gt;
&lt;br /&gt;
&lt;b&gt;&lt;i&gt;&lt;a href="http://lh4.ggpht.com/_nJ8XHcWrG0A/TQDoBAMHxMI/AAAAAAAAADg/7PeMfExiz0w/s1600-h/Waterfall%2097%5B7%5D.jpg"&gt;&lt;img alt="Waterfall 97" border="0" height="315" src="http://lh5.ggpht.com/_nJ8XHcWrG0A/TQDoCEwYhlI/AAAAAAAAADk/P8SryWorokU/Waterfall%2097_thumb%5B5%5D.jpg?imgmax=800" style="background-image: none; border-bottom-width: 0px; border-left-width: 0px; border-right-width: 0px; border-top-width: 0px; display: inline; padding-left: 0px; padding-right: 0px; padding-top: 0px;" title="Waterfall 97" width="419" /&gt;&lt;/a&gt;&lt;/i&gt;&lt;/b&gt;&lt;br /&gt;
&lt;sup&gt;Image&amp;nbsp;- waterfall-wallpapers.com&lt;/sup&gt;&lt;br /&gt;
&lt;br /&gt;
Time and time again I consult with organisations who seem to create new streams of content like water cascading across rocks. Every time the flow of information encounters an obstacle, it splits and creates a new smaller, weaker stream. &lt;br /&gt;
&lt;br /&gt;
Companies struggle as it is getting different media like print and electronic formats, or even content for different product-lines, to jive together. Not only is the web a stream of content, it’s a relatively inexpensive one to set up new tributaries and sub-streams (if you only look at the short term costs), it’s easy to be seduced into creating websites all over the place.&lt;br /&gt;
&lt;br /&gt;
There are legitimate reasons to maintain multiple websites, for example, an organisation with two clearly delineated brands with low audience overlap. For example, Aston Martin (&lt;a href="http://www.astonmartin.com/" target="_blank"&gt;http://www.astonmartin.com/&lt;/a&gt;) and Aston Martin Racing (&lt;a href="http://www.astonmartinracing.com/" target="_blank"&gt;http://www.astonmartinracing.com/&lt;/a&gt;). &lt;br /&gt;
&lt;br /&gt;
They’re both Aston Martin, but the business models, content, products and customers are vastly different. For those interested in the main brand, right off the homepage you can get to the Racing sub-brand. It’s also easy to get back (although in my opinion the link back should be more obvious).&lt;sup&gt;&lt;br /&gt;&lt;/sup&gt;&lt;br /&gt;
&lt;sup&gt;&lt;a href="http://www.mekon.com/index.php/pages/clients/luxury_car/case_studies/clients" target="_blank"&gt;Mekon case-study on Aston-Martin&lt;/a&gt;&lt;/sup&gt;&lt;br /&gt;
&lt;h2&gt;
Water-Logged Reasoning&lt;/h2&gt;
&lt;blockquote&gt;
A layer of NHS bureaucracy, represented by websites built by primary care trusts, foundation trusts and strategic health authorities, received "almost no recognition" from the public. "The question is raised why these sites were developed in the first instance," the report says.&lt;/blockquote&gt;
However, there are thousands &lt;i&gt;more&lt;/i&gt; professional websites than there are &lt;i&gt;valid&lt;/i&gt; reasons for sites to exist. Here’s some of my favourite reasons I’ve actually had explained to me, with or without a straight face, some of them various times in different projects:&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;“That site exists because IT couldn’t figure out how to control access to the content if it was on the main site.” &lt;/li&gt;
&lt;li&gt;“Our main site is marketing stuff and the other site is for our customers and technical content.” &lt;/li&gt;
&lt;li&gt;“That site exists because it was a big project so we thought it deserved its own website.” &lt;/li&gt;
&lt;li&gt;“No one around here really knows why it’s a separate site, but it’s been that way a while so we just leave it like that.” &lt;/li&gt;
&lt;li&gt;“IT (or Marketing) didn’t have time to help us with our need so we just hired an agency and set this site up.” &lt;/li&gt;
&lt;li&gt;“We could have done a common site but we didn’t realise that another department had one so similar already running.” &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
And my all-time fav:&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;“Our departmental management set up our own site because he/she doesn’t want any other departments telling us what to do” &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;h2&gt;
Integrate Content - Let Them Quench Their Thirst&lt;/h2&gt;
&lt;br /&gt;
&lt;div align="center"&gt;
&lt;i&gt;&lt;a href="http://lh5.ggpht.com/_nJ8XHcWrG0A/TQDoC7qBzyI/AAAAAAAAADo/S2LpZZgNzIY/s1600-h/A-man-enjoys-water-cooler-water%5B6%5D.jpg"&gt;&lt;img alt="A-man-enjoys-water-cooler-water" border="0" height="343" src="http://lh3.ggpht.com/_nJ8XHcWrG0A/TQDoDpYgOPI/AAAAAAAAADs/zq-Ja7GrzHI/A-man-enjoys-water-cooler-water_thumb%5B2%5D.jpg?imgmax=800" style="background-image: none; border-bottom-width: 0px; border-left-width: 0px; border-right-width: 0px; border-top-width: 0px; display: inline; padding-left: 0px; padding-right: 0px; padding-top: 0px;" title="A-man-enjoys-water-cooler-water" width="227" /&gt;&lt;/a&gt;&lt;/i&gt;&lt;/div&gt;
&lt;div align="center"&gt;
&lt;sup&gt;Image - thewaterdeliverycompany.com&lt;/sup&gt;&lt;/div&gt;
I said it in some recent posts, but I’ll say it again:&lt;br /&gt;
&lt;br /&gt;
YOUR CUSTOMER DOESN’T CARE ABOUT YOUR ORG CHART&lt;br /&gt;
&lt;blockquote&gt;
The research also warned that poor websites mean "the confidence of the public in the NHS brand may be diminished". Patients wanted to see "one NHS" online rather than a proliferation of websites.&lt;/blockquote&gt;
Most of these delivery channels just add to the issue of duplication and confusion that happens across other forms and formats of content. Content integration is about unifying process and standards in an organisation so that customers are presented information in a way that makes sense for them, not in the way that is patterned after the teams and departments that created it.&lt;br /&gt;
&lt;br /&gt;
Inconsistencies in areas like these annoy customers (and staff who need the information) all to tiny little pieces, and dilute your brand: &lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;How to do a task or process with your product or your company &lt;/li&gt;
&lt;li&gt;How to communicate with your company &lt;/li&gt;
&lt;li&gt;How to refer to or find things across your different sites, products, hardware, software, marketing, sales, user, or&amp;nbsp;maintenance materials (in short: content modelling, structural and terminology issues) &lt;/li&gt;
&lt;li&gt;What features are offered on some sites vs. others &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
Yes – even features can be annoying. For example, at the &lt;a href="http://www.online-information.co.uk/"&gt;Online Information&lt;/a&gt; show last week, we were talking to one of the world’s largest publishers. They recently implemented ‘word wheels’ (like those drop-down lists of auto-complete text for your search-terms as you type in Google) on some of their online products. The keyword: &lt;i&gt;some&lt;/i&gt;. They actually get calls to customer support from people saying, ‘You sold us access to this content, and some of it doesn’t have word wheels like our other content’. They would actually have had a better customer experience with no nifty function because they wouldn’t think some sites were ‘broken’. It’s a major organisation – they think – surely their back-end content platform was integrated such that navigation functions were consistent? Sure.&lt;br /&gt;
&lt;br /&gt;
I don’t want to trash-talk anyone by name, so for an actual example I’ll pick on a company who I’ve said good things about in past, and has already sorted out the problem: SDL. SDL has gone on the acquisitions trail (warpath?) in recent years, snapping up four organisations that &lt;a href="http://www.mekon.com/"&gt;Mekon&lt;/a&gt; worked and implemented with prior to the acquisition (Idiom, Trisoft, XOpus and XyEnterprise). If you take Trisoft + XyEnteprise, you get SDL "XySoft". As a result, lots of little websites were born of these mergers, so for a while they had (all these neatly redirect to sdl.com today):&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.sdlxysoft.com/"&gt;http://www.sdlxysoft.com/&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.tri-soft.com/"&gt;http://www.tri-soft.com/&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.sdltrisoft.com/"&gt;http://www.sdltrisoft.com/&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.sdl.com/"&gt;http://www.sdl.com/&lt;/a&gt; &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
SDL totally get the problem and in fact asked me (informally) to contribute a telephone interview / usability review to their re-architecture efforts a while ago. Even at that point at least the sites basically looked the same, you just jumped around between them and couldn’t figure out how you got there or how to get back. Also, you have to sympathise. They have one of the valid reasons to be having this issue, albeit a temporary one: acquisitions and mergers. Integrating new companies is hard, and if you keep buying them up all the time, then there’s going to be a more or less constant job of integrating their existing presence.&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;
A Wash-Up&lt;/h2&gt;
&lt;br /&gt;
Some points of consideration before you get dragged down by the content undertow and start drowning your people in content streams:&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Separate customer or audience profiles / personas don’t necessarily mean separate sites. &lt;/li&gt;
&lt;li&gt;Separate sites don’t mean different back-end architecture. &lt;/li&gt;
&lt;li&gt;A sub-domain (adding a part before the main domain, e.g.: &lt;strong&gt;mail&lt;/strong&gt;.google.com or &lt;strong&gt;maps&lt;/strong&gt;.google.com) is better than a whole new domain. &lt;/li&gt;
&lt;li&gt;Although you might think it’s ‘special treatment’ to give customers vs. other people (prospective customers) a new discrete domain with separate content, it can be annoying if you’ve not properly integrated the content and features. Existing customers are your best prospects, so don't annoy them making them jump back and forth between sites to interact with things they’ve not yet bought, or worse, linking back and forth because you’ve got some content in one site and not the other. &lt;/li&gt;
&lt;li&gt;Separate sites are a breeding ground for (needlessly) inconsistent information architectures, terminology and navigation tools. &lt;/li&gt;
&lt;li&gt;If you are going to have separate sites, have clear guidelines around when a new one should be created. &lt;/li&gt;
&lt;li&gt;See if you can make internal staff use the same content sources as external users. If they stop using ‘back doors’ to find information, you’ll get loads (tidal waves!) of usability feedback (read: screaming and yelling) when things aren’t optimised for findability. &lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
I’d love to hear your stories of navigation and content inconstancies. No need to name names, so feel free to air the details of the salmon-like upstream swimming lengths users have had to go&amp;nbsp;through to get the content they want.&lt;br /&gt;
&lt;br /&gt;
PS – Speaking of ‘findability’ – I’m becoming much more active on Twitter these days: &lt;br /&gt;
&lt;a href="http://twitter.com/nozurbina"&gt;&lt;img alt="By: TwitterButtons.com" border="0" height="22" src="http://www.twitterbuttons.com/upload/images/6a2fe834b0twitter-wb-fm.png" title="Follow Noz Urbina on Twitter" width="72" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-5954597486176943003?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=Eg-f-v92hwc:NP8A83ap6_0:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=Eg-f-v92hwc:NP8A83ap6_0:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=Eg-f-v92hwc:NP8A83ap6_0:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=Eg-f-v92hwc:NP8A83ap6_0:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=Eg-f-v92hwc:NP8A83ap6_0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=Eg-f-v92hwc:NP8A83ap6_0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=Eg-f-v92hwc:NP8A83ap6_0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=Eg-f-v92hwc:NP8A83ap6_0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=Eg-f-v92hwc:NP8A83ap6_0:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=Eg-f-v92hwc:NP8A83ap6_0:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=Eg-f-v92hwc:NP8A83ap6_0:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=Eg-f-v92hwc:NP8A83ap6_0:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/Eg-f-v92hwc" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/5954597486176943003/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2010/12/drowning-your-audience-in-content.html#comment-form" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/5954597486176943003?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/5954597486176943003?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/Eg-f-v92hwc/drowning-your-audience-in-content.html" title="Drowning Your Audience in Content" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh6.ggpht.com/_nJ8XHcWrG0A/TQDn_K0dq9I/AAAAAAAAADc/gTawuglPw3I/s72-c/ocean-wave-jj-001_thumb%5B1%5D.jpg?imgmax=800" height="72" width="72" /><thr:total>2</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2010/12/drowning-your-audience-in-content.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUMNSH8_fCp7ImA9Wx9XFkg.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-4872556856290727867</id><published>2010-11-25T21:15:00.011+01:00</published><updated>2011-01-10T10:58:19.144+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-01-10T10:58:19.144+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="DITA" /><category scheme="http://www.blogger.com/atom/ns#" term="content reuse" /><category scheme="http://www.blogger.com/atom/ns#" term="content management" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><category scheme="http://www.blogger.com/atom/ns#" term="darwin information typing architecture" /><title>Cookin’ Up Some (XML) Content</title><content type="html">This post is a response to something on &lt;a href="http://idratherbewriting.com/"&gt;Tom Johnson’s blog – idratherbewriting.com&lt;/a&gt; (upon which I is be groovin’ regularly and I highly recommend).&lt;br /&gt;
&lt;br /&gt;
On a &lt;a href="http://idratherbewriting.com/2010/11/24/forum-wiki-blog-workflow/comment-page-1/#comment-169983"&gt;recent post&lt;/a&gt; we got into a discussion regarding the use of XML. Naturally I was all over that. I felt really bad I talked so much but never addressed a direct question of Tom’s:&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;“Here’s what I am interested in with XML. How can I extract pages on a Mediawiki wiki and package them up into selective guides and then publish them in a book-like PDF format?”&lt;/i&gt;&lt;br /&gt;
&lt;br /&gt;
I felt like I was ‘flooding’ the comments so I moved this over here.&lt;br /&gt;
&lt;br /&gt;
I’m afraid I don’t know the specifics of getting content out of Mediawiki. I’ve never implemented nor have I reviewed it in depth. I can say that I doubt it’s simple. XML is not a format like others. It’s a meta-format. Saying something is XML is like saying a food is ‘French’ rather than saying it’s a ‘croissant’. You may know how to make French food generally, but that doesn’t mean you know how to bake, much less bake croissants. I’m sure there’s a better analogy than that, but that’s what I’ve got for now. So, you can’t just go to ‘XML’ anymore than you can make a ‘French meal’ without at some point nailing down exactly what recipe you’re going to be cooking up. Even DITA is somewhat flexible. You can go to DITA, but not all DITA files are equal. Like FrameMaker or Word with our without the judicious use of styles; same format, very different beast.&lt;br /&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://1.bp.blogspot.com/_nJ8XHcWrG0A/TQdtBtgkggI/AAAAAAAAAEs/WqEgxf1N5Ro/s1600/2002-07-20+Paris+0160-crp-lvls.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="246" n4="true" src="http://1.bp.blogspot.com/_nJ8XHcWrG0A/TQdtBtgkggI/AAAAAAAAAEs/WqEgxf1N5Ro/s320/2002-07-20+Paris+0160-crp-lvls.jpg" width="320" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;span style="font-size: small;"&gt;A fond memory of Paris, but god knows how they pulled it off!&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
The reason there’s no tool to do it is because there’s not much of a point. Like a machine that cooks for you, unless you’re specific in setting it up, the chances it’ll cook what &lt;i&gt;you&lt;/i&gt; want are slim. What happens in practice is that people make a mapping from the Mediawiki (source) mark-up to the XML (target) mark-up that *they* want; as simple or as complex as their business case dictates. Once you’ve got the extraction routine in place, you’ll get an XML file to your specifications from whichever WIKI entries you like. You need a publishing tool chain set up to handle that file. If you don’t already have a system to publish your XML through, there’s not a lot of point in going generic XML. DITA is better in this regard.&lt;br /&gt;
&lt;br /&gt;
DITA gets around this to a great degree by allowing you to use whatever DITA-compliant applications you want (there are far more generic DITA tools than XML tools). You could apply DITA filtering attributes turning certain content ‘on or off’ depending on your intended audience.&lt;br /&gt;
&lt;br /&gt;
This might sound a bit opaque or vague – I’m not sure you’re existing level of XML knowledge. Unfortunately, you need a critical mass of XML understanding to intuit the details. Again, back to my cooking analogy, if you’ve mastered meat dishes and someone asks you how to cook a cheese soufflé, you might not be able to answer. If they asked you how to make salami, you might not be able to make them understand the response if they don’t already have a certain background.&lt;br /&gt;
&lt;br /&gt;
Maybe I should have gone with music instead of cooking as my analogy? Anyway, unless you really had a recurring reason to do it, you’d (probably) not go through the trouble to do XML.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://lh5.ggpht.com/_nJ8XHcWrG0A/TO7D1XF5UAI/AAAAAAAAADQ/vEcD8OjyGkM/s1600-h/iStock_000005069798Large%5B4%5D.jpg"&gt;&lt;img alt="iStock_000005069798Large" border="0" height="278" src="http://lh4.ggpht.com/_nJ8XHcWrG0A/TO7D2nibPzI/AAAAAAAAADU/0qz-JJfxxwY/iStock_000005069798Large_thumb%5B1%5D.jpg?imgmax=800" style="background-image: none; border-bottom: 0px; border-left: 0px; border-right: 0px; border-top: 0px; display: inline; padding-left: 0px; padding-right: 0px; padding-top: 0px;" title="iStock_000005069798Large" width="382" /&gt;&lt;/a&gt;&lt;br /&gt;
&lt;span style="font-size: x-small;"&gt;&lt;b&gt;Industrialising content processes is highly beneficial, but you need a defined reason (a business case) that makes sense.&lt;/b&gt;&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
DITA/XML is an ‘industrialisation’ of content processes. You don’t set up a whole content strategy and governance process for something you’re only going to do once (unless that thing is a truly big undertaking). You don’t buy a 100-gallon mixing machine if you’re only going to use it once, you just get out 10 10-gallon spots and pull a few all-nighters. You don’t set an assembly line up if you want to make sculpture.&amp;nbsp; Same for XML – it makes sense for things that are going to be used on a certain volume of content, or by people (or small teams) expert enough to handle every aspect themselves.&lt;br /&gt;
&lt;br /&gt;
PS – Call for Speakers for &lt;a href="http://www.congility.com/"&gt;Congility 2011&lt;/a&gt; is still open!&lt;br /&gt;
&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-4872556856290727867?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=LU2OTQvjI3w:j6n_Kkbkrc8:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=LU2OTQvjI3w:j6n_Kkbkrc8:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=LU2OTQvjI3w:j6n_Kkbkrc8:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=LU2OTQvjI3w:j6n_Kkbkrc8:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=LU2OTQvjI3w:j6n_Kkbkrc8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=LU2OTQvjI3w:j6n_Kkbkrc8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=LU2OTQvjI3w:j6n_Kkbkrc8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=LU2OTQvjI3w:j6n_Kkbkrc8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=LU2OTQvjI3w:j6n_Kkbkrc8:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=LU2OTQvjI3w:j6n_Kkbkrc8:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=LU2OTQvjI3w:j6n_Kkbkrc8:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=LU2OTQvjI3w:j6n_Kkbkrc8:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/LU2OTQvjI3w" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/4872556856290727867/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2010/11/cookin-up-some-xml-content.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/4872556856290727867?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/4872556856290727867?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/LU2OTQvjI3w/cookin-up-some-xml-content.html" title="Cookin’ Up Some (XML) Content" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/_nJ8XHcWrG0A/TQdtBtgkggI/AAAAAAAAAEs/WqEgxf1N5Ro/s72-c/2002-07-20+Paris+0160-crp-lvls.jpg" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2010/11/cookin-up-some-xml-content.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEIARH8-eCp7ImA9Wx9XGU4.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-5037624278398222536</id><published>2010-10-13T10:39:00.003+02:00</published><updated>2011-01-13T16:29:05.150+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-01-13T16:29:05.150+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="DITA" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy audit" /><category scheme="http://www.blogger.com/atom/ns#" term="content reuse" /><category scheme="http://www.blogger.com/atom/ns#" term="content management" /><category scheme="http://www.blogger.com/atom/ns#" term="trade articles" /><category scheme="http://www.blogger.com/atom/ns#" term="technical documentation" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><category scheme="http://www.blogger.com/atom/ns#" term="darwin information typing architecture" /><category scheme="http://www.blogger.com/atom/ns#" term="workflow" /><category scheme="http://www.blogger.com/atom/ns#" term="mekon" /><title>Developing a Content Strategy</title><content type="html">&lt;span class="Apple-style-span" style="font-size: 15px;"&gt;&lt;/span&gt;&lt;br /&gt;
This post is a redistribution of my recent article in Communicator Magazine on Developing a Content Strategy. It discusses how Content Strategy works best when approached with an open mind, following the wider scope of the content lifecycle, not trying to hammer into the shape of your departmental org-chart. It should address all incarnations of content, not any one output, channel or team.&lt;br /&gt;
&lt;br /&gt;
This is somewhat slanted towards the Technical Communications audience that reads Communicator Magazine, but I'd only make minor adjustments or additions for a more marketing or 'web-based' audience when discussing Content Strategy.&lt;br /&gt;
&lt;br /&gt;
I was very happy and honoured they chose it for the top spot on the cover articles list.&lt;br /&gt;
I'm eager for comments and thoughts here for via &lt;a href="http://twitter.com/nozurbina"&gt;twitter&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
The article:&lt;br /&gt;
&lt;br /&gt;
Richard Truscott, one of Mekon's Content Strategy Audit clients, recently produced an article regarding his content journey discusses a methodical approach to revising and updating his organisation’s content strategy. Along the way he encountered many familiar pitfalls and hurdles, like the cultural impact of content process change, the departmental boundaries that may need to be crossed and a large number of tools and technologies to review in a reasonable amount of time.&lt;br /&gt;
&lt;br /&gt;
He also found, as many other organisations do, that there are assets and useful best practices available in the content industry that he could learn and apply in his work. Richard looked at and used several available options:&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;DITA content - paired with a component content management system (CCMS)&lt;/li&gt;
&lt;li&gt;A metadata classification system (also known as taxonomy)&lt;/li&gt;
&lt;li&gt;The Mekon Content Strategy Audit™ (CSA)&lt;/li&gt;
&lt;li&gt;A cross-departmental, knowledge-oriented workflow utilising subject matter experts (SMEs).&lt;/li&gt;
&lt;/ul&gt;
This article aims to address what a Content Strategy is, and how you can start building one. I will be using some practical examples to illustrate, as well as referring specifically to Richard’s experience.&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;
What is content strategy?&lt;/h2&gt;
&lt;br /&gt;
Content strategy is a term that touches upon every aspect of content. Organisations often have more content than they actually know what to do with. Nevertheless, they can still struggle to deliver the content that they would like or need. This is where strategy comes in. &lt;br /&gt;
&lt;br /&gt;
At its simplest, a strategy is an idea that, if executed, will deliver you a specific gain. It will get you from point A to point B, assuming point B is the better one. Content strategy is therefore a collection of ideas – a content-related methodology – that will deliver gain. Like any strategy in an organisation, it should uphold overall corporate strategy and brand. Wikipedia still makes a strong link between content strategy and web development, but although web-based delivery circles are where the term gained initial popularity, the need for content strategy is not determined by the publishing channel, but the business model and business context. ‘Holistic Content Strategy’ is an approach that takes into account the entire content lifecycle and the various audiences and stakeholders that are touched by content along the way.&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;
Content and knowledge&lt;/h2&gt;
&lt;br /&gt;
In practical terms, for an organisation that makes a product or delivers a service, content encapsulates knowledge, making it transferable and accessible. As in Richard Truscott’s case, content strategy and management initiatives often develop into knowledge management initiatives involving not just specialised technical communication resources, but also SMEs. SMEs are the source of raw content for repurposing/rewriting. These days, technology is enabling workflows where annotations, additions or corrections can be added easily after content goes live, extending the SME influence. &lt;br /&gt;
&lt;br /&gt;
Typically, when you buy a product you will receive a manual on how to use that product, and possibly some training that implies its own associated materials. Someone else will receive a repair/service manual to support the product, some more training, and maybe a parts manual to identify spares. Marketing will describe the product online, and support may share descriptions and how-to information with technical communications and training. Development content flows through all of these points, and has impact throughout the content lifecycle. For example, the product feature list planned in development may go on to appear in various publications as seen in Figure 1.&lt;br /&gt;
&lt;br /&gt;
Ideally, these departments are keeping shared information up-to-date and sharing content, metadata and organisational/navigational models where possible. If these are not shared, users are given disparate resources they need to make sense of themselves. Sometime this data is even contradictory when groups have not kept their updates synchronised . In Figure 2, we see an example of sharing a single resource.&lt;br /&gt;
If you are the developer of the product or service, the users may be internal staff like services and support. Poor information can affect profitability directly through inefficient staff costs and impact customers as various points of contact are hindered by a lack of good resources.&lt;br /&gt;
&lt;br /&gt;
Each contact with the customer builds the brand and encourages long, fruitful relationships. Therefore, if an organisation wants to consistently deliver quality customer experience, then a holistic content strategy needs to be established. Content storage and delivery underpins the vendor’s ability to provide the knowledge and service that facilitates customers using the product or service. &lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TLWyquiS1HI/AAAAAAAAACw/s_54sMVKK2M/s1600/fig1.JPG" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img alt="" border="0" id="BLOGGER_PHOTO_ID_5527520564783273074" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TLWyquiS1HI/AAAAAAAAACw/s_54sMVKK2M/s400/fig1.JPG" style="cursor: hand; display: block; height: 306px; margin: 0px auto 10px; text-align: center; width: 400px;" /&gt;&lt;/a&gt;&lt;br /&gt;
&lt;div class="HFigure" style="text-align: center;"&gt;
&lt;b&gt;Figure 1 (Click to Enlarge)&lt;/b&gt;: Product feature list displaying four related departmental outputs. Each number represents a slight adjustment for the new context: (1) the original specification version, (2) the user guide and quick start guide are modified, but content is identical, (3) Marketing adapts the content using the same version on the website product page and brochure, but a modified website FAQ.&lt;/div&gt;
&lt;a href="http://3.bp.blogspot.com/_nJ8XHcWrG0A/TLWyrT0yVuI/AAAAAAAAAC4/rzqzIEpxdp4/s1600/fig2.JPG" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img alt="" border="0" id="BLOGGER_PHOTO_ID_5527520574792947426" src="http://3.bp.blogspot.com/_nJ8XHcWrG0A/TLWyrT0yVuI/AAAAAAAAAC4/rzqzIEpxdp4/s400/fig2.JPG" style="cursor: hand; display: block; height: 297px; margin: 0px auto 10px; text-align: center; width: 400px;" /&gt;&lt;/a&gt;&lt;br /&gt;
&lt;div class="HFigure" style="text-align: center;"&gt;
&lt;b&gt;Figure 2 (Click to Enlarge): &lt;/b&gt;An optimised workflow where all departments update a shared resource. One resource can contain variant content for different tone or style, but all managed and updated in one place. At publish time, the variant content is processed and delivered to the appropriate audiences.&lt;/div&gt;
This is one of the reasons that knowledge management without content management rarely delivers the full functional and business benefits available. Without a methodology for delivering and refining captured knowledge into targeted content deliverables, you cannot spread the knowledge very far. A targeted deliverable is one that is fit for a specific audience, context and purpose.&lt;br /&gt;
&lt;br /&gt;
Therefore, streamlining and inter-relating the content of the various knowledge sources within the organisation is a key strategic activity for the staff responsible for managing content to support overall corporate strategy.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Content/Knowledge sources that need to be taken into account in a content inventory include:&lt;/b&gt;&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Product Managers&lt;/li&gt;
&lt;li&gt;Engineers&lt;/li&gt;
&lt;li&gt;Trainers&lt;/li&gt;
&lt;li&gt;Technical Services / Support&lt;/li&gt;
&lt;/ul&gt;
&lt;b&gt;Staff that are generally responsible for managing and delivering content include:&lt;/b&gt; &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Technical Communications&lt;/li&gt;
&lt;li&gt;Marketing&lt;/li&gt;
&lt;li&gt;IT&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
The distinction between content managers and sources is that content managers are responsible for managing more information than they originally generated. Technical Communications and Marketing take content from the SME departments and extend, add value to, re-write, and re-structure it to optimise it for use by content consumers.&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;
Key components for implementing a content strategy&lt;/h2&gt;
&lt;br /&gt;
In order to have a strategy you must first have: &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;A clear understanding of your current situation&lt;/li&gt;
&lt;li&gt;A mission or goal defined for your future situation.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
&amp;nbsp;&lt;/h3&gt;
&lt;h3&gt;
Reviewing the current situation&lt;/h3&gt;
&lt;br /&gt;
As we will see in the case studies later, it is only with a holistic understanding of the current situation that an organisation or team can build strategy appropriately and plan for its feasible execution.&lt;br /&gt;
It makes business sense to make an up-front investment of some of the time and budget allocated to a project to make sure the other, much larger, percentage are spent properly. By aligning with other departments’ goals, a Technical Communications-based initiative increases the overall mass of its business case, giving economies of scale. &lt;br /&gt;
&lt;br /&gt;
We have found when customers do not take into account cross-departmental perspectives, vital details get missed that have a detrimental affect on the project. Many organisations’ content strategy fails because they think that they can keep to their departmental boundaries when thinking about content, yet still provide the best customer experience. &lt;br /&gt;
&lt;br /&gt;
A customer is not interested in the source department of their answer. Numerous studies and our own project experience has shown that customers want the information that comes with their product to work and make sense together, and be presented such that they can actually find what they are looking for when executing a task. In an organisation, all departments are discussing the product(s) or service(s) the organisation sells. This means opportunities for reuse are frequent, but it is often only through analysis and departmental communication that these opportunities reveal themselves (see Figure 3).&lt;br /&gt;
&lt;br /&gt;
Analysis of your current situation and strategy for change must take into account: &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;User profiles, workflows and requirements – both internal and external&lt;/li&gt;
&lt;li&gt;Process – creation, management, translation, delivery and maintenance of information&lt;/li&gt;
&lt;li&gt;People and skills – who do you have? Who do you need? How will you apply them?&lt;/li&gt;
&lt;li&gt;Content and its models – both current and planned&lt;/li&gt;
&lt;li&gt;Technology – the tools and/or products to make all the above feasible&lt;/li&gt;
&lt;li&gt;Change itself – how will you manage the migration of all of the above?&lt;/li&gt;
&lt;li&gt;Business case – your justification for change&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
Richard covered some of these in his ‘Information sources survey’. As in Richard’s case, a SWOT analysis is often a useful tool for understanding your current situation. &lt;br /&gt;
&lt;br /&gt;
&lt;h3&gt;
Analysing the content&lt;/h3&gt;
&lt;br /&gt;
The subject of content analysis is complex, but to help you get started, here are some quick, widely applicable questions you can ask yourselves and your documents. The answers will help feed your implementation task list: &lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Do a content audit or 'inventory', depending on what your preferred term is. What do you have to manage? Now proceed with the rest of the questions below.&lt;/li&gt;
&lt;li&gt;Utilise user research and personas to decide what content is needed. Answer the question, ‘who cares’? If you cannot think of a user scenario where someone really needs to know this information, leave it out and see what happens. Leave in a link to a web page and see if anyone goes there. If you are documenting labelled items in the UI, leave them out. Is documenting a field always necessary? For example: ‘Database ID Form Field: Enter the Database ID in this field.’ Add value, not volume!&lt;/li&gt;
&lt;li&gt;How mature is your current content process? Organisations can only move so far, so fast. Be aware of the cultural context of your organisation.&lt;/li&gt;
&lt;li&gt;Do you have an inventory of information sources? Are the managers of all these sources participating in a shared content strategy? Are they in a single repository, or if not are the various repositories sharing metadata and search capabilities?&lt;/li&gt;
&lt;li&gt;Have you reviewed the table of contents lists, structures, and terminology across all the information sources and performed a consistency analysis? &lt;/li&gt;
&lt;li&gt;Does your content have to be delivered to multiple audiences with different needs? Are you just delivering one big deliverable because you do not have time to separate into tailored ones?&lt;/li&gt;
&lt;li&gt;Do you frequently have to resort to cross-references because reuse is unfeasible? Would it be better for the users if they did not have to switch between documents or go to another website? &lt;/li&gt;
&lt;li&gt;Do you have an easy feedback loop to facilitate updates of field knowledge into your documents from internal and external experts and users?&lt;/li&gt;
&lt;li&gt;Does your content get published through modern web-based channels and formats? Does it need to be? &lt;ul&gt;
&lt;li&gt;Wiki, Communities, Twitter and so on, can be either a great opportunity or time wasted.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;a href="http://2.bp.blogspot.com/_nJ8XHcWrG0A/TLWyrfjlVPI/AAAAAAAAADA/H5A6pjnodn0/s1600/fig3.JPG" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img alt="" border="0" id="BLOGGER_PHOTO_ID_5527520577942017266" src="http://2.bp.blogspot.com/_nJ8XHcWrG0A/TLWyrfjlVPI/AAAAAAAAADA/H5A6pjnodn0/s400/fig3.JPG" style="cursor: hand; display: block; height: 317px; margin: 0px auto 10px; text-align: center; width: 400px;" /&gt;&lt;/a&gt; &lt;br /&gt;
&lt;div class="HFigure" style="text-align: center;"&gt;
&lt;b&gt;Figure 3 (Click to Enlarge): &lt;/b&gt;A departmental content overlap model. Ideally, content will be reused by a systematic business or technology process. In many cases, however, overlap is either not noticed and new content is written to say the same thing, or is instead handled by duplication (copy, paste, tweak). At best duplication impedes usability, and at worse, contradictory information and user confusion and frustration arise.&lt;/div&gt;
&lt;h2&gt;
&amp;nbsp;&lt;/h2&gt;
&lt;h2&gt;
Case studies&lt;/h2&gt;
&lt;br /&gt;
It was difficult to narrow down a list of case studies, but here are a few of my favourites.&lt;br /&gt;
&lt;h3&gt;
&amp;nbsp;&lt;/h3&gt;
&lt;h3&gt;
Example - Richard Truscott &lt;/h3&gt;
&lt;br /&gt;
Richard Truscott quickly noted that he was in an organisation that had a long cultural history with notable lack of focussed professional attention on technical communications. This contributed to SMEs using their own sources and notes as primary sources as there was no central shared knowledge or content repository or administrator. &lt;br /&gt;
&lt;br /&gt;
He used the CSA to validate and extend an initial analysis to ensure that vital points were covered. Leading onto knowledge management from content management was a natural progression for him and his revised content strategy using SMEs as content sources to feed into a formalisation workflow made good use of limited Technical Communications assets. &lt;br /&gt;
&lt;h3&gt;
&amp;nbsp;&lt;/h3&gt;
&lt;h3&gt;
Example - Medical devices manufacturer unites the clans&lt;/h3&gt;
&lt;br /&gt;
This organisation had a long list of content issues impacting external customers directly and indirectly via hundreds of service, training and support staff. Similar to Richard’s experience, the organisation was suffering from too much content, without a corporate policy or system for governing or sharing it. Maintenance, training and support staff using documentation but were not given a unified, up-to-date source of data, and so collected their own local or departmental 'cheat sheets'. &lt;br /&gt;
&lt;br /&gt;
The content was on personal machines in a ‘laptop library’ or network folders, meaning that content went out of date quickly and any personal knowledge and notes stored were not easily transferred to other users. &lt;br /&gt;
Support and service staff were repurposing or re-writing content from manuals or official sources to avoid having to find it again for their own future use, or to send to a customer to answer recurring requests. This indicated a desire to be able to quickly retrieve smaller pieces of information that can be directly recalled when required (essentially the ability to store favourites and annotate content), as well as the option of taking sections of official content and repurposing it in a new context. It also implied that navigation of current content offerings was not optimised and searching should be consolidated. &lt;br /&gt;
&lt;br /&gt;
The executive body unanimously approved our project proposal to set global content strategy standards and implement a central DITA-based content management system. A progressive implementation across international business groups is now in progress.&lt;br /&gt;
&lt;h3&gt;
&amp;nbsp;&lt;/h3&gt;
&lt;h3&gt;
Example – Large defence manufacturer gets it right&lt;/h3&gt;
&lt;br /&gt;
This is an interesting example that illustrates the importance of meaningful information and the changing market. Rather than simply supplying a product, in this case an aircraft, the client chose to buy a full service level agreement. This committed the supplier to ensure a minimum number of aircraft would be operational 24/7/365. The quality, usability and accessibility of the maintenance documentation suddenly had a direct impact on the supplier’s bottom line costs. &lt;br /&gt;
&lt;br /&gt;
The result of analysing their repairs and spare overhaul statistics and engineer usability feedback suggested a small enrichment to the procedure for Power Shaft inspection would help engineers make decisions. Using photographs to graphically present acceptable and unacceptable damage limits resulted in a reduced number of units being sent for repair.&lt;br /&gt;
&lt;br /&gt;
Overhaul orders reduced by four per month resulted in annual savings of over £280,000.&lt;br /&gt;
&lt;h3&gt;
&amp;nbsp;&lt;/h3&gt;
&lt;h3&gt;
Example – Consumer electronics manufacturer gets it wrong&lt;/h3&gt;
&lt;br /&gt;
One the most striking CSA stories I have was meeting with a Technical Documentation manager and talking to the maintenance department about content. It turned out that the maintenance teams repairing products sent back from the field were generating their own quarterly DVD of technical tips, reference charts and other technical documentation. Every three months someone in they would collate the updates and re-issue the DVD. The Technical Communications team was unaware of the DVD or the useful content it contained.&lt;br /&gt;
This same organisation suffered from costly NFF or ‘no fault found’ returns. NFFs are when the product was in perfect working order, but the customer returned it because they could not understand how to make it work.&lt;br /&gt;
&lt;h2&gt;
&amp;nbsp;&lt;/h2&gt;
&lt;h2&gt;
Conclusion - the impact&lt;/h2&gt;
&lt;br /&gt;
Inconsistent information between departments is visible when content is published. If your information processes do not unite knowledge sources and how they flow into deliverables (web pages, help packages, training materials, manuals, and so on). When customers go to websites or read documentation there is inconsistency. Many Technical Communications teams tell us that they want more user and task orientation in their documents. Meanwhile, the user- and task-oriented content they wish they had the time to develop is being developed, sometimes even delivered publicly, but there is no internal collaboration to facilitate this or take advantage of the reuse and sharing opportunities. Remember: &lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Establish metrics: Using surveys and ROI case studies allows you to establish the problem and potential in numerical terms. Measure before change, compare later.&lt;/li&gt;
&lt;li&gt;Think long term, scope for the short term: ‘Delivery’ is not a singular or static process, no matter what the medium – organisations deliver, gather new information from multiple sources, then update and re-deliver, endlessly. Content strategy improvements are also ongoing. &lt;/li&gt;
&lt;li&gt;Content strategy is business strategy: Content strategy should be aligning user experience with both the goals of the organisation, and the expectations of users. When both buyer and seller are happy, you have a mutually beneficial recipe for repeat business and growth. &lt;/li&gt;
&lt;/ul&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-5037624278398222536?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=LsTh7wswZz0:jMn0jeC17Nw:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=LsTh7wswZz0:jMn0jeC17Nw:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=LsTh7wswZz0:jMn0jeC17Nw:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=LsTh7wswZz0:jMn0jeC17Nw:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=LsTh7wswZz0:jMn0jeC17Nw:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=LsTh7wswZz0:jMn0jeC17Nw:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=LsTh7wswZz0:jMn0jeC17Nw:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=LsTh7wswZz0:jMn0jeC17Nw:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=LsTh7wswZz0:jMn0jeC17Nw:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=LsTh7wswZz0:jMn0jeC17Nw:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=LsTh7wswZz0:jMn0jeC17Nw:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=LsTh7wswZz0:jMn0jeC17Nw:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/LsTh7wswZz0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/5037624278398222536/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2010/10/developing-content-strategy.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/5037624278398222536?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/5037624278398222536?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/LsTh7wswZz0/developing-content-strategy.html" title="Developing a Content Strategy" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TLWyquiS1HI/AAAAAAAAACw/s_54sMVKK2M/s72-c/fig1.JPG" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2010/10/developing-content-strategy.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0MMRXo7cCp7ImA9Wx5UFkQ.&quot;"><id>tag:blogger.com,1999:blog-1737166626111414.post-4911838591632913834</id><published>2010-10-07T18:26:00.000+02:00</published><updated>2010-10-22T00:18:04.408+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-10-22T00:18:04.408+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="DITA" /><category scheme="http://www.blogger.com/atom/ns#" term="fun" /><category scheme="http://www.blogger.com/atom/ns#" term="content strategy" /><category scheme="http://www.blogger.com/atom/ns#" term="darwin information typing architecture" /><title>The Computer Pirates of Penzance</title><content type="html">&lt;a href="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TLCjQLkdBcI/AAAAAAAAACg/G1eFSbTbM60/s1600/pirates.jpg"&gt;&lt;img style="float: left; margin: 0pt 10px 10px 0pt; cursor: pointer; width: 162px; height: 182px;" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TLCjQLkdBcI/AAAAAAAAACg/G1eFSbTbM60/s320/pirates.jpg" alt="" id="BLOGGER_PHOTO_ID_5526096241162520002" border="0" /&gt;&lt;/a&gt;&lt;p&gt;The first line sort of just came to me spontaneously in a bit of office banter, so I felt I had to do some more!&lt;/p&gt;&lt;p&gt;Let me know if you like it. Maybe I could be persuaded to actually record it! : D&lt;/p&gt;&lt;p&gt;(to be sung to the tune of 'I Am The Very Model of a Modern Major General', from &lt;a href="http://en.wikipedia.org/wiki/The_Pirates_of_Penzance"&gt;Gilbert and Sullivan's "The Pirates of Penzance"&lt;/a&gt;).&lt;/p&gt;&lt;p&gt;Here's the original with music and lyrics so you can (try to) sing along. (Note - not my video, so I can't fix that typo in the introduction where it says 'Major Genreal's song'):&lt;/p&gt;&lt;object width="400" height="321"&gt;&lt;param name="movie" value="http://www.youtube.com/v/wYZM__VdEjk?fs=1&amp;amp;hl=en_GB"&gt;&lt;param name="allowFullScreen" value="true"&gt;&lt;param name="allowscriptaccess" value="always"&gt;&lt;embed src="http://www.youtube.com/v/wYZM__VdEjk?fs=1&amp;amp;hl=en_GB" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="400" height="321"&gt;&lt;/embed&gt;&lt;/object&gt;&lt;p&gt;"I am the content model of a modern Major Enterprise
I feed my architecture with all of the docs I analyse
Strategical, and managed and my audit trail's historical
From R&amp;amp;D to user gen'd I've tagging categorical
I'm very well acquainted, too, with matters taxonomical
I understand equations, both MathML and graphical
Re: Darwin Information I am teeming with a lot o' news
(Newsfeeds? Maybe a little RSS?)
With many cheerful facts about best practices that you should use&lt;/p&gt;&lt;p&gt;With many cheerful facts about best practices that you should use
With many cheerful facts about best practices that you should use
With many cheerful facts about best practices that you should you should use!&lt;/p&gt;&lt;p&gt;I'm very good at translation and all my terms are consistent
And I know their costs are worthy of some very careful management
In short, in matters budgetary, I aim to reduce their size
I am the content model of a modern Major Enterprise&lt;/p&gt;&lt;p&gt;In short, in matters budgetary, he aims to reduce their size
He is the content model of a modern Major Enterprise!&lt;/p&gt;&lt;p&gt;I know our mythic history, Info Mapped SGML
I answer fiscal problems with processes that are rational
I cite case studies showing its a crime to be too product-led
It's people and their processes that move all good projects ahead
I assert there's a place for structure in just about all documents
Structure can mean XML or just workflows that make some sense!
The hard part's knowing how much, when and what it is all destined for
To have a CM system(1) that can do you had hoped before!&lt;/p&gt;&lt;p&gt;To have a CM system that can do you had hoped before!
To have a CM system that can do you had hoped before!
To have a CM system that can do you had hoped before before!&lt;/p&gt;&lt;p&gt;Oh, I can write a tidy topic up in minimalist uniform
And tell you ev'ry detail that's conditional or off the norm
In short, in matters budgetary, I aim to reduce their size
I am the content model of a modern Major Enterprise! &lt;/p&gt;&lt;p&gt;In short, in matters budgetary, he aims to reduce their size
He is the content model of a modern Major Enterprise!&lt;/p&gt;&lt;p&gt;In fact, when I know what is meant by "formattin'" v "stylin'"
When I can tell at sight a user manual from some scribblin'
and spearhead project issues and surprising user feedback that
tells you your user guides are best made outside a HAT(2)
Because I've learnt methods for better content lifecycle
I balance needs more daunting than a hippo on a bicycle
In short, with my tactics laid out all in a Content Strategy,
(oh, hmmm... that's a hard one... Strategy...)
You'll say that other Major-Enterprises' look like agony! &lt;/p&gt;&lt;p&gt;You'll say that other Major-Enterprises' look like agony!
You'll say that other Major-Enterprises' look like agony!
You'll say that other Major-Enterprises' look like agon-agony!&lt;/p&gt;&lt;p&gt;With all my ROI calcs(3), you will find that you are lucky
I've led the cutting edge since the beginning of this century
And still, in matters budgetary, I aim to reduce their size
I am the content model of a modern Major Enterprise.&lt;/p&gt;&lt;p&gt;In short, in matters budgetary, he aims to reduce their size
He is the content model of a modern Major Enterprise!&lt;/p&gt;In short, in matters budgetary, he aims to reduce their size
He is the content model of a modern Major Enterprise!
&lt;p&gt;(1) CM system = &lt;a href="http://www.mekon.com/index.php/pages/knowledge_zone/component_content_management_ccms_and_cms/technology_standards/technologies"&gt;Content Management System&lt;/a&gt;&lt;/p&gt;&lt;p&gt;(2) HAT = Help Authoring Tool. See also &lt;a href="http://hat-matrix.com/"&gt;http://hat-matrix.com/&lt;/a&gt;&lt;/p&gt;&lt;p&gt;(3) ROI calcs = Return on Investment calculations&lt;/p&gt;&lt;a class="twitter-share-button" href="http://twitter.com/share" count="vertical" via="nozurbina" related="mekonltd:Where I work"&gt;Tweet&lt;/a&gt;&lt;script type="text/javascript" src="http://platform.twitter.com/widgets.js"&gt;&lt;/script&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1737166626111414-4911838591632913834?l=lessworkmoreflow.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=iirIoi-BkWw:RLbnurvbtnc:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=iirIoi-BkWw:RLbnurvbtnc:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=iirIoi-BkWw:RLbnurvbtnc:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=iirIoi-BkWw:RLbnurvbtnc:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=iirIoi-BkWw:RLbnurvbtnc:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=iirIoi-BkWw:RLbnurvbtnc:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=iirIoi-BkWw:RLbnurvbtnc:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=iirIoi-BkWw:RLbnurvbtnc:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=iirIoi-BkWw:RLbnurvbtnc:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=iirIoi-BkWw:RLbnurvbtnc:l6gmwiTKsz0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?d=l6gmwiTKsz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?a=iirIoi-BkWw:RLbnurvbtnc:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/LessWorkMoreFlow?i=iirIoi-BkWw:RLbnurvbtnc:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/LessWorkMoreFlow/~4/iirIoi-BkWw" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://lessworkmoreflow.blogspot.com/feeds/4911838591632913834/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://lessworkmoreflow.blogspot.com/2010/10/computer-pirates-of-penzance.html#comment-form" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/4911838591632913834?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1737166626111414/posts/default/4911838591632913834?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/LessWorkMoreFlow/~3/iirIoi-BkWw/computer-pirates-of-penzance.html" title="The Computer Pirates of Penzance" /><author><name>B. Noz Urbina</name><uri>http://www.blogger.com/profile/16169742771529346975</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TQdKdzIjteI/AAAAAAAAADw/xoXH6GkdM6c/S220/nozprofile-square_reasonably_small.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_nJ8XHcWrG0A/TLCjQLkdBcI/AAAAAAAAACg/G1eFSbTbM60/s72-c/pirates.jpg" height="72" width="72" /><thr:total>3</thr:total><feedburner:origLink>http://lessworkmoreflow.blogspot.com/2010/10/computer-pirates-of-penzance.html</feedburner:origLink></entry></feed>

