{"id":4694,"date":"2015-10-08T15:25:15","date_gmt":"2015-10-08T20:25:15","guid":{"rendered":"http:\/\/www.encoretechresources.com\/insights\/?p=4694"},"modified":"2015-10-08T15:30:58","modified_gmt":"2015-10-08T20:30:58","slug":"information-most-of-it-anyway-is-for-sharing","status":"publish","type":"post","link":"http:\/\/www.encoretechresources.com\/insights\/2015\/10\/08\/information-most-of-it-anyway-is-for-sharing\/","title":{"rendered":"Information (Most of It Anyway) Is For Sharing"},"content":{"rendered":"

This needn’t be long and won’t be. But there’s a post on a blog called “Customers and Content,\u00a0Ideas and opinions about customer-focused documentation”<\/a> that deserves both comment\u00a0and assent. The blogger,\u00a0Neal Kaplan, a San Francisco Bay area technologist, is bothered by employees\u00a0who hoard information, thereby withholding it from colleagues. Unintentionally and unwittingly, maybe, but they do it, and it’s wrong.<\/p>\n

\"images\"<\/a>“Information gets locked in the heads of professional services, customer support, QA, sales…” when it may have much wider organizational pertinence.When it’s not shared, what ought to be a common effort is hobbled, sometimes drastically so.<\/p>\n

“Customer support will have a knowledge base in their support tool, professional services will have a wiki, marketing will use Slack, but there’s no central repository of corporate knowledge,” Kaplan writes. “Every team has their own knowledge base, but they might not be shared with other teams. They might not know that the other knowledge bases exist, which is why they created one in the first place.”<\/p>\n

Teams? These aren’t teams, they’re groups of “athletes” who don’t share what ought to be common signals. Organizationally, do you think they’re scoring as effectively as they could be?<\/p>\n

Somehow, what should be obvious, isn’t always so in organizations. Technical writers are apt to recognize information impasses sooner than others because they often poke\u00a0around among departments looking for threads of a common problem.<\/p>\n

Some material with personal or proprietary significance, of course, may not be appropriate for sharing, but that’s not what were’s talking about here. Information of enterprise-wide operational significance is what we’re concerned about.<\/p>\n

So, share, guys share! Your organization,\u00a0which represents, doesn’t it, your own future, requires it. And by the way, Neal Kaplan ought to give himself a byline on his own site. He’s got a photo posted, but you have to go to “About Me,” and then “How to contact me” and find that his email address is “nealbkaplan@gmail.com” or his Twitter handle, “nealkaplan”, to find him out.\u00a0Not that he’s hiding his identity, presumably. \u2013 Doug Bedell\u00a0<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

This needn’t be long and won’t be. But there’s a post on a blog called “Customers and Content,\u00a0Ideas and opinions about customer-focused documentation” that deserves both comment\u00a0and assent. The blogger,\u00a0Neal Kaplan, a San Francisco Bay area technologist, is bothered by employees\u00a0who hoard information, thereby withholding it from colleagues. Unintentionally and unwittingly, maybe, but they do […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-4694","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"aioseo_notices":[],"_links":{"self":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/4694"}],"collection":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/comments?post=4694"}],"version-history":[{"count":8,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/4694\/revisions"}],"predecessor-version":[{"id":4703,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/4694\/revisions\/4703"}],"wp:attachment":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/media?parent=4694"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/categories?post=4694"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/tags?post=4694"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}