Monday, 15 September 2008

The Enterprise 2.0 Rulez

Talking of Key Forums, it reminded me that I had a list of rules that Paul McDonald from Gilbert + Tobin put forward for discussion in his presentation at Enterprise 2.0 - I thought it worth republishing them here to give you something to think about:

  1. Don't forget the user! You are building it for them, so always keep them in mind.
  2. Content rules: should there be any?
  3. Trust in your employees.
  4. Retain a high level of user input and autonomy.
  5. Easy to operate: can't afford another layer of cost i.e. training.
  6. Empower the user to create a set of rules as they develop their use of the technologies and online spaces.
  7. Do not implement unless it is going to make life easier for the user or relieve the burden from other information systems.
  8. A bit at a time - do things slowly and not all at once to build confidence and maintain interest.
  9. "Please explain" - understand what it is you're talking about. Think about what particular Enterprise 2.0 component you want to introduce, what it will offer and why you want to introduce it. Do you use it in "real life"?
  10. Assumption is the mother of some very bad things - talk to your users, and establish what it is they want. Remember they are unlikely to tell you that one of your ideas if terrible. Factor this in.
  11. Don't try to run before you can walk - 2.0 is unlikely to fix obvious flaws in your 1.0 systems and processes. Blogs don't save dogs.
  12. Keep it simple stupid - if it's harder to use than Google, then go back and try again. If you're coming second to Google you might as well be coming last.
  13. Training is for toddlers and monkeys - the Internet changed the world, and it didn't come with an instruction manual.
  14. "Plans are useless, but planning is indispensable" - if your plan has more than 2 pages, throw it away. If it has fewer than 3 drafts, keep planning.
  15. There are enough rules in the world, and far too many wannabe policemen.
  16. Don't try to fix a problem than doesn't exist.
  17. Keep your BS detector on full bore. If something sounds like it'll cost a lot of money or will involve consultants in flash suits, you should hear a beeping sound. And the you should run in the opposite direction.
  18. Once you know the rules you can break them.

The idea is to get your thinking - during his presentation, Paul asked us to discuss if we agreed or disagreed with any of these rules, and if we wanted to add any new rules. So feel free comment away!

1 comment:

  1. Nice list! I agree with most of them. A short comment: I agree with 'not too much training'. But I do find we should train each other to improve our e2.0 skills, like blogging and wiki usage. Getting together regularly with colleagues to talk about how you use these tools can be very inspiring. Having everybody sort things out for themselves is very unproductive.


Note: only a member of this blog may post a comment.