Creating a Usable Intranet Despite the Backend :: UXmatters

3 Flavors of Intranet Deployment

During the build stage, you’ll define the level of impact you can have on the intranet’s overall user experience. The look and feel of some solutions can be very rigid. You’ll need to consider key aspects of what is important to users, how to better structure information or data to meet their needs, and how you can improve the information’s organization, the workflow, and access to the information. Think through the following questions to inform the appropriate flavor of intranet deployment:

  • Can we put our own user interface framework in place?
  • Can we use JavaScript?
  • Can we create a headless solution and make API calls to the backend?

Now, let’s look at each of the three flavors of intranet deployment in greater detail.

1. Leverage the out-of-the-box user experience of a packaged solution.

Your enterprise technology platform or content-management solution (CMS) might include some useful features such as enterprise search, news, employee directory, personalization, team collaboration spaces, blogs, and wikis.

Many businesses just license a product, set up security and governance, and think they’re finished. What they fail to understand is that they’ve just begun the process. A packaged solution is not immediately ready to use once it’s been installed. You must first customize the platform for your organization, by configuring features and setting up the taxonomy, terminology, and content types that map to your organization. The better you understand your users’ mental models, the more successful your implementation will be.

2. Customize the out-of-the-box experience with scripts, modules, and plugins that add or extend features.

For example, to create a seamless user experience for the U.S. Fish and Wildlife Service’s portal, we harnessed SharePoint’s community capabilities to connect disparate groups across the organization. The agency’s in-house IT department and business managers did their best to leverage the out-of-the-box features, but the communities were not getting as much traction as we had expected. Surfacing community content outside the individual communities made it easier for people to find the content. Building a portal page provided a place for key discussions across communities. The portal also served as a directory, letting people know what communities existed and allowing them to engage with them. You can also leverage search to surface community content to other parts of the intranet. If you provide access to information and features in contextually meaningful ways, people will find and use them.

It’s equally important to determine what content should continue residing in other systems. Whenever you send users to other systems, be sure to create a consistent user experience that makes the transition from the portal to other key systems as seamless as possible. Provide details that inform users about what they can do in the other system.

3. Develop the entire user interface, using APIs to communicate with the core intranet system.

Determine whether it’s possible to use APIs to connect to the existing backend and create a new or separate custom user interface that leverages the capabilities of the backend solution. A potential issue with this third flavor of deployment is that, if the pace of changes to the intranet is high, the cost of maintaining this type of solution would be costly.

In most cases, the intranet must be highly integrated with other existing solutions and software applications, so it’s better to select a platform that plays well with the existing ecosystem. When building an intranet, you need to keep in mind that it will evolve constantly, along with the company, so leveraging a platform that is already part of that ecosystem is key.

The U.S. Fish and Wildlife intranet, shown in Figure 1, is based on SharePoint 2016. At the left is the community portal landing page, which has many positive attributes—such as a visually pleasing, on-brand design and simple navigation that makes it easy for employees to find the content they need. Our UX professionals focused on the users throughout design, build, and launch, making the intranet a useful communication and collaboration tool that employees have come to rely on.

Figure 1—U.S. Fish and Wildlife intranet based on SharePoint 2016
U.S. Fish and Wildlife intranet based on SharePoint 2016

Step 3: Launch

Of course, you shouldn’t wait until launch to start communicating about your new intranet. Getting internal users prepared and excited about using the new system long before it goes live is just as important as what you design and build into the solution.

Inform employees about the new intranet initiative as early as the discovery phase, then keep them informed throughout the development process. If they know what’s happening, when the go-live date finally arrives, there won’t be any surprises. From early on, everyone should be educated on the value of the intranet, how the intranet will impact their day-to-day roles, and how it will improve their ability to communicate and collaborate with others in the organization. Using such a soft-launch approach provides opportunities for employees to provide feedback, which you can incorporate as the system gets built. This is why training should happen long before the launch of your intranet.

When you’re developing your launch and training plan, connect the dots, leveraging the learnings from your user research during the discovery and design phases, when you discovered the types of training that would work best for the employees who will be using the intranet. Usually, the same type of training does not work for all employees. A multipronged approach to training works well and could include in-person training, online support within the application such as chat, and self-service tools such as FAQs and videos.

Engage Evangelists to Drive a Surge in User Adoption

To increase the overall adoption and success of the new intranet, recruit internal champions or evangelists. These are the people who were most excited about and interested in the new intranet after the early user research. Have them conduct training for other employees rather than the consultants. By using the train-the-trainer model, consultants train the clients’ evangelists on how to use the system, as well as on how to train others internally within their own organization. This will prepare everyone for the change that is to come. Having these evangelists do the training and roll out the intranet ensures optimal knowledge transfer. As a consultant, you can rest assured that your client has employees who truly know the system.

Engage Users Through Internally Led Workshops

The U.S. Fish & Wildlife Service took an inclusive approach to ensure its constituents were informed about the progress of their new intranet. They held internally led workshops in each of their regional offices, sharing a prototype of the intranet prior to its launch.

Senior leaders from the U.S. Fish & Wildlife Service led the workshops, presenting the core features, functions, and benefits of the new intranet to help employees get orientated to the new system. They invited the subject-matter experts who designed and built the intranet to answer employees’ questions, identify issues that they needed to address, and gain feedback and insights. They used video conferencing during the workshops and made video recordings of them for remote workers not able to be there in person. They later edited the video to include screenshots of the final intranet, providing a guided video tour of the intranet to use as a training tool and for onboarding new employees.

Determining whether such a staggered approach to launching your intranet is appropriate depends on the scale of your project and the number of users. But, when using this approach, great fanfare on the go-live date is less necessary because your users have been informed about and trained on the intranet from the start of the initiative.

Measure the Success of Your Launch with KPIs

Once you’ve gone through the entire project lifecycle—design, build, and launch—you may think it’s now time to bask in the glory of your successful new intranet. Not so fast. The launch is not the end of your project.

Remember the KPIs you decided to use at the start of the project? You’ll want to make sure that you do training in such a way that you can measure the success of the launch against those initial KPIs. For instance, if a KPI is to have 50% of the organization up and running on the intranet within six weeks of the go-live date, you’ll want to have a training plan in place that enables you to achieve this level of user adoption.

Just like your business, your intranet is an evolving, dynamic system that continually requires resources and investment. The employees who use the intranet on a daily basis can provide the best feedback on it. Listen to them, communicate with them, and act on their recommendations to ensure your intranet remains a relevant and valuable tool.

Conclusion

UX research and design can make a tremendous difference in the success and adoption of your intranet, regardless of the technology on which it’s built. As a UX professional, it’s your job to understand the users’ needs, then design the intranet’s user interface, keeping your focus on what users need to accomplish with the system throughout the project lifecycle. You can help your company to focus on the experience they need to build for their users. 

Source link