Gimme! Gimme! Gimme my intranet page!
You received a call, or an email, or someone stopped by your desk (neatly ignoring the submission form you have on your intranet), asking you to create them a page or team/project site. And, they don’t just ask for a page, they demand it! Disinterest may be an intranet manager’s biggest challenge, but over-enthusiastic demands run a close second.
Let’s not be too cynical; it’s great news that colleages see the intranet as important. You might also, for a brief moment, feel a small glimmer of hope that they really thought this through. In reality, your colleague (or, more likely, their manager) has decided they need a page and they need it NOW, but they don’t really know what they need it FOR. As the intranet manager it is your role to ask the hard questions; to challenge their request. But, how do you go about this without squashing their enthusiasm?
Did that sound like a typical scenario to you? Have you experienced this on numerous occasions? Sometimes the request is easy. Within two minutes you already know this page or site is needed on the intranet and should be added right away. Those are the no-brainers where everything just clicks and your content owner and you are on the same page.
But, what happens when a colleague comes to you and they have it all wrong? They want a page for the sake of a page and they really haven’t thought through the purpose or goals or how it fits into the overall strategy of the intranet. This is where you come in – you’re the intranet expert, and you can’t really expect many your colleagues to think this way. That’s your job. How do you start?
Rather than lecturing them on how far off the mark they are (because no one likes a smart-ass), begin the conversation by asking some questions. Here’s some questions the Intranetizen team put together to help start your conversation:
What has changed?
What event has happened, or is about to happen, that warrants this new content? Is it entirely new or related to (or replacing) something that already exists. Ask questions like:
- Why didn’t we have this page before?
- Is there an area on the intranet that is similar to this initiative/topic?
- Where have we published things like this in the past? Did that work?
Try to find out if anyone will ever read or use the content. Unread content is better unpublished. Does the content meet any user goals? Ask:
- Who is the primary audience?
- What business unit and/or region does this affect?
- Has anyone ever complained they can’t find this information? Is there evidence people are searching for it?
- What will this page allow people be able to that have haven’t been able to before?
What’s in it for the business?
Is there a business case? Does this content meet any business goals? Does it drive a desired behaviour? Ask:
- What is the purpose of the page/site?
- What information do you want to display?
- What is the call to action?
- Does this fit into the intranet vision and strategy? (your colleague may need your help on this)
Do you promise to love and care for this page?
Every new page on the intranet makes the rest of the intranet worse. More pages mean more clutter. The search engine has to struggle more and the navigation gets a little longer or more complex. If there’s a good reason to add something, make sure it doesn’t outstay its usefulness. Ask:
- Who is the business owner? Who is the content owner?
- Who will be managing the area after launch?
- When can we set an expiry date or archive date for this content?
By asking the above questions you are not discounting your colleague’s request, but evaluating the best course of action. You may want to scream back, ‘No, that is a stupid idea!’ but you can’t. Or, we wouldn’t suggest it. Put the pressure back onto your colleague. If they push back and aren’t willing to answer your questions, then they really don’t need that page. If they do take the time to answer the questions and debate them with you, then you know with a bit of work you can create an area on the intranet that achieves what your colleague wants and what your end users need.
Have you tried this approach before? Is there a question we haven’t asked? Let us know!