Tag Archives: E20

Drive for Show, Putt for Dough – a Lesson for Enterprise 2.0 Platforms

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.

Photo courtesy Flickr user Stev.ie

Continue reading...

Dear IT Guy, Can You Actually Use the Tool You’re Creating?

Do the top developers for Google’s Android operating system use Blackberries?  Do the IT guys developing Windows 7 use Macs?  Do the folks at WordPress use Blogger to host their personal blogs?

These are purposely ridiculous questions – wouldn’t the best developers use the actual tools they’re responsible for building?  Wouldn’t they do their job more effectively if they were actually a user of the product they’re developing? Doesn’t the product have more credibility if the people behind it are believers in the product’s features?  Out of everyone, shouldn’t the development team, at least, be the biggest advocates of the very software they’re implementing?  Shouldn’t they be the ones drinking the Kool-Aid?

Unfortunately, IT departments at large companies and government agencies are too often doing the equivalent of developing Android apps at work and using the iPhone at home. Sharepoint developers implement Sharepoint, yet they don’t use it to manage the implementation. The guys installing your organization’s blogging software don’t realize that the “Add a Picture” button doesn’t work because they don’t have blogs.  The team responsible for increasing awareness of your Enterprise 2.0 platform haven’t even created profiles of themselves.

Now, take a look at the official support areas for WordPress, Telligent, MindTouch, Jive or any of the dozens of social software vendor sites.  Notice anything? The developers are often the most active members of their respective communities and they’re using their own software day after day in the course of doing their jobs. If there’s a glitch involved with posting a new comment to a forum, they’re going to be the first ones to see it, diagnose the problem and fix it.

Sadly, I’ve been seeing these situations increase with the emergence of the Enterprise 2.0 and Government 2.0 initiatives. IT departments are increasingly being asked to implement wikis, blogs, social bookmarking, video-sharing, and dozens of other varieties of collaboration software – software they may know how to code, but often have no idea how to actually use.  They’re just told to “give us a wiki” or “develop a blog for me.”  Actually using the blog or wiki isn’t a requirement.  As as I was told by one programmer a year or so ago when I recommended he start a blog to inform the rest of the community about the latest enhancements and maintenance activities,

“Every hour I spend playing around on a blog post is an hour I spend away from coding!”

Well, that was helpful – thanks! Instead of getting frustrated and ending the conversation, I should have instead elaborated on the benefits that a developer enjoys when he becomes a user instead of just a developer.

  • Higher quality product – you can identify bugs and feature improvements before they become problems for other users.
  • Increased credibility – If, as a user,  I ask how to upload my photo, guess whose response I’m going to be believe – the guy with an empty profile or the guy who’s been active on the community for the last year?
  • Increased “forgive-ability” – Look, we know that these sites will go down occasionally, especially when they’re first being developed.  We can deal with that…if we’ve been reading your blog and know that it’s down this Saturday night because you’re installing the new widget we’ve been asking for. If the site goes down and all we get is a 404 error page stating that the site is down for maintenance…again, we’re going to be less than pleased.
  • Content Seeding – Clients are always asking,  “how are we going to get people to actually work on this site and add content?”  Well, before you even launch, if your project team (including developers, community managers, comms people, etc.) actually use the site you’re building, you’ll create a solid base of content before you even start to open it up to more people.  Adding to existing content (even if it’s not related) is always easier than creating something new.
  • Common Ground – you become a member of the community instead of the guy behind the curtain making changes willy-nilly. You gain trust and respect because they know that you’re dealing with the same issues they are.  You’re struggling to access the site on your phone too.  You’re not getting the alerts you signed up for either.  You’re not able to embed videos correctly.  You go through what they go through.
  • Greater ownership in the final product – The community becomes YOUR community, not something you’re just developing for a bunch of “users.”  You become invested in it and want to make it faster, add new features, win awards, etc. because you’re a part of it.

For all you non-developers out there, would you like your IT staff to be more visible?  Would you be interested in learning more about what’s happening under the hood of your Intranet/Enterprise 2.0 platform?  What other benefits do you see to getting them more involved?

For you developers, what’s preventing you from getting this involved in the communities/platforms that you’re responsible for creating?

Continue reading...

When Was the Last Time Your Intranet Empowered Anyone?

This post originally appeared on AIIM’s Enterprise 2.0 Community Blog.

Think about your Intranet for a moment (stop groaning) and answer the following questions.  When was the last time:

Image courtesy of Flickr user Search Engine People Blog

  1. Someone spent their own money to purchase promotional items to help build awareness and get more people to participate?
  2. Someone voluntarily put the name of the Intranet on their softball team jerseys?
  3. Someone voluntarily created an entire instruction manual for new users?
  4. Dozens of people volunteered to be the welcoming committee for new users, greeting them and offering to help?
  5. Dozens of people took shifts to be online and act as an ad hoc help desk for other users?
  6. Someone voluntarily created PowerPoint presentations to help others better understand the Intranet?
  7. People routinely logged on at midnight just to see what they missed during the day?
  8. Regular users are routinely “pitched” by official internal communications staff to post content because they have a greater readership?
  9. People beg, beg! for access outside the firewall, and ask for easy mobile/remote access so they can read/contribute?
  10. People voluntarily create mashups and plug-ins to enhance the interface and then share those with other users?

All of these situations are ones that I’ve witnessed, either internally with Booz Allen’s hello.bah.com, our own implementation of Enterprise 2.0 tools, or with my clients. True, in many cases, Enterprise 2.0 communities have failed to build a critical mass of users, they can quickly become echo chambers, they don’t have full leadership support, and they often fail to make it “into the flow.” but despite (or maybe because of) these challenges, Enterprise 2.0 communities can ignite a passion among its users that hasn’t been seen internally since the introduction of the Internet.

If you stopped using the terms “social media,” and “Enterprise 2.0” and just started telling people that you “have some ideas for improving our Intranet that will make our employees want to log on at night to see what they missed and spend their own time writing code to improve it,” getting buy-in for these tools would be a no-brainer. Who wouldn’t want their employees to be this engaged with their Intranet?

So what is it about Enterprise 2.0 that gets users so excited?  It’s because Enterprise 2.0 is about more than just disseminating information – it’s about giving each employee a voice; it’s about flattening the organization; it’s about ending approval chains; it’s about being a part of something new.  But most of all, it’s about empowering people.

When was the last time your Intranet empowered anyone to do anything?

Continue reading...

Interested in Being at the Tip of the Spear? Be Prepared for…

 

Image courtesy of Flickr user Percita

Over the last three years, I’ve met a lot of people who are their organization’s social media evangelist, lead, POC, pioneer, ninja, guru, etc., and I’ve met many others who are aspiring to take on that role.  Hell, I even wrote my last post to help those people get started.  While it’s easy to get caught up in all the hype that often follows the people in these roles – the promotions, the raises, the invitations to participate in selective working groups, the personal branding, the ability to make your living using Facebook and Twitter – I’d like to take this opportunity to help balance out the expectations.  The following statements aren’t necessarily good or bad, but they do paint a more realistic picture.

So, if you’re itching to become “the guy” at your organization when it comes to social media, be prepared:

  • To be expected to know EVERYTHING about social media, not only about Twitter, Facebook, and wikis, but also all of the policies, trends, statistics, and laws too
  • To know who else in your organization is also involved with social media and if you don’t, why not
  • To encounter people who assume that because you’re on Facebook or Twitter while at work, that you’re never actually busy with anything
  • To justify the return on investment (ROI) of  all the time you spend using social media
  • To get dozens of emails from people every time a there’s a negative, controversial media article discussing the risks of social media (you should have seen how many people pointed to the Wired article came out showing how terrorists could use Twitter and told me, “see, that’s why we shouldn’t use social media)
  • To be always on, all the time. No matter what meeting you go into, there’s always a chance that you may have to give an impromptu presentation
  • To have people constantly asking you for your thoughts on the latest social media-related email/blog/memo/article/news/interview that came out
  • To justify your existence to your managers when there are organizations who outsource their social media for a few cents per tweet
  • To get inundated with requests like this – “I just read [insert social media link here]. Do you have like 30 minutes to meet with me so that I can ask you some basic questions?”
  • To see your work (even within your own organization) turn up in other people’s work without any attribution
  • To be told that “all this collaboration is great, but what real work have you accomplished?”
  • To change teams and/or organizational alignment at least once

I’ve encountered all of these situations to varying degrees over the last three years, and at times, I’ve felt frustrated, excited, nervous, entrepreneurial, scared, sometimes all simultaneously, but through it all, I’ve always felt proud to be on the cutting edge of changes that need to be made. I’ve never wondered if it was worth it, and I can definitely say that I’ve always felt challenged and stimulated through it all.

If you’re considering being at the tip of the social media spear within your organization, make sure that you’re prepared…for everything.

Continue reading...