Sean R. Nicholson

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 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’s a lot of risk involved.

So, to help you understand why Facebook shouldn’t be considered when selecting the platform for your Intranet, here are 10 more reasons why it just doesn’t stack up to the competition out there.

10) No integration with organizational LDAP – Your employees are going to want to login using a “single sign-on” 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.

9) No document sharing – Don’t be confused by the recent announcement that Groups will allow the sharing of documents. That’s a bit of a misnomer. Facebook does not currently allow for the storage/sharing of documents and the new  “document’ functionality will simply allow members of the group to create a “document” (think Notepad) and share it within the group. You won’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.

8 ) Search isn’t designed for Intranet purposes – If you have an Intranet right now, ask your employees which functionality they wish worked better. My bet is they’ll say “search”.  Facebook’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.

7) Facebook is architected as an entertainment platform, not an organizational Intranet – Ever build an organizational information taxonomy for your Intranet? It can be incredibly painful, even with the right tools. Facebook doesn’t offer you the flexibility to build your Intranet navigation structure in a way that will work for your team. Instead, you’re stuck with what they give you. Also, you’d better hope they don’t change it in the future. Also, would you really want your intranet competing for resources with the likes of Farmville and Mafia Wars?

6) Changes that might not be in the interest of your organization – Facebook is in the business of making money…for Facebook. They aren’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’s likely nothing you can do about it. Facebook will do what’s good for them and their future, not yours. If Facebook feels it’s more important to their pocketbook to place your competitor’s ads on your private group, they’ll do so.

5) Groups are limited to 250 members – 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.

4) Discussions and walls offer no pre-moderation options – Although many organizations don’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.

3) Employees may not like the “forced” blending of work/social – 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’s out there on Facebook isn’t really the business of the organization and blending business/personal poses a potential risk.

2) No integration with your other enterprise applications – 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 the 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’t offer the service-oriented architecture that is required to serve as a centralized portal.

1) Privacy, privacy, privacy. Facebook was not developed with privacy in mind. In fact, the concept of Facebook is pretty much anti-privacy. Share everything…and restrict access to those things you don’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.

So there you have it….10 more reasons that Facebook shouldn’t be considered for a corporate Intranet. Have suggestions for the list? Feel free to add them in the comments!

Sean R. Nicholson

Ready to roll out your new Enterprise 2.0 Strategy? Looking to save the company millions by implementing an internal social strategy? Think that implementing a blog will help you increase sales, cut support calls, and help unclutter your email Inbox?

Before you jump into the deep end and propose implementing any E2.0 solutions, you might want to take a look around and assess whether your organization has an understanding of what E2.0 really is and whether it is ready to take on an internal social strategy.

To help you along, here are my top 10 signs that your organization hasn’t quite figured out what Enterprise 2.0 really is:

10. Executives don’t know the difference between SAS and SaaS.

9. The person that manages your document management system never talks with the person who manages your Intranet.

8. A single organization (HR, Corp Comm, etc…) has complete control over the future roadmap of your Intranet.

7. You believe that social media has no place in the work environment and/or your organization has blocked communication channels like Facebook, Twitter, and LinkedIn.

6. Your CRM system hasn’t been upgraded in more than 5 years and has no social media integration.

5. Your executives groan when they hear terms like Wiki, blog, knowledge base, or community.

4. You’ve been working on a SharePoint implementation for more than 12 months and believe it will be a turnkey Enterprise 2.0 solution.

3. You don’t know the difference between an Enterprise Content Management system and Document Management system.

2. You have no clue as to what a Service-Oriented Architecture is.

1. You continue to buy and install software that relies on a desktop client, instead of being accessed through the browser.

There you have it…10 signs that your organization hasn’t figured out what to do with E2.0. Have another good example? Have a suggestion on how to overcome any of these? Feel free to share in the comments!

Sean R. Nicholson

Last week was a great week for online discussions relating to Intranets. On Monday, Alex Manchester of Step Two Designs posted an article to his blog asking whether the term Intranet is dead. His thoughts were sparked by a recent presentation by Jane McConnell of NetJMC and the conversation that ensued was a healthy dialog on the future of Intranets, their relevance in a world of social media, and whether the term “intranet” was really the best way to describe an interactive workplace. The conversation continued throughout the week and I’d encourage anyone who works with Intranets to check out the threaded discussion and add their $.02.

Tuesday continued the interesting online conversations as Jarrod Gingras and Alan Pelz-Sharpe of CMS Watch made his predictions for technology in 2010. One of particular interest to me was his prediction #1 that :

1) Enterprise Content Management and Document Management will go their separate ways
ECM as a marketing and technical concept has great validity. But the idea of having a single overarching platform to manage all sources of content management only works well in those enterprises that follow a unified and services-oriented architectural approach to IT.

I agree with Jarrod and my interpretation of this prediction is that organizations that aren’t able to settle on a single vendor for all of their information systems or aren’t able to invest in a comprehensive services-oriented architecture just won’t be concerned with Enterprise Content Management (ECM) because they won’t be able to address every departmental business process problems with a single ECM tool.

To expand on Jarrod’s prediction, I’m thinking that as more and more vendors build document management functionality into their applications, organizations will be less concerned with where it is stored, as long as it is stored properly, is accessible to the end-users that need it, and can be discovered and produced in time of legal necessity. Instead of costly redevelopment of business processes to restructure where content is stored, organizations will invest in search technology that allows content to be stored in native applications and use search tools like Microsoft Enterprise Search, Autonomy, and Google appliances to ferret out information.

In other words, federated search will become crucial to organizations that choose not to implement a structured ECM architecture.

The results of this kind of shift are as follows:

1. Content and documents  will reside in their native application, allowing the information to have more context than if it were stored in a centralized ECM system.
2. Those ECM vendors who wish to provide value to the enterprise must figure out how to store the content centrally, yet serve it back to end users in a context that is meaningful to their end users.
3. ECM vendors who provide true, enterprise-scale software MUST offer a full services-oriented architecture that will allow business applications to easily access the content and surface documents in the context of the business application.

S0…this brings me to my question of the week. Is Enterprise Content Management going the way of the Intranet and becoming an outdated notion? Will better federated search technologies negate the need for a central repository? Are organizations better off investing in the functional elements of ECM like document management, records management, and business process management instead of buying the whole enchilada?

I’m curious to see what others think…looking forward to thoughts/comments.

Sean R. Nicholson

Having been in the field of information management for quite a while now, I have developed a few credos that seem to prove more and more useful as the volumes of organizational information continues to grow. I used to drive one of my previous team absolutely crazy with this one:

“The only thing worse than no information is BAD information”

Think about it. When you have no information, you seek out answers, solutions, and advice. When you have bad information,  it’s likely that you don’t know it’s bad, so you react to the information. Only after you have used the information and determined that it was incorrect do you (after a few choice words) continue your search for good information.

Take an example of a call center representative who answers the phone and provides the customer on the other end with what they think to be the most current product prices from a document they printed yesterday. Little do they know that a new copy of the rate sheet was published a couple hours ago with significant rate changes that is now impacting their potential sale.

Did they have information? Yes! Was it good information? No!

The reality is that organizations are generating more and more information on an hourly basis. Take a moment and think about all the documents, spreadsheets, presentations, emails, voice mails, and sticky notes you generated on a daily basis just 3 years ago. Now, add modern day blogs, tweets, text messages, forum posts, comments, status updates, videos, podcasts, and wiki posts to your list and what do you get? More information? Definitely! But the larger problem is the fact that the information is now spread out in more places, making it harder for other employees and customers to find it.

In the past customers could simply call a 1-800 line for support and get one-stop service. In the modern day of social media, though, they can call the 800 number, tweet their problems, look for solutions in a knowledge base, email, complain in an online forum, post a video on YouTube of your product malfunctioning, or blog about it. Compound the problem with the fact that your employees are having a difficult time finding the most current methods to resolve the customer issues and you have quite an information disaster in the making. In fact, it’s a situation that could have a negative impact on both customer and employee satisfaction.

For some, the temptation might be to throw their hands up in the air and surrender to the fact that there are just too many channels out there. If you’re curious as to how confusing it really is, just take a look at all the new channels being created in the social media space alone via the Social Media Prism! Now think about what your employee-to-employee and employee-to-customer communication channels are going to look like in 5 years. Believe me…I understand the desire to just crawl back in bed and ignore social media. The reality is, however, that few business ever succeed by ignoring change. Instead, you’re going to need to stop dismissing social media (both internal and external) as a fad and start working on how to resolve the issue.

Unfortunately, I don’t have a magic product that I can sell for $19.99 to serve as the magic bullet. This one’s going to require smart people in your organization rolling up their sleeves and building a solid information management architecture. No, it’s not easy, but it’s going to be a requirement for businesses to survive in the future! A good place to being would be by looking at the following criteria:

1. How do your employees work? Are they being asked to store information in multiple locations (e.g. My Documents, file shares, document repositories, WIKIs, etc…)?
2. Do your employees know where to go for the single source of truth? (hint, hint…it should be your Intranet)
3. Where are you storing your information? In legacy applications that aren’t searchable? In repositories that require no periodic content review?
4. Does your organization offer a single search interface that allows employees to search information in multiple repositories?
5. Is your information governance killing your employees ability to share information (e.g. no blogs, wikis, microblogs, etc…)?
6. How are your customers interact with your organization? Are they seeking answers from multiple sources (e.g. Phone, website, Twitter, etc..)
7. Do your customers know where to go for a single source of the truth (hint, hint…it should be your Web site)
8. Do you have the infrastructure in place to respond to new types of interactions? Do you have corporate accounts for sites like Twitter, YouTube, Blogger, LinkedIn, and Facebook? Does someone monitor searches on your company and products?
9. Are you making it as easy as possible for your customers to get help and resolve issues?
10. Are YOU embracing internal and external information tools that will allow your employees to share information more easily and provide customers with more ways to serve themselves or seek assistance?

If you haven’t started a review of your current information architecture, it’s time to start and because I find the Social Media Prism to be so useful in explaining the external growth challenge that faces organizations, I have also put together an internal information stratification diagram that hopefully will help IT, Intranet, and ECM professionals demonstrate the internal complexities that exist inside the firewall.  Click on the image below for a larger view or feel free to print out a PDF version.

As always….this is a work in progress and all input, comments, feedback are welcome!

Internal Information Stratification Wheel