Today I literally had one of those idea-in-the-shower moments. (Aside: does being surrounded by warm water relax our minds by taking us back to a womb-like state?)
I've been struggling to identify specific actions to take on analytics. Suddenly I thought of another way to act on the activity segmentation levels (ASL) that I have been developing. People who are highly active, especially those who are working on new, different or potentially widely applicable things are persons of interest for me and the local community managers. Our community development feedback loop process is surfacing names and activities that merit watching over time.
Why do I want to watch people?
We have thousands of community members, so it's hard to pick who to focus on in our development efforts. POI and COI are a logical place to look in developing champions.
When I visit offices, I will have people I can reach out to in advance and arrange to meet face-to-face. Again, developing champions as well as providing support, training and consulting.
We want to understand how people progress in the community, so following people over time will teach us about the processes they go through.
I want to support people who are trying to be active community members. By watching them I hope to pick up on opportunities to assist them and detect moments when they may need assistance. There's nothing like the teachable moment.
I want to keep track of the people are I can cite as models or examples for people who need help or ideas. If I can connect those needing assistance with someone who is doing what they want to do, they can learn from a peer.
And there are likely many more reasons...
Similarly, the planned community activity segmentation levels (still in development) will yield communities of interest: communities that merit watching over time so we can learn from them and also nurture them further.
So, armed with two new acronyms, I'm thinking of the best ways to watch and keep up with these POI and COI. The list could quickly become large and overwhelming. I'm thinking right now of a document for each POI and COI that's based on a template to capture basic info consistently. I can put these in a space or group in our Jive community and limit access to it, since I don't want everyone to know who I am "watching." That could get a little weird. If I title and tag the docs well and use categories, I should be able to find and filter pretty well even if the number of POI and COI grows large.
And if I title and tag with the division name, too, then I can let local community managers find their community members and get value from this, too. I don't want to have to serve up information and push it out to people if I can avoid it.
I also need to tag and use categories to capture the reasons I am tracking the POI and COI. For example, what specific ways are they using the community? What benefits are they realizing?
OK, this is just a new concept I'm working on, but any feedback would be welcome.
Benchmarking. Benchmarks. Sought after by some people with a fervor only slightly below the Crusaders' determination to find the Holy Grail.
I'm a benchmarks/industry standards skeptic and long have been. Let me admit that right up front. I see so many places and ways that benchmarks can be misapplied that I tend to avoid them, or maybe give them the same kind of glance that I'd give to gruesome wreck on the highway (I'm curious, but don't really want to get involved).
But I do believe careful, thoughtful comparisons make a lot of sense. If you take the time to understand the full context of what you are comparing and make sure you account for the complex differences between the environments you're comparing, then there are tremendous opportunities to learn.
The crazy vision I have for this group is that people will get to know each other in here and make connections that they want to pursue. Call it benchmarking, if you like, or call it sharing and comparing. Whether you do this one-on-one offline from the group or form an offline group to share with, or openly share here in this group -- if it helps you develop your community and understanding, that's a good thing.
Even if you don't share the results with the group, I'd love to have you tell us about what we're doing. You may inspire others to try the same. And maybe I'll become less skeptical!
Configure your Jive Community experience by selecting a track. We'll use this track on the homepage to show you relevant content and help you find resources quickly. You can change your track easily from the homepage or your profile.
As a community manager, you're an ambassador for your Jive community as you build places, curate content and engage with fellow community members. To help you go further with your site, we'll share success stories and other resources.
Whether considering a new purchase or working on an upgrade, technology managers need insight on the best ways to implement a community and learn more about the various upgrades in software releases.
An effective community starts with sound business strategy. As your community matures, you'll want to learn and share best practices for implementation and continued success.
Whether you're a developer, system administrator or a designer, you need insight on building a great user experience for your Jive community. Get the scoop on theming, API's, upgrades and more.
We've got a special area for partners to get essential information and best practices they need for describing and selling Jive to potential customers.
Whether or not you have a specific role in your Jive community, this track highlights areas of interest to Jive users such as training materials, community best practices and an opportunity to network with other customers.