Stop worrying about hitting the big drive and concentrate on the fundamentals
Ever hear the phrase “Drive for Show, Putt for Dough?” It’s time-honored sports cliche that refers to the oohs and ahhs that a huge golf drive off the tee will elicit from the crowd. However, despite all the attention a big drive gets and hundreds of dollars a good driver costs, that shot is used maybe 12 times each round. The real money is made on the green where an average player will take almost 3 times as many strokes. You can make all the highlight reels you want with your 350 yard drives, but if you can’t make a 10 foot putt consistently, you’ll be in the same place I am on Sunday….on the couch watching someone else who CAN make those putts.
I bring this up because I’ve seen one too many Enterprise 2.0 implementation – be it a wiki, a blogging platform, discussion forums, microblogging, or Sharepoint – fail miserably because they forgot to focus on the fundamentals. They end up being too concerned with the big drive off the tee that they forget to practice the short putts that are needed to truly succeed. Nearly every Enterprise 2.0 vendor out there offers a similar set of features – blogging, microblogging, wiki functionality, profiles, tagging, search, etc. – they all hype up the fact that THEIR platform is the one that can do X or can do Y, that they have this one unique feature that puts them out in front of the competition. Likewise, once these platforms are purchased and installed, the client teams responsible for customization and integration get enamored with all of these features as well. I’ve seen way too many internal launch emails that sound something like this:
“Visit our new website, the one-stop shop for all your collaboration needs. This new website offers all of the Web 2.0 functionality that you have on the Internet, here in a safe, secure, professional environment – blogs to share your expertise, a wiki that anyone can edit, profiles so that you can connect with your colleagues!”
Seeing all this empty promotional language makes me think of my friend who absolutely crushes the ball of the tee. After another monster shot from the fairway, he’s now gone 524 yards in two shots and the crowd is loving it. He then proceeds to take three putts to go the final 10 yards because he spent all of his money on a new driver and practice time on perfecting the big drive.
Unfortunately, Enterprise 2.0 implementations are suffering from this same, all too common problem.
Day 1: After being enticed by the blogs, the wikis, the microblogging, and the rest of the features, you visit the site, you poke around a little bit – so far so good. Everything looks great. The design is eye-catching, there’s a lot of great content up already, some of my peers have friended me, and I already found a blog post relevant to my job. This is the best site ever! Enterprise 2.0 FTW!
Day 2: I visit the site again and invite a few of my managers to join as well…well, I tried to invite them to join, but the invite a friend button wasn’t quite working. That’s ok – I’ll try again tomorrow – must be a bug. I can’t wait to get them using all of these cool tools too!
Day 3: Well, that invite-a-friend bug still isn’t fixed, but everything else is going pretty smoothly…other than the fact that the blogs don’t seem to work in Firefox. I guess I’ll have to use Internet Explorer for those, but that’s ok.
Day 7: I’ve got a big meeting today with the new VP at this conference we’re both attending – I’ll demo all these new social media tools for him and show him how he can start a blog too!
Day 7 (later on): Damnit! I didn’t realize that I wouldn’t be able to access the site unless I was behind the firewall in one our corporate offices 🙁
Day 14: On my way to a meeting, I was checking out my co-worker’s Facebook page on my iPhone when I saw his latest status update – “OMG – I can’t believe that someone said that about our new HR policy on our corporate blog!!” Intrigued by what was said on the new blog, I try to navigate to our blogs…foiled again!!! No mobile support….I guess I’ll check it later tonight.
Day 17: Working late on a report again – luckily, I’ve been posting all of my findings to our new wiki so that when I leave for my vacation tomorrow, everyone will have easy access to the latest and greatest data.
Day 18: Disappointed to receive an email on my way to the airport that our Enterprise 2.0 site is down for maintenance for the rest of the day, rendering all of my data unusable to the rest of my team. They can’t wait a day for the wiki to come back up so it looks like they’ll be working extra hard to recreate everything I did last night.
Day 19: &*%$ I’m DONE!!! Why is this thing so slow? What does Facebook have 500 million users yet is always up? Why can I download a movie from iTunes in 3 minutes, but it takes me 25 minutes to download a Powerpoint presentation? Why can I read Deadspin from my phone no matter where I’m at in world, but can’t access the blog I’m supposed to be using for work?
Sound familiar to anyone? This is what happens when Enterprise 2.0 is too focused on the teeshot, and not enough on the fundamentals of the rest of the game. Features galore that will get people ooohhing and aahhhing, but lacking the fundamentals of speed, accessibility, and reliability that will keep people coming back. If you’re talking about implementing an Enterprise 2.0 platform, before you start talking about all of the bells and whistles you want, make sure that you take care of three very fundamental issues.
Make it Fast – People have to expect anything online to be fast. If I click something, it should take me there immediately. There are no exceptions. Load times for simple html pages (we’ll give multimedia an exception here) should be almost non-existent. I don’t care if I’m behind a corporate firewall or not – if it takes 4-5 seconds to load a page, that’s going to severely limit how often I can use it. If my bank’s site can be secure and fast, why can’t my Intranet sites?
Make it Accessible – Laptops, desktops, iPads, iPhones, Android devices, my old school flip phone, hell, even my TV all allow me to get online now. I can access Pandora, Facebook, Twitter, and a whole host of other sites from a dozen different devices while on the subway, in my house, in a rain forest, or in my office. But, you’re telling me that I can only access my work from one kind of computer that’s located in one place? Doesn’t seem to make much sense.
Make it Reliable – There shouldn’t be a fail-whale on your internal work systems. If I need to access some information to do my job – be it a blog post, a wiki page, or a file – I need to be able to access it, with 100% certainty. If I need access to some data for an important meeting, and I can’t access it because our site is “down for maintenance” or it was accidentally deleted in some sort of data migration error, that’s a serious breach of trust that is going to make me question whether I should be using the site at all.
Concentrate on perfecting the fundamentals before you start getting into the fancy stuff – practice your putting before your driving, learn to dribble with both hands before entering a dunk contest, practice catching the ball before you choreograph your touchdown dance, and make the wiki work in Firefox before you start working on some drag and drop home page modules.
at
Well said Steve
at
Thanks Tim – glad you liked it!
at
Day 7: Ouch. 🙂
All excellent points. The focus of a system like this is to enable the users. Well, at least that is what we think the focus should be. Competing internal and external elements may blur that focus a bit, resulting in the imperfect system you describe here.
at
I love the analogy