- Whether to mention a pregnancy in a job interview
- A possible meeting protocol
- What are an end-user's responsibilities?
- Another take on opening PCs, or not
- Getting some process going
- Selling a more open environment to management
- Running an effective meeting
- Licensing rules for virtual machines
- The ROI of metrics
- Legal challenges to virtual machines
July 12, 2006 | Comments: (0)
Comparing different interaction forums
Dear Bob ...I have run into an interesting situation that probably is fairly common.
Actually, what makes it interesting for me is not the situation itself, but rather a possible opportunity to learn something.
I was involved in a discussion through a Yahoo discussion group in which the topic was the suitability of using a wiki to maintain a business data dictionary. One fairly common theme among the nine participants was freeing people up from the constraints of bureaucracy. One thing notably absent from the discussion was a comparison of the merits of various tools and governance methods, in spite of my effort to introduce those topics into the discussion. I also mentioned at least two requirements I am facing that I believe can't be addressed by using a wiki. Not one of the other participants addressed either of these concerns, either to agree or to disagree. It seems to me that these people were so focused on their particular agenda that other concerns didn't even register.
Now, here is what I am asking you.
Are you aware of any research that anybody has done to determine in an objective fashion how online discussion groups in general deal with issues that individuals raise, and how this compares with other approaches to seeking assistance, such as face-to-face informal meetings, facilitated meetings, etc? One issue is how likely it is that a discussion might be hijacked by someone with an ideological point of view.
Another issue is what kinds of people tend to take an active role in maintaining publicly accessible documents such as are found in Wikipedia.
How likely is it that the type of people who take it upon themselves to contribute to such repositories will also be the type of people who would introduce an ideological point of view? This could vary according to subject matter. More controversial subjects would likely attract more ideologues.
What I am really after is a way to assess whether the experience I described above is the exception or the rule. Opinion based on first-hand experience is a little helpful, but I would place much more value on the results of formal research by sociologists, cultural anthropologists, psychologists, and other qualified people.
Are you aware of any such research?
- Archie
Archie ...
I don't know of any formal research, which doesn't mean it's nonexistent, merely that I haven't run across it. Much of the comparison is straightforward and doesn't require research, though. Just list the different media (face-to-face meetings, telephone conversations, on-line chat and so on) as rows in a matrix; list attributes to be considered as columns (synchronous vs asynchronous; sequential vs parallel "posting,"; impact of personality; potential for one person to dominate; potential for a group to invade and hijack ... whatever is important to the analysis). Then rate the attributes for each of the media. It becomes pretty easy to figure out where each is strong and each is challenged.
Just remember to be sufficiently fine-grained. There are open wikis and edited ones, for example; they'll have different characteristics in some of the attributes.
I'll post this to Advice Line; keep an eye on the Comments section to see if any of those posting know of the kind of study you're looking for.
As you do, take note of those posting. To date, while plenty of ideologues post, none have hijacked the blog, for the simple reason that there's no way of hijacking a blog. You can post whatever comment you like; that doesn't interfere with anyone else's ability.
What can happen to on-line discussion forums of all kinds is that a group of "loudmouths" (print version) flood them with postings that can range from pointless to annoying to offensive. Especially with an internal business forum, that's easily dealt with: Track down the offenders and say, "Don't do that anymore."
Also, you'd have the same control I do with the Comments to my blog, which is to not approve them. In my case I only delete the increasing tide of spam and commercial comments, and one or two that are clearly irrelevant and offensive. In yours, you could impose whatever guidelines seem most appropriate to the situation.
I'm less familiar with wikis. I understand that the technology does provide for editorial control when that's desirable, which is another way of referring to governance.
Just my opinion, which I'm forming soley from your account of events, so I'm doing a lot of inferring and imagining: What you experienced wasn't the influence of ideologues. It was the influence of people who had no interest in the topics you were raising. They were excited about the potential of the medium to free people from the constraints of bureaucracy. You were raising the importance of governance. But one person's governance is another person's bureaucracy. To me, it's unsurprising that none of the participants had a lot of interest in discussing it.
Again, I know of no studies. My guess is that people who contribute to forums like Wikipedia are enthusiasts - amateurs and professionals who love a particular field and want to share their knowledge. Many enthusiasts in any field also have strongly held opinions about it. If you're on the other side of those issues, you'll consider them to be ideologues.
And most likely, they'll consider you to be an ideologue for disagreeing with them.
- Bob
Posted by Bob Lewis on July 12, 2006 04:58 AM
RATE THIS ARTICLE:
-

- COMMENTS
This topic reminds me of many technical and sales discussions, meetings, etc in my past. The behavior is NOT exclusive to blogs or on-line forums. It's equally annoying and counter-productive.
Remember the mid '90s, when Microsoft was getting up a head of steam in the network server business? I was a Novell guy through and through. Many a client of mine, when considering upgrades or replacments, was under intense pressure to replace that NetWare 3 or 4 server with an NT server. No matter the technical merits as a file-and-print server, many times (most actually) they gave in to either management of the sheer weight of opinion and bought Windows. Ignoring the reality back then that for a simple file-and-print server, Novell ate Microsoft's breakfast and lunch, Novell lost share bigtime.
Many of these situations included programming staff, non-IT management, and sometimes other consultants from other sales firms. Of course, everyone comes to the table with their point of view. Programmers working in Microsoft like the server interface to be the same as their IDE (or lack of one), or desktop. Management reads the magazine ads (no offense to InfoWorld or others intended) and logically asks why not buy such popular stuff? And of course, the consultants that learned Microsoft have an interest in selling their product also. Like many decisions, these did not always end in choosing the technically and fiscally 'best choice'.
In a discussion of a database server for an application, this discussion is of course moot. You buy what is needed, and if it's SQL Server or Oracle or PostgreSQL or Advantage or whatever, that usually drove the platform.
But yes, to paraphrase an Oriental proverb, to a Wiki, everything looks like a Wiki to be made.
Sometimes, I know I said 'Novell' because I had that as my bias. But more often, a sound choice was ignored in favor of a popular choice.
It sure happens. Even on line.
rick
Posted by: Rick at July 12, 2006 05:40 PMActually this whole thing is old, going back to groupware, CSCW and the 'virtual community'. There have been TONS of studies, but the particular questions are slippery.
One classic piece of web-work is the gallery of 'flame warriors' - you may find some familiar personalities depicted.
http://redwing.hutman.net/%7Emreed/index.htm
more generic is the old groupware subject...
http://en.wikipedia.org/wiki/CSCW
Posted by: chuck at July 13, 2006 10:54 AMWhile it may be that the other participants had no interest in the topic, there may also be some cognitive dissonance in play here. Someone enamored of the technology will tend to ignore potential downsides because they conflict with opinions backed by little more than emotion or partisanship.
This is where we get "religious wars" over technology. Few if any of the participants are ever wholly rational on such issues, though they may believe otherwise! If a participant isn't aware of their own cognitive dissonance, they can ignore an amazing amount of evidence counter to positions they hold.
There is nothing evil or boneheaded about this: cognitive dissonance seems to be one of the mind's defence mechanisms against too many competing ideas. Once a suitable believe system is assembled, the mind tries to maintain that belief system. It takes more than simple rational argument to break the mind out of a cognitive dissonance situation. You either have to be aware that it's happening, or be presented with such overwhelming evidence that you finally break down your internal walls.
The tricky bit is that if you think your opponent is experiencing cognitive dissonance, you should be darn sure it's not actually *you* who is trying to fend off a better idea to protect your own belief system!
The podcast Intellectual Icebergs covered this topic in show #5, in this very context. See:
http://www.digitalpodcast.com/detail.php?id=2272
Posted by: Warren Young at July 18, 2006 10:15 AMThank you all for your thoughtful responses. I didn't make it clear in my original message, but the topics I was trying to introduce into the conversation were not about governance. They were about specific functionality that my user community (both business and technical) say they need. The wiki approach doesn't provide a non-labor-intensive way to integrate business metadata and technical metadata. No matter how "free", "democratic", or whatever, if the process requires too much work, people won't do it. Also, wikis are searchable, but not queryable, so I would have no way of generating quality statistics. These are issues that no one in the discussion group even indicated that they heard. Their responses to me were about governance, not about functional requirements. As has been pointed out, these people certainly have a right not to be interested in that. However, if we accept that form should follow function, then it seems to me that governance should follow functional requirements. I'm interested in addressing my user community's stated requirements.
Posted by: Archie at July 24, 2006 05:33 AM|
Three books. Three ways to change the world, your life, or at least Bob Lewis' bank account. Leading IT: The Toughest Job in the World distills the world of IT leadership into eight learnable skills and gives you concrete, practical techniques for each one of them. Bare Bones Project Management: What you can't not do makes project management manageable, even for first-time project managers with no formal training in the discipline. ManagementSpeak: What managers say/What they mean … well, it won't help your career, and won't make you a better manager. Mostly, it will make you chuckle, guffaw, and maybe even chortle. Make friends - it's the perfect gift for anyone who has ever suffered through one of those meetings. Order your copies today! |
TOP STORIES
HP buys EDS for $13.9 billionCorporate software spending slows
MS targets smartphone market
SOA Software buys LogicLibrary
Phishers scamming IRS rebates
Sun to clarify JavaFX plan
MS' dev tool service packs
Developers' role shifting
MS: SP3 reboots OEMs' fault
Apple: iPhone out of stock
ADDITIONAL RESOURCES

- Virtualization: A Step by Step Approach to Success
- Dialing up Agility with Business Transformation
- 5 Things You Need to Know About Storage Virtualization

- Is your smaller organization ready for High Availability?
- Is system maintenance doing more harm than good?
- Virtual Test Lab Automation: Manage development infrastructure





