Enterprise 2.0 is one of those terms that’s been going around business circles for the past few years. I’m not sure it ever really meant anything sensible and I’m not sure it is a meaningful way to approach a very real problem in business.
The big problem we face in business is that of communication. We face challenges in communicating with each other, with our consumers, our staff and with other stakeholders such as boards, the general public and government.
If communication is the problem then I don’t really understand how enterprise 2.0 is the answer. Rarely has the answer to an actual business problem been to throw another layer of technology at it.
But if one more person suggests that simply installing YASMT (Yet Another Social Media Tool) as the solution to the problems of internal or external communication in business I will probably throw something (possibly a crying tantrum on the floor).
If anyone seriously wants to tell me that installing something like Yammer or Jive (both tools I’m a real fan of) or the latest trendy thing will miraculously transform a company into a happy tribe singing kumbuya around a campfire I’ve got some reality to introduce them to.
Success in changing how people behave in organisations rarely happens from randomly throwing tools into the workplace without a plan. I’ve been re-visiting Steven Covey’s 7 Habits of Highly Effective People (inspired by the MEGA NSW program) and these remind me of some important things that are also useful to consider when creating change within organisations.
- Habit 1: Be Proactive
- Habit 2: Begin with the End in Mind
- Habit 3: Put First Things First
- Habit 4: Think Win-Win
- Habit 5: Seek First to Understand, then to be understood
- Habit 6: Synergize
- Habit 7: Sharpen the Saw
These are all good points to keep in mind when embarking on an effort to change the way people behave. And behavioural change is the intended outcome of most enterprise 2.0 efforts.
Typically I see enterprise 2.0 programs rolled out in a big bang way, with little appreciation for the need to start small and to use an iterative approach based on results and feedback to improve and extend the program.
Alternatively I see the approach where an executive within the organisation notes that they already own product ‘x’ and just install it and call enterprise 2.0 done.
Each of these approaches has the seeds of its own failure built-in. Take up rates can be low, user behaviour may not be that desired by management without effective rules of engagement spelled out, results might be hard to measure if metrics were not part of the design.
In an ideal world people would think about the end they seek to create and determine a path towards it. The tools would be among the last considerations in this instance.
Instead the key considerations are people, how they behave now and any barriers to changing their behaviour. Also key is understanding why people might agree to change. Then last of all comes the technology that might assist in delivering the desired change.