<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Intranet Experience Blog &#187; taxonomy</title>
	<atom:link href="http://www.intranetexperience.com/ourblog/tag/taxonomy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.intranetexperience.com/ourblog</link>
	<description>Topics relating to Intranets, portals, enterprise content management, internal communications, and social media in the workplace</description>
	<lastBuildDate>Mon, 04 Jul 2011 18:47:51 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Facebook as an Intranet Part 3: 10 More Reasons Not To Consider Facebook For Your Intranet Platform</title>
		<link>http://www.intranetexperience.com/ourblog/2010/10/facebook-as-an-intranet-part-3-10-more-reasons-not-to-consider-facebook-for-your-intranet-platform/</link>
		<comments>http://www.intranetexperience.com/ourblog/2010/10/facebook-as-an-intranet-part-3-10-more-reasons-not-to-consider-facebook-for-your-intranet-platform/#comments</comments>
		<pubDate>Mon, 11 Oct 2010 03:18:02 +0000</pubDate>
		<dc:creator>Sean R. Nicholson</dc:creator>
				<category><![CDATA[Document Management]]></category>
		<category><![CDATA[Enterprise 2.0]]></category>
		<category><![CDATA[Intranet]]></category>
		<category><![CDATA[Intranet Portal]]></category>
		<category><![CDATA[Intranet Tips]]></category>
		<category><![CDATA[Services Oriented Architecture]]></category>
		<category><![CDATA[Social Networking]]></category>
		<category><![CDATA[Application Integration]]></category>
		<category><![CDATA[document management]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[portal]]></category>
		<category><![CDATA[search]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[social media]]></category>
		<category><![CDATA[social networking]]></category>
		<category><![CDATA[taxonomy]]></category>

		<guid isPermaLink="false">http://www.intranetexperience.com/ourblog/?p=1160</guid>
		<description><![CDATA[First, let me start off with a bit of a disclaimer. I'm not an anti-Facebook zealot and my goal isn't to discourage the use of Facebook by companies and organizations. To the contrary, one of the biggest roles of my job is to explain how social media channels can be used effectively. So, with that said, my goal with this series of posts is to educate anyone considering the use of Facebook as their corporate Intranet to seriously reconsider. Using Facebook for a corporate Intranet is like using a hammer to loosen a nut. It can be done, but...why??]]></description>
			<content:encoded><![CDATA[<div id="attachment_128" class="wp-caption alignleft" style="width: 90px"><a href="http://www.intranetexperience.com/ourblog/wp-content/uploads/2009/03/sean1.jpg"><img class="size-full wp-image-128" title="Sean R. Nicholson" src="http://www.intranetexperience.com/ourblog/wp-content/uploads/2009/03/sean1.jpg" alt="Sean R. Nicholson - Intranet Evangelist at IntranetExperience.com" width="80" height="80" /></a><p class="wp-caption-text">Sean R. Nicholson</p></div>
<p>First, let me start off with a bit of a disclaimer. I&#8217;m not an anti-Facebook zealot and my goal isn&#8217;t to discourage the use of Facebook by companies and organizations. To the contrary, one of the biggest roles of my job is to explain how social media channels can be used effectively by organizations and within organizations. So, with that said, my goal with this series of posts is to educate anyone considering the use of Facebook as their corporate Intranet to seriously reconsider. Using Facebook for a corporate Intranet is like using a hammer to loosen a nut. It can be done, but there&#8217;s a lot of risk involved.</p>
<p>So, to help you understand why Facebook shouldn&#8217;t be considered when selecting the platform for your Intranet, here are 10 more reasons why it just doesn&#8217;t stack up to the competition out there.</p>
<p><strong>10) No integration with organizational LDAP</strong> &#8211; Your employees are going to want to login using a &#8220;single sign-on&#8221; with your company domain. Facebook does not provide this type of integration, meaning that your users will need to manage separate accounts. Not a huge problem (because they probably already do), but most platforms built for Intranets will include this functionality, reducing the number of logins your employees require.</p>
<p><strong>9) No document sharing</strong> &#8211; Don&#8217;t be confused by the recent announcement that Groups will allow the sharing of documents. That&#8217;s a bit of a misnomer. Facebook does not currently allow for the storage/sharing of documents and the new  &#8220;document&#8217; functionality will simply allow members of the group to create a &#8220;document&#8221; (think Notepad) and share it within the group. You won&#8217;t be able to share PowerPoint decks, MS Word docs, or Excel spreadsheets. This means that your employees will be using local drives or shared network drives to save information, which can turn into an IT nightmare. Retrieving lost documents or dealing with document versions without a system designed to handle the complexities will consume a lot of IT bandwidth.</p>
<p><strong>8 ) Search isn&#8217;t designed for Intranet purposes</strong> &#8211; If you have an Intranet right now, ask your employees which functionality they wish worked better. My bet is they&#8217;ll say &#8220;search&#8221;.  Facebook&#8217;s search is designed to find people and pages, not information. Even if Facebook did add document storage and sharing, the chances of your employees actually finding anything would be slim to none.</p>
<p><strong>7) Facebook is architected as an entertainment platform, not an organizational Intranet</strong> &#8211; Ever build an organizational information taxonomy for your Intranet? It can be incredibly painful, even with the right tools. Facebook doesn&#8217;t offer you the flexibility to build your Intranet navigation structure in a way that will work for your team. Instead, you&#8217;re stuck with what they give you. Also, you&#8217;d better hope they don&#8217;t change it in the future. Also, would you really want your intranet competing for resources with the likes of Farmville and Mafia Wars?</p>
<p><strong>6) Changes that might not be in the interest of your organization</strong> &#8211; Facebook is in the business of making money&#8230;for Facebook. They aren&#8217;t really interested in making your organization successful and if they need to add or change functionality that is adverse to your organizations needs, there&#8217;s likely nothing you can do about it. Facebook will do what&#8217;s good for them and their future, not yours. If Facebook feels it&#8217;s more important to their pocketbook to place your competitor&#8217;s ads on your private group, they&#8217;ll do so.</p>
<p><strong>5) Groups are limited to 250 members</strong> &#8211; The recent enhancement of Groups functionality has spurred additional interest in Facebook as an Intranet platform. Keep in mind, however, that in the announcement of the new Groups Mark Zuckerberg continually mentioned the 250 member limitation and that these groups are really intended to be used on a smaller scale.</p>
<p><strong>4) Discussions and walls offer no pre-moderation options</strong> &#8211; Although many organizations don&#8217;t want post moderation in their intranet discussion forums, there are some that do. With Facebook, there is no pre-moderation of wall posts or discussion posts.  That means when an employee posts it, it goes live. This makes some Intranet managers uncomfortable.</p>
<p><strong>3) Employees may not like the &#8220;forced&#8221; blending of work/social</strong> &#8211; Many of your employees may view Facebook as their personal social network and may not like the forced blending of their personal and professional lives. Before setting your mind on Facebook as your Intranet platform, you might want to get the input of your HR executives. They may feel that what&#8217;s out there on Facebook isn&#8217;t really the business of the organization and blending business/personal poses a potential risk.</p>
<p><strong>2) No integration with your other enterprise applications</strong> &#8211; While Facebook does offer an application platform, it is definitely not geared toward integration with a corporate Customer Relationship Management (CRM) tool or an Enterprise Content Management (ECM) system. Your corporate Intranet should be <em>the</em> place where your employees work and where they can access their timecard apps, PTO management system, online form builder, ECM system, and ERP applications. Facebook just doesn&#8217;t offer the service-oriented architecture that is required to serve as a centralized portal.</p>
<p><strong>1) Privacy, privacy, privacy.</strong> Facebook was not developed with privacy in mind. In fact, the concept of Facebook is pretty much anti-privacy. Share everything&#8230;and restrict access to those things you don&#8217;t want shared. A corporate Intranet should be exactly the opposite. Share nothing, and decided what you want shared with the outside world. Can you imagine sensitive documents being shared on Facebook and someone accidentally forgetting to set the right restrictions? For a private company, it could be a nightmare. For a public company, under FTC regulation, it could be full-blown Armageddon.</p>
<p>So there you have it&#8230;.10 more reasons that Facebook shouldn&#8217;t be considered for a corporate Intranet. Have suggestions for the list? Feel free to add them in the comments!</p>
<p><a href='http://www.twitter.com/seanrnicholson' class='twitlink' target='_blank' onclick="pageTracker._trackPageview('/outgoing/www.twitter.com/seanrnicholson?referer=');"><img src='http://www.intranetexperience.com/ourblog/wp-content/uploads/2009/04/twitter_badge2.png' alt='Follow Me On Twitter!' /></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.intranetexperience.com/ourblog/2010/10/facebook-as-an-intranet-part-3-10-more-reasons-not-to-consider-facebook-for-your-intranet-platform/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Top 10 Must Haves For Every Good Intranet</title>
		<link>http://www.intranetexperience.com/ourblog/2009/04/top-10-must-haves-for-every-good-intranet/</link>
		<comments>http://www.intranetexperience.com/ourblog/2009/04/top-10-must-haves-for-every-good-intranet/#comments</comments>
		<pubDate>Fri, 10 Apr 2009 03:25:29 +0000</pubDate>
		<dc:creator>Sean R. Nicholson</dc:creator>
				<category><![CDATA[Application Integration]]></category>
		<category><![CDATA[Content Management]]></category>
		<category><![CDATA[Governance]]></category>
		<category><![CDATA[Intranet]]></category>
		<category><![CDATA[Intranet Portal]]></category>
		<category><![CDATA[Searchability]]></category>
		<category><![CDATA[Social Networking]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[collaboration]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[interoperability]]></category>
		<category><![CDATA[navigation]]></category>
		<category><![CDATA[personalization]]></category>
		<category><![CDATA[search]]></category>
		<category><![CDATA[taxonomy]]></category>
		<category><![CDATA[wiki]]></category>

		<guid isPermaLink="false">http://www.intranetexperience.com/ourblog/?p=203</guid>
		<description><![CDATA[Okay Intranet fans, here it is...the 2009 completely unofficial list of must have functionality for every Intranet:

{drumroll please....}]]></description>
			<content:encoded><![CDATA[<div id="attachment_130" class="wp-caption alignleft" style="width: 90px"><img class="size-full wp-image-130" title="Sean R. Nicholson" src="http://www.intranetexperience.com/ourblog/wp-content/uploads/2009/03/sean2.jpg" alt="Sean R. Nicholson" width="80" height="80" /><p class="wp-caption-text">Sean R. Nicholson</p></div>
<p>Okay Intranet fans, here it is&#8230;the 2009 completely unofficial list of must have functionality for every Intranet.</p>
<p>**Please note that we reserve the right to update this list and expand it beyond 10 based on the great feedback and comments we will undoubtedly receive.</p>
<p>{drumroll please&#8230;.}</p>
<p><strong># 10) </strong><strong>Application Interoperability</strong> &#8211; There&#8217;s nothing like a good Intranet mashup. Being able to search for a user and see not only who they are (from the HR application), what they are working on (from the Project Management application), and where they are located (From HR + Google Maps) is pretty cool, not to mention that it brings relevant information to the user on a single page. Look for creative ways to mash up your applications and streamline information gathering. Remember that good mashup also leverage a &#8220;<a href="http://www.intranetexperience.com/ourblog/?p=73" target="_blank">simpler sign-on</a>&#8221; schema so that users don&#8217;t have to login over and over to see data in different applications.</p>
<p><strong>#9) </strong><strong>A Clean Design</strong> &#8211; Lot of functionality is good, but be sure to spend time up front determining what should be on the front page and what can be moved to secondary pages. Your users should be able to find content quickly and easily. Spend some time watching how your users physically navigate the Intranet and strive toward reducing the number of clicks they have to make to locate the information they are looking for. Need help creating a design? Bring in a consultant from the outside to provide an objective point of view.</p>
<p><strong>#8) </strong><strong>A Good Name</strong> &#8211; I always love hearing people refer to the Intranet by it&#8217;s given name, rather than &#8220;the Intranet&#8221;. Creative names allow folks to create an identity for the Intranet that gives it a life of its own. If you don&#8217;t have a name for your Intranet, try holding a company-wide contest to come up with names and then have your company vote on it. Your even more likely to get strong buy in if the name is chosen by your organization as opposed to being assigned by a developer with a Star Wars fetish.</p>
<p><strong>#7) </strong><strong>A Strong Navigation Taxonomy</strong> &#8211; Yes&#8230;.it&#8217;s a Google kinda world, so folks like to find content through search, but when they find that content, they also like to see where they are in the navigation, using a folder taxonomy or breadcrumbs, so they can find other content that is similar in nature AND know how to get back to the content in the future.</p>
<p><strong>#6) </strong><strong>Personalization</strong> &#8211; Users need to be able to customize pieces of the Intranet. Whether it&#8217;s their weather, stock quote, news headlines, horoscope or other content, allow them to make the Intranet more useful to them as an information source. Also, by allowing users to relocate portlets or widgets, they can create a design that meets the way they work. Need a good source for personalized information? Look to subscription information providers such as <a href="http://www.yellowbrix.com" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.yellowbrix.com?referer=');">YellowBrix</a>.</p>
<p><strong>#5) </strong><strong>A Good Rich Text Editor</strong> &#8211; Nothing helps an Intranet grow more than content, so making the creation of content easy is important. A good WYSIWYG (&#8220;what you see is what you get&#8221;) editor is important. Don&#8217;t forget to make sure your editor has a spell check. I speak from experience on this one (ahem&#8230;Plumtree/BEA/Oracle WebCenter)</p>
<p><strong>#4) </strong><strong>Governance</strong> &#8211; No need to go into full-blown lockdown mode, but governance is a good thing for any organization. It keeps your Intranet from becoming the wild, wild west and ensures that the content created has meaning and is relevant. Some areas of the Intranet (WIKIs, forums, etc&#8230; ) can be looser than others, but your governance strategy should be flexible enough to accommodate for these different needs.</p>
<p><strong>#3) </strong><strong>A Strong Collaboration Toolset</strong> &#8211; User created content will drive your Intranet page views through the roof. A good, spirited conversation about the latest product or marketing campaign can help spread the word about what your organization is doing and can drive new innovations. Try adding an &#8220;Idea Center&#8221; to your Intranet and challenge your employees to come up with new ways to do business. Products like user-driven blogs, forums, and WIKIS can turn your readers into contributors growing your content exponentially. Daily polls can also be used for gathering user sentiment on a corporate topic, or just for a little fun.</p>
<p><strong>#2) </strong><strong>A Federated Search Engine</strong> &#8211; Again, it&#8217;s a Google kinda world, so make sure your search works and it can talk to other applications. No one likes to have to search 10 different places for information, so leverage tools like Google appliances or federated search engines like <a href="http://www.fastsearch.com/" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.fastsearch.com/?referer=');">FAST</a> or <a href="http://www.autonomy.com/" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.autonomy.com/?referer=');">Autonomy</a> to bring all of your content together into one search. If you haven&#8217;t ever seen a demo of one of these &#8220;meaning&#8221; based search engines, give them a call and ask for one. You&#8217;ll be amazed at what modern search engines can do.</p>
<p><strong>#1) </strong><strong>Meaningful Content</strong> &#8211; The best design, the coolest name, even a great governance strategy&#8230;they&#8217;re nothing without meaningful content. If your users don&#8217;t find value in your Intranet, they won&#8217;t adopt its use. In addition (and I can&#8217;t stress this enough), the content <strong>MUST</strong> be timely and accurate. <em></em></p>
<p><em>The only thing worse than no information is bad information</em>&#8230;Your employees will act using bad information because they don&#8217;t know it&#8217;s inaccurate. There&#8217;s nothing worse than a sales rep sharing an outdated rate sheet or a customer service rep providing an inaccurate solution to a problem. To avoid this, be sure your Intranet content is up-to-date and reviewed frequently.</p>
<p>There you have it, Intranet fans! 10 must haves for any good Intranet.</p>
<p><strong>Additions:</strong></p>
<p><strong>Accessibility</strong> &#8211; Everyone needs to be able to use your Intranet. Ensuring that your pages comply with the <a href="http://www.w3.org/WAI/gettingstarted/Overview.html" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.w3.org/WAI/gettingstarted/Overview.html?referer=');">accessibility guidelines</a> will ensure that folks with disabilities can read or hear the content. Thanks to Russell <a href="http://twitter.com/theparallaxview" target="_blank" onclick="pageTracker._trackPageview('/outgoing/twitter.com/theparallaxview?referer=');">@theparallaxview</a> for the suggestion</p>
<p>Have input? We&#8217;d love to hear any additions, suggestions, or constructive criticism in your comments!</p>
<p><a href='http://www.twitter.com/seanrnicholson' class='twitlink' target='_blank' onclick="pageTracker._trackPageview('/outgoing/www.twitter.com/seanrnicholson?referer=');"><img src='http://www.intranetexperience.com/ourblog/wp-content/uploads/2009/04/twitter_badge2.png' alt='Follow Me On Twitter!' /></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.intranetexperience.com/ourblog/2009/04/top-10-must-haves-for-every-good-intranet/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
