
An intranet performance review is something that you can find on every intranet manager’s roadmap – and if you can’t, then there’s something wrong with the map. Reviewing content, usage levels, effectiveness and other key factors on a regular basis is absolutely vital to ensuring the long-term viability of any intranet installation.
So, cutting to the chase, how should you go about reviewing intranet performance? Well, there’s no single answer to that question, but there is a wealth of advice available on the subject, with most of it just a quick Google away.
There should be no doubting the validity of a theoretical perspective on the issue, for those people in the front line of intranet deployment – intranet managers and internal communications professionals – there is real value in obtaining practical advice from the people responsible for reviewing intranet performance on live, real-world installations.
We turned to Twitter once more to find out more about performance reviews: we’re always interested to hear what members of the online intranet community have to say, so we looked back at some conversations we had that related to performance reviews, and found some useful guidance on different aspects of the review process.
Looking back at our tweets, the first observation that we made was that there was no fixed format to a performance review. For some people, it was a major annual event that assessed the previous twelve months’ progress using a specific intranet installation. For others, it seemed that performance review was an ongoing process that meant staying in regular contact with key individuals and/or intranet teams to gauge progress on an ongoing basis, while for other still it was more a mix of the two.
There are obviously benefits to both the one-off annual basis and the regular approach: annual reviews allow you to build up a large base of system data, giving you an information resource that you can use to map overall usage trends, analyse adoption for new applications or functionality, monitor popularity levels for different types of content published at different times, and generally develop a high-level, strategically-focused approach.
On the other hand, regular reviews allow you to stay in touch with user requirements as they happen, which produces a more immediate and reactive way to ensure intranet usage by taking immediate steps to resolve any issues. As a manager or comms professional, this approach has the benefit of showing intranet users that you are always in touch with what they say and that you have an open and organic approach to the management process.
Of course, frequency of review is a key factor here: taking too long to implement a review runs the risk of your intranet being seen as immovable, unchanging and unfriendly to its users. We really wouldn’t recommend much longer than a year at most between reviews. At the other extreme, scheduling reviews on too regular a basis stops reviews being reviews at all – they start to blur uncomfortably into the area of technical support. If the review doesn’t have to be a monolithic event, you can achieve effect and keep content relevant by holding regular, ‘bite-size’ reviews of important elements like intranet content along with the strategic side of things – but not too often.
Ideally, then, there is a balance between the two approaches, where users are able to obtain quick responses to their everyday needs, while intranet managers are able to analyse and take action on a strategic level by looking at long-term and the emerging trends from an analytical perspective.
So, then to the tweets and the practical advice itself: @markmorrell is the intranet manager for BT, and a very well-respected member of the intranet community on Twitter; anyone who values sound, practical advice on intranet management – as well as useful snapshots of the daily life of an intranet manager – should be a regular reader of his blog at http://markmorrell.wordpress.com/. We’re one of his followers on Twitter, and earlier this year while we were thinking about the intranet review process, we noticed Mark tweeted that he had received ‘Over 800 responses to intranet survey in first 24 hours’. We were instantly interested, with the receipt of such a high number of responses indicating a large user base and therefore a sizeable review process, and the timescale indicating that there could be more responses to come.
We asked Mark whether the focus of his survey was intranet management per se, and he replied that ‘User satisfaction and views with intranet overall, key sites, applications, etc.’ was his focus – a wide-ranging remit for the review, and one that indicated to us that the review would be taking place on a strategic level.
Citing the impressive response rate we asked whether he conducted the survey via the intranet itself, and enquired as to his methodology. Mark told us that ‘GfK NOP (excellent agency) send an email with link to online questionnaire. Can track who has/hasn’t completed and guarantee anonymity and allow completion in chunks rather than just 1 go.’
We thought that the section-by-section, save-as-you-go approach was an excellent idea, giving users space to breathe by allowing them to dip in and out of the survey, providing a good strategic method for longer surveys. Of course, the use of an outside agency to provide the survey takes the responses out of the intranet zone and de-links them from any intranet user profiles – we asked whether this was to allow anonymous responses, and how highly Mark rated anonymity as part of the process.
Mark replied that he ’would like anonymity not to be an issue for any organisation’s survey because respondents are encouraged to be honest.’ It is an interesting point to ponder – is anonymity the best way to ensure honest responses? It certainly seems to work for Mark, and we replied that this could vary depending on a company’s management structure and style. Perhaps anonymity is the right way to go for questionnaires across your entire end-user base, with accountability more appropriate for those directly involved in intranet teams or project discussions.
Moving away from the finer points of the survey’s implementation, we asked whether Mark found that such surveys extend intranet lifecycles in general; he (not unreasonably) asked us to clarify the term ‘intranet lifecycles’ as it could mean several things. We replied that we ‘assumed it was a satisfaction survey conducted pre-intranet revamp for guidance on enhancements to prolong the intranet’s lifespan, though it could easily have been to produce a new iteration or any other purpose’. Using two tweets, of course, given the character count.
Mark replied that ‘it could turn out to be that! It is a check taken each year on user satisfaction and where any improvements needed’, indicating that his review is a high-level survey designed to focus on the strategic side. Furthermore, we can see that this is an example of an intranet review being conducted on an annual basis with significant success; whether there are more regular reviews in during the year is not specified, but Mark seems to be gaining a great response rate for a genuinely in-depth review model, using anonymised user surveys that include saveable sections that allow users to come back. This seems like a perfect fit for an intranet with a large user base, and takes the respondents themselves, the scope of the review and the size of the user base into account in its model and delivery. Whether the survey represents the whole review or a preliminary stage, this is a good benchmark for a successful review on a strategic level.
A differing approach was offered by one of our other Twitter contacts when addressing the idea of a content review. Content is the lifeblood of any intranet, and implementing a review process to ensuring that content production is at its optimum should be just as important as strategic analysis at a management level.
A few months back, @ChristySeason – who regular readers should remember from her extremely valuable input in defining the role of an Intranet Manager – tweeted about how to engage content authors, mentioning that she chairs bi-annual Best Practice sessions where everyone comes together to audit each other’s separate sites on her intranet.
We noticed her tweet, and decided to ask Christy how her site managers react to others auditing their content, and whether the review process itself was conducted on an open basis or in closed groups. Christy tweeted that ‘We pull everyone into a computer lab – swap sites – & everyone gets a check list 4 guidance & we spend an afternoon auditing.’
This demonstrates a very user-focused approach. Rather than having a review team come in from outside of the user loop, Christy employs an organic approach that draws on the very people who produce her intranet’s content, creating a community that regularly reviews its own output on a collective basis – a great way to build trust and foster team spirit among those responsible for making the intranet a success.
We were interested to find out more about the format, suggesting that perhaps the prospect of peer review motivates users to write more frequently & make more of their content. Christy confirmed as much, telling us that ‘everyone appreciates having another set of eyes reviewing their sites & catching things they missed + new feedback’. Clearly, Christy’s management and review method is very well suited to the requirements and setup of her intranet team; keeping your key users onside is of great benefit to any intranet manager or strategist.
Christy’s stated six-month content review timeframe sits right in the middle of the review frequency range, providing a bridge between the annual, strategic approach and the everyday user engagement method. By creating ‘go-to’ teams that are responsible for maintaining different intranet areas, she has created a hierarchy of responsibility that is shared across her user base to encourage accountability, creating key user groups on which she can rely when it comes to conducting regular reviews.
Christy’s approach is based on breaking her user base down, and engaging her end users for a compare-and-contrast, workshop-style session on a bi-annual basis. From her comments on user acceptance, the arrangement seems to go down very well with her user base, and this level of acceptance can only help to ensure a consistently high level of content for her intranet while fostering goodwill towards the intranet and its management group within her end-user base. This is another extremely useful reference point for those investigating the intranet review process.
So, now we know what works for two of the people who manage large-scale intranet installations on a day-to-day basis, and hopefully this has been an interesting analysis of two methods that intranet professionals use within their review processes.
When we mentioned the value of a theoretical perspective earlier, though, we neglected to provide an example of such a perspective. So, to finish, it definitely seems worth pointing our readers towards an article that addresses the motivation behind intranet performance reviews with real breadth and depth: this blog post from @seanrnicholson provides real insight into what makes performance reviews so important – engaging and building trust with your intranet users, which is something that Christy and Mark both touched on in their tweets.
Sean is another of our favourite Twitter contacts within the intranet community, and he’s another person you might remember from our ‘So You Think You’re An Intranet Manager?’ post last month: his blog at www.intranetexperience.com is a regular source of valuable guidance, and this post is a good example of that. Fostering and developing trust and value in your intranet is at least a significant part of the purpose of your performance review, if not the entire purpose itself, and Sean dispenses some great advice on how to avoid some of the issues that users have.
The post delivers some practical advice grounded in the real world, as well as a good theoretical piece, so it represents a good piece of further reading after this post. In fact, it was this particular blog post that inspired us to write this piece, so please do click through and have a read – it’s well worth it, and we thought it would be only polite to give him the credit for inspiring us.
Before you go, though, if you have any other great advice or links on the intranet review process then please pop what you’ve got in our comment box below – we’d love to hear what you think.
Check back soon for the next Intranet Ideas blog post; in the meantime, why not visit us and see what we do at www.orchidsoft.com.