Comments on: Fear of wikis and blogs at a corporate level

Question: Fear of wikis and blogs at a corporate level

vincentm — Tue, 30 Aug 2005 05:16:31 -0800

How do you explain the reluctance (hesitation) for developing blogs and wikis (and social softwares in general) on the big companies' intranets (if you have succeeded so far please contact me) ?

By: socratic

socratic — Tue, 30 Aug 2005 05:30:08 -0800

The desire to compartmentalize information to protect the advantage of people who know key information? Lack of understanding about what blogs and wikis are and what they can contribute to the bottom line? I have no idea if this unwillingness to use the tools is a serious problem, but these would be two of the things I'd guess would cause hesitation to adopt them.

By: malevolent

malevolent — Tue, 30 Aug 2005 05:48:57 -0800

A lot of people worry about employees 'wasting' time on such things. Their misguided work ethic leads them to frown upon anything that isn't directly related to immediate productivity.

By: vincentm

vincentm — Tue, 30 Aug 2005 06:13:56 -0800

E-mail already represents a huge amount of wasted time (funny powerpoints and porn movies...). But smart use can lead to a better productivity (I think).

By: mkultra

mkultra — Tue, 30 Aug 2005 07:36:51 -0800

Liability. Blogs and Wikis, by their nature, have zero centralized control. Big companies need to protect themselves from stupid/incorrect/law-breaking/contract-breaking things their employees say.

For example, what do you do when...

... a disgruntled employee starts mouthing off?
... someone accidentally leaks some sensitive news?
... someone, at a senior level, starts contradicting corporate policy?
... someone starts talking about "the hot new girl upstairs in art"?

By: josh

josh — Tue, 30 Aug 2005 07:39:32 -0800

It's because the internet is already a huge source of time-wastage in offices everywhere. It's huge and out-of-control. In every company I've ever worked for, the management hasn't known what to believe: the euphoric, utopian, unrealistic conception of the internet and its productivity potential that they get from geek employees and the media, or the reality of the internet in actual offices: employees checking email, playing Snood and poker, and reading blogs and newspapers from 910 and 45 every day.

Obviously there can be benefits; but I think it's self-evident why a manager would be very reluctant to actually encourage employees to, for example, post to a blog. I don't think it has to do with some kind of stodgy control-freak Luddism. It's basically because the internet and email have created many headaches and productivity slow-downs.

In my own experience, the best way is to focus on process. For example, if you want to have a corporate wiki to share resources and knowledge, new content needs to be routed through an editor. Articles need to be rated and comments moderated or filtered outright. Etc.

By: whatnot

whatnot — Tue, 30 Aug 2005 07:45:28 -0800

I work at a .edu, and some of the resistance here is based on the perceived "faddishness" of blogs and wikis and lack of tech savvy (or willingness to learn new things) among many of our staff. Most of my coworkers are also very social people and prefer "face time" over any other form of communication.

I don't agree with either, but then if it were up to me, everyone would have IM/Rendezvous on for at least part of the day, and office communication would take place on a blog w/ comments, and collaboration on projects and reports would take place on wikis.

By: josh

josh — Tue, 30 Aug 2005 07:55:45 -0800

It's also, I'll add, because writing skills are very poor in many workplaces. Methods of communication and collaboration that depend on writing--email, wikis, blogs--can seem straightforward and easy to one person, and onerous and time-consuming to another. Some--perhaps many--people express themselves better in person than in writing; these people will understandably resist the wikification of the workplace.

It can be a challenge to implement a wiki, for example, if half of your office has no interest in writing comments and doesn't look forward to being represented by their written output. These people do not want to be 'left out.'

By: vincentm

vincentm — Tue, 30 Aug 2005 08:07:48 -0800

> Josh. I mainly agree with you but there is a great amount of knowledge that is already put down on MS Word documents, unshared among teams. These knowledge (information) producers could, in my humble opinion, switch easily from Word to a wikiwyg editor. The only big change would be that the information (if valuable outside the present team) would not stay in the sub-sub-sub folder of a hard drive or an email client but could be propagated (pulled or pushed via RSS) to "unpredicted" readers.

I hope my english is not to bad...

By: mischief

mischief — Tue, 30 Aug 2005 10:03:22 -0800

For wikis, Sarbanes-Oxley may be partly responsible. In today's regulatory climate, businesses are examining every facet of computer usage, and accountability must not only be established, but documented and possibly reported.

As for blogging, time spent writing is time not spent doing other tasks, and good writing eats up a lot of time. Unless the position calls for writing, the return on that investment is very difficult to determine.

By: mischief

mischief — Tue, 30 Aug 2005 10:06:56 -0800

In this post-"Sarbanes/Oxley" business age, accountability must not only be documented, but possibly reported as well.

By: mischief

mischief — Tue, 30 Aug 2005 10:07:35 -0800

Hmm, I thought that first comment had disappeared...

By: advil

advil — Tue, 30 Aug 2005 14:26:50 -0800

employees checking email, playing Snood and poker

er, you don't need the internet to play snood (or solitaire, or the other things people did on computers in offices before the internet came along).

On topic, I have implemented a wiki for internal documentation in a research group I used to work in. It worked reasonably well, but the main problem was that no one wanted to actually add to it or change it. Wikis work best if everyone is using them, even if just to fix typos/small errors etc, but no one wanted to do that. One coworker of mine did pick it up and is probably still using it. Even if only a few people did modify it, though, it still was tremendously useful for documentation. But I'd guess the problem with wikis is that most people don't understand how they work enough to effectively make use of them.

By: smackfu

smackfu — Tue, 30 Aug 2005 16:23:48 -0800

We have blogs at work. No one uses them, me included. What am I going to write about? Most non-work blogs are just bitching and web links. Well, I'm not going to bitch about work stuff that just creates a paper trail that can come back to bite you. And I'm not going to link to web stuff, because why would I do that on a work blog?

And at the most base level, if I actually talk about what I'm working on, I run into that compartmentalization thing. Not everyone who has intranet access should know our next product or our plans or our problems. Our intranet web access is basically assumed to be public, in a confidentiality sense, and I would have to respect that. What if our competitors got access?

By: raster

raster — Wed, 31 Aug 2005 10:07:59 -0800

I started using a wiki at work for documentation and as a knowledge base for the applications we support. I'd say I was the only user for maybe a year or so. I figured if I was the only one who found it useful it was still worth it, because it was easy for me to find any docs I needed. I did end up pointing others in my group to it and some of them found it useful, and even contribute to it now.

As for the liability part of it, use software that forces people to log in (I know that is somewhat anti-wiki spirit, but ya gotta do what ya gotta do.)

As for time-wasting, years ago people misused the phones and copy machines, so being a responsible employee is not a new concept in the age of the internets...

By: jaimystery

jaimystery — Wed, 31 Aug 2005 10:28:02 -0800

I'm actually in the process of convincing MGT here at a small manufacturer to use wiki software. There are so many details to our processes that can and do change on a daily basis so wiki would be perfect to track the changes, inform the work groups & store a history.

I've got a start on getting the basic info in wiki form and I've shown off how easy it is to change & update to a couple of bigwigs but so far, I haven't had much luck getting MGT to see *why* we need this and how helpful it could be. I haven't given up and even if the company doesn't adopt it, I still find it a very useful tool just for myself (since my job is to be the gatekeeper of this info)