Go to People Connection Blog main page
feed SUBSCRIBE to our RSS Feed.

MESH Team Update: Tools, Standards, Training & Communication

My last entry promised a series of posts about items on the MESH Team's to-do-list. Let me climb over the 800 pound elephant sitting between us to say that layoffs and reorganizations have eaten up a lot of everyone's time for the last two weeks. To add to the headaches, there's been some mutating virus (of the physical kind) that slowed many of us down. But, we've rallied and we're back. So, let me give you an update on the items that lead our task list:


Smarter moderation and enforcement tools: Two things have occurred to help speed the way to completion of this task. First, our team now "owns" the support and fix functions as well as the development of these tools. This means that we control prioritization of both feature development and support rather than having to vie with other teams for time and resources.

Second, all the MESH Team members sit near one another now, so the people responsible for policy, process and technology can toss requests, suggestions and feedback back and forth all day long. Prairie dogging and trips to the "war room" have increased exponentially. In fact, I think I heard them yell "war room" and clomp over there just a few minutes ago.

Easy to understand community standards: Once everyone has signed off on these, you will be the first to know when they'll be rolling out. There won't be any surprises except that you'll actually understand the standards if you couldn't before. And, those who did understand them (but claimed not to in attempts to worm their way out of a legitimate, well documented block) will have no excuses.

I'm tempted to call the new standards "The Seven Deadly Sins." We're aiming to have these done this week. Short of fires or floods, it should be so. In the meantime, remember that community standards are all based on Terms of Service and we all know those by heart.

New training for our teams: Though we review and train our teams on a weekly basis around here, we have done a thorough review of our curriculum. This resulted in expanded definitions and better processes related to the review and removal of user-generated content. Most of the changes were driven by a focus on our users' experience. First, we referred to all the mail we receive from users via our various feedback boxes. Then, each time we made a decision, we asked ourselves: "Can we explain this to our users? If not then why are we doing it this way?"

Clear channels for user feedback and escalations: Okay, this is a big one, especially since there are fewer of us and we want to be able to respond as quickly and effectively as possible. We've discovered that folks write to a multitude of mailboxes, some of which are appropriate and some of which don't even exist. I think many people just slap TOS in front of any old screen name and think it will go to the right place. Others write to 10 different TOS e-mail boxes each time they raise a concern. This is neither efficient nor effective if we want faster turn around times.

We want your e-mail to get to the right person and for that person to handle it quickly. When the community standards roll out we'll include the correct mailboxes to write to. We'll post that information here and in other areas, too, to get the word out. In the meantime, if you send things to AOLPeopleMGR@aol.com your mail will definitely get to the right person.

Frequent and ongoing communication with users: We will be using this blog as a way to keep you up-to-date on universal community related issues. We do not have the bandwidth to hit all message boards to ensure that folks get the information they need. Though we will still roam the boards and respond if we run across a question, we may miss something. Having this place to centralize messaging provides for better consistency. Everyone reads the same message and there's an opportunity for clarification if people need it. So feel free to ask questions of us here.

Developing better communication channels and closer relationships with product owners: This is something we work on all the time and we will continue to do so. As people step in to fill the gaps left by the actions of two weeks ago, our team will be reaching out to say hello and to bring them up to speed on what our customers are looking for in the way of features.

That's it for today. Stay tuned for more.

Reader Comments (Page 1 of 1)

Blog Search

Most Commented On (Last 30 Days)

About This Blog


Just a group blog for AOL and AIM employees who work on social media, online messaging and online community