Sean R. Nicholson

Ahhh…reinventing the wheel. It’s an age-old tradition for a lot of organizations, especially when it comes to changes in technology.  Some new class of productivity software comes along and the entire IT organization has to come to a grinding halt while a new strategy is defined. Remember stopping to define an ECM strategy? Or maybe it was an ERP strategy. Or could it have been an CRM strategy. Don’t even think about that amount of time and energy devoted to developing a .com or eCommerce strategy!

Sound familiar? Ever been locked in the “paralysis by analysis” situation where you can’t get anyone to decide because there are just too many so-called “experts”, “gurus” and “SMEs” guiding the conversation? Ever felt like you’d rather just DO something rather than sitting in yet another, non-productive meeting discussing what might happen?

Unfortunately, many organizations are living this situation right now when it comes to defining their social media strategy.  So many new tools, so many new rules, so many unknown risks…where to begin??  But the reality is, the questions being asked aren’t that different from those that have been explored in the past.

For instance, these are some of the questions/concerns facing the enterprise with respect to social media:

1) How do we engage our customers?

2) What tools should we use to listen to our customers, capture information, and interact?

3) What do we do if a customer says something bad?

4) What do we do if a customer says something good?

5) How can we best learn from our customers to create new products and services?

6) How can we make sure that we’re communicating effectively with our customers?

7) Are there experts out there that can help us engage our customers?

8 ) Do we need to put policies and guidelines in place setting expectations for how we interact with our customers?

9) How do we keep our customers coming back and engaging with us?

10) How do we measure the Return on Investment (ROI) on customer engagement?

Sounds about right…Right? Now, flash back 10 years and see if these (slightly modified) questions sound familiar:

1) How do we engage our employees?

2) What tools should we use to listen to our employees, capture information, and interact?

3) What do we do if an employee says something bad?

4) What do we do if an employee says something good?

5) How can we best learn from our employees to create new products and services?

6) How can we make sure that we’re communicating effectively with our employees?

7) Are there experts out there that can help us engage our employees?

8 ) Do we need to put policies and guidelines in place setting expectations for how we interact with our employees?

9) How do we keep our employees coming back and engaging with us?

10) How do we measure the Return on Investment (ROI) on employee engagement?

Sound familiar? These are the questions that organizations found themselves facing when they were analyzing the value of a corporate Intranet portal and the additional of Web 2.0 components like discussion forums, knowledge bases, and (more recently) wikis and blogs. Seems like very similar questions have been in front of organizations for a long time and, in most, serious time and energy has been devoted to answering the employee engagement questions.

My point isn’t to say that employees and customers are the same and the same rules should apply. Having worked extensively in the Intranet space and currently being very involved in defining organizational social media strategies, I will tell you that employees and customers are very different. My point, however, is that if you are in the process of developing your social media strategy and you haven’t invited your Intranet Manager to the table for the discussions, you are missing out on some potentially useful experience and input.

Maybe, by involving your Intranet Manager, you won’t have to reinvent the wheel….just modify one that already exists.

Angie Cullen

When building a business case around a social Intranet, there are a few key components to consider.  Here are five suggested features that you might ask your potential vendors to demonstrate.

Forum Collaboration
By using a forum or threaded discussion  tool, you can engage your employees around specific topics and challenge them to start talking about topics that matter to them. For instance, Project Managers might discuss the project they are working on along with the status of that project, IT employees may share valuable technology updates, and HR personnel may share links to recruiting best practices.  Be sure that the tool  allows employees to create a profile and specify the topics they are interested in. This also provides a way for employees to get to know their colleagues and share information.

Social Tagging and Ranking
Although search engines are getting smarter by the minute, nothing replaces the ability for an employee to indicate whether an article or piece of content was useful to them in their job. Especially if the search engine takes that ranking into account in ordering their search results (e.g. articles they ranked higher, should be placed higher in the results). In addition, if employees are able to add their own keywords that helps influence search results, they will be able to find information that is more meaningful to them much more quickly.

Document Storage & Collaboration
With a document storage and collaboration tool, employees can find and share documents easily.  This tool will allow employees to create, open and edit documents by placing them in a centralized location that’s easy to access. Having this tool will allow multiple users to work and collaborate in real-time, based on the permissions that are set by the owner, on a document simultaneously.  A document collaboration tool can also help you cut down on storage costs. Employees will no longer need to email a status report, PowerPoint deck, or Excel spreadsheet to the entire project team (these multiple copies take up storage on the email server). Instead, they can simply email a link to the single copy stored on the Intranet and use check in/check out functionality to edit that single document.

Expertise Finder
Employees consistently rank the company directory as one of the most used functions of their Intranet. An expertise finder takes that directory one step further and allows users to identify employees that hold specific knowledge or expertise. This is paired with the ability for employees to create their social profiles and self-report their skills. Similar to tagging content, employees should also be able to tag other employees with terms that they could use in the future to find that expert again (e.g. tagging someone as “Intranet administrator”)

Knowledge Base or Wiki
Your employees have a great wealth of knowledge and given the opportunity many of them want to share it. Be sure to ask your potential Intranet vendors whether they offer a knowledge base or wiki functionality that would allow your employees to quickly, easily share nuggets of knowledge that may assist other employees. Keep in mind that it must be easy to use and be integrated with the search functionality so employees can use a single search to locate people or content.

These five key components  are just a few of the items to consider when reviewing potential software solutions for a social Intranet. Be sure to ask each of your vendors to demonstrate the functionality and consider inviting a few of your end users or members of your Intranet Governance Council to the demos to get their input, as well.

Have additional features that you think would be critical to a social Intranet? Feel free to leave a comment and let us know what you think is important or what has turned out to be a popular social feature for your employees.

Sean R. Nicholson

Sometimes opportunities knock quietly….and sometimes they hit us with explosive force. The trouble is, we often miss them even though they are staring us right in the face. As an example, take a look at the recent volcanic explosion in Iceland. This natural disaster has demonstrated the need for business travelers to have access to their corporate information, regardless of where they are located.

The reality is that modern business travelers are more reliant on technology than ever. Sales professionals need access to updated rate sheets and sales contacts, marketing professionals need their product collateral, legal professionals need access to up-to-date case notes, and the list goes on. Without access to the critical information required to do their jobs, traveling professionals would be at a significant disadvantage to those that are able to access their corporate information remotely.

The MODIS instrument on NASA's Terra satellite captured an Ash plume from Eyjafjallajokull Volcano over the North Atlantic at 11:35 UTC (7:35 a.m. EDT) on April 15, 2010. Credit: NASA/MODIS Rapid Response Team.

In addition, the ability to keep in constant contact with employees in the home office allows travelers to make alternate arrangements for travel,meetings, and information distribution. If a sales professional is stuck in the airport in London but has access to email, their travel reservation system, and their Contact Relationship Management (CRM) system, they could reserve a train ride to France, reschedule a business meeting with their customer, and send updated product information…all from the airport.

Estimates indicate that the recent eruption caused more than 100,000 flights to be canceled. Business travelers from Okinawa to Orlando were impacted and their activities potentially disrupted. In many cases, however, employees were able to continue operating remotely due to application access provided via Virtual Private Networks (VPN), remote meeting technology like GoToMeeting, and Web-based email systems.

As a result, Intranet professionals should be looking for ways to highlight the importance of portal, security, and productivity benefits offered by Intranet applications. Demonstrating to executives how internal social media kept employees in touch and helped them conduct business during potentially disastrous times demonstrates the value of investment in an Intranet infrastructure and highlights its benefit.

I’d love to hear stories of travelers who benefited from remote technology and access to the corporate intranet. Feel free to comment and share!

Sean R. Nicholson

While listening to Marketplace yesterday, I heard a great article on a French campaign that is aimed at sparking the entrepreneurial spirit in French workers. According to the piece by John Laurenson, the advertisements feature successful business people in clown outfits and makeup to highlight a new web site at http://www.jesuisunclown.com/ (i am a clown.com). The purpose behind the campaign is to feature successful individuals who have struck out on their own despite others telling them that their ideas were silly.In a time when the French economy needs innovators, the goal is to encourage citizens to risk their pensions and security for the life of an entrepreneur.

The article had me thinking today about employees around the world during these tough economic times and wondering whether employees are encouraged to innovate and share ideas. In the US, we are certainly seeing employees in “hunker and bunker” mode, where they are working hard to keep their jobs in the face of looming corporate cutbacks and downsizing. Unfortunately, when employees are hiding in cubeville, they are usually focusing on just doing their job and not innovating, for fear of looking like “a clown” and risking their employment. The problem with this is that our  global economy needs innovation now more than ever. We need employees to bring new product ideas to the forefront and innovate new service offerings. Managers and executives should be encouraging employees to come up with every new idea possible, regardless of how silly it might initially seem.

As Intranet Professionals, think about whether your Intranet is being used to encourage new ideas. Do you have a campaign asking employees to behave like clowns? Do you have an idea center where employees can submit their ideas and vote on those that they feel would be valuable? Are your executives open to new ideas and are they actively encouraging innovation?

Think about it…products like the slinky, magic eight ball, lava lamps, and mood rings might all probably seemed like silly ideas at the time, yet they have all been significant profit earners for their creators and are still considered by some to be among the top “It” products.

If you’re already finding unique and creative ways to inspire the “clowns” in your organization, please post a comment and share your strategies, tactics, and successes. If you haven’t started an innovation program yet, now might be a great time to start a clown college inside your organization. Your clowns, might just be the key to growing your business and our economy.

Sean R. Nicholson

Continuing with my posts on great Twitter resources, this is a followup to my 99 Great Internal Comms Resources,  99 Great Intranet Resources and 99 Great ECM Resources posts. Below is a link to my list of 99+ great SharePoint Resources on Twitter. If you’re looking for the folks who tweet about SharePoint as an Intranet platform, ECM solution, and a collaboration tool…these are your folks! Pay careful attention and you may see folks who are also providing links to some valuable SharePoint alternatives, as well.

Sean’s list of 99+ Great SharePoint resources on Twitter

Know someone that I missed from the list? Definitely let me know. Shameless self-promotion is also allowed if you think you should be included, just make sure your tweets back up your request.

You can check out the list below, and feel free to leave a comment if there’s anyone else I should add.

Angie Cullen

When developing your Intranet, it’s best not to develop in a vacuum. You may not be the best person to make decisions on how employees will use the intranet to do their job.  Be sure to identify employees that will be involved in the maintenance of the portal and get everyone involved in the design process. Create an Intranet Governance Council that will include at least one member from each department throughout your company. Bigger departments might have 2 or 3.  Let the members of the governance council represent their department and tell you what employees in their department need to be able to do their job more efficiently.

Be sure to let the members of the governance council know that while you value their input and opinions, the final decisions regarding design and functionality are the responsibility of the Intranet team.  In other words, everything that the members of the governance council submit on their wish list, might not make it in to the final product. By setting this clear direction and making the members of the council a part of the design process, you can leverage their excitement and promote collaboration, while ensuring that the Intranet design meets the needs of all departments and employees.

Sean R. Nicholson

Imagine, for a moment, that you have accepted a new position as a corporate executive tasked with figuring our how to make your company work better, faster, cheaper.

Along with the details of your position, you have been informed that you have access to a wealth of competitive intelligence, product experience, and innovative thinking at your fingertips. Sounds like a recipe for success, right?But what if you had no means of capturing, storing, and retrieving that information? Bad situation.

It’s likely, however, that it would be easy to justify an investment in a tool that would allow you to leverage the information. But what many execs don’t realize is that they actually have the potential for this exact type of information at their disposal…if they were to invest in a social Intranet platform.

Classic Talent Management Systems vs. Social Intranet

For years, Intranet and HR professionals have been working to implement successful “Talent Management systems” with very little measurable success. The difficulty with legacy Talent Management systems is they required manual updates of employee history, competencies, training, and certifications and they rarely provide the employee with an opportunity to share their experience.

One of the  biggest shortcomings of these systems was the method used to capture and maintain the information. The process of updating employee records usually occurred (if at all) once a year during the employee annual review process. Managers would discuss employee competencies at the review and either update the system themselves or ask the employee to provide the updates. Unfortunately, a once-a-year update doesn’t provide the timely information required to operate a business and since the system was rarely referenced to identify subject matter experts, employees had no motivation to keep them up to date. As a result, these Talent Management systems quickly became outdated and useless and future investment in these types of tools were difficult to justify.

As Social Intranets are becoming more commonplace, however, a unique phenomena is occurring. Employees are sharing their previous experiences, subject knowledge, and expertise with fellow employees, management, and executives each day, providing a huge resource for internal knowledge that changes by the day, hour, and minute.

The Engagement Experience

To see how Social Intranets can play the valuable role of a Talent Management system, imagine a situation where a Sally Sales, a Sales Executive, creates a post on the Intranet forum asking:

Sally Sales: I am traveling to SmithCo Enterprises tomorrow to show them a demo of the latest version of our ERP  software. Does anyone have information about their culture, personnel, etc…that they can share?

Sam Support, a customer support rep – a role that isn’t traditionally engaged by Sales for input – posts back stating:

Sam Support: FYI, I used to work at SmithCo and you need to be aware that they are wary of “vaporware”. Be prepared to show the software in action and provide them with references of other customers who are using the latest version.  Also, I worked as a contractor with the team that implemented their existing BigCO ERP system and they have some serious limitations that need to be addressed relating to the accurate matching of POs, receipts, and invoices. If you can show how well we address that requirement, it will go a long way.

Able Accountant, an invoicing specialist chimes in with another post stating:

Able Accountant: I have used both our new version and the BigCO system they are using and the difference is night and day. Our automatic invoicing abilities are significantly better than BigCO and our implementation timeline averages 12 months, where BigCO’s implementation at my previous company took 36 months and was almost $1M over budget.

…and the conversation goes on.

While this type of dialog obviously helps the Sales Exec know how to refine their sales pitch, approach their prospect, and hopefully win the deal, there is a secondary benefit that is occurring behind the scenes. Employees are identifying what they know, where they have worked, what skills they hold, and whether they can be leveraged as subject matter experts on a specific product or topic.

As a result, the next time any Sales Executive is selling to SmithCo or any company where BigCo is implemented, a simple search of the Intranet for the terms “SmithCo” or “BigCo” will identify Sally Sales, Sam Support, and Able Accountant as resources that have information and experiences with the BigCo product. This is the exact result that Talent Management systems have sought to accomplish for years.

Through this one interaction, employees have reported to the company that they have valuable competitive information and the fact that they respond to posts like these frequently keeps their information up-to-date. While neither Sam or Able were hired into a position specific to tackling BigCo as a competitor, the fact that they both have and shared previous work experience potentially helped the company make a sale.

As the newest executive looking to improve processes and drive revenue through employee productivity, you now have a gold mine waiting to be tapped.

Sean R. Nicholson

Okay Intranet fans, here it is…the 2009 completely unofficial list of must have functionality for every Intranet.

**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.

{drumroll please….}

# 10) Application Interoperability – There’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 “simpler sign-on” schema so that users don’t have to login over and over to see data in different applications.

#9) A Clean Design – 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.

#8) A Good Name – I always love hearing people refer to the Intranet by it’s given name, rather than “the Intranet”. Creative names allow folks to create an identity for the Intranet that gives it a life of its own. If you don’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.

#7) A Strong Navigation Taxonomy – Yes….it’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.

#6) Personalization – Users need to be able to customize pieces of the Intranet. Whether it’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 YellowBrix.

#5) A Good Rich Text Editor – Nothing helps an Intranet grow more than content, so making the creation of content easy is important. A good WYSIWYG (“what you see is what you get”) editor is important. Don’t forget to make sure your editor has a spell check. I speak from experience on this one (ahem…Plumtree/BEA/Oracle WebCenter)

#4) Governance – 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… ) can be looser than others, but your governance strategy should be flexible enough to accommodate for these different needs.

#3) A Strong Collaboration Toolset – 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 “Idea Center” 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.

#2) A Federated Search Engine – Again, it’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 FAST or Autonomy to bring all of your content together into one search. If you haven’t ever seen a demo of one of these “meaning” based search engines, give them a call and ask for one. You’ll be amazed at what modern search engines can do.

#1) Meaningful Content – The best design, the coolest name, even a great governance strategy…they’re nothing without meaningful content. If your users don’t find value in your Intranet, they won’t adopt its use. In addition (and I can’t stress this enough), the content MUST be timely and accurate.

The only thing worse than no information is bad information…Your employees will act using bad information because they don’t know it’s inaccurate. There’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.

There you have it, Intranet fans! 10 must haves for any good Intranet.

Additions:

Accessibility – Everyone needs to be able to use your Intranet. Ensuring that your pages comply with the accessibility guidelines will ensure that folks with disabilities can read or hear the content. Thanks to Russell @theparallaxview for the suggestion

Have input? We’d love to hear any additions, suggestions, or constructive criticism in your comments!

Sean R. Nicholson

A few years ago, I was in charge of an RFP for a Fortune 500 company to select an Intranet portal application and portal content management system. Thinking about the requirements for that portal and how they would change in this age of social networking got me thinking about how the requirements would change if I were to conduct that same RFP today.

Portal Requirements in 2005

Back in the “olden days” of horizontal portal requirements (you know…a few years ago),  the top requirements for our enterprise portal were as follows:

1. Enterprise scalability, with current requirements at 25,000 end-users, but scaling to 100,000 with additional hardware and licenses.
2. Easy to use, graphical user interface that allows end users to view targeted content and easily navigate to pages within the portal using  either an organizational or functional page taxonomy.
3. Provide portal administrators with the ability to secure content to groups, organizations, and individuals.
4. Provide a WYSIWYG rich text editing interface that allows users to create and edit content, based on their permissions and group membership.
5. Provide a single search interface that allows users to search for content that is target to their account based on assigned permissions
6. Provide a workflow tool that allows content to be reviewed and approved prior to publication
7. Provide a customizable portlet or widget-based interface that allows end-users to customize their experience.
8. Provide portal administrators with a flexible design and administration interface that allows administrators to create page templates that standardize on some page elements (e.g. header, navigation, mandatory portlets).
9. Provide functionality to interface with an enterprise Identity Management Solution.
10. Provide analytical reporting that details usage activity, content quantity, and hyperlink status (e.g. number and location of broken links)
11. The ability to integrate with existing enterprise applications such as the document management system, time reporting system, and expense management system using a Services Oriented Architecture.

Like I said, these were the high level requirements that we looked at. We actually had more than 300 specific technical and functional requirements, but these hit the major functionality we were looking for.

As you can see, though, these portal requirements are based on an “information-push” concept, where a core group of individuals (maybe 50-75 for the entire corporation) create all of the content and push it out to the masses. While we did have requirements for collaborative items like forums, they were listed as optional and we weren’t quite sure whether we wanted to allow end-users to start creating content on their own in a forum environment. Pretty much typical information control tactics that are present (even today) in many large organizations.

Changes To The Portal Requirements In 2009

While many of these requirements would still hold true, an information portal in today’s culture would definitely focus more on collaboration and content management than the pushing information out to the masses. Based on my experiences with some of the popular social networking platforms, my top requirements for the same sized organization would probably look more like this:

1. Enterprise scalability, with current requirements at 25,000 end-users, but scaling to 100,000 with additional hardware and licenses.
2. Easy to use, graphical user interface that allows end users to view targeted content and easily navigate to pages within the portal using  either an organizational or functional page taxonomy.
3. Provide portal administrators with the ability to secure content to groups, organizations, and individuals.
4. Provide both a rich-text content management system that allows portal administrators to deliver content and a WIKI environment that allows end-user to create their own page content
5. Provide a single search interface that allows users to search for content that is target to their account based on assigned permissions
6. Provide content creators (both in the CMS and WIKI environments) the ability to review content additions and comments if they choose to enable the feature.
7. Provide a customizable portlet or widget-based interface that allows end-users to customize their experience.
8. Provide portal administrators with a flexible design and administration interface that allows administrators to create page templates that standardize on some page elements (e.g. header, navigation, mandatory portlets).
9. Provide functionality to interface with an enterprise Identity Management Solution.
10. Provide analytical reporting that details usage activity, content quantity, and hyperlink status (e.g. number and location of broken links)
11. Provide the ability to integrate with existing enterprise applications such as the document management system, time reporting system, and expense management system using a Services Oriented Architecture.
12. Provide end-users with the ability to create custom application and information widgets that can be shared across the enterprise.
13. Allow users to easily share updates with others on their work through personal status updates
14. Allow users to create and manage groups/networks that can collaborate through a WIKI interface or a discussion forum interface. Users should be able to store and review documents as attachments within these groups. Users should be able to collaborate and version these documents and the applications should maintain an audit trail.
15. Allow users to create custom events and invite users and groups to those events. Individual and group events should roll up to a common corporate calendar that displays events to users based on their permissions and group memberships.
16. Allow users to share digital media including photos, audio files, and video files. Users should be able to collaborate and version these files and the application should maintain an audit trail.

So What Just Happened? Those Don’t Sound Like Portal Requirements!

Basically, in the process of writing those new requirements, I changed my RFP from being one focused on a portal, to one focused on an Enterprise Content Management system. Not an ECM as we know it today (which are primarily focused on Web/Intranet content management, document management, and digital asset management), but to an ECM platform that requires the following:

• A customizable presentation layer (the portal)
• A flexible content management system (traditional WYSIWYG content management and collaborative WIKI)
• The ability for end-users to create application mashups
• A lightweight document management system
• Social networking capabilities through collaborative groups/networks
• A lightweight digital asset management system
• Enterprise search functionality

Previously, ECM players such as Stellent, Documentum, and OpenText have not offered a portal interface to their products. Instead, they focused on their ability to interface with portal such as WebCenter Interaction (formerly AquaLogic User Interaction (formerly Plumtree)), IBM WebSphere, Microsoft SharePoint, and Vignette portal.

As a result, some of those solutions are being gobbled up by the portal players in hopes of creating the true Enterprise Content Management System of the future. Some of the portal players, like Vignette and Microsoft have anticipated the merging of portal and CMS, and have opportunities to add social networking to their platforms. In the end, the days of offering a standalone portal are probably long gone and we’ll soon see the horizontal portal players roll into the ECM magic quadrant.

Thoughts or comments? I’m always open to additions and constructive criticism in you comments.

Sean R. Nicholson

A couple of years ago, I was involved in the selection and construction of a new Intranet portal for a large telecom company. The organization had nearly 25,000 employees at the time, distributed all over the United States and they had previously relied heavily on an Intranet portal to communicate corporate events, share HR information, and collaborate on business documents.  The project I was working on at the time was focused on creating a brand new Intranet portal for a spin-off company.

One of the most memorable moments of the project occurred during one of the initial funding conversations, when a Senior Executive at the company asked a very simple question. Amid all of the discussions about functionality, Identity Management, timelines, user adoption, and vendor selection, the Senior Exec simply asked “Do we really need an Intranet portal?”  The question was powerful enough to quiet a room of 25 people and, for an uncomfortable 30 seconds or so, I mentally wrestled between blurting out a visceral response like  ”Are you kidding?” and taking a more tactical response explaining the value of a portal. Luckily, while I was pondering the choice, one of my IT Execs jumped in and provided a quick, concise answer as to the value of the Intranet portal, which was good enough to get the funding conversation back on track. Eventually the project was funded, proved to be wildly successful (on time and under budget is always a good thing), and that particular Senior Exec got to fully realize the value of the portal in ways that had not previously been used in his organization. I still kick myself every once in a while for not having an “elevator speech” response prepared for the occasion.

How often do we question the value of the technologies we support?

An interesting aftereffect from that meeting, however, were that rumors of the conversation quickly spread throughout our IT organization. I can’t tell you how many times I got on an elevator with other IT professionals and, after a few moments of silence, one of them would turn to me and ask ”So…do we really need an Intranet?”.  We’d have a good laugh and part our separate ways on different floors.

To this day, I often reflect on the power of that simple question. The more I think about the situation, the more impressed I am with the fact that one person, in the midst of turbulent conversations had the courage to ask the simple question of “why”. Too often in IT, we press forward with technology, especially when it comes to legacy systems, without asking why we’re doing it. Sometimes we feel like we’re trapped by a proprietary platform, or maybe our end-users are resistant to change, so we simply pour money into costly upgrades or development efforts without raising our hand and asking “Why?” or “What is the alternative?”.  Different options always exist, so in these rough economic times, maybe it’s an ideal time to take a closer look at the technologies that are fueling your organization, compare them to the feature-functionality of new products, and determine whether a new product could actually do the job better for cheaper…or maybe whether you actually need the technology at all.

The second reason I often think about that situation has to do with a mindset of automatically assuming that the technology we advocate for is invaluable to the company. Regardless of whether your area of experience is Intranet, Business Intelligence, Data Warehousing, CRM, or any of the other IT realms, you need to be prepared for the question of “Why”. As your business partners begin to look for places to cut costs, reduce their overall application portfolio, or move to a Software as a Service (SaaS) model, you need to be able to realistically justify the technology you support.

To that end, here are my top 10 justifications for a corporate Intranet portal. I’d be very interested to hear additions that readers feel are important.

1. A centralized location for corporate communications – This is more important to larger organizations than it is to companies of 25 employees. The larger and more distributed the organization, the more important it is to the corporate culture to have a single place where all employees can go to find information on company strategies, announcements, HR information, and special activities.
2. Application and information aggregation - There is nothing more frustrating to employees than to have to open 15 different browser applications and 10 different application clients to find the information they need. Employees (especially those facing the customer) need to find information quickly and almost need the information to find them. Case in point, one of the more recent Intranets I worked with allowed the employees to look up a customer by name in the Intranet portal. The resulting page created a mashup of application information including links to the customers service contracts, open service tickets, and even a Google map of where the customer was located with the closest service technician shown on the map via an integration with a Global Information System (GIS) application. All of this information came from several different applications, mashed into a single view of relevant information.
3. Federated Search – A good Intranet portal offers a federated search model, allowing end-users to use a single, simple search interface to find information stored in a variety of applications. For instance, the portal should be able to leverage APIs from the corporate HR system, document management system, as well as CRM and ERP applications. The value of locating information stored in disparate systems makes a strong business process improvement case for the ROI of a portal.
4. Identity Management (aka “simpler sign-on”) – Modern portals provide a single point of entry to corporate applications and information, so they should either include an Identity Management (IdM) solution, or leverage a third party system. To ensure a high rate of user adoption, end-users should be required to authenticate as few times as necessary to support corporate security policies. This “simpler sign-on” schema reduces the number of times a user has to log in, saving time, and enhancing employee satisfaction.
5. Knowledge Management and Collaboration - Through the use of collaboration tools such as knowledge bases, Wikis, forums, chat rooms, or blogs, Intranet portals capture the corporate knowledge of how things get done. These collaborative tools ensure that commonly repeated solutions are captured in a searchable manner that can be discovered easily by future employees. In addition, these tools mitigate the danger of allowing knowledge to “walk out the door” when employees leave the company.
6. Decentralized Content Management – Intranet portals with integrated security and content management systems allow each department within the organization to manage their own content creation/management strategy. Long gone are the days where every article published to the portal had to be scoured and approved by a Content Manager in Corporate Communications. Instead, the Corp Comm group often establishes guidelines and best practices for the departments (and sometimes at the individual level) to follow. This allows for information to flow more freely within the organization and updates to the content to made in a more timely manner.
7. Organizational Transparency (aka “silo-busting”) - An added bonus to the decentralization of content management is a transparency factor. The more content that is published by each department, the better the chance that the rest of the company will gain an understanding of their goals and strategies. This helps drive cross-departmental communication, reduces the amount of overlapping work being done, and drives organizational collaboration.
8. Environmental Sustainability – More information stored in electronic format that is easily searchable naturally results in fewer file cabinets full of paper. Intranet portals can serve as document repositories for smaller companies and integrate with third party document management systems in larger organizations. The end result is less paper, and a better solution for the environment.
9. Employee Satisfaction – The easier information is to find, the more likely an employee will be able to resolve the business problems they face in their daily duties. Whether it’s locating customer information in order to resolve a customer issue, or locating research information that the employee can leverage in their next presentation, the more business information that is available throughout the organization, the better decisions employees can make in their jobs and the more successful they will be.
10. Customer Satisfaction – Last, but by no means least, is customer satisfaction. By centralizing information and providing access to federated search tools, customer-facing employees can reduce the amount of time it takes to locate customer information and can make better business decisions that reduce call handling times, increase first-call resolution in call centers, and lead to upsell opportunities that provide customers with enhanced services that meet their needs.