Showing posts with label Communities. Show all posts
Showing posts with label Communities. Show all posts

Wednesday, 27 July 2011

Performance and community

 

   I’ve been thinking more about the role and importance of community, partly following on from my last set of comments about the MIX, and also because I’m getting ready for the next event (a tweet-up) being run to support the main community that I’m involved in (ConnectingHR).

People always seem to have lots of energy and enthusiasm for the community leading up to and following on from these events, but we find it hard to maintain much, even just in the way of conversation, between the events – at least on the community site (connectinghr.org).

Yes, there’s quite a lot of chat which continues on twitter (some using the hashtag #connectinghr) but I think partly because of the 140 character limitation, and also because the chat gets mixed up with so many other things, this can only go so far in supporting the community.

We’re trying different ways of generating more ongoing support for the community, for example we’ve recently established a council of ‘elders’, or ‘lowerarchy’ (vs hierarchy) but even here, we’ve struggled to get much input from our community elders.

Please don’t misinterpret these comments – I’m definitely not complaining about a lack of input.  Everyone is increasingly busy these days, with any number of priorities, and increasingly a growing number of community roles too.  We also suffer in that ConnectingHR is a inter-organisational community, so it doesn’t have the focus and context that an intra-organisational community has.  It also doesn’t have a formal purpose – it’s only real objective is to be a community.  (I don’t think there’s anything wrong with this – being part of a community does provide benefits in its own right, and should lead to the development of further, outcome focused sub-objectives, like the current mentoring programme, or CSR focus, as the community develops.  But it also definitely makes it harder to maintain interest.)

But many of these challenges are shared by intra-organisational communities too.  This is why I think ConnectingHR is so important – if community management is the new HR, then HR professionals need to gain experience in participating in and leading communities.  And there are some big questions associated with communities which I don’t think have been firmly answered yet.  An example is the including of community participation in performance management.

What we do know is that community participation is a discretionary activity, based upon intrinsic motivation to participate, and that therefore it can’t be directed in the same way as participation in projects and in undertaking day-to-day tasks.

However, as communities become more important, and an increasingly important aspect of many peoples’ jobs, I think they’re also too significant to leave out of performance management.  The key for me in doing this is understanding that no-one is ever going to be able to contribute to all communities in the same way.

We know from Jakob Nielson’s (90-9-1) theory of Participation Inequality (or Jake McKee’s variant) that in social groups, some people actively participate more than others.  In fact, in most online communities, 90% of users are lurkers who never contribute, 9% contribute a little, and 1% of users account for almost all of the action. So, for example:

  • 167,113 of Amazon’s book reviews were contributed by just a few “top-100″ reviewers.
  • Over 50% of all the Wikipedia edits are done by just .7% of the users … 524 people.
  • In December 20, 2007 on the MSDN Community site, 1866 edits out of 10851 total edits were made by the top five contributors (three of whom are Microsoft employees). That percentage is slightly above one percent at 1.72%.
  • Just 0.16% of all visitors to YouTube upload videos to it, and 0.2% of visitors to Flickr upload photos.

 

Now it used, maybe, to be the case that people retained these roles from community to community, but I think as more people climb the social technographic ladder (or Altimeter’s Socialgraphic pyramid, Brian Solis’ behaviourgraphics etc), this is starting to change.

The new corollary of the 90-9-1 theory, is, I believe, my theory of Individual Divided Participation (as I’ve never seen anyone else propose this before).  In this theory, most people can only manage to contribute extensively to 1 (or 2 or 3) communities, maybe support another 9, and to take a back-seat role (to lurk) in another 90.

Performance management needs to reflect these different expectations.  So a line manager might expect a report to be able to identify a couple of communities that they are actively involved in, as curators and creators.  Hard objectives shouldn’t be mandated for these roles, but a manager and report should be able to discuss the broad approach that the employee is going to take to their communities (which ones they are going to invest in, and in what sort of ways).  Their performance can they be reviewed, loosly, against these expectations, or against defined behaviours (or competencies).

They may also be able to identify a handful of other communities which they involve themselves in, but not to anything like the extent of the above.  And they shouldn’t be expected to do anything other than lurk in the other 90.

Community oriented performance management should also focus on improving someone’s community involvement, ie for development, than for assessment – initially at least.

As for ConnectingHR, the challenge for us, it to find ways that will mean people will attach more importance to this community, so that more people put it as their top, or in their top 2 or 3, community/ies.  Not easy to do, but we’re not going to give up.  And in the meantime, I look forward to another highly engaging tweet-up tomorrow night!

 

 

 

  • Consulting  - Research - Speaking  -  Training -  Writing
  • Strategy   -  Team development  -  Web 2.0  -  Change
  • Contact  me to  create  more  value  for  your  business
  • jon [dot] ingham [at] social [dash] advantage [dot] com

.

Wednesday, 4 May 2011

Moon Shots on the MIX: Developing Communities of Passion Hackathon

 

  I’ve posted previously on Gary Hamel’s Moon Shots for Management and on my support for these.

I’m particularly interested in (and passionate about) this one:

 

Moonshot #22: Enable Communities of Passion

“Passion is a multiplier of human effort, but it can’t be manufactured. It’s present only when people get the chance to work on what they truly care about.”

Passion is a significant multiplier of human accomplishment, particularly when like-minded individuals converge around a worthy cause. Yet a wealth of data indicates that most employees are emotionally disengaged at work. They are unfulfilled, and consequently their organizations underperform. Companies must encourage communities of passion by structuring work and revising management processes to help people tap into a higher calling at work, by connecting employees who share similar passions, and by better aligning the organization’s objectives with the natural interests of its people.”

 

For a year I even moderated a ning-based community focused on further exploration of these moonshots - wanting to better understand the enablement of communities from a practical as well as conceptual perspective.

More recently, I’ve kept an eye on the development of Gary Hamel’s new forum for developing the future of management: the Management Innovation eXchange, or the MIX.

So when the MIX announced the formation of a Hackathon to develop hacks focused on developing communities of passion I was keen to get involved and am now working as part of a small group to develop a shared understanding about the value and attributes of these communities, the barriers in their creating and sustaining them etc.

 

Developing the Hack

  The hackathon is definitely producing some interesting outputs already – you can see these up at the MIX.

I particularly like Steve Todd’s definition of a community of passion, based upon his Wordle that I’ve included above:

“Together, an innovative new group of members share their interest and ideas, for the purpose of one common goal, and build many different, unique solutions.”

 

As well as his definition for what it means to enable a community of passion:

“Question your mind,think of others, identify talent, find knowledge.”

 

Todd suggests the key enabler for communities of passion is selflessness.  I’d certainly agree selflessness is good, which is why I think other heavy users of social media often make such good social companions.  But I think there’s more to it than this as well.

For me, the real key goes beyond selflessness, it’s togetherness.  It’s not about me, but it’s not just about you – it’s about us.  (The problem I think is that Todd took out all the words such as passion, community and people in creating his Wordle – but this means that this means the essential truth of what community is about.)

 

My input focused on the problem of limited time / priority.  People have so many other things to do that there are only a couple of communities they can ever be that active in.  This means that the strongest contributors in one community are often limited to being lurkers (legitimate peripheral participants) in others.

In organisations, this means leaders need to:

  • Educate their employees that participation in community is important
  • Provide their people with enough free / unallocated time to invest in community activity
  • Help / allow their people to prioritise – to decide which two or three communities are most important to them (feedback from these would then provide the basis for these employees’ performance management, accepting that the employee would be a lurker in any others).

 

Developing the Community

  The other thing that has interested me is how the Hackathon group / team has itself been developing as a community (I’m not actually sure whether it has ever been designed to be a community, and in some ways falls out of the confines of a community as defined above in that the group has a very clear task focus.  However, for me, there’s a clear logic in the group becoming a community which is to provide an experiential, action learning based approach to developing the communities of passion hack.

 

It’s one of the things I’ve never liked about the MIX – it’s really a very anti-social site.  There’s no real way to discover who’s there (other than using google - site:www.managementexchange.com), or to communicate with them, other than in the context of a particular update.  And it’s also very hierarchical – with regular posts from Gary Hamel’s friends (the mavericks) – meaning it’s even less likely that effective collaboration and innovation is going to take place.

Not everyone has liked the system we’ve been using for the hackathon – Saba’s Collaboration Suite – eg there have been quite a few comments on its clunkinness.  But I actually prefer the Saba system to the MIX – it’s at least got an element of social – allowing people to connect to each other and chat more generally.

However (and I don’t know if this is a flaw with Saba’s system or just the way it’s being used), I’ve also found the hackathon process very constraining.  We’re following a design thinking approach which I think has been useful in helping us work together in a systematic way to achieve something of value, but hasn’t enabled much bonding.

I think we needed a sense of who we are and how we relate before we started to put those relationships to use.  I think doing this lies at the heart of most innovation, and communities of passion too.

 

Also see these posts:

Gary Hamel on the Future of Management:

Management Lab:

Julian Birkinshaw on Reinventing Management:

My / other hacks at the MIX:

 

 

  • Consulting  - Research - Speaking  -  Training -  Writing
  • Strategy   -  Team development  -  Web 2.0  -  Change
  • Contact  me to  create  more  value  for  your  business
  • jon [dot] ingham [at] social [dash] advantage [dot] com

.

Monday, 28 June 2010

HR and Communities (Talking HR 029)


   Yes there was a reason why I suddenly did those two posts on communities (1, 2): so that I could refer to them in tonight’s podcast on the role of communities, their importance, their management (or facilitation!), and also on the HR function’s role in supporting them (see this post at Strategic HCM).

For this show, Krishna and I were joined by Claire Boyles from Management Matters.  Thanks a lot, Claire, it was great speaking with you.

You can listen to the archive here.

 

Picture: Community Maturity Model from the Community Roundtable

 

  • Consulting  - Research - Speaking  -  Training -  Writing
  • Strategy   -  Team development  -  Web 2.0  -  Change
  • Contact  me to  create  more  value  for  your  business
  • jon [dot] ingham [at] social [dash] advantage [dot] com

.

Enterprise 2.0: Communities aren’t sites, they’re people

 

    The first session on communities at the Boston E 2.0 conference was part of the Black Belt Practitioners workshop on the first day:

 

Community Roles and Adoption Planning (Stan Garfield – Deloitte, Luis Suarez – IBM)
  • Stan is community evangelist for Consulting at Deloitte Touche where he leads the SIKM Leaders Community with over 400 members globally and Luis is Knowledge Manager, Community Builder and Social Computing Evangelist at IBM
  • Communities behind the firewall are groups of people who share specialty, passion, interest, roles, concern, set of problems. Communities are living organisms so very difficult to manage
  • Community members deepen their understanding of the topics by interacting, asking questions, sharing knowledge, reusing ideas, solving problems together, developing better ways to do things
  • People join a community to share, innovate, reuse solutions, collaborate, learn from others

 

Luis Suarez started the session by explaining that whereas some people feel every group is a community, this isn’t the case.  Communities need a shared passion about a common interest.

Most of the session was the taken up focusing on Stan Garfield’s Communities Manifesto and some of the key points from this, eg that communities should be independent of organisation structure – people shouldn’t be forced to join, so that members want to be part of the community.

I particularly liked this slide examining the differences between communities, organisation sites and teams:

 

 

Luis and Stan also provided suggestions for community building programmes.

Firstly, you need to find a compelling topic.  This needs to be made interesting.

 

Most importantly, communities need to be facilitated, actively nurtured – they won’t necessarily expand naturally.  People set up communities and 2-3 weeks later find them dead - people wonder why.

We need to ask them have you engaged people?  Have you provided the opportunity for the community to have community activities?

Communities need to be nurtured ever day, every hour of the day, by engaging with them and providing a plethora of activities - including physical activities.  Web 2.0 tools aren’t enough.

They need good content to ensure good health but this is only part of the solution.  You need to focus on connections, and help people connect with each other.  Connecting people with content and other people.  Focus on the interactions between people.

 

One key question is who is going to lead the community – and this could be several people  - these need to have passion for topic and time to build and sustain it.

When selecting a leader it’s useful to watch peoples’ communications.  Who are the hubs / connectors / mavens?  Who do people trust? – go to for advice?

But note, the best conversation leader may not be best facilitator.  So they’ll need coaching and up-front training.  And you can then have a community of community leaders.

 

Another interesting point was that lurkers are valuable.  Without them, we often wouldn’t have a community.  And they may eventually move from being passive consumers to active producers.

 

Communities generally manage themselves, ie the “we” eg if people post inappropriate content.  It’s not something the community manager needs to get involved in.

 

You can never communicate enough about a community, eg communicate to the community what is happening in the community.

And cross-pollinate across communities.

 

Note, because of the differences on the slide above, particularly I guess the lack of a clear purpose, managing a community takes more effort than managing a team.

However, it is potentially more valuable as well.  Communities provides a reason to stay in the company – they reduce attrition rates.

 

Of course, as Luis and Stan noted, communities have always been there - for decades.  We all have a very natural need to participate in communities – we want to bond with people.

But I’m not sure they’re often that actively created or managed in most organisations…

 

I thought this was a really engaging and interesting session.  While the presenters were talking I was thinking about a community that I’ve been ‘managing’ recently – called ‘Moon Shots’ this is a ‘community’ of 250 management regades bought together by an interest in Gary Hamel’s writings on management innovation.

Only it’s not really a community – a result of me not really managing it.  So I’m probably not going to continue it when ning changes its conditions next month. 

Yes, I’ve got the passion, but I’ve been a bit short of time.  And I’ve never really thought that much about my role - so these guidelines from Luis and Stan would have really helped as well.

 

 

Slides are available at http://www.slideshare.net/20adoption

Follow my posts from the conference at bit.ly/e20conf.

 

.

  • Consulting  - Research - Speaking  -  Training -  Writing
  • Strategy   -  Team development  -  Web 2.0  -  Change
  • Contact  me to  create  more  value  for  your  business
  • jon [dot] ingham [at] social [dash] advantage [dot] com

.