• Home
  • About Jon Mell
Jon Mell – Web 2.0 ideas and strategy
  • Contact me

    If you would like my help with your Enterprise 2.0 project or strategy please contact me:
    Email: jonmell at me.com
    Phone: +447973257146
    Find out more about me
    Find Jon Mell on Linked In
    Find Jon Mell on Facebook
    Follow Jon Mell on Twitter
  • Subscribe

     Subscribe in a reader

  • Recent Posts

    • Business 2.0
    • Openness, transparency and MP’s expenses
    • Headshift hosting Breakfast event in New York
    • Best. Holiday. Ever.
    • See you later… and as a married man!
  • Follow me on Twitter...

  • Categories

    • Apple
    • Basketball
    • behaviour
    • blogging ROI
    • blogs
    • business process exceptions
    • clearspace
    • community
    • compliance
    • corporate facebook
    • cost saving
    • customer insight
    • Dell
    • democratising information
    • ease of use
    • email
    • Enterprise 2.0
    • facebook
    • facebook fatigue
    • Generation Y
    • Google
    • Headshift
    • IBM
    • Ideastorm
    • innovation
    • instant messaging
    • Jive
    • long tail
    • Lotus Connections
    • Lotus Notes
    • Lotusphere
    • MacBook
    • MacBook Air
    • mobile
    • Northern Rock
    • online community
    • pbwiki
    • Quickr
    • revenue growth
    • roi
    • sales
    • Second Life
    • social software
    • Starbucks
    • tagging
    • Thinkpad
    • Twitter
    • Uncategorized
    • unified communications
    • Web 2.0
    • Web 2.0 adoption
    • Web 2.0 behaviour
    • web 2.0 roi
    • wiki adoption
    • wiki roi
    • wikis
    • wisdom of crowds
  • Blogroll

    • A Portal to a Portal
    • AppleInsider
    • Caspar Craven
    • Colin Mooney
    • Collaboration Matters!
    • Connected
    • Ed Brill
    • Euan Semple
    • Idealpeople recruitment blog
    • Inside Out
    • Keri Owen
    • Luis Suarez
    • Mandy Shaw – iPerimiter
    • Ross Mayfield (Socialtext)
    • Stewart Mader
    • Trovus
  • Archives

    • June 2009
    • May 2009
    • April 2009
    • March 2009
    • February 2009
    • January 2009
    • December 2008
    • November 2008
    • October 2008
    • September 2008
    • August 2008
    • July 2008
    • June 2008
    • May 2008
    • April 2008
    • March 2008
    • February 2008
    • January 2008
    • December 2007
    • November 2007
    • October 2007
    • September 2007
    • August 2007
Jun 23

Enterprise 2.0 Conference… and a holiday!

Enterprise 2.0 3 Comments »

Am off to the Enterprise 2.0 Forum in Varese tomorrow – and taking the opportunity to spend some time out in Italy – so may not be posting for a week or so. I should stay active on Twitter though.

Am really looking forward to the conference, there’s quite a lot of buzz around it and am especially looking forward to meeting a lot of people I’ve got to know over the last year through blogging and twitter.

If you enjoyed this post, make sure you subscribe to my RSS feed!

Possibly related posts:
  • You can’t stifle debate
  • Off on holiday
  • How to make people engage with Enterprise 2.0 – your vote counts!
  • Share this:

    del.icio.us:Enterprise 2.0 Conference... and a holiday! digg:Enterprise 2.0 Conference... and a holiday! spurl:Enterprise 2.0 Conference... and a holiday! wists:Enterprise 2.0 Conference... and a holiday! simpy:Enterprise 2.0 Conference... and a holiday! newsvine:Enterprise 2.0 Conference... and a holiday! blinklist:Enterprise 2.0 Conference... and a holiday! furl:Enterprise 2.0 Conference... and a holiday! reddit:Enterprise 2.0 Conference... and a holiday! fark:Enterprise 2.0 Conference... and a holiday! blogmarks:Enterprise 2.0 Conference... and a holiday! Y!:Enterprise 2.0 Conference... and a holiday! smarking:Enterprise 2.0 Conference... and a holiday! magnolia:Enterprise 2.0 Conference... and a holiday! segnalo:Enterprise 2.0 Conference... and a holiday! gifttagging:Enterprise 2.0 Conference... and a holiday!

    Jun 21

    Product Packaging

    Apple 3 Comments »

    Have just finished reading Inside Steve’s Brain which talks about Apple’s obsession with packaging and the ‘unboxing’ experience.  Jobs is apparently obsessive about people’s first interaction with his product, and it should be as seamless and as in keeping with Apple’s overall philosophy as possible (such as the handle of the original iMac being the first thing you see when you open the box).

    Sounds neat, but maybe a little over the top.  That was until I ordered my Logitech presenter.  I used one at Lotusphere and it was great to be able to click through slides without having to return to a laptop.  It has to be the most difficult packaging to open ever.  It’s not a big device, just fits in the palm of your hand, and it comes in a moulded plastic wrap about the size of a greeting card.  Which is impossible to open.  It required scissors and a rather dangerous slashing motion with a sharp kitchen knife to get past the plastic.  Once open, the instructions for such a simple device had to be ripped out of their plastic wrapping and were completely over-engineered.
    Don’t get me wrong, it’s a great product, but the packaging has me already annoyed.  Maybe Steve has a point…

    If you enjoyed this post, make sure you subscribe to my RSS feed!

    Possibly related posts:
  • So why wouldn’t you blog?
  • Joining Headshift!
  • Jive Seminar – Building Communities to Grow Your Business
  • Share this:

    del.icio.us:Product Packaging digg:Product Packaging spurl:Product Packaging wists:Product Packaging simpy:Product Packaging newsvine:Product Packaging blinklist:Product Packaging furl:Product Packaging reddit:Product Packaging fark:Product Packaging blogmarks:Product Packaging Y!:Product Packaging smarking:Product Packaging magnolia:Product Packaging segnalo:Product Packaging gifttagging:Product Packaging

    Jun 20

    Organisations using twitter

    Twitter No Comments »

    I mentioned in a previous post that Jive were talking about Comcast paying people to monitor Twitter and engage with people having issues. Have just seen VMWare doing the same thing with Stuart McIntyre. Seems like a fantastic way to engage customers.

    Update – read more about Comcast on Twitter.

    Stuart: Busy morning already. Fighting to import VMWare ESX image onto VMWare Fusion on the Mac… 07:54 AM June 19, 2008 from twhirl

    VMWare: @stuartmcintyre Fighting? ESX image should just run on Fusion. Fusion VMs to run on ESX though, you have to run through VMware Converter about 3 hours ago from twhirl in reply to stuartmcintyre

    Stuart: Mentioned issues with VMware ESX/Fusion yesterday and got a reply overnight from @vmwarefusion. Vendors really are starting to get this… about 2 hours ago from twhirl

    Stuart: @vmwarefusion Thanks. The issue was that the disk image files came from ESX2 and were in flat format. Have converted on ESX3. Now works. Ta!

    If you enjoyed this post, make sure you subscribe to my RSS feed!

    Possibly related posts:
  • Twitter
  • Headshift hosting Breakfast event in New York
  • Corporate use of Twitter
  • Share this:

    del.icio.us:Organisations using twitter digg:Organisations using twitter spurl:Organisations using twitter wists:Organisations using twitter simpy:Organisations using twitter newsvine:Organisations using twitter blinklist:Organisations using twitter furl:Organisations using twitter reddit:Organisations using twitter fark:Organisations using twitter blogmarks:Organisations using twitter Y!:Organisations using twitter smarking:Organisations using twitter magnolia:Organisations using twitter segnalo:Organisations using twitter gifttagging:Organisations using twitter

    Jun 19

    Lotus Connections 2.0 Install Guide

    Lotus Connections 7 Comments »

    IBM has released Lotus Connections 2.0. The install process for pilots is greatly improved but there’s still some tricky steps if you’re doing an install for test, staging, proof of concept or production so I’ve updated my install guide for Lotus Connections 2.0.

    Please let me know if you have any ideas for improvements or corrections!

    Update: IBM have asked me to join a group of us helping to improve the Lotus Connections Infocenter.  Let me know if you have any feedback you want me to pass on.

    If you enjoyed this post, make sure you subscribe to my RSS feed!

    Possibly related posts:
  • Lotus Connections Install Guide
  • Help us improve the Lotus Connections Infocenter
  • This is why we do this
  • Share this:

    del.icio.us:Lotus Connections 2.0 Install Guide digg:Lotus Connections 2.0 Install Guide spurl:Lotus Connections 2.0 Install Guide wists:Lotus Connections 2.0 Install Guide simpy:Lotus Connections 2.0 Install Guide newsvine:Lotus Connections 2.0 Install Guide blinklist:Lotus Connections 2.0 Install Guide furl:Lotus Connections 2.0 Install Guide reddit:Lotus Connections 2.0 Install Guide fark:Lotus Connections 2.0 Install Guide blogmarks:Lotus Connections 2.0 Install Guide Y!:Lotus Connections 2.0 Install Guide smarking:Lotus Connections 2.0 Install Guide magnolia:Lotus Connections 2.0 Install Guide segnalo:Lotus Connections 2.0 Install Guide gifttagging:Lotus Connections 2.0 Install Guide

    Jun 19

    Jive Seminar – Building Communities to Grow Your Business

    Jive, clearspace No Comments »

    Attended the Jive Seminar on Building Communities to Grow Your Business yesterday. Was a great event and very well attended. Sam Lawrence from Jive stole the show with a very engaging presentation/discussion on the how’s and why’s of community building (both internal and external) without pushing his product.

    Here is a brain dump of some of the points made (probably how I would have live blogged it…)

    • On a non-scientific poll of the audience Sam thought there were definitely more people participating in on-line communities that he sees elsewhere in the world (close to 90% as opposed to an average of 50%). I think everyone in the room put their hand up when he asked if they read blogs.
    • Nike’s community is really important to them. They fly the ’stars’ of their community around the world to talk to other community members, and one is even the star of their new commercial. The community is about running not about shoes.
    • Gen Y will be 50% of the workforce in 6 years
    • Social software is happening now because it’s cheap and easy to get going
    • Comcast pay people to sit on Twitter and engage with people who have issues with them

    Here are some things I’m really glad they said as it fits in very neatly with what I’ve been talking about here:

    • It’s not about the technology, it’s the culture that will make or break “Enterprise 2.0″
    • The most important question to ask yourself is “what is my community for?” and tie metrics and your focus to that objective
    • The metrics and success criteria will depend on your strategy. The ROI or business value will come down to a business problem you are trying to solve – access information more quickly, product research with your customers, generate leads – and will be tied into the ROI of that initiative, rather than the technology having an innate ROI itself.

    All in all a great seminar, also good to see Jive with a permanent presence in the UK! Hope to be able to work with some Clearspace projects in the future…

    If you enjoyed this post, make sure you subscribe to my RSS feed!

    Possibly related posts:
  • Organisations using twitter
  • And it’s not just for big companies…
  • Headshift hosting Breakfast event in New York
  • Share this:

    del.icio.us:Jive Seminar - Building Communities to Grow Your Business digg:Jive Seminar - Building Communities to Grow Your Business spurl:Jive Seminar - Building Communities to Grow Your Business wists:Jive Seminar - Building Communities to Grow Your Business simpy:Jive Seminar - Building Communities to Grow Your Business newsvine:Jive Seminar - Building Communities to Grow Your Business blinklist:Jive Seminar - Building Communities to Grow Your Business furl:Jive Seminar - Building Communities to Grow Your Business reddit:Jive Seminar - Building Communities to Grow Your Business fark:Jive Seminar - Building Communities to Grow Your Business blogmarks:Jive Seminar - Building Communities to Grow Your Business Y!:Jive Seminar - Building Communities to Grow Your Business smarking:Jive Seminar - Building Communities to Grow Your Business magnolia:Jive Seminar - Building Communities to Grow Your Business segnalo:Jive Seminar - Building Communities to Grow Your Business gifttagging:Jive Seminar - Building Communities to Grow Your Business

    Jun 16

    How to sell Enterprise 2.0

    Enterprise 2.0, roi No Comments »

    Came across a presentation by Mike Kavis on how to sell SOA. It’s a great presentation and worth registering to listen to.

    I was struck by the parallels between how we try to position Enterprise 2.0 or Web 2.0 and his story around implementing SOA. His view on how they had been successful was:

    • They engaged the business in their language – profit and loss rather than technology. This key getting sponsorship for Enterprise 2.0 which is vital for successful projects. Even if we evangelists don’t like ROI, the people who sign the cheques do.
    • The business doesn’t care about governance. When implementing SOA the business wanted functionality implemented as soon as possible. Wikis and blogs are so easy to start up if an organisation is not careful they may end up relying on multiple unsupported technologies for business critical applications. IT has to get involved at some point to consolodate and standardise.
    • They now spend more time on cultural change rather than technology. Cultural change has always been the X-factor in any Enterprise 2.0 engagement.
    • My favourite quote from the presentation “it’s not about the technology, it’s about the people” would be at home in any Enterprise 2.0 presentation.

    So SOA faces similar challenges around cultural adoption as does Enterprise 2.0. The irony was that they used Enterprise 2.0 tools, blogs and wikis, to overcome their cultural challenges around SOA. These tools were seen as a way to spread knowledge around how to use a new business process management system to automate what had previous been paper based workflow.

    Wikis and blogs were not part of the cultural problem, they were part of the solution. It seems more and more likely that a compelling reason to use Enterprise 2.0 software, such as familiarity with a new system as in this case, or information that can help you sell more as discussed previously, is the silver bullet for adoption.

    If you enjoyed this post, make sure you subscribe to my RSS feed!

    Possibly related posts:
  • Broadband contract lengths
  • Web 2.0 ROI – cost saving or revenue growth?
  • Wikis as alternatives to email – find the ROI
  • Share this:

    del.icio.us:How to sell Enterprise 2.0 digg:How to sell Enterprise 2.0 spurl:How to sell Enterprise 2.0 wists:How to sell Enterprise 2.0 simpy:How to sell Enterprise 2.0 newsvine:How to sell Enterprise 2.0 blinklist:How to sell Enterprise 2.0 furl:How to sell Enterprise 2.0 reddit:How to sell Enterprise 2.0 fark:How to sell Enterprise 2.0 blogmarks:How to sell Enterprise 2.0 Y!:How to sell Enterprise 2.0 smarking:How to sell Enterprise 2.0 magnolia:How to sell Enterprise 2.0 segnalo:How to sell Enterprise 2.0 gifttagging:How to sell Enterprise 2.0

    Jun 12

    Web 2.0 ROI discussion at Web 2.0 Strategies

    blogging ROI, roi, web 2.0 roi, wiki roi 2 Comments »

    Was at the Web 2.0 Strategies forum today and took part in a social software ROI discussion. The discussion wandered quite easily onto the ROI of blogging or the ROI of wikis, and the features and functions of the tools. This has never really helped develop the ROI case for Web 2.0 or Enterprise 2.0 and didn’t in this case. It got more interesting when we turned our attention to a problem that Web 2.0 could solve (maybe using blogs or wikis).

    For example, if a software company has a problem where support calls cost too much, a wiki may be a good tool to lower the cost of fielding support calls. Jive Software recently quoted an organisation where phone support cost the organisation $12 per incident, whereas wiki support cost $0.25. A wiki therefore supports the ROI case for the reducing the cost of providing support – there’s no ROI for the wiki in it’s own right. It’s just that organisations that adopt Enterprise 2.0 can improve the ROI’s on many different projects.

    The conclusion I took away was that ROI only makes sense when applied to a specific business problem – then you piggy-back on the ROI of that business problem, rather than trying to make a generic ROI case for widespread wiki, blog, or social software adoption.

    If you enjoyed this post, make sure you subscribe to my RSS feed!

    Possibly related posts:
  • Web 2.0 Return on Investment (ROI)
  • Web 2.0, Web 3.0, Web 4.0, Web 5.0 – where will it end?
  • Wiki ROI Calculator
  • Share this:

    del.icio.us:Web 2.0 ROI discussion at Web 2.0 Strategies digg:Web 2.0 ROI discussion at Web 2.0 Strategies spurl:Web 2.0 ROI discussion at Web 2.0 Strategies wists:Web 2.0 ROI discussion at Web 2.0 Strategies simpy:Web 2.0 ROI discussion at Web 2.0 Strategies newsvine:Web 2.0 ROI discussion at Web 2.0 Strategies blinklist:Web 2.0 ROI discussion at Web 2.0 Strategies furl:Web 2.0 ROI discussion at Web 2.0 Strategies reddit:Web 2.0 ROI discussion at Web 2.0 Strategies fark:Web 2.0 ROI discussion at Web 2.0 Strategies blogmarks:Web 2.0 ROI discussion at Web 2.0 Strategies Y!:Web 2.0 ROI discussion at Web 2.0 Strategies smarking:Web 2.0 ROI discussion at Web 2.0 Strategies magnolia:Web 2.0 ROI discussion at Web 2.0 Strategies segnalo:Web 2.0 ROI discussion at Web 2.0 Strategies gifttagging:Web 2.0 ROI discussion at Web 2.0 Strategies

    Jun 11

    Case study on wiki use for revenue growth

    pbwiki, roi, wiki adoption, wiki roi, wikis 2 Comments »

    I attended a webinar last night hosted by PBwiki titled “Growing in a down market with PBwiki“. All in all it was very interesting. Here are the main points:

    The webinar went very smoothly. This is not to be underestimated, I’ve lost count of the number of webinars where there are problems with sound/video but this was great. Slides/screenshare and question submission was handled by GoToMeeting - and I was very happy to find out I could stream the audio via Ustream rather than have to pay for a 60 minute international call to the States. Video was snappy, and audio was crystal clear, made the experience much more enjoyable.

    The case study was RMC Vanguard, a mortgage company in the States which is experiencing the slowdown of the US mortgage market. The benefits they obtained from the wiki were as follows:

    • Time saving – wiki pages with frequently asked questions, links to important websites (with usernames and passwords where appropriate) were all included on the wiki
    • Productivity – with four underwriters serving fifty loan officers, and a habit of loan officers to keep asking a question until they got the answer they wanted, having a place where underwriters could post information rather than having it asked of them constantly made both the loan officers and the underwriters vastly more productive, which resulted in more time spent with clients which ended up with increased sales
    • Retention – there is a strong attrition rate in the loan officer role. Many role officers worked from home and struggled to remember the details to access internal systems once they returned to their home office, and felt isolated. How-to’s on the wiki increased their productivity when they first joined, which meant they earned more, which meant they were happier, which meant they didn’t leave
    • Improved customer experience – in a down market you need to retain customers. By providing loan officers with a single point of reference where they could obtain information in a fast changing market meant that they could answer clients’ and potential clients’ questions on the phone there and then. This led to a significantly improved customer experience and increased customer retention, which is essential in a down market.

    What was really interesting is that this successful wiki implementation hit nearly all of our principles of wiki adoption:

    • Targeted – there were clear reasons for the wiki – internet passwords, How-To’s for working from home and market information. There were also clear audiences who would use it slightly differently, underwriters (generally content contributors) and loan officers (generally content seekers). The motivations of each were addressed differently – for the underwriters posting wiki content stopped them being asked the same questions several times a day. For the Loan Officers using the wiki as a first point of call allowed them to provide an improved customer experience and therefore sell more.
    • Sponsorship – the wiki manager worked for the President of the company. Interestingly, he commented that during a ‘down’ period was actually a good time to introduce new technology, as people actually had some time to get used to it!
    • Marketing/communcations – a lot of company communications were pushed out on the wiki. A catchphrase developed in the office when people asked “where is…?” with the response “it’s on the wiki!”
    • Champions – there was a clear champion for the wiki who spent a great deal of time educating and working with users to ensure that the adoption was successful
    • Support – a lot of support was provided. Effort went into ensuring that templates were available so that people were not presented with a blank page when creating new content. Effort was put into ensuring the wiki was searchable so that people could find what they needed quickly. The wiki champion spent time one-on-one with staff to ensure they knew how to use it
    • Accessible – the wiki could be accessed by those who worked from home, which was key to driving adoption with the loan officers
    • Enforcement – people started to say “it’s on the wiki” when asked a question rather than providing the answer
    • Get rid of the old – the wiki champion slowly started to take away the old sources of information. After one week of information being posted into the wiki and one on one training showing the users how to find it, it was removed from its original source
    • Measure – this is the one principle not followed. Any measurement was word of mouth and anecdotal. Given adoption was so high, however, I can see why this was not a priority.

    When asked what the number one benefit that provided growth in a down market, the strong response was that it was the improved customer experience. RMC Vanguard won best customer experience award for mortgage providers in the US – and the wiki is seen to be key to this, and allowing them to cope with the downturn in the US mortgage market.

    Many thanks to both PBwiki and RMC Vanguard - it was a great webinar!

    If you enjoyed this post, make sure you subscribe to my RSS feed!

    Possibly related posts:
  • Wiki case study – collaboration
  • Instant Messaging ROI – IBM case study
  • Case study of corporate adoption of Web 2.0 and social networking
  • Share this:

    del.icio.us:Case study on wiki use for revenue growth digg:Case study on wiki use for revenue growth spurl:Case study on wiki use for revenue growth wists:Case study on wiki use for revenue growth simpy:Case study on wiki use for revenue growth newsvine:Case study on wiki use for revenue growth blinklist:Case study on wiki use for revenue growth furl:Case study on wiki use for revenue growth reddit:Case study on wiki use for revenue growth fark:Case study on wiki use for revenue growth blogmarks:Case study on wiki use for revenue growth Y!:Case study on wiki use for revenue growth smarking:Case study on wiki use for revenue growth magnolia:Case study on wiki use for revenue growth segnalo:Case study on wiki use for revenue growth gifttagging:Case study on wiki use for revenue growth

    Jun 10

    Principles of wiki and Enterprise 2.0 adoption

    Web 2.0 adoption, wiki adoption 1 Comment »

    There’s a great conversation going on at the Enterprise 2.0 forum community site around barriers to Enterprise 2.0 adoption. It’s probably one of the most common questions we come across so I thought I’d share our principles for successful wiki/Enterprise 2.0 adoption.

    • Targeted – there has to be a clear objective or problem that the platform solves. Preferably a small one so that you can run a small pilot at insignificant cost to see if it works or not. If it does, you can start to extrapolate an ROI – if it doesn’t, try again
    • Sponsorship – you need support from senior management if you want wide adoption.
    • Marketing/Communications – you need to market you community if it is external, and equally include it in formal communications if it is internal. It needs to be incorporated into a wider marketing/communications strategy and not left out on a limb as an ‘experiment’
    • Champions – they exist. Find them and support them
    • Support – you also need to support those who need it most, the second wave of adopters who may be scared/uneasy about using new technology
    • Accessible – if people run their lives on a Blackberry or work from home, make sure they have access!
    • Enforcement – if the answer’s on the wiki, point people to the wiki. Don’t give them the answer over email or over the phone
    • Get rid of the old – at some point, you’re going to have to take away the old way of doing things. If half the users think it’s too soon, and the other half think it’s too late, you’re probably right.
    • Measure. You won’t get it right first time. Get some metrics agreed (preferably around outcome not activity) and find a way to track them
    These aren’t particularly ground breaking, and only repeat what people like Stewart Mader have been talking about for ages, but these are principles that have helped us adopt Enterprise 2.0 software, and for our customers.

    If you enjoyed this post, make sure you subscribe to my RSS feed!

    Possibly related posts:
  • Wiki case study – collaboration
  • Case study on wiki use for revenue growth
  • Jive Seminar – Building Communities to Grow Your Business
  • Share this:

    del.icio.us:Principles of wiki and Enterprise 2.0 adoption digg:Principles of wiki and Enterprise 2.0 adoption spurl:Principles of wiki and Enterprise 2.0 adoption wists:Principles of wiki and Enterprise 2.0 adoption simpy:Principles of wiki and Enterprise 2.0 adoption newsvine:Principles of wiki and Enterprise 2.0 adoption blinklist:Principles of wiki and Enterprise 2.0 adoption furl:Principles of wiki and Enterprise 2.0 adoption reddit:Principles of wiki and Enterprise 2.0 adoption fark:Principles of wiki and Enterprise 2.0 adoption blogmarks:Principles of wiki and Enterprise 2.0 adoption Y!:Principles of wiki and Enterprise 2.0 adoption smarking:Principles of wiki and Enterprise 2.0 adoption magnolia:Principles of wiki and Enterprise 2.0 adoption segnalo:Principles of wiki and Enterprise 2.0 adoption gifttagging:Principles of wiki and Enterprise 2.0 adoption

    Jun 09

    ROI of Social Software

    roi, social software 12 Comments »
    A lot of social software evangelists hate the ROI argument. We like to compare it to the ROI of email and phones and complain that no-one ever asks an ROI proof for those technologies. We like cartoons like these:

    2008 06 09 1648 744079 ROI of Social Software

    Yet the fact of the matter is that the people signing the cheques tend to be 1.0 thinkers. Those of us who want people to get people to buy this stuff have to be able to talk their language. And that’s “Value” and “ROI”.

    I think most ROI discussions fail because people go straight to the ROI of their favourite social software platform in terms of the features and functions it offers, rather than deal with the underlying principles. At the heart of any social software ROI argument is the belief that your personal network is a powerful and valuable that helps you deliver more value to your company. More specifically in internal social software deployments we’re talking about your network inside your organisation. Forget software, forget IT, I’m just talking about your little black book of internal contacts, and that it adds value to your employer. If this point is not agreed, there is no way that a social software ROI case can be made. This has to be agreed upon before you go anywhere near software.

    If this is agreed, then the question then becomes “how much”? Social software is simply an IT tool which helps you maintain business relationships which may otherwise lapse, and increase the number of relationships available to you. If you have already agreed that a personal network is a good thing it becomes easier (although not easy) to quantify the benefits of a tool to make the network “better” – namely social software.

    “Social” software can get a bad press from line of business because work is not meant to be “social”. We have had conversations with clients who say “I don’t want to hear about social software, I want to know how an engineer in Argentina can find an engineer in Slough who can help with a customer situation”.

    So move away from the ROI of “Social Software”, and instead when involved in ROI discussions you have to find out what the real problem is. Is it that they think that an employee’s network is not valuable, or do they need help in finding out just how valuable it is? They are two very different arguments and many ROI cases are not convincing as they fail to understand which they are supposed to be addressing.

    If you enjoyed this post, make sure you subscribe to my RSS feed!

    Possibly related posts:
  • Web 2.0 ROI discussion at Web 2.0 Strategies
  • Wiki ROI Calculator
  • Enterprise 2.0 ROI
  • Share this:

    del.icio.us:ROI of Social Software digg:ROI of Social Software spurl:ROI of Social Software wists:ROI of Social Software simpy:ROI of Social Software newsvine:ROI of Social Software blinklist:ROI of Social Software furl:ROI of Social Software reddit:ROI of Social Software fark:ROI of Social Software blogmarks:ROI of Social Software Y!:ROI of Social Software smarking:ROI of Social Software magnolia:ROI of Social Software segnalo:ROI of Social Software gifttagging:ROI of Social Software

    Previous Entries
    Powered by WordPress .::. Designed by SiteGround Web Hosting

    cssandhtml