At the Enterprise 2.0conference two weeks ago, Tony Byrne (President, the Real Story Group) and Rob Koplowitz (VP and Principal Analyst, Forrester Research) were joined for the SharePoint Analyst Panel. David Carr's Information Week column Does SharePoint Have Future As A Social Platform frames the debate as lopsided with a simple conclusion: No.

In Water Cooler ROI - Putting Social Software to Productive Work I pointed to some terrific research that uncovered the extent to which project work relies on communication (in various mediums) and how digital networks actual enhance productivity (with a 7% increase in one case). More fuel for the fire comes from Why Project Networks Beat Project Teams, a study published in the MIT Sloan Management Review last month.

  1. cummings-170.jpg  (22.6 KB)

In our own Customer Forum, Rolf Isaksen (click here for blog's main page) recently asked: "Why do we need incentives to share?" Some of the follow-on conversation converged on "we don't" with some good pointer to experience and research supporting that premise. Rather, focusing on intrinsic motivation rather than rewards can net greater benefit and long lasting E2.0 success.

I found a common thread on process centric adoption in the Deloitte Center for the Edge's Social Software for Business Performance report and Michael Sampson's User Adoption Strategies book. This advice is reflected in my post on Emergineering from last fall.

Jordan Frank writes: At the Gilbane Conference last month I stood in for Greg Lloyd in the Portal or Enterprise Social Software: Which Collaboration Environment to Choose? panel with David Seuss (CEO, Northern Light) and Jay Batson (Co-Founder and VP, Acquia).

In my role as an emergineer, I talk a lot about best practices and how they can be leveraged in a given customer deployment. One practice that works in any sphere from email to social software and journalism is to write a good headline.

Since introducing the idea of Social Process Reengineering? earlier this week I've socialized it virtually and personally (at E2.0 Boston) with at least a dozen customers, bloggers, analysts and other leading thinkers.

Consensus on the concept was generally positive with a variety of feedback ranging from the matter that the "facebook" approach doesn't just work in the enterprise to the matter that the social, structural and business pain have to be taken into account for successful E2.0 efforts.

  1. NickGallShirt.png  (118.3 KB)
  3. RoboProgrammer-p33.jpg  (25.2 KB)

As much as I hesitate to introduce this term into social software lingo, I think it's exactly what Enterprises are doing with social software on the road to Enterprise 2.0 - striving for a fundamentally new way to work.

  1. SearchAskShare.png  (53.4 KB)
  2. Gustavo1.jpg  (9.6 KB)

I talked to two customers yesterday, both who came to me with some questions about attaching and linking to excel files. Easy enough, but before responding with a simple answer I challenged them: Why are you using Excel?

  1. Requirement.png  (79.4 KB)
  2. Requirement Table.png  (109 KB)
  3. RequirementTableExpanded.png  (112.8 KB)

Rather than thinking about communication, collaboration and KM software in terms of Return on Investment, isn't the real goal to achieve Return On Information?

After reading 10 Social Media Commandment for Employers, I was reminded of Blogging Policy = Blabbing Policy, a blog entry I wrote back in 2006 when the the "conversation" in the blog-o-sphere started to center on corporate blogging policies.

Enterprise 2.0 Social Software is appealing for many reasons, but a core value is the facilitation of emergence. Many in our community may quibble with McAfee's definition of Enterprise 2.0 but I think all will agree that the need to support emergence is a key trait. However, an emergent discussion shines a light on the interacting role of structure and emergence.

  1. 280px-Sand_dune_ripples.jpg  (8.6 KB)

Glen Alleman at Herding Cats offers really nice distinctions in Risks and Issues Are Not The Same. In the course of working with a lot of teams as they deploy TeamPage as a project wiki, I've seen a wide range of terms for project artifacts. The more these concepts are discussed and hashed out, the better.

At our market launch in 2002, I recall all kinds of skepticism passing off the wiki and blog markets as a fad. Today, with a complete social software platform and the most robust wiki framework on the market, we are skiing on Gartner's Slope of Enlightenment. Gartner reports that Social Software suites are headed for the trough of disillusionment (a good and necessary transition before hitting the slope of enlightenment), though our customer case studies show little illusion about the tangible and necessary business value delivered by Traction TeamPage. » Read Gartner's press release and ReadWriteWeb's report. ReadWriteWeb's writeup.

I found Tom Davenport's discussion of Why 1.5 is Greater than 2.0 by way of Bill Ives in Mixing Old and New School Communication. Davenport talks about the social reasons in favor of a blend between social and traditional approaches. I think an answer to How 1.5, in this context, is Greater than 2.0 is both social and structural.

Innovation starts with words, and ways to convey them.

These case studies are a taste of how ideas and issues turn into action, how tasks evolve from conversations and how boundaries have to appear to disappear for W2.0 ideas to meet E2.0 execution. See you at E2.0.

Recent posts by Michael Sampson, John Tropea and Thomas Vander Wal converge on the need for Enterprise 2.0 tools to smash the silos segregating content types and isolating workspaces.

  1. Silos-p75.jpg  (74.5 KB)

A tweet from John Tropea identifies our Kuka Systems case study as the "Seminal enterprise 2.0 task based / process solution." THANKS! I can't imagine a better endorsement of a case study, or the product supporting it.

This conversation started with Stewart Mader and continues with Bill Ives. While most of our customers run the easy installer and are up and running readily, many benefit from our front end advice as well as more formal professional services engagements. This exchange offers two simple benefits that are strategic to the customers and to the software producer (and, in turn, to the customers).