Updates from January, 2010

  • The Personal Enterprise

    Jevon 12:04 pm on January 4, 2010 | 1 Permalink | Reply

    Pete and I have been talking a lot about our Organizational Design work as we have reflected back on 2009 and what that means in terms of Social Business Design as we go forward. For each piece of strategy that we deliver, we always need to be able to back it up with concrete changes at the organizational level for customers who are ready to act. There will be a post from me on the Collaboratory (You can subscribe to the RSS feed here) later this week with some more thoughts on this.

    The reason I bring that up is that in looking at better ways that an organization can operate, we often look at the current service delivery model. How are services shared, delivered and managed? Which functions and resources are centralized and which are distributed? Does centralization mean less flexibility? Does distribution mean less reliability? We look at services inside the organization through the lenses of People, Process and Technology.

    This is a long way of saying: I’ve been thinking about “shared services” and how that concept is going to change very soon.

    Then over the weekend JP wrote about the The Facebookisation of the enterprise.

    JP’s dream is more than just the Facebookisation of the enterprise, he is talking about the personalization of the enterprise.

    imagine an “enterprise” world where:

    • You chose your own phone
    • You chose your own portable computing device (which may be your phone)
    • You chose your own desktop computing device (which may be your television)
    • You chose the operating systems you put on these devices
    • In other words, the IT department had “lost control of the device”.

    I’m not sure whether we need IT departments to “lose control” of the devices used for work, so much as we need them to “give up control” of the data that is available to whatever devices the user chooses. I think that the Personal Enterprise is one where the definition of “shared services” includes thinking about what the user provisions for themselves, not just what is given to them.

    The personalization of the enterprise is already happening. It couldn’t be more obvious these days. People are literally carrying two laptops and two cellphones with them. Sit down in any meeting (although I notice this trend far more in the US than in Canada right now) and you can be sure that a handful of the people there will reach in one pocket for their Blackberry, and then they will reach in to another pocket for their iPhone.

    How do Police officers coordinate and communicate while working? Ask some of them: More and more it is happening on their personal cellphones. The radios and dispatch systems provided by most police departments are insecure, lack privacy and have centralized dispatching.

    So, where do you draw the line? Where is the walled garden and where are the open spaces? I think this is the trick, and where a lot of enterprises will get caught.

    The Personal Enterprise (or the Facebookisation of it) is not about picking and choosing which services get opened up and which have controlled delivery, instead it is about opening up as much data as possible and creating an ecosystem that allows personalization to be developed.

    We are now coming out of an era where IT delivery was more efficient when it was done as an end-to-end controlled process. I do not believe that has been anything malicious or wrong about how things have been done to date. Controlling the platforms, devices and information that the end user can have access to was simply more efficient: Laptops were expensive, so you wanted to do a volume deal. Blackberries and service plans were very pricy, and then you needed a “Blackberry Enterprise Server” on top of that, and that only really worked with a full on Microsoft Exchange server setup.

    Don’t forget how much Databases (still) cost. Doing millions of transactions? You used to have just a few options. For some of your data those are still your options, but you can now deploy MySQL or Postgres at a web, departmental, workgroup and even personal computer level. So you have 4 of the 5 major database types covered right there with free and highly reliable software.

    Lets also not forget how “standards” never really used to be standards at all. They were lock-in tools, and the vendors who supported them gave you just enough rope to hang yourself. Having DCOM flashbacks here. Now you can feel free to tell your vendor to bake that RESTful API in from the start, otherwise you are happy to have it built yourself.

    Open the data and create incentives for developers and designers to create practical and beautiful things. Users will scream loudly, designers will listen and developers will build. Utopia perhaps, but not far away to be honest.

    The thing that is standing in the way of the Personal Enterprise is that we believe that being complicated is a prerequisite for IT. The truth is however that the services that mean the most to end users are some of the simplest and need the least “engineering”. They are rich profiles, SMS (or BBM) messaging, Email, phone and document sharing.

    The personalization of the enterprise is happening in communication first, and the sooner that IT departments can get out of the communication business and focus on data, then we will be in a much better place.

     
  • Etherpad is now Open Source

    Jevon 12:06 pm on December 21, 2009 | 0 Permalink | Reply
    Tags: collaboration, hivemind, open source

    This is worth taking note of in the enterprisey world: Etherpad has gone open source and it immediately becomes one of the best Enterprise 2.0 tools available. It is built on a Java/Scala/Mysql stack.

    Etherpad is a real-time collaborative editing tool. In short: you can work directly on editing text with other people and be fully aware of what they are doing. In Social Business Design terms it is the ultimate in Hiveminded content creation tools.

    Here is a document I created that you can also edit. It is Public.


    If you go to the doc you will see just how simple the environment is. No fancy word processing features, just straightforward Rich Text editing.

    A lot of energy inside organizations is spent writing documents, sharing notes and creating small pieces of text. Until now, as a public webservice, etherpad hasn’t really been an option for mid-large organizations. Writeboards were an attempt to solve this problem, but they have been a huge pain to use well in my experience.

    Why did it go open source? The team behind Etherpad has been hired by Google to start working on Google Wave.

    Which brings me to my next point. You can think of Etherpad as a sort of useful and focused version of Google Wave. Where you probably said “Why would I use this?” or “What does this do?” when you tried Google Wave, you will know immediately how Etherpad could be used in your organization.

    I am hopeful that Etherpad development will continue now that it is Open Source, but it is hard to tell if that will be the case. Integration in to existing enterprise systems (specifically ECM and Document Management systems) will not be simple. There is a lot of work ahead.

    In the meantime, you can try Etherpad at iEtherpad.com or just play around in the document I created. Etherpad.com itself will not be live for much longer.

     
  • Interview with Shel Israel on Enterprise Social Media

    Jevon 7:32 am on July 18, 2008 | 2 Permalink | Reply

    Shel just published an interview he did with me about using Social Software inside the enterprise.

    For all the shit he has taken lately, I have to say that Shel is a great interviewer who did his homework first and certainly made me feel comfortable and in control through the process. None of the usual stuff where the reporter is just fishing for a particular angle.

    Go read it if you dare, it was fun to do some reflecting on the past and thinking about the future again.

     
  • What should be free and what should you pay for?

    Jevon 9:28 am on June 9, 2008 | 5 Permalink | Reply

    Figuring out what’s what in Enterprise software is tough, and it is definitely no easier when it comes to choosing Enterprise 2.0 tools.

    So, a question comes up: What should you pay for, what should be cheap, and what should be free?

    What should you pay for?

    Support
    This is a lot more critical than you realize. Having reliable and reasonably priced support is critical to making sure that you don’t disappoint your users.

    Vendors used to traditionally “milk” their customers when it comes to support fees. This is changing as more and more minor support issues are handled by user communities. This is an example of Enterprise 2.0 eating its own dogfood. Vendors and consultants are then able to offer much more focused technical support without having to worry as much about the “It’s all in spanish?!?!” calls.

    Data Backup and Accessibility
    Most people would say that this should be free. I agree: It should be. But it is also something I am more than willing to pay for. Ideally, you can set up an external repository, such as an Amazon S3 account or a private file vault inside your own datacenter. If you are using a SaaS vendor, then they should automatically back up to this external repository in a non-proprietary XML format.

    The reason that you should pay for this is so that you can ensure some sort of minimum service level. If something goes wrong, you don’t want to find out that all your backups are a week old.

    User Experience
    We all like to think that design comes cheap. And sure, you can go on Elance and get a cheap graphic designer who can make something reasonably pretty. The truth is however that because every organization is different, you are going to use software in different ways. You need to be willing to invest in the User Experience if you plan to keep your users happy.

    Many pieces of new software look really nice, but when you start using them, the experience degrades quickly. Non-standard interfaces and poor design decisions are the primary culprits.

    Future Innovation
    This is a hard one to measure, and you can only really base you decision off past performance. Will this vendor or developer keep innovating and updating tools in the future? The reason you need to be willing to pay for this is that they need to put food on the table as well.

    What should be cheap?

    Hosting
    I believe that hosting and provisioning costs should be broken out and separated from software cost. Current SaaS pricing models obscure the hosting cost and bundle application delivery in with the cost of the actual software. This is a mistake for a few reasons, but the primary one is that highly reliable vendors cannot easily differentiate their service level from a cheaper alternative. Everyone makes the claim “99.99999% uptime”, but it actually means very little.

    If single vendors allowed multiple choices for delivery, then the customer could choose what their comfort zone is in terms of cost.

    Integration
    Integration is not a simple matter, but this is where your own IT folks need to play nice. You should expect them to know what the integration points are in your current infrastructure and they should be familiar with how to do that integration. Whether it is a link on a Sharepoint site, or access to an LDAP server, those options should not be difficult to execute on.

    What should be free?

    Design Patterns
    There really is no such thing as Intellectual Property in the Enterprise 2.0 world. The difference between one vendor and another is not that they know more than the other, it is execution and design capability. Some vendors are incompetent when it comes to integrating features, designing workflows and in paying attention to the overall flow and “tightness” of the product. Do not let yourself be sold on “proprietary” anything.

    Community Support
    Low level support provided by other users and the vendor itself should always be free.

    Deployment Speed
    There should be no premium to pay to get tools deployed quickly. Vendors should be ready to deploy a base platform immediately which can start adding value to your organization.

    What do you think

    There is no way I covered everything here. What do you think? What should be free? What should be cheap? What should customers pay big money for?

     
  • Annals of Enterprise 2.0: Picking up Drag Queens

    Jevon 9:44 am on June 4, 2008 | 15 Permalink | Reply

    My use of the term “Drag Queens” to describe some enterprise software companies was outed today by Vinnie.

    What did I mean when I said “old enterprise companies dressing up like a pretty E2.0 babe”

    Here is the story of Tim, an Enterprise 2.0 customer who is a little timid, but has decided go for it and party the night away.

    Dress up baby, we’re going out tonight

    Tim, a friend of Charlie, is out at a club, the lights are low, the music is loud and he has had a few drinks.

    The place is packed, and it seems like it is all new faces. Interesting people, great dancers and they are all buying you drinks. There are even a few celebrities hanging around. He dances until 3am, and before the lights go up, Tim ducks out the door.

    As he is walking home through the rain, Tim is feeling pretty good. He had a fun night of dancing, good friends and he now has a girl on his arm. She’s pretty and says all the right things.

    This story ends with an IT Project Failure, to say the least.

    Who is he/she anyway?

    The story is much the same for customers in the Enterprise 2.0 world. Those customers who are actually making purchases right now are a little timid and not sure exactly what to expect, and usually it was a friend who took them out to the party.

    When the lights go down and the drinks start flowing however, things aren’t as clear as they were before and it isn’t always obvious who you are getting in bed with.

    The Drag Queens of Enterprise 2.0 are those old Enterprise software vendors who haven’t done anything to change their products, but instead they went out and have bought a nice dress and have put some eye shadow on their football player physiques.

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
esc
cancel