-
Website
http://andrewmcafee.org/ -
Original page
http://andrewmcafee.org/blog/?p=525 -
Subscribe
All Comments -
Community
-
Top Commenters
-
immunity
3 comments · 1 points
-
digiphile
11 comments · 8 points
-
Amy
4 comments · 1 points
-
Doug Cornelius
3 comments · 3 points
-
Gil Yehuda
4 comments · 2 points
-
-
Popular Threads
-
The S Word
1 week ago · 40 comments
-
Thoughts at the End of the Year
5 days ago · 8 comments
-
Geeks Tweak Balloon Seek Technique
2 weeks ago · 2 comments
-
Why Yes, I’d LOVE to Talk About My Book…
3 weeks ago · 1 comment
-
The S Word
1)Is "value" a supply-derivative metric or a demand-derivative metric? Or some mixture?
2)What is the weight of quality, and how is qualitative value established? Does the transition of SNS from popular media (in which popularity is per se the standard of value) into the corporate world require a new/different notion of quality besides popularity?
There is a definitely a need to come up with a global reputation idex if you will for any Enterprise 2.0 ecosystem. To get there, we would need to be able to roll-up or aggregate reputation across multiple social platforms.
While looking at "tasks" within each social platform is important to begin with, I think it is important to look at each social system holistically and choose the right reputation pattern based on more strategic objectives. For instance, a social Q&A; platform holds good potential of acting as a "proxy" to the users expertise and perhaps a pattern like a "LeaderBoard" or "Named Levels"[ Guru,Expert,Beginner etc.,] makes sense. Please see these reputation patterns from Yahoo - http://tinyurl.com/6jlul3 - I guess they are very relevant to enterprises as well.
I think that E2.0 ratings can indeed visualize the productivity of a knowledge worker, but ratings shoud really only be the affirmation of what you already have experienced. In my view it is best to review the actual (E2.0) 'products' of a knowledge worker, to ask him or her what he or she is proud of and finally, in asking a few peers for review. Ratings can then affirm your conclusion.
I have no doubt that some organizations will attempt to quantify participation. Enabling the various workstreaming tools is an essential component of the whole E2.0 suite. It's important for colleagues to know, in a radically transparent way, where and how people are contributing.
As soon as you try to quantify it, however, you will kill the goose... This would be something akin to paying people to contribute to a KM system. You'll get nothing but garbage. People will try to game the system and it will distort the very results you were hoping to achieve.
I spend most of my working hours meeting and talking with organizational leaders from the business community, government, and academic institutions about E2.0 (we have developed and are now installing a collaborative workspace called FlowThink). Rarely am I able to talk about 'Enterprise 2.0' and maintain their interest. Instead, I have to focus on the effects that proper group communications and knowledge capture will have on their workforce's ability to achieve organizational goals. I also stress the positive impact these tools have on the lives of their organizational leaders. With these tools they will gain the ability to manage group work without having to be physically present 24/7. This message really resonates with professionals who can never seem to take time off because they are central to all group activities given that the information flows through them. Remove the leader and work stops. E2.0 addresses this problem.
So, I suspect that you'll need to ensure that the results of your performance measurements can be easily understood in the context of Enterprise goals. The NFLÂ’s passer rating is useful because it directly relates to the probability that your team will win the game.
We need to remember that E2.0 is as much about the Enterprise as it is about the 2.0. We need to be careful that these measurements put the use of 2.0 into context for the Enterprise. Business leaders won't care how much their workforce uses these tools if they aren't able to also see the impact the increased use of these tools is having on their organization.
The evidence is similar in the workplace (http://hbswk.hbs.edu/item/6011.html) - the silo lives. So the question is, can we use the kind of approach you're suggesting to incentivise people towards broadening their horizons and exploring more widely? For example, if I tag a resource prepared by my near neighbour, should this score lower than if I tag one from a very different business unit a continent away? Maybe we could build a 3D radar chart with distance as the third dimension.....
I have given some thought to whether it would be valuable to incent people to use the tools since I do believe that people would find them useful. However, I see two problems with that approach. First, I agree with others' comments that it would be difficult to determine the correct incentive that does not produce "garbage" while also not requiring large amount of manual effort to review and rate content. Second, I tend to believe that Enterprise 2.0 tools should be collaboration outlets that employees want to use willingly and not something that is force fed to them. To me, that is the time when you see the greatest benefit.
As far as a rating system is concerned, I would be hesitant to implement one around Enterprise 2.0 because I would not want to stifle an individual's willingness to contribute. As I mentioned above, I feel like the biggest benefits to Enterprise 2.0 should come when employees realize the benefits on their own and contribute at will. If a regular contributor sees that their personal feedback rating is very low will that reduce the amount of time they spend editing wikis and writing blog posts? Perhaps believing that people will see the value on their own is an idealistic point of view and I'll come around to wanting some sort of rating system eventually...
One other note, Dinesh, thanks for the link to the Gartner article. Definitely gave me some insight into some viewpoints about why our Enterprise 2.0 software is not being utilized to its fullest potential.
I had a lot of experience with salespeople, CRM utilization champions, who could not meet their sales quotas and IT trying to keep them from firing.
Don't put a carriage in front of a horse. It never works.
Awesome idea. I do quite agree with you that participation in social computing cannot be reduced to one number, but as you said, this could be treated as a set of numbers ... some folks would be good at edits, others at authoring ... In addition, this is making the entire idea of social computing what it should be ... fun!
Something on lines i wrote about ...
http://atulrai1.blogspot.com/2008/09/sabre-soci...
Check out the way Sabre are giving "Karma" to folks based on how they are answergin to other people's questions, etc.
If social software is to become mainstream in the enterprise, you'll have to measure community participation. Otherwise you can't calculate return on investment, effectiveness of training programs, or compare on suite of tools with another.
It's a short step from measuring participation in the aggregate to measuring the contributions of an individual employee. At many companies -- and in academia -- employees are already measured by the amount they contribute to the organization's intellectual capital. Whether it's objective measures such as number of articles published or patents filed, or more subjective measures like reputation or peer reviews will depend on the nature of the enterprise.
On the public internet, "karma" rankings on social networking sites such as Slashdot or Digg have been around for some time.
a = (((Comp/Att) * 100) -30) / 20
b = ((TDs/Att) * 100) / 5
c = (9.5 - ((Int/Att) * 100)) / 4
d = ((Yards/Att) - 3) / 4
a, b, c and d can not be greater than 2.375 or less than zero.
QB Rating = (a + b + c + d) / .06
Rating Knowledge Workers based on their activities even when in collaboration might miss the point: create something which was not there out of what you have. Rating results of knowledge work makes sense because there may be many other factors affecting the ability of a person to produce those results. This scale overemphasizes activities; they should only matter if they produce something that the organization values.
I've also seen a scoring system work within a company. I know the designers that work at Zurb, and they boil down their contribution to their company's blog to a single number, and keep track of who's winning: http://www.zurb.com/article/88/team-motivation-... [they say this has lead to both more and better work]
1. Attention. The amount of traffic to your "content" for a given period of time.
2. Participation. The extent to which users engage with your content in a channel. Think blog comments, surveys, wall posts, ratings, or widget interactions.
3. Authority. (like Technorati), the inbound links to your content - like trackbacks and inbound links to a blog post or people linking to a YouTube video.
4. Influence. The size of the user base subscribed to your content. For blogs, feed or email subscribers; followers on Twitter or Friendfeed; or fans of your Facebook page.
We developed an algorithm for a client to rate Facebook Pages by looking at a handful of FB Page activity metrics. The results helped us identify some techniques to develop an active FB Page.
Then we realized that we don't care about having an active FB Page unless it's helping accomplish some other strategic objective. Focusing on the metrics we'd identified (which are similar to yours here) would make our clients more popular, but, as Scott's second point addresses, the value of that popularity is hardly fungible.
The activities you're looking at in this example could certainly lead to the creation of some good content, but looking at them per se, even in aggregate, doesn't seem that useful at the end of the day.
After all, you do not know what the best outcome would be, or else you could design and formalise the process. But then, why introducing self-organising collaboration tools in the first place?
You also have to consider that the tools, like authoring, serve different purposes in a knowledge discovery and innovation process. Authoring aides creativity teams to form, managers to transparently discuss and communicate decisions, departments to get an understanding for concerns present in the organisation as well as channelling customersÂ’ feedback.
So what we should measure instead is not the frequency people made use of E2.0 tools, but the frequency they have been applied to processes or decisions in the different areas of organisation. Since the core question is, which processes have benefited the most, which have emerged, which have ceased existence?
I think your radar chart has good categories, though you will find that tagging is more likely to sky-rocket since it is the most efficient and a highly effective tool to connect person to people to content (three-tier). My hypothesis is, that using that chart to analyse fuzzy-front-end of innovation processes, you probably find that more authoring, editing, and interacting categories dominate. At later stages once the ideas have become more focused positive feedback becomes stronger as the transparency of decision-making process increases..
Finally, interesting would be to measure, where those collaborative tools help reaching a decision. I.e. when managers have to make a decision on, for example, going ahead or stop the idea project, there should be qualitative measures such as top three most influencing discussions (discussion name + link + summary 150). This decision should be an aggregated info dossier, tagged accordingly and made available to the OrganisationÂ’s network.
It is certainly useful to be able to quantify some aspects of Enterprise 2.0. But until we do have sufficiently accurate tools, lets not even try it.
My thoughts are that focusing on what we are trying to use Enterprise 2.0 'stuff' for might be a more useful focus than measuring the 2.0 activities themselves. OR if possible some combination.
For example, in a performance plan require at least one cross-organizational project with a 2.0 technology. It seems to me that sometimes we focus too much on symptoms and work hard to mask or overcome them, rather than looking at the problem and how to solve for that.
I think that E2.0 ratings can indeed visualize the productivity of a knowledge worker, but ratings shoud really only be the affirmation of what you already have experienced. In my view it is best to review the actual (E2.0) ‘products’ of a knowledge worker, to ask him or her what he or she is proud of and finally, in asking a few peers for review. Ratings can then affirm your conclusion.
There are all sorts of neat mashups that can be made to help judge interaction, but when it comes to qualitative measures the best approach is for both worker and management to work in the tools together. I could easily write my colleagues' performance evals because I read their blogs, subscribe to their social bookmarks, and watch the same wiki pages.
Management cannot view this interaction from a distance.
Clay Shirky does a great job of explaining power law distributions in this talk
http://www.youtube.com/watch?v=sPQViNNOAkw
If these activities are part of peoples job/position descriptions, then let's measure them as part of people's performance reviews. This type of graph could then be one good way.
If it's not part of their job, then who are we to impose this measurement? And to what end? How is this aligned with their job and business performance, not to mention business outcomes?
I think it's great to talk all this through, but we have to keep reminding ourselves that collaborative organisations will be created by management decisions, not our enthusiasm.
Cheers, James
Interestingly virtual group research also indicates that the active behavior of a small number of individuals in a group can drive overall behavior norms. Given this fact I believe leveraging the proposal to set objectives for a small group of "rainmakers" responsible for the success of the social networking site could prove effective.
Patrick McHugh
Managing Director
BitInsight LLC
implementing set of web 2.0 tools (Blog, Wiki's) our main focus right now is to attract all the early adopters and creators. I believe we should offer them some incentives, mainly not financial as most of creators and contributors seek recognition and feedback from the community. Still I'm not sure how to approach it long term, I will be following this post Thanks.
However, such ratings show great promise for reviewing the general use of the available infrastructure as well as tendencies amongst employees. Social software is most likely not adopted at the same speed everywhere. Improvements to the software and specific training can be offered to those groups of employees that have not yet adopted new possibilities.
The diagrams do have another potential weakness. As a power law distribution will most likely always be present, most of the rating charts will consist of a mere blip in the very center. The graphs will possibly need to be improved, so that the lower percentages account for more space on the chart.
Our own personal incentive derives from the participation in internal Wikis. However, this is not the sole reason for the participation. In addition to this, we enjoy sharing and spreading our own knowledge, and we see this as advantageous for our reputation.
For us, who actively participate in the company Wiki out of conviction, the ranking is not a disadvantage, instead we consider this a confirmation of our position.
On the other hand, what about employees who only participate in ESSPs for the ranking? We consider this a "mechanical" participation, and this brings up the question on whether time will transform it into conviction.
We believe that currently these ESSPs are still in an early phase considering their use in the industry, and that therefore they need certain degrees of freedom regarding the measurment / ranking of the employees. As mentioned before, a change in culture is required, which can be reached, in our opinion, rather by convincing people than forcing them into participation. One way to do this is to present successes achieved by using ESSPs to the employees.
Once such a change of culture has begun, it may make sense to implement a ranking. The presented 6-point radar chart, generated automatically, would allow each employee to check their status and to determine, which aspects can still be "improved".
Not least, such a chart will reflect the methods and the social competence of the employees.
One issue not considered is the following: what happens to an employee who has reached the maximum in all six dimensions? Will they continue their participation or rest on their laurels? Hence, measurement and ranking can serve as a personal determination of the status, but not as a comparison to co-workers.