The "catalyst" role is critical to Open Projects Net and an essential building block of channels. There is currently no formal training program for catalysts, but such a program will be formulated as OPN grows. No one is required to be a catalyst, but the users who perform this role ensure the smooth and efficient functioning of the network.

IRC does not automatically produce a stable culture of cooperative effort. Even in cases where cooperation is intended, misunderstandings and personality incompatibilities can result in an extremely chaotic and hostile environment. Catalysts help prevent and resolve misunderstanding, calm the waters when users have difficulties dealing with each other and provide examples of constructive behavior in environments where such behavior might not otherwise be the norm.

Catalysts try to resolve problems, not through the use of authority and special privilege, but by fostering consensus, gently nudging participants in the direction of more appropriate behavior and by generally reducing the level of confrontation rather than confronting users with problems.

Channel and network administrators may be catalysts and, indeed, are encouraged to take on that role. Channels which recognize the importance of the catalyst role will foster more effective coordination of effort. An important characteristic of successful catalysts is the infrequency with which they wear authority or invoke special privilege.

OPN staffers and sponsors are advised that an understanding and appreciation of the role of catalyst is essential to understanding the nature and intended purpose of Open Projects Net. As OPN grows in size, formal training in the catalyst role will be provided.

An effective catalyst is:

• Relaxed. To keep things calm, you yourself must be calm. Learn the skills of staying genuinely relaxed. Know your limitations; when you can't handle a problem situation calmly, get calmer heads involved.
  
  
• Unobtrusive. It's not necessary to invoke authority to help solve a problem, and far better if you don't. Look for an opportunity to nudge the situation into a more productive track. Don't critique someone if a quiet change of subject will produce the desired effect.
  
  
• Realistic. Accept the personalities of your users and concentrate on problem resolution. Don't expect people to suddenly change their personalities to make problem resolution easier.
  
  
• Careful. Everything you say will be interpreted by the users with whom you interact. Consider how your remarks will be interpreted before you make them. Make sure the message you convey is the one you intend.
  
  
• Attentive. Understand the situation you have walked into before you act. Question your assumptions. Look for signs you have misinterpreted the situation, in order to avoid causing difficulties for a user who did not create the problem.
  
  
• Minimalist. Don't do more than you need to in order to resolve a problem. A problem scene is often the wrong time and place to set policy. Concentrate on the resolution, and on collecting information you can think about later.
  
  
• Courteous. Even under time pressure, courtesy costs little and impresses people a lot. It's not about whether working with the person is easy or difficult; it's about setting the right tone.
  
  
• Cooperative. Look for opportunities to get people involved in the resolution of their own and others' problems.
  
  
• Someone with an internal locus of control. Catalysts concentrate on solving problems, not bestowing blame. Treat the situation as the problem, accept the users for who they are and try to figure out how best to help resolve the difficulty.
  
  
• A user. Remember that you're not in charge. Everybody runs their own little corner of the world. Let them do the job they're capable of. Just help the process along as unobtrusively as possible. Other catalysts are users as well, and nobody is perfect. We're all just here to do our best to keep things running well.
  
  

Copyright © 2001-2002 Open Projects Network.
Current network date and approximate time: Friday, 14-Jun-2002 23:44:02 GMT.
.