Thoughts on Enterprise Social Media Protocols, Pt. 2

Star status is important to some and not to others. Knowledge that they've been part of the end product sometimes carries its own limelight. To cut the negative side of competitiveness, it's important to acknowledge the more significant contributions of certain members of the team. However, the leader also needs to recognize how the rest of the team contributed to reaching that plateau.

Secretiveness among members needs to be discouraged. If there's an offsite meeting or finding, the results need to be shared with those who could not be present. It's such bad form to have suspicion coloring what's done. It leads to mistrust and eventual exits that create delays in the project while the replacements are hired. And the project will then have to absorb at least some of the replacement costs of search, intake, training, and returning to the point where the team was before the loss of manpower.

Make certain systems work. If there's a malfunction, the basis for it needs to be discovered and disclosed so that it won't happen again and so that successors don't have to deal with it. The basis for the malfunction, once discovered, needs to be revealed so it can be avoided and personnel can feel as though their efforts are subject to being thwarted (i.e., a major waste of time).

If someone on the team is promised feedback, more information, asked to attend a meeting, they need to receive what they've committed to. Make it on time, or as close to on time as possible. They may be sitting on something that requires that bit of information; delay causes their part to either not be delivered or delivered late. Coming back to the team member for a meeting that's before the appointed time is the same as telling them their schedule has no value and that you feel they're simply sitting around with nothing to do and waiting for your precious presence. Don't come off as smug and self important.

Additionally, the team member may have quite a bit on their plate. Putting the meeting (whether in person, by phone or Skype, or some other mode) on their calendar and clearing out a point when they can give you their undivided attention allows them to keep their workflow moving and timely. A spontaneous change because one has jumped the gun or suddenly has an open slot in the day is quite simply selfish. Other priorities then get shifted to a different situation. Progress is thrown off to the point of having to be rescheduled to another day or may even be lost because there simply is no longer any time for the exercise. Keep appointments. If it can't be done and you realize it, reschedule for another time that is mutually convenient.

Now that we're in the 21st Century, people seem to forget some of the Web 1.0 netiquette we used to practice. There used to be these cute little abbreviations and initials that gave us clues, initials such as "afk" which stood for "away from keyboard" (a tactful way of saying I need to get something, put out the fire, go to the bathroom, etc.) and "brb" which stood for "be right back." Both of those let us know that the person on the other end was no longer available for a short duration.

Unfortunately, we've lost touch with those practices. Now people will walk away from the computer and have a meal, go visit with someone in another building, have a conversation with someone else in person for 30 - 60 minutes. Respect your team mates and their time. Let them know when you're stepping away. Let them know when the absence will be protracted. You're more apt to get their future cooperation when they're shown that they and their time are valued.

Thoughts on Enterprise Social Media Protocols, Pt. 1

Enterprise Social Media relates to shared information from one department manager to the rest of their personnel as well as from one department to another (or several), and then from the CxO office to the rest of the enterprise. That means reaching out to all of the teams, whether in the 2-3 person business as well as the global enterprise with thousands of employees.

Because the reach is so vast, and the message can be distributed so quickly, great care needs to be taken that people who are hired appreciate and respect the sensitivity of information that is shared. Team members need to keep project details and findings within their team until they are told it is ready for distribution. Even then, their leader needs to define the breadth of the distribution.

Corporate culture with regard to feedback and results of work can be playful on occasion just to keep things fresh and not oppressive (or boring and tedious). However, the jocular moments need to be defined as such because a text message or email doesn't contain voice inflections (unless they're composed on a voice synthesizer) and not everyone from the same country, let alone the same region, understands some things that are humor. But I digress.

Team members need to respect one another in every way. Likewise they need to be imbued with the power to build the results of what they do by being able to offer a different perspective or even object to something that's been put on the table. But they also need to take responsibility for those positions by offering the basis for the position. When points of differences are defined, it's easier to understand where the idea won't work in a particular situation but may be one of the potential solutions in another setting. And understanding the reasoning behind the support or rejection helps to shed light on the project side of it and not allow it to be construed as a matter of personality.

There's no room for gossip (unfounded information about others or things); there's no room for needless distractions that tend to cause panic or discomfort. Constructive criticism should be encouraged for the sake of growth and learning. Learning should be encouraged. Good communication skills through open, tactful speech should be encouraged. Tact is paramount followed by exchanges between parties for the sake of transmission of information as well as building alliances. And exchanges of information mean confirming that the correct message was heard by the correct party(ies). Confusion about terms and terminology should be cleared up quickly so everyone is on the same page.

Nor should there be any space in any way for threats of punishment, suggestions of coercion, destruction of input to work or research or work, withholding of privileges for lack of consent. Abusive and retaliatory consequences simply do not belong in your corporate culture much less on any of your teams. Isolation, being ostracized, personality differences, failure to recognize the advantages of diversity of culture, ethnicity, abilities, and even age make being in your enterprise not a healthy place to be. Get rid of all of it and don't let it slide under the door.

Star status is important to some and not to others. Knowledge that they've been part of the end product sometimes carries its own limelight. To cut the negative side of competitiveness, it's important to acknowledge the more significant contributions of certain members of the team. However, the leader also needs to recognize how the rest of the team contributed to reaching that plateau.