The top 3 dimensions to prioritise intranet developments. Benefits, Reach and Influence.
If you are anything like me you have an ongoing long list of people in your organisation who want something on the intranet. Whether it is a new workflow or some new content there is a never ending stream of demand to develop. This is a good thing, but your time and resources are limited so how do you make decisions about what to do first?
I use 3 simple tests when discussing new opportunities. First, does the development have a direct benefit to the bottom line - and to support this are all of the right people (finance, procurement, senior management) in support of the cost savings that will be achieved. Are the cost savings built into local business plans and are they clearly measurable. If you can't pass this test move on to the next one.
Secondly, does the development significantly increase reach of your intranet. If you are like me you have a strategic goal to weave the intranet into a way of working around your organisation. To achieve this you need a critical mass of users and must-have features. Is this new feature going to extend the intranet to a new set of users (who are not currently using it) or drive increased repeat usage in a community that are already using your intranet. This one is a bit harder to judge than the previous one as every stakeholder who is looking for a new feature will usually be enthusiastic about the likelihood of every person in the company using their page on a regular basis. However, this test should be obvious - if everyone has to book their leave on the intranet and there is no paper alternative then it will obviously increase traffic for the affected groups.
Lastly, if the initiative doesn't pass the previous two tests is it going to significantly increase your influence. In a situation where you have been working to co-operate with a stakeholder for some time it does not make sense to turn them down when an opportunity finally arises. Equally if the CEO calls you and asks for some content or online process it makes equally little sense to refuse. Importantly I would use these opportunities to make a trade. If you have to agree to some vanity publishing against your judgement then make sure you negotiate time to come and explain intranet strategy and benefits to the people who are asking. There are all sorts of things that you can get in return if someone wants something.
What do you use to make priority calls?
Subscribe to:
Post Comments (Atom)
Posts
I would add, that a good intranet strategy should provide the answer. From my point of view, it should even be the first test to be done. If a request isn't in line with your intranet strategy and doesn't bring you closer to the agreed upon goals (even via a detour), then 'No' should be the answer (naturally exceptions prove the rule...).
ReplyDeleteOf course, the strategy has to be very practise focussed in order to help make such a decision. The nebulous mission statements one usually encounters wont go a long way here... ;-)
Totally agree, I have a feeling that there are quite a few intranets out there with fluffy mission statements. If you are not specific about your goals how are you going to know what to do next?
ReplyDeleteThanks for your comment.