Sean R. Nicholson

It never ceases to amaze me how few people trust their organizational intranets. A tool that was designed specifically for the purpose of helping employees do their job better and faster is often the joke of the water cooler. Yet organizations knowingly ignore the fact that employees don’t use or trust the information stored on their intranet.

Periodically, I have the great opportunity to sit in front of a group of employees and ask them about their intranet experiences. Often, it’s in anticipation of an intranet revamp, so the need for a “do-over” or an evolution has already been defined at some level. While the individual users and comments might be different, they usually go start with something like this:

Me: Who here uses the Intranet fairly consistently?  (half the hands in the room go up).

Me: For those of you whose hands aren’t up, why don’t you use it?

Response #1: The content stinks.

Response #2: I can never find what I’m looking for.

Response #3: Yeah, and when you do find something that looks right, it’s two years old.

Response #4: The last time I searched the intranet for the latest information on new Java libraries, the first five search results were the hours and

specials at the local coffee shop.

Me: For those of you with your hands up, (you can put them down now) tell me how you choose to use the intranet?

Response #1: I use the employee directory. It’s right most of the time because it’s tied to our active directory and employees are added/removed as they join or leave the company.

Response #2: I use it to see what’s being served in the cafeteria. They do a good job of updating the menu each morning.

Response #3: I used it to download the forms to change my 401(k). I did have to choose between last year’s forms and this year’s forms, but I navigated directly to the HR landing page, and didn’t use the search tool.

…and the conversation goes on for another hour. Each employee sharing their stories of frustration or limited successes with the intranet platform. One failure feeds another employee’s stories and the negative sentiment in the room grows. Frustrations often include multiple logins, confusing navigation, multiple windows, and ugly design but the vast majority of their frustrations are around the relevancy of content, outdated information, and poor search results.

Now, imagine for a moment that, instead of the corporate intranet, these comments and stories were being said about another employee. If an employee had a history of providing inaccurate information, was behind the times and slow in their responses, and didn’t collaborate well with other employees it’s highly likely that they wouldn’t survive their next performance review. Yet organizations continue to ignore the fact that a tool that is key to their business success is unable to provide employees what they need. In fact, many companies invest more money in licensing fees and servers for their Intranet than any single employee in their company. Yet, the investment in keeping the content fresh and relevant is minimal. When you present your Intranet in this light, it seems like a logical deduction that an annual review of the performance of your Intranet is worthwhile.

The conversation continues to get more interesting as the focus shifts toward what the employees would like from their Intranet:

Me: First, are you interested in having a functional Intranet? If so, why?

Response #1: Definitely! It would make my job a lot easier if I could find updates to our products and pricing easily.

Response #2: Not really, we purchased a different tool for our group to store information because the Intranet is is bad.

Response #3: I would use the Intranet if I knew the search worked. Right now, it’s just too hard to navigate around a hope that I find what I’m looking for.

Response #4: I think a good Intranet would really help the company do business. It just needs to be a lot easier to use. No one asks the employees how they want it to work, they just give us a tool and say “Figure it out”.

Response #5: They should probably just start over and build something like Facebook. I’m already friends with most of my co-workers, anyway, so it would be easier if we could just make a private place on Facebook where we could share company information.

From these responses, it clear that the desire for an intranet exists in some format. Even responses #2 and #5 indicate that there is a need for a tool, they just opted to use something else or want a different tool since the organizational intranet wasn’t meeting their needs.

Steps To Develop Organizational Trust In Your Intranets

1) Ask Your Employees For Input

Most employees that I talk to feel like they have no ownership or input to the Intranet. They view it as a tool that is given to them by the organization and its structure and content are set in stone. They are, however, interested in making it a better tool and have plenty of input on how to improve it. Some of the input is good, some of it is wishful thinking, and some of it is so focused on their specific job that it may not be useful to others. Little changes to navigation and content, based on their feedback, does increase positive sentiment and gives employees a sense that they had an impact on organizational change.

2) Give Employees The Chance To Shape Content

Because content woes are top of the list when it comes to frustration with their intranet, many employees would welcome the opportunity to contribute content or, at the minimum, provide feedback on the value of the content. Although most aren’t interested in writing blogs, they would like to be able to suggest content or changes to ensure that information is accurate. To accommodate this, feedback forms, commenting systems, and content rating tools can help employees flag or suggest content. By providing these tool to employees, organizations remove the excuse that “content isn’t useful” and put the onus on the employee to shape the quality of the content.

3) Conduct Scheduled Content Audits

Empowering your employees to help shape the quality of the content doesn’t mean that employees responsible for maintaining the Intranet can sit back and relax. Consistent auditing of search logs to find failed searches (those with zero results returned) can help determine a need for creating or re-purposing content. In addition, face-to-face conversations with your employees to ask what they would find valuable can result in a gold mine of  content requests. Obviously, the need to evaluate future functionality is a key responsibility, ensuring that employees are armed with tools and features that will help them in their daily activities.

4) Optimize Your Pages To Work With Your Search Engine

Although it’s tempting to blame the technology behind poor or failed search results, it’s usually not the intranet search engine that’s causing failed searches. Instead, it’s likely poor search optimization or old content that results in failed searches and employee frustration. Taking some time to understand the fundamentals of search engine optimization and tuning your pages to meet the search patterns of your employees can make a huge difference, without having to rip out and replace your search engine.

Just like any employee in your organization, neglect of your Intranet will result in poor performance and dissatisfaction. If you’re really interested in improving your business processes, doing more with less, and helping your employees do their job try investing a little more time and energy into ensuring that your content is good and is able to be found.

EAVB_ZUCRRVMRCL

Sean R. Nicholson

As the centralized point of access to organizational information, your Intranet portal may also represent a potential security risk. This is especially true if your portal is accessible to employees via the Internet. If your Intranet authentication is tied to your Active Directory or LDAP, be sure to put policies in place that ensure that your employees change their passwords on a periodic basis. In addition, be sure to encourage (or require) employees to use “strong” passwords, that are comprised of a combination of alpha characters, numbers, symbols and mixed cases.

Unfortunately, according to Wired Magazine the most common password successfully used in a recent Hotmail attack was “123456″. Yes, that’s correct…virtually the same password used by Mel Brooks in Spaceballs to secure his luggage.

As an Intranet professional, it’s important that your employee communications focus on employee education around the topic of frequent password changes, password strength, and their ability to identify and avoid password phishing scams. The Journal of Accountancy provides a great analysis of different types of passwords and their ability to be compromised, as well as a five step process that can be followed to analyze your existing application password strength.

1. Start by developing a full understanding of how your computer system stores passwords.

2. Determine whether your encryption method is powerful enough to safeguard your system, and ensure users choose passwords wisely.

3. If your analysis reveals that your password security is inadequate, begin your search for improvements at the lower end of the cost spectrum.

4. If your assessment reveals that you need an entirely new password management system, look for “yes” answers to each of the following four questions when you evaluate products. (click here to view the additional 4 questions)

5. Regardless of how confident you are in the accuracy and completeness of your security assessment and any remedial solutions you may choose, consider conducting a penetration test.

Source: Journal of Accountancy, July 2009.

If you haven’t run a recent campaign reminding employees of their responsibility to keep corporate information secure, it might be a good time to put one together and teach your employees how to avoid weak passwords and phishing scams.

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

Regardless of whether you are a seasoned Intranet Professional or just getting started with your first Intranet design, I highly recommend adding What Every Intranet Team Should Know by James Robertson of Step Two Designs to your library.  At 110 pages, this handbook packs a wealth of valuable information into a quick-read offering a background understanding of the evolution of Intranets, guidance on identifying the needs of your organization, and useful tips on designing a solution that meets those needs.

What Every Intranet Team Should Know by James Robertson

Rather than trying to educate the reader on every possible situation that could be encountered in an Intranet build or redesign, Robertson focuses on sharing industry best practices and real-world experiences that the reader can easily adopt.  Robertson’s straight-forward writing style, coupled with sample images and supporting graphics makes the content easy to understand and apply.

Although the book might appear small at first glance, Robertson proves that good things come in small packages by tackling complex issues such as requirements gathering, usability design, and governance. Each chapter provides clear, actionable steps while surfacing potential pitfalls and providing guidance on how to avoid them.  Throughout the text, Robertson progressively lays out the fundamental concepts necessary to understand not only how to design an Intranet, but how to design one that your employees will actually use.

What Every Intranet Team Should Know has found a permanent place in my library and will become a must-read for those involved in current and future Intranet projects.

Sean R. Nicholson

Building a great Intranet environment is often about balance. Balancing acts like those between openness and security,  corporate needs and individual desires, and the balance between content and culture often make for long meetings and tough decisions. Internal communicators and Intranet managers often have to determine how much to share and the right format in which to share it.

Take, for instance, the topic of how much strategic corporate information should be shared internally with employees, and at what time.  Some organizations are willing to post strategic information like corporate earnings and key performance indicators on their Intranet in real time or prior to formal announcements. Others are concerned about employees sharing strategic information outside the firewall where it could impact stock prices or competitive behavior. Usually, the key cultural component as to whether this information is shared with employees is one of trust.  It boils down to whether the organizational leaders trust that employees understand the critical nature of the information being shared.

In situations where a strong bond of trust has been formed between the executive layer and the employees, leaders see the sharing of this information as critical to the success and growth of the company since it tells employees where they are doing well and points out where they can focus their energies to improve. These organizations often use the Intranet to openly share corporate goals and strategies, as well as the performance metrics to measure success. Along with the communication comes a consistent message of the importance of using the information internally and only sharing when and to whom it is appropriate.

At companies where that bond of trust has not been formed or has been previously violated, executives often feel that employees simply don’t understand that sharing earnings or performance information prior to formal announcements can have an adverse impact on the operation of the organization?In these cases, Intranets are often void of critical performance measures and are used, instead,  as communication vehicles for corporate events, product announcements, and HR information. Each of these are important functions, but of little value to the employee in determining whether their day-to-day activities are helping the organization advance its corporate goals and strategies.

In organizations where executives prefer to guard the information and release it to employees at the same time they announce to the public, employees often feel as though they aren’t “in the loop” and, at times, learn about important corporate strategies online, from local news sources, or colleagues at other companies. Hearing corporate performance news and announcements from third parties, rather than hearing the news directly from their executives, often propagates a feeling of mistrust between executives and the employees.

Realistically, it would be naive to state that the best practice is to always share strategic information with employees via the Intranet. The reality is that in large organizations or those with little governance, it just may not be reasonable to assume that providing real-time feedback on performance indicators is possible without having the information leak. Even in small organizations, disgruntled employees or accidental disclosure may result in the information leaking.

Therefore, the best practice for when to share key performance metrics will have to be based on the balance of trust within the organization and the employees’ understanding of when/where/to whom it is appropriate to share. As a result, Intranet professionals will have to work to educate employees as to the importance of keeping the information secure and disclosing only when their organizational culture dictates.

Thoughts, comments, or experiences? I always welcome feedback via comments!

Sean R. Nicholson

Searchability is key in allowing your users to find content on your Intranet. While most users are happy with conducting a simple keyword search using a single text box, an advanced search feature allows users to find information and find it faster.

In typical Intranet search results, users are presented with content and documents that contain the keyword or keyphrase they have entered. What’s often not present is the context in which the information is stored. For example, suppose that the user searched for the phrase “key performance indicators”. Likely, they’d receive a lot of content and documents in their results, but the results may not necessarily specify whether the results are KPIs for the Sales department, IT, Marketing or another department.  As a result, the user spends time sifting through the information to find the specific content they are seeking.

By leveraging advanced search functionality, Intranet Administrators can provide their users with the ability to refine their search sources prior to ever clicking the “Search” button. Maybe the user is only interested in the PKIs that are located within the IT departmental content and are stored in PowerPoint documents. By using advanced search, this type of filtering could be offered making it easier to find the correct content located in the appropriate context.

Sean R. Nicholson

If you haven’t figured it out already, it’s a Google kinda world out there and your Intranet users expect your search functionality to provide them with accurate, relevant results to their search queries. With that in mind, if you haven’t already begun the process of building a federate search strategy, it’s time to do so.

While the term “federated” might sound fancy, it’s just a high-tech way to say “cross-functional”. In a nutshell, if your Intranet search is federated, it means that it can go beyond searching your portal content and also retrieve results from your document management system, Enterprise Resource Planning (ERP) system, Customer Relationship Management (CRM) system and any other relevant applications.

When putting together your federated search strategy, keep in mind that while returning a broad set of results from multiple systems is important, maintaining the security standards set forth by those applications is key. In other words, your federated search results should only return content and documents that the user is allowed to see in the originating application. This can often be the trickiest part of federated search, but many application vendors have begun exposing search APIs and Web Services that only return appropriate search results with security in mind.

The first steps to defining a federated search strategy is to take an inventory of all applications inside your Intranet that users currently search. Next, determine what roles might have a need to search which applications and prioritize the need to federate your search to those applications based on the business need. For instance, if a high volume of your users search your enterprise knowledge base and it isn’t tied into your portal search, that might be a good place to start. Your priority list will be defined on which applications are searched most frequently.

Once you have developed your priority list, work with your application vendors to determine whether they already expose Web services that would allow you to easily pass search terms and integrate results into your portal. Be sure to test your integrated functionality extensively to ensure that the results that are being returned are the same as if the user had searched in the originating application and be thorough in your security assessment of the results.

As you progress down your list of applications that are integrated into your portal search, be sure to let your users know that they can now use the portal search to quickly locate content across the enterprise. The more federated your portal search becomes, the more quickly your users will be able to locate information, which will drive portal adoption.

Sean R. Nicholson

When it comes to managing Intranets, governance is one of those topics that tends to divide folks into some pretty extreme camps. One side contends that users should be able to govern themselves freely and, when left alone, content driven by the users will be rich and meaningful. The folks on the other side of the fence believe that content should be generated by one or more specific departments (usually Corporate Communications or HR) for consumption by the end-users.  Their position is often based on the argument that end-users would pose a risk to the organization by sharing incorrect, privileged, or inappropriate content if the wild west of end-user content were allowed. The reality is that these two camps each have their valid points, but the best practice is to land somewhere in the middle by allowing individual contribution, but providing some oversight.

While it’s always good to have one or two Intranet experts who understand the technical architecture of your portal and Intranet applications, it’s also valuable to seek input from not-so-technical Intranet power users from across your org. One tried and true method is to form an Intranet Governance Council that consists of the primary power user from each of the departments in your organization. By ensuring that each department is represented, you’ll hear about issues and concerns from throughout the entire organization and these representatives can solicit feedback from their end-users as well as help you spread of the word about upcoming changes or the addition of features/functionality.  When forming your Intranet council, it’s best to keep it to a small group, usually one or two representatives from each department and make sure to schedule a recurring meeting to get together and review your content management strategy and hash through any issues that might arise.

At the start, it might feel like there are too many cooks in the kitchen and some departments might attempt to set the expectation that their department should have more influence over the direction of the functionality or content. If this occurs, remind each representative that all departments have an equal share in the success or failure of the Intranet and working together is the key to success.  Sometimes this great quote from Henry Ford can help set the tone — “Coming together is a beginning. Keeping together is progress. Working together is success.”

Sean R. Nicholson

Over the years, I have been privileged to work on a variety of Intranets ranging in shapes and sizes. Some were for large corporations, others were for small non-profits. Some were heavily governed, others were driven by user content. Even though each of these Intranets were unique in their own ways, they had one key element in common – strong user adoption. Without a strong user community that recognized the value of the Intranet, each would have failed.

Follow these 5 best practices and you’ll be on your way to showing your users the value of your Intranet and ensuring that they keep coming back for more.

1) Give your Intranet an identity – Just as with any Web site, your Intranet needs a strong brand that means something to your employees. Give your employees an opportunity to help choose the name and you’ll take an additional step in not only selecting something that is meaningful to your audience, but allows them to have a sense of ownership over the brand.

2) Find Your Advocates And Help Them Spread The Word – If you’re in an medium or large organization, it’s likely that you won’t be able to drive user adoption all by yourself.  Instead, recruit a team of employees who understand how valuable the Intranet can be and arm them with tips and tricks that they can use to show the value to others.  Be sure to find folks who may not have recognized the value of the Intranet in the past and work hard to convert them into advocates. You’ll be surprised how much weight their endorsement carries.

3) Give Employees A Voice – Whether it’s through forums, blogs, polls and/or Wikis, give your employees the opportunity to add content to the site. Allowing them to contribute will enhance that sense of ownership and give them a reason to come back.

4) Make It Easy To Use – It’s a Google world out there and if your users can’t find information quickly and easily, they’ll seek it somewhere else. Make sure your Intranet has an easy-to-navigate taxonomy as well as a strong search engine.  Also, be sure your following the best practice on when to open new windows with hyperlinks so your users to get lost in multiple browser sessions and can always get back to your site.

5) Update, update, update – Users come to Intranets for content. If your information is stale, your user adoption will plummet. Find ways to add new content as well as new functionality. If a feature or widget  isn’t getting any traffic, ask yourself whether it’s worth the real estate. Also, be sure to periodically ask your users what they think and make changes when it makes sense.

As always, I’m interested to hear feedback and comments, as well as strategies that you have used to drive Intranet adoption in your organization.

Sean R. Nicholson

When creating hyperlinks in your Intranet portal or social media application, it’s important to know when to create a link that reuses the existing browser session and when to open a new browser.

Best Practice #1 – When your hyperlink is pointing to another page within your Intranet, reuse the same browser window. The purpose of reusing the same browser is that creates a sense of continuity and flow and doesn’t leave the user with 20 different windows open after just a few minutes of browsing.

For instance, if your Intranet portal is called OurPlace and the URL to reach it is http://ourplace, then any URL that begins with http://ourplace should reuse the existing browser.

Best Practice #2 – When your hyperlink points to an external application or Web site, it is acceptable to open a new browser session. By opening the link in a new browser window, you ensure that the user can easily return to your portal, specifically to the page they were reading when they clicked the link. This also signals the user that they are exploring a link that is outside or your Intranet portal and, potentially outside your firewall.

Using the example of the OurPlace portal, if you create a link to a news story published on the local newspaper’s Web site, the best practice would be to open that link in a new browser window.

Reminder: Best practices are guidelines for common situations. There are always exceptions and it is up to you as an Intranet professional to use your best judgement as to what works best for your user experience.

Comments and feedback are always welcome!