Archive

Posts Tagged ‘enterprise 2.0’

My Ten Favorite Tweets – Week Ending 110609

November 7, 2009 Hutch Carpenter Leave a comment

From the home office along the former Berlin Wall in Germany…

#1: McAfee: Bad practice of #e20 evangelists = Declare war on the enterprise. Presents a bad msg to corporate buyers. #e2conf

#2: Frappaolo: His work finds that age has little to do with #e20 adoption. Creative thinkers span all ages. Org culture is the issue. #e2conf

#3: Yup, SharePoint 2010 is a platform: Microsoft To Offer Application Marketplace In SharePoint 2010 http://ow.ly/zYM2 via @rww #e20

#4: Google Wave product mgr. Best way to use #googlewave is for collaborative activities, not wholesale replace email. #e2conf

#5: RT @Brioneja: Google’s Wave Might Find Its Real Home Inside Company Servers http://bit.ly/2VJkxP #collaboration #software

#6: For #innovation, conflict is good. Conflict is right. Conflict works. Read @AndreaMeyer’s post to find out why: http://ow.ly/za7v

#7: Good take @zeroinfluencer: All User Centric Design is modeled around the ego. Good software design keeps that in mind. http://bit.ly/39gim3

#8: Gov 2.0 – City of Manor Taps Citizens’ Ideas for Improvement (via Spigit blog) http://bit.ly/4A1hNc #gov20 #innovation

#9: RT @zee RT @jestei I find twitter #lists weirdly, narcissisticly fascinating; they provide a rare window into how others would define you

#10: http://twitpic.com/noz7d – Tonight’s Jack O’ Lantern is a wink emoticon ;) My 5 yo’s choice. Future geek.

Innovation ROI – Why Every Enterprise 2.0-Enabled Connection Counts

October 27, 2009 Hutch Carpenter 6 comments

In a recent post on the Spigit blog, Study – Collaborative Networks Produce Better Ideas, I described the research of Professor Ronald Burt. He found that employees who are better connected across the organization generate higher quality ideas than those with limited connections. Wider access to the ideas, knowledge, experiences and judgment of colleagues makes employees stronger in innovation.

I posted this write-up in the Continuous Innovation group on LinkedIn. One person made this observation:

Need to keep in mind that collaborative networks have little to do with technology. There are certain personality types that keep the organization connected. The proportions of those people in an organization is related to the specific corporate culture.

There’s a good alternative perspective. That really, the same people that connect via collaborative networks are those that would be doing it in an offline world as well. The rest of the employee population likely continues to work in a more insular world.

I see it differently though. First, I agree that there are people with natural connector personalities. They would span the different parts of the organization no matter what. Anyone think David Armano wouldn’t be one of those types?

But not everyone need be an uber connector to see benefits from plugging into a more connected network. My personal experience on sites like Twitter and FriendFeed tells me that everyone benefits from these online social networks. We may not all be uber connectors, but we do increase our degree of connectedness.

The graph below is my concept for how this effect manifests:

Offline vs online degree of connectedness
Assume a population of employees: 25 in this hypothetical example. The blue line is the level of connectedness for employees working the way they have for decades. Your connections tend to be local and departmental, with some tenure you gain a larger informal network. In Professor Burt’s terms, most workers are relatively insular in terms of who they access for information and ideas. But some broker connections across different corporate “tribes”.

The red line represents the level of corporate connectedness for employees including the ability to find others online. To me, this is a no-brainer. Of course people are going to connect with others they wouldn’t have otherwise. The number, diversity and depth of connections increase.

The gray zone between the red and blue lines represent that improvement. Some people won’t get too much increase. They really are in-person types of connectors. But others thrive in the online environment. They have more specific interests, and didn’t know who else in the organization held them. Through the social software, they find more people with interests similar to theirs. Or at least with experience relevant to their interests.

Don’t need to be an uber connector there. Just need to be able to make connections.

Next…the ROI math.

The Natural Logarithm Method

Take a look at the graph below. It shows the scatter plot of how ideas were rated for different employees (Y axis). The X axis represents the degree of connectedness for employees, based on actual social network analysis conducted by Professor Burt in his study:

Measuring Innovation ROI from E2.0 Connections

The scatter plots show that employees who have a high diversity of connections across the organization provided higher quality ideas. The converse holds true as well.

Regression shows the equation that represents the observations:

Value of Idea = 5.51 – 0.91 * ln(Level of Network Constraint)

The equation shows that, on average, every increase in a person’s level of connectedness with different parts of the organization produces higher quality ideas. Note the natural log curve. The effect increases as connectedness improves. What I like about that is that the benefits increase, even if the work of increasing employees’ network diversity gets more difficult as you try to connect those last holdout groups.

Extrapolate the effect out to the organization at large. Raising the overall level of workforce connectedness will have a salutary effect on the average quality of ideas generated. In an era of ever higher levels of market volatility, improving the organizational “innovation IQ” is a critical aspect of surviving and thriving.

One thought on the accelerating benefit – increased idea quality – as connectedness improves. In a large population, would this have any correlation to network effects?

It’s not perfect, but Professor Burt’s analysis demonstrates a strong ROI basis for leveraging social software to increase the diversity of connections.

My Ten Favorite Tweets – Week Ending 102309

October 24, 2009 Hutch Carpenter 1 comment

From the home office in Kabul, Afghanistan…

#1: Twitter’s Web Traffic Flatlines http://ow.ly/viH9 …while Facebook continues to grow.

#2: Initial take on MSFT’s Twitter integration (http://ow.ly/vLGF)…that is sweet! Now will they show tweets beyond the last 3 days?

#3: RT @danschawbel REPORT: 65.6% of CMO’s feel that social media should be done in-house http://tinyurl.com/ygdjtfb

#4: If the Enterprise 2.0 crowd wanted to share a link, my guess for the top 5 services: Twitter, Facebook, LinkedIn, Posterous, Yammer. Agree?

#5: Study – Collaborative Networks Produce Better Ideas (via Spigit blog) http://bit.ly/3xoPM5 #e20 #innovation

#6: Interesting point from #spc09 – SharePoint is a critical driver of MSFT’s future growth. #e20

#7: Two SharePoint 2010 articles – RWW http://bit.ly/1zjI49 | @olivermarks http://bit.ly/4f9en0 – paint a good picture of its #e20 initiatives

#8: Southwest Airlines is running a “test lab” of ecofriendly products on its new Green Plane http://ow.ly/w3fR

#9: RT @Cubba: @bhc3 I thought this was timely based on our conversation at Patsy’s; http://bit.ly/1WQGwH = “10 Tips for Retrosexing on FB”

#10: http://twitpic.com/m13gk – It’s pumpkin patch time! Kids have their own. #halloween

Would You Manage CRM with a Wiki?

October 19, 2009 Hutch Carpenter Leave a comment

Or human resources with a blog? How about project management with forums?

Funny questions to ask, no doubt. Of course it’s not possible to effectively address many of the critical business functions using basic Enterprise 2.0 tools. Yet when it comes to social software, it often seems that the only game in town is to be a provider of such tools. For instance, Gartner’s Social Software Magic Quadrant requires that vendors have wikis, blogs and forums to be considered (side note – for the record, Spigit has all three social software tools and more).

I am fully on board that there are great opportunities for new types of communication, collaboration and information discovery in these tools. For instance, see my post, Microblogging Will Marginalize Corporate Email.

But there’s an enormous opportunity for applying the ethos and value of  ’social’, ‘transparency’ and ‘collaboration’ to a wider range of business processes. Key here is not to force specific processes into a general purpose tool, but to bring social software ethos to longstanding enterprise activities.

Hmm…sounds Dachis Group-like (“social business design”), eh?

Activity-Specific Social Applications

In the recent Gartner Social Software Hype Cycle, analyst Anthony Bradley introduced a new category, Activity-Specific Social Applications:

“As social software implementations mature, application patterns are evolving, and the software industry is responding with activity-centric social application offerings rather than with generic social software capability suites. Delivering a targeted social solution with a general purpose social tool (such as wikis and blogs) can involve significant development, configuration, and templating effort.”

Bradley has identified the next opportunity in enterprise social social software. Integrating the valuable characteristics of social software into the in-the-flow activities that make up our days. As a percentage of employees’ time, activity-specific social applications will be quite large.

Back in March 2009, Sameer Patel wrote, don’t confuse Enterprise 2.0 with social computing concepts. He was making this exact point, and included this illustrative diagram:

Credit: Sameer Patel, Span Strategies

Credit: Sameer Patel, Span Strategies

His point is that the left side are tools, whereas the right side are results-based activities. Key here is to create applications aligned with the processes for those activities. That means going deeper than a general purpose tool.

Successful Applications Will Be Designed for Results

So back to the original question. Would you manage CRM with a wiki? Could you? Perhaps there’s a geek hack to do this, but for mainstream business, the answer is ‘no’. Customer relationship management includes:

  • Case management
  • Customer revenue analytics
  • Sales pipeline
  • Individual prospect opportunity workflow
  • And lots of other stuff

It would be really hard to use generic off-the-shelf social software to deliver the above functionality. Yet, going back in time, here’s what was prescribed for CRM success in April 2002:

People [who fail] don’t integrate CRM into the other parts of their business or implement CRM as a stand-alone and don’t have it communicate with core systems. A bigger and more frequent stumbling block is forgetting to address the people issues around a CRM implementation. In almost all of the cases we described earlier, CRM is a behavior modification tool.

There is a need for the “hard” functions that CRM can provide, like case management, campaigns and analytics. But that’s not enough (e.g. see social CRM), and enabling the customer-centric firm seems to require a good bit of what makes Enterprise 2.0 tick: cross-organizational perspectives, contributions from different departments, a more collaborative orientation to an end-goal. Integrate CRM into “other parts of their business”.

Wikis, by themselves, don’t provide the necessary CRM functions that are table stakes to be useful for companies. But CRM platforms could benefit from integrating more social software tools and conventions.

And that’s the case for a lot of the current processes that define companies today. They aren’t going to be addressed by off-the-shelf generic social software tools. But they benefit by incorporation of social software tools.

“Activity-specific social applications”. A few examples:

Dachis Group talks about social business design as “the intentional creation of dynamic and socially calibrated systems, process, and culture.” Indeed, there’s a huge opportunity to apply social software to the multitude of applications and processes that make up organizations, beyond the insertion of standalone generic tools.

Watch this space.

My Ten Favorite Tweets – Week Ending 101609

October 17, 2009 Hutch Carpenter Leave a comment

From the home office in a balloon 7,000 feet above Colorado…

#1: Well, this was unexpected. The Spigit funding news has hit Techmeme http://bit.ly/3ETPFp #e20 #innovation

#2: LinkedIn: 50 million professionals worldwide http://ow.ly/uq7s “Last million took only 12 days” Wow. Tipping point?

#3: RT @mwalsh: Seth’s best post of the year – get over yourselves…you’re not that cool, interesting or smart. http://bit.ly/3HwrV6

#4: Is Social Media the New Cigarette? asks @billives http://ow.ly/u8IY Looking at social media addiction

#5: RT @nyike First Jive, now Spigit building #e20 and collaborative functionality on top of Sharepoint http://bwbx.io/hina

#6: Within firms, collaboration technologies are dictated by most powerful person involved in the collab http://ow.ly/tJgf by @amcafee

#7: Just as interesting as this WSJ piece is, Why Email No Longer Rules… http://ow.ly/tZpj are the skeptical cmts left by readers #e20

#8: If companies like $GOOG and $MMM excel and incl employee 15-20% personal time for innovation, why haven’t others adopted same?

#9: Wind farm firm makes sure its wind mills are 30 miles away from nearest Starbucks. http://ow.ly/tRQP Why? Best way to avoid NIMBY’s

#10: When a company gets funding, all sorts of interesting “opportunities” emerge. Just got a solicitation for Spigit to sponsor a NASCAR driver.

My Ten Favorite Tweets – Week Ending 091109

September 12, 2009 Hutch Carpenter Leave a comment

From the home office in Athens, Santorini and Crete…

#1: Salesforce emerging as a competitor to Jive, Socialtext, Atlassian, Telligent? http://bit.ly/71hbn That’ll be tough #e20

#2: What Exactly is a Social Business? http://bit.ly/2g9u82 by @lehawes #e20

#3: 15,000 Thoughts per Day – Why We Need Constraints for Innovation (via Spigit blog) http://bit.ly/ltaxP #innovation

#4: “Innovation is one of the easiest & least risky areas that can be tapped by organizations” http://bit.ly/uLk6K by @dhinchcliffe

#5: RT @armano “innovation happen in the corners of an organization—they need to be connected” (we call this Ecosystem) #futurebiz

#6: McKinsey has created the “innovation performance score” http://bit.ly/2YWPQ9 It’s, of course, a smart analytical tool #innovation

#7: Love @fredwilson’s attitude here: The Foursquare “Crush” http://bit.ly/10g4kb Using his blog as valuable feedback for future investments

#8: RT @GraemeThickins Wall Street Journal & New York Times plan San Francisco editions http://bt.io/AwZ (via @thefutureofnews)

#9: RT @skap5 Is it possible to have an economy where everyone is a consultant?

#10: RT @Danny_DeVito I just joined Twitter! I don’t really get this site or how it works. My nuts are on fire.

Noted: Innovation Management races past Enterprise 2.0

September 9, 2009 Hutch Carpenter 2 comments

I belong to two groups on FriendFeed, Enterprise 2.0 and Innovation Management. These groups track tweets and Delicious bookmarks related to their respective topics. The Enterprise 2.0 Group was set up in June 2008, meaning it’s about 15 months old.  The Innovation Management Group was set up July 24, 2009, meaning it’s  about 1 1/2 months old.

So the Enterprise 2.0 Group has a 13 1/2 month head start in terms of attracting members.

Which makes this all the more remarkable:

Innovation Mgt vs E2.0 - FriendFeed GroupsThe Innovation Management Group tied the Enterprise 2.0 Group in membership last Friday (9/4/09). It now has 607 subscribers vs. 590 in the Enterprise 2.0 Group.

Noted.

My Ten Favorite Tweets – Week Ending 090409

September 5, 2009 Hutch Carpenter Leave a comment

From the home office in Los Angeles Station fire…

#1: CNN: Hired! I got my job through Twitter http://bit.ly/1L7lT8

#2: Reading: New Approaches for Analyzing Influence on Twitter http://bit.ly/lz6VP Deep, detailed analysis. Focuses on 12 big hitters.

#3: What an interesting concept. Check the social web to see who scores high on key terms. http://test.jobshouts.com/ (via @gyehuda)

#4: Collaboration King picks the top 3-5 vendors in 11 different categories of collaboration software http://bit.ly/j22WW #e20

#5: Enterprise 2.0: If you (just) build it, they won’t come http://bit.ly/XumO9 “Focus on the low-hanging fruit of human behavior”

#6: Delicious blog: Two PhDs are working on a reputation system for Delicious to make finding good content easier http://bit.ly/4sbGyI

#7: Innovation = problem to be solved + ideas/knowledge of others + presence of mind

#8: Jeffrey Phillips of OVO: External Innovation Communities (via Spigit blog): http://bit.ly/13MJC9 #innovation #spigit09

#9: Do Users Want Innovation? http://bit.ly/Zk5Mp by @jkuramot Truly breakthrough? Not initially – only early adopters. #innovation

#10: RT @innovate Cash for Clunkers – 10 out of Top 10 clunkers turned in were American, but only 2 of Top 10 purchases were. #cars #usa #green

Management by Community

September 3, 2009 Hutch Carpenter 2 comments

At the Spigit Customer Summit, Gary Hamel described an innovative management approach that has stuck with me. W.L. Gore management has a hands-off approach to managing employees. Each employee is free to say ‘no’ to any request by a colleague. That’s right. Refuse to do something a colleague asks.

Damn, that sounds pretty good, doesn’t it? No more of those annoying requests that drive you insane.

But doesn’t it also sound like a recipe for anarchy? I mean, companies need employees to get specific things done, on a timely basis. It’s what make companies “go”. You get people refusing to do work, things will grind to a standstill.

All true, if the story stopped there.

Say ‘No’ But Watch the Repercussions

The figure below demonstrates the power of community in regulating excessive refusals to do work, or in providing work that is of inferior quality just to get someone off your back:

Mgt by Community

Employees learn community expectations about what constitutes quality work, responsiveness and collaboration. As you see in the graphic, each employee is requested to work on different projects over the course of a year. And true to the W.L. Gore way, an employee can say ‘no’ or ‘yes’ to each request.

The kicker is that at year-end, peers will rate the employee’s performance. A normal, conscientious worker will do fine in this scenario. But one who is an underperformer will have trouble hiding from the judgment of peers.

Consider how this maps to current processes:

  • Executives and other employees set direction and launch new initiatives, just like today
  • Employees are expected to contribute to multiple projects during the year, just like today
  • Employees need to work in a collaborative team environment, just like today
  • Peers provide a 360 review of employees, just like today

The biggest difference is the primacy given to the peer feedback. It is the crucial input on performance reviews.

It is the crucial input on performance reviews. This is how individuals internalize expectations that might normally come from a single boss. In the usual work setting, your boss is the final arbiter of your performance. Which means you really need to focus on winning the opinion of just one person.

In management by community, you need to think larger than that. The work everyone does plugs into a larger objective of growth and profitability. By tying one’s performance to the interactions with multiple colleagues versus one, companies like W.L Gore alter the influences on employees’ work. And it has paid off for Gore. As noted in FastCompany recently:

In its 50th-anniversary year, the $2 billion-plus private company is on pace for record revenues and profits, thanks to a number of clever new products with a lot of potential.

Visibility Becomes More Important

One outcome of management by community is that the visibility of one’s work becomes more important than ever. Two reasons for this:

  • You want a record of the work you have done, so others will see it  and be able to find it
  • You need evidence of the work you are doing when you inevitably have to say ‘no’ to someone

Others will know that you are accomplishing things as you deliver your work for projects. But the visibility will be limited to only those involved at that time on that task. You’ll likely email your work to others for use in a project. That includes your boss, which is all you really need usually.

Creating public spaces for the sharing of work allows you to deliver on a specific task to a group of people in the same way. But it also lets others know what you’re doing. Someone who may be rating you down the road may not have been on that specific task. But they are now aware of your work. Think that might help influence their opinion come peer review time? I’d say it will. It also makes you more valuable to others for future work, which is an important aspect of management by community.

The other thing is that you will have to say ‘no’ to people. They will be disappointed, even a bit angry. This is a reality, as there is only so much of you to go around. But what can help mitigate those feelings of rejected “work suitors” is a demonstration that:

It’s not you. It’s me.

You didn’t say ‘no’ to someone because you don’t like them, or the work they need. It’s because you’re just so tied up currently on other things.

Final thought on visibility. One could take this to an extreme of tracking the tasks you’re asked to work on. You then signal whether you are in or out on some sort of online site. Considering that many task requests come in the form of email, perhaps not so farfetched to imagine them being made online.

Better Match between Employees Interests and Their Work

Another aspect of management by community is that employees will tend to associate to projects with work that matches your skills and interests. As you make decisions about what to say ‘yes’ and ‘no’ to, there will inevitably be a pattern to them. Generally, I’d expect a bias toward ‘yes’ on projects requiring talents matching yours.

This has two upsides and one downside. One upside is that projects get a better mix of diverse skills from people with above average talents for a given task. This is great, as it improves the output of a team.

A second upside is that employee satisfaction rises. Imagine a world in which you got to employ your skills in something bigger than yourself, and that was your primary work. Not everyone gets to do this. Having more control over your career destiny and work that you personally enjoy is a recipe for happier employees.

The downside is that there are always going to be those grunt tasks that need to get done. Having liberated workers who determine that their time is better spent on meatier projects can risk a failure to get the grunt work done. We all know what employees who exhibit these traits are called: prima donnas.

An interesting question is how much the community dings employees who refuse the more menial tasks that make up everyone’s day. If you truly are world-class talented for something and applying those skills for bigger picture work makes everyone’s projects better, I suspect you can get away with it. But suppose your chosen work is of decent quality, but not earth-shattering. Or what you’re good at is in low demand by peers. I think you risk serious prima donna backlash in the community reviews by saying ‘no’ too many times to grunt work.

Employees will have to do a serious self-assessment in such an environment. Which may be one of the best outcomes of management by community.

There is a lot to commend this concept of management by community. It plugs employees much more into the hive mind of the organization than do traditional management models. And it seems to work. Aside from W.L. Gore’s record financials in its 50th year of business, note that the company is consistently ranked as One of the Best Companies to Work For by Fortune Magazine.

Management by community: worth a closer inspection.

My Ten Favorite Tweets – Week Ending 082809

From the home office in Boston, Massachusetts…

#1: Ten Great Ways to Crush Creativity http://bit.ly/FR5PJ by @PaulSloane I’ve seen many of these in my work history #innovation

#2: “The kind of mistakes you make define you. The more interesting the mistakes, the more interesting the life.” http://bit.ly/Yqs2X by @berkun

#3: WSJ: Why Multitaskers Stink at Multitasking http://bit.ly/swsd2 “If you think you’re a good multitasker, you most certainly aren’t.”

#4: Forbes: “Their passion is for what they do, not for who they work for” in The Odd Clever People Every Organization Needs http://bit.ly/iWDTs

#5: Interesting survey: “Who is the most important living management thinker?” http://www.thinkers50.com/vote My vote? Gary Hamel

#6: Is engaging customers in social media Enterprise 2.0? Or is it Enterprise Marketing 2.0? Comment on @vzrjvy’s blog http://bit.ly/LcMQk

#7: Jakob Nielsen, guru of web design, provides his take on what makes a good tweet: http://bit.ly/1UqHIA

#8: Have you heard of this dude? @shitmydadsays tweets funny stuff his father says. Only 21 tweets, but 139k followers.

#9: The Onion – Study: 74% Of Children Tenting Out In Yard Don’t Make It Through The Night http://bit.ly/zmqkZ Need to let my little ones know

#10: Dear @SantaClaus25: my son Harrison would like Lego City for Christmas. “The whole Lego City” he says, as he watches me type this.

Democracies Don’t Suffer Famines: Implications for Corporate Governance

August 24, 2009 Hutch Carpenter 1 comment

In his keynote at the Spigit Customer Summit, Gary Hamel said that something that caught my attention: democracies don’t suffer famines. Hearing this, I was intrigued and did some research.

Amartya Sen, winner of the 1998 Nobel Prize in Economics, made this empirical observation:

One of the remarkable facts in the terrible history of famine is that no substantial famine has ever occurred in a country with a democratic form of government and a relatively free press.

Why? In a paper from the John F. Kennedy School of Government at Harvard University, Sean M. Lynn-Jones puts forth two reasons:

First, in democracies governments are accountable to their populations and their leaders have electoral incentives to prevent mass starvation. The need to be reelected impels politicians to ensure that their people do not starve.

Second, the existence of a free press and the free flow of information in democracies prevents famine by serving as an early warning system on the effects of natural catastrophes such as floods and droughts that may cause food scarcities.

Isn’t that powerful? Simplifying things, I distill those two reasons into these: (i) organizational responsiveness, and (ii) distributed trend detection.

Both of which describe the realm of what Enterprise 2.0 is about, albeit without the life-and-death issue of starvation. That in itself is interesting enough. But when you try to apply those findings to companies, you realize they don’t quite mesh with today’s corporate governance models.

Corporations Aren’t Democracies

You, the reader, probably say “duh” to the observation that corporations aren’t democracies. But to consider the benefits of organizational responsiveness and distributed trend detection, it’s important to understand a crucial difference between democracies and corporations. The diagram below shows the corporate governance model:

Corporate Governance Model

In the context of making organizations more responsive, and distributing trend detection, where does that happen? It’s the employees. They’re the ones on the front line. They’re getting creative to solve issues everyday. They hear things from the market before most do. They want to make a difference and see their companies progress.

This is the equivalent of the voters in a democracy. The ones who are experiencing issues firsthand. But employees aren’t empowered to change their organizations. That’s the C-Level suite: CEO, COO, CFO, etc.

The C-Level suite lives a life of leading employees, and listening to the Board of Directors. Well listening, and leading, the Board. And the Board serves at the pleasure of shareholders.

In this model, shareholders look at company results and estimate future overall growth in revenue and profits. Fail to hit the numbers, and they put pressure on the Board. Board feels the pressure, and begin to question the C-Level suite. C-Level suite makes changes, and/or is replaced.

Notice that train of actions – it’s not the feedback from employees that drives changes. It’s a look-back at the results by shareholders. This isn’t to say that C-Level executives do not listen to employees. But the structural governance model sets the pecking order for who and what gets attention.

Bringing the Voice of the ‘Governed’ into the Enterprise Conversation

As someone who went to business school, I’m a firm believer in the accountability to shareholders governance model. Capital is scarce, and its efficient allocation across the economy is valuable for ensuring generally sufficient supplies of products and services needed by the population.

But that doesn’t mean the C-Level executives can’t change the way they manage to improve the prospects of their companies and returns for their shareholders. As has been pointed out before, companies are experiencing unprecedented levels of volatility in markets today. Sources of industry change come from multiple directions, and their speed of invasion is much faster.

Maintaining a model of listening only to their senior executives, their Board and their shareholders is becoming a risky strategy for CEOs. It means listening to people whose interests are certainly in seeing a strong, healthy company, but whose capacity to provide early trend detection and problem-solving creativity is limited. Shareholders aren’t in the trenches of your company’s operations. The Board of Directors is made up of C-Level executives from other companies, who need to worry about their own operations.

Gary Hamel discussed W.L Gore as a model of a company where employees are much more a part of the corporate governance model. From Fast Company in February this year, here’s a quick update on W.L. Gore:

Gore has spun a fortune from constantly reinventing the polymer polytetrafluoroethylene. In its 50th-anniversary year, the $2 billion-plus private company is on pace for record revenues and profits, thanks to a number of clever new products with a lot of potential.

An article in Sales and Marketing Management noted that employee teams help to hire new staff members, assist in determining each other’s pay, and pick their own leaders. Crazy eh? But note the same article says this:

An almost eerie optimism radiates through the hallways at Gore, which is best known for its Gore-Tex lining for weatherproof jackets, and which remains a private company despite its size, in order to protect its culture from outside interests.

Ouch! Here’s a company that exemplifies a governance model of innovation, encourages employee innovation and distributed market intelligence. And it has to stay private to protect this culture?

My sense is that the Enterprise 2.0 movement in general is a vanguard toward improving the way companies are managed. Being a public company, used to a top-down order of things and paying a lot of money to outside consultants to understand the market, is hard to change overnight. But companies can begin to improve the way they engage their employees and leverage their vast, distributed know-how and creativity. There is a wide spectrum of how far companies can take this. The key is to begin understanding how new approaches can work in your organization.

Enterprise 2.0 as a movement, not a technology, is quite promising for enabling companies to improve their overall strategies and operations.

Alternatively, we can continue to do things the way we always have, with a limited set of decision-makers and market intelligence gatherers. As seen with the increased rate of companies gaining and losing positions in industries, this model is becoming less reliable.

Remember, there’s a reason democracies don’t suffer famines.

My Ten Favorite Tweets – Week Ending 082109

August 22, 2009 Hutch Carpenter 1 comment

From the home office at the World Track Championships in Berlin…

#1: Spigit Innovation Summit Wrapup http://bit.ly/4zIqo1 by @innovate “It’s important to have connectors on your #innovation team”

#2: Jeff Bezos on corp #innovation: For innovative ideas to bear fruit, companies need to be willing to “wait for 5-7 years” http://bit.ly/tP9vj

#3: Like this by @paulsloane – Given unlimited resources to solve something, we’d dev something expensive & over engineered http://bit.ly/Qa3tY

#4: Zopa isn’t disruptive argues @bankervision http://bit.ly/ZYela His key points: same customers, same credit scoring, same pricing as banks

#5: Gary Hamel last week: “We have a state of creative apartheid, where some are *really* creative, some aren’t. That’s BS.” #spigit09

#6: Bookmark this: 14 Reasons Why Enterprise 2.0 Projects Fail http://bit.ly/3piYNF by @dhinchcliffe #e20

#7: Bookmark this: How To Kick Start A Community – an Ongoing List http://bit.ly/641dA by @jowyang

#8: Mashable: “14% of surveyed employers disregard candidates who use friendly smiley faces in social media” http://bit.ly/1ajvd8

#9: RT @skap5 Is IMHO a necessary descriptor? Unless of course the rest of your opinions are not humble.

#10: My son starts kindergarten in a couple weeks. Then I see this: “Tutoring tots? Some kids prep for kindergarten” http://bit.ly/3htw0 No…