Portfolio

Staff intranet solutions for engineers

Engineering group engages its staff through intranet development

Influential Software redesigned an engineering company’s staff intranet to help technicians in the field communicate more effectively.

Graphic showing someone logging into the internet representing staff intranet

Executive brief

Empowering staff with a modern intranet

Our client is an engineering company that works with clients across the UK. Influential Software’s digital portal experts redesigned the company’s intranet system. The new design helped communication among remote workers and boosted engagement with a modern interface. The main benefits of this redesign were:

simpler intranet interface

better staff engagement

rewards scheme promotion

accessible on all devices

Curious about how we achieved this portal solution? Read on to find out more.

The full story

Purple arrow encouraging readers to scroll down for the rest of the GDPR data solutions case study

The challenge

Lack of communication

Staff engagement was low and the client believed that their outdated intranet portal was to blame. With most of their staff working out of the office, it was important to keep engagement and communication high. The pre-existing intranet design had the following issues:

 

  • no personalisation for staff
  • looked like a corporate newsletter
  • slow and difficult to navigate

 

In brief, the company needed a new design that was less corporate and more engaging. The client also wanted to make sure that staff could easily access and interact with the intranet from any device in any location.

 

As the main objective was engaging staff in the field, it was important that workers could access the intranet from their phone or tablet. As part of this effort, the company wanted to promote a new benefits scheme through the intranet as well.

 

The primary goals of this new portal were to:

 

  • promote the new staff benefits
  • mirror company branding
  • ease internal communication

The solution

Building a modern SharePoint intranet

Based on our reputation as SharePoint development experts, the client approached us to redesign its SharePoint intranet.

 

As the intranet’s foundation was fit for purpose, we focused on redesigning the interface and branding. One of our main goals was to make the intranet more comfortable to use for non-technical staff. SharePoint was a good fit for the following reasons:

 

  • fully customisable branding
  • promotes the flow of information
  • encourages transparency
  • enhances productivity

The benefits

Unified workforce with staff intranet

The primary benefit of this digital portal solution was enabling better communication through an intuitive design. Staff both in the field and in the office felt more connected to the company and their fellow employees. By promoting the employee rewards scheme through the intranet, the company developed a culture of recognition.

 

On top of this, having a forum for staff communication helped the team speak more effectively. Despite not being in the same office, the team were able to access internal news, company communications, and contact info with ease.

 

Overall, the business benefits of this digital portal solution were:

 

  • enabling remote working
  • boosting staff engagement
  • matching company branding
  • enhancing communication

 

From SharePoint implementation to continual support, we’re helping this company optimise its business efficiency and productivity in the short and long term.

Work with data portal experts

This engineering company is one of the dozens of mid-level to enterprise businesses that benefit from our expertise. To find out how we can help you, check out our software development page.

Info

17th November 2020
digital portal, intranet, Sharepoint, software development

Privacy Preference Center

Necessary

Advertising

Analytics

Analytics cookies collect information that is used either in aggregate form to help us understand how our Websites are being used or how effective our marketing campaigns are, or to help us customise our Websites for you.

Google Analytics
The cookie _gcl_au is used by Google Analytics to understand user interaction with the website.

For example, in order for Google Analytics to determine that two distinct hits belong to the same user, a unique identifier, associated with that particular user, must be sent with each hit.

The analytics.js library accomplishes this via the Client ID field, a unique, randomly generated string that gets stored in the browsers cookies, so subsequent visits to the same site can be associated with the same user.

By default, analytics.js uses a single, first-party cookie named _ga to store the Client ID, but the cookie's name, domain, and expiration time can all be customized. Other cookies created by analytics.js include _gid, AMP_TOKEN and _gac_. These cookies store other randomly generated ids and campaign information about the user.

Google Analytics
_gcl_au, _gid, _ga, gtm_preview

Other

WordPress uses cookies for authentication. That means that in order to log in to our WordPress site, you must have cookies enabled in your browser.

There are two types of cookies set by WordPress.
1 — Session cookies — These are ‘strictly necessary’ cookies as WordPress will not be able to function without it.
2 — Comment cookies — These are not ‘strictly necessary’ cookies and are set when users leave a comment on a post.

Wordpress Session cookies:
Users are those people who have registered an account with the WordPress site.
wordpress_[hash]
wordpress_logged_in_[hash]
wordpress_test_cookie
wp-settings-{time}-[UID]

Wordpress comments:
Comments are usually turned off by default.
If by chance they are still active on a post, asides being turned off when spotted, data from these are not saved by Influential.
- When visitors comment on a post, they too get cookies stored on their computer. This is purely a convenience so that the visitor won’t need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters:
comment_author_{HASH}
comment_author_email_{HASH}
comment_author_url_{HASH}

Wordpress, Intercom
comment_author_{HASH} comment_author_email_{HASH} comment_author_url_{HASH} wordpress_[hash] wordpress_logged_in_[hash] wordpress_test_cookie wp-settings-{time}-[UID]
intercom-id-[app_id],intercom-session-[add-id]