Dipping into Twitter is always good for getting a temperature check on issues or getting a sample of experiences and opinions. Put ‘intranet’ into a Twitter search and you’ll find a whole slew of tweets.
Filter out the marketing messages (apologies for those on behalf of all intranet consultants) and the noise, and you get an interesting slice of feedback about user’s intranets. Here’s a few examples from a few hours in early February:
What’s interesting about all these is that they would invariably be very useful feedback for intranet teams, either for issues which are quite specific (and could therefore be solved), are more general comments or need digging to find out why somebody is saying they are going into battle with the intranet.
However the fact that all these users are venting their intranet frustration using external social media makes one wonder if they have bothered to feedback internally.
Don’t miss the opportunity
If they didn’t give feedback it’s a missed opportunity for the intranet team involved. Gathering feedback has many uses and benefits:
- It identifies issues and problems with content and functionality which can be solved by the intranet team, the IT help desk or content owners or site managers
- It identifies more deep seated issues and trends about how users find your intranet
- It can provide statistics and data which can act as KPIs, arguments for a business case and so forth
- It can capture feedback specific to a site or page which can help motivate or galvanise individuals responsible for that section into action
- It shows both stakeholders and users that their input is valued, encouraging employee involvement and also team accountability
- It means you don’t miss an opportunity for vital engagement or interaction with a key stakeholder or individual who gives feedback
- It means you get to know your users better to create a better user experience
- It can help identify individuals and make connections which you can draw upon later, for example during projects when you need detailed feedback
Go forth and gather
In practice user feedback on intranets is delivered or captured in a number of different ways, ranging from the formal to the informal.
Outside projects where feedback will be gathered as part of the design process, when intranets are in business-as-usual mode, feedback is gathered through:
- Informally at meetings and interactions
- In IT help desk calls
- Through site managers and content owners
- Through a dedicated or intranet team email account
- Via a feedback form on the intranet
- In discussion forums dedicated to intranet issues and support
- Via annual or regular user satisfaction surveys, or even through the main employee satisfaction surveys
- Via snap polls, perhaps on the intranet homepage
- And as we have seen, even through external social media like Twitter or sites like Glassdoor
You need process and structure
Despite all these avenues, most organisations fail to have a structured approach to actually acting on this feedback. There might be some emphasis on sorting out urgent individual issues, but the collective sentiment is rarely acted upon.
Not having a proper process for acting on feedback is dripping with risk. You can upset stakeholders and users, and miss an opportunity to engage with individuals and content owners, and overall improve your intranet.
Of course not every user is going to give you valuable feedback but this is even less likely to happen if users give you some and then see nothing happening as a result.
It is quite possible that all feedback can be dealt with by an individual as part of their role, but in larger organisations inevitably some sort of process is needed.
Here are a few thoughts on approaches which can help. Of course your ability to carry out some of these ideas will be influenced by how you capture feedback and also time and resourcing. Dealing with feedback can take time.
- Focus on one or two ways to give feedback on the intranet to avoid user confusion. The intranet-based form available from the page footer or header is a potential option.
- Collate and record all feedback in one place so it can be acted upon. This could be helpdesk software or a trusty spreadsheet.
- Make sure this place also records the actions and person responsible for that action.
- Speak to your IT Helpdesk and see if you can get any statistics or output from the intranet related queries that come in.
- Codify the feedback that comes in so you can derive statistics, even if the volume of feedback is small.
- Ensure content owners get the feedback which is relevant to them.
- Always report back any actions to the person who made the feedback. This is absolutely key.
- Celebrate success. Let your team and your stakeholders know when you get good feedback.
Overall getting your house in order when it comes to gathering and acting upon intranet feedback is well worth the effort. Not only does it mean you get to know about things which are and aren’t working, but you also engage with users. And that ultimately means a better intranet.
I once worked with an intranet team (they KNOW who they are) whose sole way of inviting feedback on their intranet was a big link at the top that said something like “REPORT A PROBLEM WITH THIS PAGE”. They were happy that this was sufficient for any sort of user feedback.
Here is a picture of Travis Bickle, placed without further comment:
And my friends at the unnamed organisation were the enlightened ones. When I ask some organisations whether they have a process for intranet feedback so say they don’t bother because they don’t receive much. They. Don’t. Receive. Much. Yeah, sure, because there is one tiny link that says feedback in the footer of the homepage.
On the other hand, you can come across like an over keen puppy indiscriminately slobbering over people. What do you think of this? Do you like that? Your colleagues then may think that a) You don’t know how to do your job and b) They have more important things to do with their job than tell you how to do yours.
Basically the essential part that most people miss about feedback is ‘conversation’. It is a two way street. You need to be approachable and once you have some feedback from someone, they need to know that you don’t file it in the bin. If you as a team are too remote or if you don’t have the ability to change anything why would someone bother. Concentrating on being receptive and on the ability to change and the feedback process becomes a lot more useful.