Pages

Showing posts with label poc. Show all posts
Showing posts with label poc. Show all posts

Monday, November 24, 2008

Learning Experiences: A Successful Social Software PoC

View Comments

The following is a summary of a successful social software PoC that I participated on for a customer in Texas. I'm sharing it here so that you can compare how this company did things right, as opposed to that other PoC that went downhill.

Customer Y is an account I have been working closely with around Quickr and Connections. We've successfully setup a PoC for both products - the IT Manager signed off on a formal PoC Closure to ensure that it met his criteria. Technically it is successful, but it wasn't sold in our eyes - some understood the value immediately while it didn't seem of much value to others. Connections, just like any other social software, is really a product which should have content to understand its potential and value. Think of the early days of Facebook when none of your friends were there... how useful was that?

Last Friday we held a "user-adoption" or "getting started" workshop around Connections and Quickr (promoted internally by the customer and content/material/prizes provided by IBM).

The Goal

  • Pump their environment with relative and pertinent content
  • Have attendees "invite colleagues", share Dogear'd bookmarks, added to a Community, Team place or Activity so even those that do not come are notified about the products
  • Have users understand that they don't have to be content authors to benefit from the value - you can take advantage of the info in Connections to gain business value
  • Walk away with a simple understanding of what it is and have them access it from their desk the next time they work.

The Challenge

  • We had 1 room with 10 workstations, for 4 hours - only have web browser to interface the products (do not have the chance to expose connectors and integration capabilities).
  • Users will be coming in and out at their convenience, so no formal presentation that can reach everyone at once.
  • Expose as much of Connections and Quickr as possible in 15 minutes max.
  • Have them use the pilot environment again from their desk after they walk away from the workshop.

What Did We Do To Make This A Success?

We secured funding for prizes to attract attendees. I worked with the customer's resource to create a promo flyer which he posted on their digital bulletin board and printed flyers for distribution/posting within the customer site.

Laurisa Rodriguez created content titled "Getting Started with Lotus Connections". However, it covers each service in great detail - to complete all labs it would take a user at least an hour. I revised the material to the idea of "jump start" users. I took the easiest pieces they would find immediate value for in each Lotus Connections Service, and if they really like it, they can always come back and explore further from at their own convenience. In addition, knowing that we cannot reach the masses by attendance, I geared the material so they share and connect with folks that were not present. The authentication was against their real LDAP server and both products were configured to their production SMTP servers.

Even with the material reduced in content, we faced an issue of reaching the time limit, so we improvised and made 4 labs mandatory and 2 optional - it would change for users based on a discussion of what they wanted to walk away with.


Last, knowing that anyone who walks away with a 10-15 page packet will probably place it on a shelf and never look at it again - had to come up with an idea of how they would remember this even and hopefully access it again. I took existing slideware and created double-sided postcards (4 prints per sheet on stock card that was cut afterwards); it had the key message of "what is?" with links to their internal PoC environment and the other side had details to each of the services of Connections and Quickr so they know what might fit their use case if they forget.

Results Of This Effort

We had a turn out of 66 users (after only promoting the event for 2 days) from different lines of businesses (IT [including Directors], Marketing, R&D, Service Desk, Business Analysts, Sales, Customer Operations, and a few more). Within the first 20 minutes of the start, all workstations were occupied with folks waiting in the back to participate (3 more workstations were added to handle the additional users). Each person sent an invite from Profiles to at least 5 others to be their "colleague", expanding the network to 330 users from this event! More users were exposed from the other services as well. And folks were asking to take more than one postcard to distribute and share with their peers as they think it is very powerful or very cool. The feedback was great and the product sells itself when it's exposed in the right manner.

We met with the admin Monday ~1 PM after event, and he said 2 comments that really stuck:

  • "My inbox is getting full with messages of attendees sending emails to their teams saying they didn't realized this was setup with real email integration and now telling their teammate about it."
  • "It's growing virally since the introduction on Friday afternoon and I think we're going to have to give the VM's more resource as it gains popularity"
  • "I'm surprised how the PoC environment was stable to handle this surge of data and run smoothly"

The best part is so many folks were exposed to it and if it gains popularity by different lines of businesses, it makes it that much more easier for the product to stick. And even if people do not contribute content, they will consume just from the Profiles service as it was pre-populated with real data. I think it was a real success and please feel free to re-use the material to help push the value further.

Tuesday, August 5, 2008

A PoC that went downhill

View Comments
Last week, I received the sad news that the social software PoC (Proof-of-Concept) at a customer in the West coast has failed. For all vendors involved!!
I have to say that I'm pretty disappointed, but not surprised. Tried as we might, the customer didn't want to follow our recommended practices. Reasons for the PoC to fail became clearer as I read the explanation from the customer. Let me give you some background first.
Now, I wasn't heavily involved in the PoC, but assisted on an as-needed basis. My teammates on site kept me on the loop as needed. The PoC was led by the organization's IT department. There was a sponsor from the business side, but it seemed, in my opinion, that their feedback was not considered at any time.
There were 4 vendors participating in the pilot and all systems were deployed as-is and "thrown" at over 200 users. The users were given no instruction on how to use the system. They were simply given a URL and a survey with over 20 questions: "Did you like this? Did you like that?, etc". Is there any surprise all vendors failed in this scenario? Not at all.
Looking at the 10 Principles for Social Software Adoption, I don't see that this company followed them. One of the users' complaints was that the system didn't provide valuable information. I don't think that's a surprise given the system wasn't properly populated with data. Think about it... if you go to a social site and it's empty.. Would you like it? I remember when I first joined Facebook I was loner and didn't really use it since my friends were not there. For the longest time, I only had 10-20 friends . Even my wife, who's a graduate from MIT didn't find it cool for a while! But as more people joined, I was hooked!
Additionally, the customer was considering and making the 4 vendors compete in their best of breed areas.. i.e. profiles vs blogs vs communities vs social bookmarking etc. They even tried integrating all of them to provide a "better" user experience, but the user experience was the biggest complaint from end-users.
So let me throw out some recommended practices for a social software PoC (Mike Stopforth blogged about this earlier too):
  1. Identify business goals - In order to measure the success of a PoC, there needs to be a goal to be met. Define it (e.g. improve communication with blogs)
  2. Choose your audience - Needs to be people who need to share knowledge (e.g. R&D, development, etc)
  3. Choose your evangelizers - These will be your salesmen. They already exist in your enterprise. Who do people go to most often for answers? That's who you need. Or you can use Atlas for Lotus Connections to find out. Have them start populating the system.
  4. Conduct a pre-assessment - Ask your audience how they accomplish, today, their day to day tasks such as finding people, finding collateral, keeping up with topics, etc.
  5. Get input from evangelizers - Based on the enterprise's culture what should be deployed first? How should it be deployed?
  6. Train your evangelizers - so they can train others...
  7. Conduct a post assesment - After a reasonable length of time, figure out what worked and what didn't, fix it and keep going.
  8. Integrate with other tools - Is your enterprise mobile? Deploy the BlackBerry plugin. Do they mostly live in a portal? Deploy the Connections portlet. Make sure that employees can access Lotus Connections from where they work! Hey, it's all free, so you might as well!!
And there you have it. If you follow those tips and hints, you'll be on your way to a successful PoC. Need more ? Contact me and I'll be glad to help your organization through it.
How about you? Have you had any successes / failures deploying social software? Any that you want to share with us?