Newsletter Sign-Up FaceBook del.icio.us Twitter Subscribe

Archive for the tag 'enterprise 2.0'

Ben Kepes

First published at CloudAve

At last year’s Enterprise 2.0 conference in San Francisco, the highlight presentation for me was one given by Kathleen Culver and Greg Lowe from Alcatel Lucent. Their presentation was an excellent look at some of the benefits of Enterprise 2.0, and then some of the detrimental impacts that those benefits can bring.

Last week I posted about one of these very pitfalls, telling the tale of social media being used in a professional setting by a bully trying to build themselves up by dragging others down. Enterprise 2.0 Adoption Council founding member, practitioner and thought-leader Susan Scrupski left a comment reminding me of the presentation Greg and Kathleen gave. I reached out to Greg who graciously agreed to let me use the presentation and write a blog post around it.

What’s interesting for me about their presentation is that, despite there being some skepticism about Enterprise 2.0 generally, most commentators are couching that skepticism in terms of “where is the value” type questions – looking to prove the real benefit from the tools we’re all evangelizing, These commentators tend to be a little hypocritical, using these social media tools to build their own personal brands while at the same time pouring scorn on the value of the same tools within the enterprise.

Kathleen and Greg however take the benefits the tools bring as a given, but then parse those benefits in terms of some real risks that go alongside them. They do so along several themes – flexibility, accessibility (both geographical and chronological, context specificity, information availability and retrievability.

It’s an excellent presentation and well worth a few minutes viewing.

Key is their summary – bear in mind these are two Enterprise 2.0 proponents who, despite understanding the risks, still see the value in the tools. Their advice in order to mitigate the risks?

  • Avoid “Alert Fatigue”
  • Unplug yourself
  • Focus on your audience
  • Make your smile count (in person)
  • Don’t be stupid (watch what you type)

Kathleen helpfully provided a link to the references they used in the talk. Again this reiterates a bit of a theme of mine relating to the perils of enterprise 2.0  definitely not a reason to avoid using the tools but something to bear in mind.

As part of a new offering that fellow CloudAve blogger Krishnan Subramanian and I are developing, I’m looking at doing some work in this space in the next few months – hoping to develop some whitepapers and practitioner guides touching on these issues – watch this space for more.

Ben Kepes

First published on CloudAve.com

I have a friend called Jennifer (name and details changed, obviously). At school she was a loner without many friend who, as loners often do, overcome loneliness by bullying smaller kids in the playground. Jennifer managed to gain “friends” by doing this, although they weren’t really friends, rather individuals who were scared that they’d become the target unless they joined in with Jennifer’s shenanigans.

Well, luckily for her schoolmates, Jennifer grew up, studies and entered the workforce where she was forced, at least to a certain extent, to forego her bullying behavior in the interests of fairness, due process and the common good.

Until today that is…

You see the advent of social media in its various guises has given Jennifer the opportunity to once again throw her weight around and make life difficult for others. Involved in a part of an organization that makes extensive use of social media type tools, Jennifer has a wide following in her vocational field and uses this following to bully others the way she used to use her heft to do so all those years ago in the schoolyard.

Now my enterprise friends will tell me bullying in the work place has always existed but social media and enterprise 2.0 tools have extended the reach an individual can communicative with – this is an unquestionably great thing when it comes to collaborating on specific projects, but it’s also a dangerous thing when used inappropriately.

I’ve spent long time talking with Enterprise 2.0 practitioners, attending enterprise 2.0 events and hearing about the barriers to adoption. Generally we’re grasping to find either good case study examples of enterprise 2.0 being put to work or fixes for the oft mentioned barriers to adoption – none of however 9at least in public) are prepared to front up and tell the stories of Enterprise 2.0 gone wrong and used for ugly purposes.

And in this we run a real risk – by burying our heads in the sane and not “outing” the dark side of social media, we play into the hands of those who view the blogosphere, Twitter and social media generally as a complete waste of space. If we don’t tell the stories, and develop ways of avoiding the pitfalls these tools enable, they’ll use the same tales to discount E20 outright.

So here’s a plaintive call to those using social media generally and Enterprise 2.0 tools more specifically: Don’t hide the use-cases that feel uncomfortable, rather use them as case studies, develop solutions and show that like a community of old, so too can a virtual community stand up and police its own.

Everyone would be a little happier if we did that…

Irwin Lazar

Bill Pray blogged today on the Supreme Court’s decision to take on a case involving the privacy rights of an employee’s use of a government-provided mobile device for personal text messaging. This case further highlights the growing concerns around privacy and compliance as companies embrace emerging communications applications. In almost every conversation I’ve had with end-user organizations the topic of compliance is front and center as they evaluate tools such as SMS, Instant Messaging, Microblogging, and social computing platforms. Our recent SRO session at Enterprise 2.0 in Boston explored many of these issues as well. Bottom line is that its wise to involve your governance and compliance officers early on in as you develop your enterprise 2.0 strategy.

Ben Kepes

This is the one in answer to a recent post by provocateur Dennis Howlett in which Howlett asked whether Enterprise 2.0 is in fact a crock. Moderated by David Berlind from TechWeb he had a bevvy of Enterprise 2.0 practitioners.

Therein lies the Big Lie. Enterprise 2.0 pre-supposes that you can upend hierarchies for the benefit of all. Yet none of that thinking has a credible use case you can generalize back to business types - except: knowledge based businesses such as legal, accounting, architects etc. Even then - where are the use cases? I’d like to know.

Five principles;

  • Workforce transformation
  • Business process/operations
  • Intellectual property/Privacy/governance
  • Religious wars (technology/generational biases)
  • Bottom line business benefits

Greg Lowe from Alcatel-Lucent talked about their desire to unlock institutionalized knowledge and enable collaboration. Berlind asks why that desire is any different now from in the past. Lowe’s answer was that tools and technologies available today enable those aims. Claire Flanagan from CSC and Bruce Galinsky from Metlife agreed that it’s the technologies that really enable the promise of sharing and co-creating.

Berlind asks how that actually transforms the workforce. Megan Murray from Booz Allen Hamilton says this is happening no matter – expectations are higher on both the organization’s and the employee’s sides. Enterprise 2.0 technologies are enabling that to happen faster, better and more readily.

Berlind asked about the cultural change that needs to occur within an organization. Bryce Williams from Eli Lilly agreed and said that they see Enterprise 2.0 as a gateway to moving the organization into a more open approach – it’s the “starter drug” to get the organization hooked on open communications.

Jamie Pappas from EMC mentioned that Enterprise 2.0 isn’t a cure all or fix all – it’s an enabler and relies on the advocates throughout the organization to adopt it.

Much discussion about business process – have we hit the wall in terms of agility? No – it’s just baby steps and there are profound benefits yet to be realized.

Governance, there is a culture shift happening and the technology needs to keep up. One good approach can be called “participatory governance” where those who have skin in the game develop the governance models for those tools but do so in concert with the traditional governance approached.

The intellectual property concerns. All panelists agreed that organizations need to stop not trusting their employees. People are generally inherently good and those who are not will always find ways to maliciously expose data. Sure put good governance in place but beyond that trust the people to do the right thing. “I can’t stop you from doing stupid things but I can make it visible when you do them”.

In terms of the business value the difficulty is that its very hard to show true metrics for the gains that can be made form enterprise 2.0 – there are significant anecdotal benefits that need to be extrapolated to an organization-wide benefit. Booz Allen Hamilton gave an example where a 3000 employee reply-all email was analyzed and once the cost of people replying and unsubscribing was taken into account, there was an internal cost of $250000 – enterprise 2.0 can solve many of those issues. Extrapolating that up through the organization, the contention is that if a simple thing like reply-all can create such costs for an organization, high level operations can drive huge benefits.

It was very much a case of the converted preaching to the converted – it’ll be interesting to see what the originator of the title has to say about what the panelists had to offer.

Ben Kepes

The one we’d all been waiting for – ever since the Rasmussen brothers announced Wave at Google I/O in May, we’ve been waiting for some hard examples of the power that Wave can bring. Gregory D’Alesandre (Dr Wave), Product Manager for Google Wave ran presented three examples of Wave integrations from Novell, ThoughtWorks and SAP.

Every time you use any sort of communication technology you’re trying to achieve a goal, to get something done. With Google Wave the idea is that rather than understanding the “end goal”, users can start a Wave which can conform with the shifting objectives over time. D’Alesandre gave an introduction to Wave for the one or two people in the audience who haven’t seen it before. He explained that Google use Wave internally a lot and they find that all current communication technologies are a poor replacement for face to face interactions however every now and ten it’s better to interact electronically (he gave the example of a 12 person meeting with everyone trying to talk at the same time) – Wave enables this mass interaction without so much noise (although I’d have to say it does introduce significant dissonance as heavy users of multiple person IM will know).

The Wave team has purposely avoided giving lots of lock-down options to Wave – if you allow people to lock their content down, Wave becomes very email-like – openness and flexibility increases the collaborative potential.

D’Alesandre talked about Wave as a platform and invited their platform partners to show their offerings.

First up Alexander Dreiling, Program Manager from SAP who demoed two gadgets that SAP has built – Gravity is a gadget that allows business process modeling to be collaboratively built. See the demo video below;

Second up, Chad Wathington, VP, Product Development, ThoughtWorks demoed the integration of Wave with a software development project management tool. I covered the offering in more depth in another post but basically it allows for tasks to be created relating to a project all from within Wave and have them reflected in the project management tool. As I said in my post – this integration doesn’t show much more than could be achieved with a standard email/PM integration.

And lastly Andy Fox, Vice President Engineering from Novell showed their integration using the Wave federation protocol – Pulse. Pulse aggregates multi channel communication as well as a list of relevant contacts – it’s effectively a social CRM/communication offering. It brought to mind Gist’s offering and, while it helps aggregate lots of data, it does little to ease the burden of the firehose of information. The addition it does bring is the enablement of visibility in real time – but it does raise some question as to the value of asynchronous vs synchronous communications.

Some interesting integrations… but yet again nothing entirely ground breaking.

 

 

 

 

Ben Kepes

First posted on CloudAve

Andrew McAfee, from the Center for Digital Business, MIT Sloan School of Management, believes we’ve reached a tipping point in terms of the acceptance of the tools and techniques of enterprise 2.0.

McAfee sees some positive signs and some danger areas - “We have the opportunity to snatch defeat out of the jaws of success”. The way that’ll happen;

  • Declare war on the enterprise
  • Allow walled gardens to flourish – an interesting analogy to Napoleonic land division in Paris where smaller and smaller lots were created all divided with hedgerows – let’s not go there…
  • Accentuate the negative – the risks aren’t quite as bad as people make out, don’t dwell on them
  • Try to replace email
  • Fall in love with features - “what’s the simplest possible thing that could work”
  • Overuse the word “social”

Andrew is the father of the Enterprise 2.0 term – while his shtick is getting perhaps a little tired – he’s still got a valuable voice to add to the discussion.

Ben Kepes

First posted on CloudAve

A live blog of the presentation….

Christian Finn, Director of SharePoint Product Management, and Alina Fu, Product Manager, Social Computing talk about the SharePoint 2010 offering.

An interesting approach – Christian and Alina ran a “speed dating” session trying to message the major thrust of 2010. Christian pushed the big customers who use SharePoint to collaborate and, with honesty, admitted the failings of an ActiveX-centric approach.

Personal connections, finding subject matter experts, consumer features for the enterprise. 2010 has a dynamic newsfeed directly to an individual site. Personal profiling linked with contextual search.

2010 has a better user experience across blogs and wikis – unleashing the creativity of the users. Enabling the use of podcasts within the product.

User rating and commenting of content inside or outside of SharePoint. Tagging linked to newsfeeds.

The security question - “It’s Microsoft so it’s safe”. Content management extends to the social media content.

Flexibility – 2010 enables advances customization, within the browser for an individual user or a team. A full range of APIs and tools to customize the look, feel and functionality.

And the speed date is over… And the audience goes wild… (not so much)

Ben Kepes

First posted on CloudAve

Tammy Erickson, President of nGenera Innovation Network proclaimed that 2009 will be remembered as the year of “A-ha!”. Her presentation was very much in the spirit of Alvin Toffler’s Future Shock. Erickson pointed out some problems impacting upon the adoption of enterprise 2.0 and the changes needed to mitigate those problems. She believes that the train is leaving the station for enterprise 2.0 but that the fundamentals need to be addressed.

Problem #1;

  • Old approaches have been mastered
  • Technology enables a very different level of performance
  • Competition will shift the playing field

Erickson believes that Enterprise 2.0 is as game changing as the telex was in days gone by. The twentieth century icons where those who had the ability to master scale and cost. The steel mills, the auto makers. Today’s organizations are simply not optimized for the future. Reason #1 - they’re optimized with;

  • Division of responsibility
  • Specialization
  • Strict accountability – providing excellent control

Going forwards though, enterprise 2.0 mobilizes intelligence;

  • The utilization of complex knowledge
  • Innovation through the contributions of many
  • Harnessing the smallest units of knowledge

Reason #2 - traditional organizations are underpinned by;

  • Loyalty, reciprocated with protection and care
  • Individual autonomy
  • Identification with organizational units and individual managers
  • Based on planning

Whereas new organizations have different assumptions;

  • performance based arrangements
  • collective purpose
  • identity with shared objectives
  • they’re based upon coordination not planning

The ten factors that shift organizations – enables of collaborative capacity.;

  1. Highly engaged, committed participants
  2. Trust-based relationships
  3. Networking opportunities
  4. Selection, promotion and training based on collaboration
  5. Organization philosophy supporting a “community of adults”
  6. Executives who create a “gift culture”
  7. Leaders with both task and relationship management skills
  8. Productive and efficient behaviors and processes
  9. Clearly defined individual roles and responsibilities
  10. Important challenging tasks

Reason #3 – The strategic role. Today the paradigm is

  • This is something we have to do to keep Gen Y happy – the recession put paid to that!
  • It’s extra, nice to have like fitness centers and day care
  • We don’t even know what “it” it

Contrasted with the future organization

  • 2.0 supports a broad range of activities – with clear business objectives
  • Each best achieves through different organizational approaches and supported by different technologies

Driving outcomes through collaborative intents;

  • Connect previously unrelated ideas
  • Access untapped people or expertise
  • Distribute work or risk
  • Co-create
  • Detect emerging patterns or trends
  • Pool judgments
  • Determine group-wide preferences
  • Air and debate multiple views
  • Influence views or norms
  • Coordinate in time and space

Problem #4 – The technology itself. The concerns are;

  • It’s overwhelming – and difficult to harness
  • The solutions are heterogeneous and disconnected
  • Not secure or necessary relevant

The coming realities;

  • Unifying approaches
  • Ways of partitioning and aggregating data
  • Ability to manage relationships

Problem #5 – Engagement

  • Management 101 dictates
  • Directed activities
  • Clear instructions

Participation 2.0 means;

  • Individual discretion
  • Dealing with rich content that flows through infinite links
  • Forming and maintaining complex relationships
  • Having trust, a stake, a voice, an impact and a community bond
Ben Kepes

First posted on CloudAve

Oliver Marks and Sameer Patel – two of the leading lights in Enterprise 2.0 (that is experience in actually doing it rather than merely talking about it) presented this session. Their aim with the session was to move from “pontification to real world discussions” – a noble objective.

In discussing “the Big Idea” around Enterprise 2.0,the presenters pointed out that the ultimate sell comes from articulating the realistic business value propositions – Enterprise 2.0 technologies are just that, technologies. They’re not a holy grail of themselves and their needs to be a valid business case to sell the change. They cautioned attendees from comparing the business case for Enterprise 2.0 with the general Web 2.0 trends – web 2.0 is fundamentally a desire driven activity, whereas in a work setting people generally want to do their 9-5 and do what they have to do – no more.

People’s fundamental driver is “What’s in it for me?” – those trying to ease adoption of Enterprise 2.0 need to realize this and provide some sort of value to those making the decisions and end users. Understand the incentive structure in place, the politics and culture of the organization and the people within it.

In terms of the governance, risk management and compliance discussion, Oliver and Sameer recommended that this discussion happens early and happens openly. Discuss the issues and the plans at an early stage in order to (hopefully) get them onside. Explore the real reasons for negativity – is it really because of risk or is there a hidden agenda at work?

Oliver gave some examples of the ad-hoc shadow IT department that exists within many enterprises – where people faced with rigid and difficult enterprise grade software use cloud services like Zoho and Google docs in order to simply get their job done. It’s important to frame the context of the solution for management – help them understand the landscape within which the solution exists.

Joining the presenters before the break were a panel made up of Chris Mcgrath from ThoughtFarmer, Scott Schnaars from Socialtext and Tom Kuegler from PBWorks. Some points from their panel;

  • Scott advised looking at the other priorities the CFO may have to balance against the enterprise 2.0 proposal.
  • Chris brought up the reality that most collaborative solutions will come up against SharePoint and corporate IT will often take the perspective that collaboration happens only through SharePoint.
  • Tom suggested that the only approach that was really viable was to kneecap IT in order to get solutions moving within an organization – using a bottom up approach to prove the initial concept to the business.
  • Chris raised the point that you can build a fantastic collaborative platform within Sharepoint – but that you have to physically build it. Third party products enable those collaborative gains to be made more quickly then a complete design and build process.He also suggested that gains through social software tend to be serendipitous – as such it’s very hard to show a ROI pre deployment – how do you put metrics on serendipitous gains?
  • Tom said that the approach really needs to be one of replacement – it’s no use going into an enterprise trying to pitch a tool which is completely different to what they currently do. Enterprises prefer like-for-like comparisons and replacements.
  • Chris suggested that internal salespeople trying to pitch an idea to internal management utilize the assets of the vendors who are pitching everyday – tell them the requirements and let them help create collateral.

With getting executives on board it is critical that the requirements gathering is robust. Sameer discussed the “switching costs” involved in adopting new technology. It’s not simply the CAPEX involved in deploying a solution; there’s the business risk, the training, the deployment time etc. Ensure your proposal utilizes case studies from organizations in a similar space – make the pitch attuned to the company itself.

In terms of execution planning always be looking to mitigate the risk of the project and ensure you develop the right metrics to track expectations and actuality.

Oliver and Sameer invited Bevin Hernandez from Penn State University Outreach to tell their tale of developing sand deploying a social software offering. Their project planning document is interesting (image below and, yes, it’s the back of a napkin). For a more in-depth view – check out this post on the ThoughtFarmer site.

3254121850_bbfe3b51b4_o

All in all it was an interesting session. I’ve posted before about Enterprise 2.0 and specifically the problems needing to be overcome to ensure its adoption and success – it’s nice to spend a few hours discussing more than just the shiny gadgets but an in-depth look at what can make this stuff actually happen.

Ben Kepes

First published on CloudAve.

In two weeks time I’ll be winging my way across the world for the inaugural San Francisco holding of the Enterprise 2.0 conference. As is the norm before large events like this, the emails have started pouring in already asking for times for briefings on products and services to be released during the conference.

In a bid to save frustration on all sides, and as a suggestion to my fellow media attendees, I thought I’d publish here my simple guide to securing time with me (bear in mind there’s hundreds of companies going to be at the event, I’m in SF for just one week and I like to sleep from time to time);

  1. Please make it relevant. I’m a Cloud computing and SaaS guy with an interest in business process software and the culture shift needed to ease adoption of “Enterprise 2.0”. Sorry but there’s a bunch of things that simply aren’t in my sphere of interest. Please do some research and read my stuff to get a feel for what will interest and be relevant to me
  2. I live in New Zealand, that’s a long way from SF and is in an entirely different timezone – if you want to engage me in a pre event briefing (something I’m not at all against), please take the time to work out when might be a suitable time for me. While I’m a very early riser who partly works in Pacific time, 3am is not a good time to be showing me the latest micro-blogging service for enterprise
  3. Find out ways to engage me when you’ll get good attention. I’m a fitness fan and jog most mornings, especially when attending high-stress events like Enterprise 2.0. If someone comes to me and suggests a chat over a leisurely 5 mile run they’re likely to capture my undivided attention – it’s a good opportunity!
  4. Work out what pushes my buttons – we all get jaded from lots and lots of calls and a million and one “me too” offerings. Find some way to reach out to me (and Cocktails are definitely NOT my thing) and your chances go up exponentially. I’ve written fairly extensively about a couple of companies lately precisely because their PR people connected with me in all the right ways – this is in no way a “pay for play” situation, merely a way to ensure you’re heard above the hubbub

So there you have it – a simple four step guide to ensuring your investment in media relations pays off. I’d be interested to hear what my fellow media attendees thoughts are….

Next »