I recently presented a review of our Team System community programs to the leadership of our business. This was a particularly interesting task for me as less than 3 months ago, I hadn't really spent much time thinking about community but as it became one of the three main parts of my job recently, I now care a lot. (Funny how that happens). I'm actually very excited about the addition of this role to my other responsibilities as it helps balance out my perspectives on our product and customers. I worry a lot about folks in 'release management' roles that don't have a strong connection to the customer. They might be great at getting products out the door but how do they know it's the right product that they're releasing? Yes, there are others on the team with tight customer connections, but the person beating the drum and driving discussions around priorities really benefits from having a balanced perspective between the team / company point of view and the customer / community point of view. More on that philosophy at a later date...
We have a dozen community programs that we've selected to manage over the next year. We selected these based on the product team's ability to affect the outcomes and the expected impact on the community at large. Our overarching vision here is to:
As we break this down to the program level, categorize our efforts as follows:
Whew...that's a lot of programs and things to keep track of. We'll be monitoring our progress through a series of metrics for each program and making adjustments as needed. Fortunately, I don't have to do it on my own. Members of our Community Council that have blogs available include:
I'm eager to hear your feedback. What of all of this is working for you? What are we missing? Where could we improve?