Intranet branding is often confused with the user interface design. Although user interface is part of the brand there are more elements to it such as: intranet logo, intranet name, tone of writing, and design.
In this post we’ll take a look at some of the best practices when it comes to branding your intranet to make it relatable to your organization.
Style Guide & Theme
When building a brand new or redesigned intranet, many organizations reuse their public-facing website style guide.
Style guides typically contain:
Logo usage guidelines
Fonts and typography
Image usage best practices etc
There is nothing wrong with using your public-facing style guide for an intranet, but it’s important not to copy the public website’s look and feel completely.
Here is why:
Avoid Source Confusion
Often times intranet contains links to your public site. We’ve seen users confused when they click on the link in the intranet and end up on the public site thinking they’re still on the intranet. This is more typical for intranets which have near-identical design as the public site. Try to avoid that.
Remember Intranet Use Cases
Another element to consider are the types of devices people will be using when working with the intranet. This will dictate:
Supported screen resolutions. Intranets typically support wider screens to utilize screen real estate for document management
How you present content on the site. Intranet users come to your intranet much more often and content needs to be optimized for quick access.
How do you handle mobile devices. Mobile is less prominent for the intranet and you may save budget with only branding key areas where mobile access is important, as opposed to entire site.
Remember Intranet Audience
How and what you target as your intranet audience will drive what content should be on it.
Content targeted to employees and staff is different from content you write on the web. The table below illustrates how the audience and technology is quite different between platforms.
Public sites usually have a dedicated team authoring and maintaining the content. Intranet in turn is usually a part-time team of contributors.
Opensource that’s highly flexible
Full-time large team, fair budget, fair timeline
Millennials, Gen-X, Baby Boomers
Intranet solution (ex.: Office 365) that does the heavy lifting, but dictates much of the UI design
Part-time small team, small budget, short timeline
Source: Nielsen Norman Group
Style Guide Best Practices
With that, here are the best practices on what to use from your public facing website style guide, and things to consider:
Don’t overbrand it or make it into an art showcase
Remember who your users are and what they need from an intranet
Don’t deviate from corporate branding to the point of being unrecognizable
Don’t replicate the public site look
It will set unnecessary expectations and confuse others
Keep fonts and colors
Keep page header simple
Majority of real estate will be used for document management; avoid taking up space
The intranet name is another important aspect of branding. In fact, there are many strategies to help you come up with a creative name for your intranet including crowdsourcing with your staff.
Organizations are often afraid that crowdsourcing will produce really bad results and the company will have to either stick with it or come up with a better name. There are strategies you can use to avoid a negative outcome.
Define Intranet Purpose
It all starts with why you’re rolling out the intranet. Your staff (even if it’s just a handful of decision makers) needs to agree on that. It can’t just serve or be understood by one or two people.
Is your intranet there to:
Help people connect
To help find information
All of the above?
Define key goals behind the intranet and come up with the name that suites that goal.
For example, the name “watercooler” sounds like it’s geared towards employee news, events and other employee related topics and not much of a place for corporate information or document management. If that’s your goal for the intranet - then it’s great; if not, you might want to reconsider.
Some Bad Examples
Avoid naming your intranet with generic terms such as:
“[company name] Portal”
Hard to pronounce names
NOTE: Intranet URL and intranet name are not one and the same
Your intranet URL can be sharemuch.sharepoint.com due to naming restrictions but have a meaningful name for the site itself which can be used for as an intranet logo.
Intranet logo is best when it’s clear and simple, and includes your intranet name.
Things to consider:
Ensure you maintain square proportions as much as possible
Office 365, for example, uses the logo everywhere on the site and in some places, you can’t control how the system resizes it.
Avoid all white color logo
Again, office 365 out-of-the-box components use this logo everywhere. In some places you may end up with “blank” square if your logo is completely white.
Avoid intranet name + company logo together
The issue is here is that users may be confused which logo they should click on to get “back to home,“ as the logo is often link to the home page.
Another issue is that it increases the length of the logo and Office 365 may squeeze or resize the image, making it look disproportionate or cut off.
The purpose of the footer is to help the user find other important pages on the site and contact information for the intranet team.
It’s become common to have a large footer on the intranet and mimic site top navigation in it. It’s not a bad strategy but there are few things to consider:
Ensure links and information in the footer are up to date
Top navigation usually changes with the site structure automatically, the footer often gets forgotten and links become broken or obsolete.
Avoid social media icons in the footer especially if you have social media feeds on the site - this becomes duplicate information.
Keep number of sections less than 7 (see below; 4 sections already look busy)
Avoid making it flashy, it’s just a footer
Intranet branding goes beyond the colors of the site. It’s about the purpose and serving the content to the right audience. Make it relatable and unique enough from your company public site but not an art project on its own. Remember the resources typically available for maintaining the intranet are less than that for public site and those need to be considered.
Have a comment? Drop us a note!
Yaroslav Pentsarskyy is the Director of Product at Origami. He's also 8 time Microsoft MVP, speaker at many local and worldwide tech events, and a published author of several SharePoint related books.