Tag Archives: practice

Fifth Annual Enterprise 2.0 Conference Illuminates Current State of Social in Organizations

Milestone birthdays customarily spark reflection on the past and future of the celebrant. The Enterprise 2.0 Conference celebrated its 5th birthday last week with a solid program of pre-conference workshops, keynote speeches, and breakout sessions. The event, as always, provided attendees with a good feel for both the current state, as well as the future, of enterprise social software, networking, and business. This post will focus on insights, gleaned from the conference, about the here and now of social in the enterprise. A subsequent post will address the implications for its future.

Practice: A Bias Toward “How”

An early observation from the Enterprise 2.0 Conference was that several of the most visible “doers” of enterprise social were not participating this year. Dion Hinchcliffe, Gia Lyons, and David Armano (among others) were too busy helping customers plan and deliver enterprise social initiatives to attend. Their absence is, of course, a positive indicator of the current interest in, and embrace of, social activity in organizations.

Those who were at the conference also voiced a bias toward action. One of the most commonly heard pieces of feedback on the event was that the content focused too much on selling and justifying the concepts of E2.0 and social business. Attendees were looking for more information and knowledge about how to use social to successfully achieve business objectives. To paraphrase one attendee’s tweet, we get why, but thirst for how.

One tell-tale sign of this sentiment was the prevalence of the topic of adoption in informal conversations, despite it’s (intentional?) exclusion from the official E2.0 Conference program. Perhaps the early adopters who have attended multiple iterations of the conference have largely moved beyond adoption concerns, but the fresh faces at the event have not and asked for more of the kind of guidance provided in the pre-conference Practitioner’s Black Belt workshop.

Another indication of the need to understand how, as opposed to why, was the enthusiastically positive reactions to the conference sessions that dealt with topics such as organizational design and behavior, leadership, and performance management. Past E2.0 Conferences have conveniently put forth organizational culture as a bogey man standing in the way of adopting social behaviors and tools, without offering ways to affect cultural transformation. Several of this year’s sessions addressed concrete aspects of organizational change management. Most notable were the remarks delivered by Cisco’s Jim Grubb, Sara Roberts of Roberts Golden, Electronic Arts’ Bert Sandie, Deb Lavoy from OpenText, Amy Wilson of Wilson Insight, and Altimeter Group Fellow Marcia Connor.

Technology: Focus on Integration

It was clear before the conference even began that the topic of integration of newer social technologies with well-established enterprise systems would be front and center this year. While that topic was in the spotlight, the current lack of meaningful integration stood out against the talk of plans to integrate enterprise social software with other applications, systems, and business processes. The harsh truth is that the current crop of enterprise social software is dominated by stand-alone applications and suites – collaboration destinations that are not in the flow of work for most and that have created new silos of information and knowledge in organizations.

Enterprise social software vendors have begun to build and offer integrations between their systems of engagement and established systems of record (to use Geoffrey Moore’s crystal-clear terms) such as Enterprise Resource Planning, Customer Relationship Management, and Enterprise Content Management. However, most of these integrations assume that the social application/suite will be the place where people do the majority of their work. Data and information from other enterprise systems are brought into the social layer, where it can be commented upon and shared (socialized) with others. This flies in the face of reality, as evidenced by the limited success of enterprise portals deployments intended to create a personalized aggregation layer sitting on top of existing enterprise systems. People want to communicate and collaborate with others in the original context of specific business tasks. Accordingly, social technology should be embedded (or, at least, exposed) in the systems of record where decisions are made and business process activities are completed, not the other way around.

It was interesting to observe that the need to integrate with systems of record was primarily voiced by enterprise social software vendors exhibiting at the E2.0 Conference. Those vendors claimed that their customers are demanding these integrations, but the topic did not prominently appear in customer-led sessions or conversations. Only one system of record was universally identified as a critical integration point – Microsoft SharePoint. This observation seems to underscore deploying organizations’ preference to communicate and collaborate directly in systems of record.

There was also much discussion of the need to integrate social into business processes themselves. A prominent theme from the E2.0 Conference was that enterprise social software can, and should, support specific business processes to make them more transparent and efficient. Presentations and vendor demos at the event revealed that the current generation of enterprise social software can effectively speed resolution of process exceptions through expertise location and engagement features. However, integration with normal business process activity is essentially non-existent in most enterprise social software offerings, and the vision of social process support remains unfulfilled.

Summary

The 2011 Enterprise 2.0 Conference Boston was a very well run event that provided attendees with a fairly clear picture of the current state of enterprise social practices and technologies. It is clear that practitioners are past experimenting with social concepts and technologies and have moved on to applying them in their organizations. However, it also clear that practitioners need more information on how to organize for, lead, and incent social business practices. Social technology adoption remains a key concern for the second wave of adopters.

Over the last 5 years, enterprise social software has matured and added functionality needed to build comprehensive, enterprise-ready systems of engagement. However, integration of that functionality into the flow of work – within traditional enterprise systems of record and business processes – has yet to be achieved. It will be interesting to see if that marriage of social and transactional systems can be accomplished. If it can, we will have created next-generation technology that supports a new, better way of working.

This entry was cross-posted from Meanders: The Dow Brook Blog

Advertisements

You Are Your Organization’s Chief Collaboration Officer

I Want You!There have been a couple of interesting blog posts about organizational collaboration leadership penned recently by respected, influential thinkers. Last week, Morten Hansen and Scott Tapp published Who Should Be Your Chief Collaboration Officer? on the Harvard Business Review site. Yesterday, Dion Hinchcliffe posted Who should be in charge of Enterprise 2.0? on Enterprise Irregulars.

It is logical that the question of the proper seat of ownership for enterprise collaboration efforts is being raised frequently at this moment. Many organizations are starting the process of rationalizing numerous, small collaboration projects supported by enterprise social software. Those social pilots not only need to be reconciled with each other, but with legacy collaboration efforts as well. That effort requires leadership and accountability.

Both of the posts cited above – as well as the comments made on them – add valuable ideas to the debate about who should be responsible for stimulating and guiding collaboration efforts within organizations. However, both discussions miss a critical conclusion, which I will make below. First, allow me to share my thoughts on the leadership models suggested in the posts and comments.

While it is critical to have collaboration leadership articulated and demonstrated at the senior executive level, the responsibility for enterprise collaboration cannot rest on one person, especially one who is already extremely busy and most likely does not have the nurturing and coaching skills needed for the job. Besides, any function that is so widely distributed as collaboration cannot be owned by one individual; organizations proved that long ago when they unsuccessfully appointed Chief Knowledge Officers.

Governance of enterprise collaboration can (and should) be provided by a Collaboration Board. That body can offer and prescribe tools, and establish and communicate policy, as well as good practices. However, they cannot compel others in the organization to collaborate more or better. Yes, Human Resources can measure and reward collaboration efforts of individuals, but they can only dangle the carrot; I have never seen an organization punish an employee for not collaborating when they are meeting other goals and objectives that are given higher value by the organization.

There is only one person (or many, depending on your perspective) for the job of actively collaborating – YOU! Ultimately, each individual in the organization is responsible for collaboration. He can be encouraged and incented to collaborate, but the will to work with others must come from the individual.

Collaboration in the enterprise is similar in this regard to knowledge management, where the notion of Personal Knowledge Management (PKM) has been gaining acceptance. PKM advocates believe that having each member of the organization capture, share, and reuse knowledge, in ways that benefit them personally, is far more effective than corporate mandated knowledge management efforts, which generally produce benefits for the enterprise, but not the individuals of which it is comprised.

So it is with collaboration. If an individual does not see any direct benefit from working with others, they will not do so. Conversely, if every employee is empowered to collaborate and rewarded in ways that make their job easier, they will.

The Enterprise 2.0 movement has correctly emphasized the emergent nature of collaboration. Individuals must be given collaboration tools and guidance by the organization, but then must be trusted to work together to meet personal goals that roll-up into measures of organizational success. The only individual that can “own” collaboration is each of us.

Back In The Saddle Again

horseback-cowboy

I am pleased to share with you that I have rejoined the workforce today, after having been unemployed for 3.5 months. I am now Lead Analyst, Collaboration and Enterprise Social Software Practice, at the Gilbane Group. I am honored and thrilled to be associated with Frank Gilbane and his stellar roster of analysts and consultants.

For those of you who are not familiar with the Gilbane Group, they are one of, if not the, preeminent analyst firms focused on Content Management practices and technologies. In my new role, I will be heading up Gilbane Group’s Collaboration and Enterprise Social Software Practice. As a practice, we will be working with many constituents to define and deliver on a research agenda examining industry trends related to enterprise collaboration tools and social software. However, our analysis will be different from others’ in that it will focus intensely on the content management aspects and implications of collaboration and social software.

I am very excited to have been blessed with this opportunity to lead a practice, especially at a firm of Gilbane Group’s caliber. I will have much more to say about my new job, collaboration, social software, and content management in the days and weeks to come. I will continue to blog here about the broader aspects of collaboration and social media, but you will also be able to find my thoughts on the content management angle of those technologies at the Gilbane Group Blog. I will, of course, continue to use Twitter to publically explore these subjects as well.

Here is how you may contact me at the Gilbane Group and the URL for the company’s blog:

email: larry@gilbane.com

phone: 617-497-9443 x154

blog: http://gilbane.com/blog