Showing posts with label intranets. Show all posts
Showing posts with label intranets. Show all posts

Thursday, 27 December 2007

Intranets: the tech-head perspective

This interesting post over at 37signals is effectively the company polling its universe of customers and friends over possibilities in the intranet software market. That's an interesting communications exercise in itself, but I link to it because it suggests (in line with a previous post here) that the concept of "an intranet" is not in good shape.

What comes out of the "tech-head" perspective is that no-one has come out with an earth-shaking software product as yet, but Microsoft Sharepoint seems to be edging into an industry lead.

Sharepoint's special value is in facilitating collaboration over documents (through the integration with MS Office apps.) It also includes things like RSS and blogs.

To me, the lessons for IC types are:

1) People will choose and stick with communication channels that make their life easier. There's a lot of talk about the possibilities around "new social media" in IC, but that will inevitably involve technology choices. The right medium is one that people will get some value (for them) out of using.

2) Point One highlights the potential for IC professionals to gain extra traction if they work to understand and influence the information management policies in their organisations. People are happy to find that Sharepoint has blogs and many become enthusiastic users of them, but the system lives or dies by it's usefulness in "information management" rather than "internal communication" per se. (That might not be a fun fact, but it is a financial reality at a lot of companies.) As such, it's important to make sure that these two agendas complement each other rather than conflict. That means both an interest in the widgets IT is buying to solve intranet problems and a wider interest in the connections between "information management" and "internal communication overall.

 

Monday, 10 December 2007

Intranets in trouble

 

Over at a shel of my former self, Shel Holtz has a post called Intranets in Trouble which references a study by the Irish Computer Society.

As someone who concentrates on the people side of communication, I tend to be the one asking sceptical questions about technological solutions, but even so, the key results are rather disappointing:

  • Nearly half say they don’t use the intranet to support their everyday work
  • Nearly one in three say the intranet does not help with daily work
  • Half find their intranets’ search engines to be ineffective and 80% think both navigation and search need to be improved
  • 35% of respondents cannot access the information they need on their company intranet
  • Fixing these problems won't solve all your communication problems, but if a third of workers can't get the information they need through the company intranet, then that's a serious performance issue.

    To me, the results highlight a couple of things:

    1) Too often, "the intranet" is purchased in the manner of a telephone system. No-one is given the responsibility (or indeed the resources) to ensure that existing content is kept up to date and that new information is chased down and documented online.

    2) One oddity of the internet is that it puts cutting edge tools in our hands for free. As a result, people develop a reliance on tools like Google for navigating complex information landscapes. If you have a lot of information on your intranet, you either need to invest in replicating these tools or if you have a bespoke tool, you have to train people to use it.

    Failing to address these issues simply means you won't get much out of your initial investment in the intranet. Of course, some people don't see the business value in better information and communication. It's true that if your main business is an automated widget production facility, the intranet might not be all that important. If your business relies on people working with information, collaborating with each other and keeping track of complex projects, then the quality of information exchange may be the difference between success and failure.