image description
« Back to blog

Six Mistakes You Must Avoid When Designing Your Mobile Corporate Intranet

Corporate intranet is the center of digital communication with employees. The move to mobile intranet is one of the most critical transformations that these portals have undergone in recent years. KLIPR, DIGITAL55’S platform for creating mobile intranets, offers an ideal solution for these situations.

To ensure success, we encourage preventing the following mobile intranet design and management mistakes:

1 – Responsive intranet is not a mobile intranet

Bringing the intranet to a local app instead of turning to a responsive version has great advantages. Web versions of intranets can not use push notifications’ communicative power. The impact of a push notification is much higher than that of an email.

The app has more uses than a web. When a user manages something on his cell, he prefers app support to a browser. Also, one does not have to re-log in to an app if he is using private browsing.

2 – Copying the contents from the desktop version and putting it on the mobile intranet

In general, corporate intranets are saturated with information and services. Technology and design have not evolved in most companies. The versions they offer employee are very poor.

The move to a mobile intranet is an opportunity to create a reduced version of the corporate intranet, with services and information that are truly relevant to the company. Also, the content should be much more agile and light, since reading on a mobile device is faster.

A big mistake is to clone the desktop intranet on the mobile intranet. It condemns the project to fail.

Cloning mobile intranet from desktop intranet can doom the project.

Cloning mobile intranet from desktop intranet can doom the project.

3 – Having all employees read the same content

Corporate mobile intranets should allow the employee to choose the information they want to consume. Sorting the information in subjects we get that the employees can subscribe to the channels that interest them.

In any case, the platform must give the administrator the ability to sent content to everybody, even though it is not on the channels selected by the employees. For example, a message from the company president should be visible to all employees, even if it is not on the selected channels.

4 – Do not give content decision-making ability to project management

All departments and services of the company want to be present in the mobile intranet. Of course, everyone wants to be the protagonist in such an emblematic project.

Different departments will each push to have a presence in the app. Project management must have sufficient powers to select what should be moved to the app and what should be maintained only in the web version. If they do not have sufficient selection power, the result will be an overloaded and uncharged mobile intranet.

Project management must have sufficient powers to select what should be moved to the app and what should be maintained only in the web version.

5 – Do not overuse push notifications

The mobile intranet should be accompanied by a strict policy on the use of push notifications. Push notifications are a very powerful communication tool, but at the same time can be intrusive.

If all published content is accompanied by a push alert, the employee will soon deactivate the notifications and the company will have lost their most direct line of communication.

It is recommended to ration the notifications and make them predictable by the employee. Push alerts will only be used when content is important or meets a predetermined pattern known to the employee. For example, they are accompanied by push notifications, important news, events and training courses, and the rest is not notified.

This does not mean that the employee will not see the rest of the contents. By cascading the information in the mobile phone itself, when you access the app to consume the information notified, you will read the rest of the news.

Content with notifications should be used sparingly. Otherwise, it will be abusive and have a lower reading rate. Thus, it is important to design the app so that information is accessible and encourages reading alerts.

Push alerts will only be used when content is important or meets a predetermined pattern by the company and known to the employee.

6 – Not giving sufficient prominence to corporate information

Corporate information is the protagonist of mobile intranet. Desktop intranet has buried company information in the tangle of services and information. The result is that the employee does not read information about his company.

When we take intranet to a phone, company information must be accessible and, where possible, include sharing options on social networks. In this way, we have made employees the ambassadors of our brand.

When companies have large templates, this can have a high impact because they will begin to share corporate information on social and professional networks.

We turn employees into ambassadors of our brand.