Geek of the Week (it's a good thing)

One of the things we have started in our quest for cool IT is what we call Geek of the Week. It is given out to folks that demonstrate some special "geekiness" that week. I actually kicked this off before I opened the "Are we cool enough?" can of worms, and folks seem to like it. Even other departments have heard of it and asked if they could join in.

I've kept it simple; people submit nominations to me, and I am the sole judge. Folks can nominate anyone, including  themselves. Nominations can be for any cool new bit of tech, or a new application of some existing tech that they have discovered and want to share. It is especially good if it solves a problem the business faces. A good example from a few weeks ago was the discovery of Tungle to share free/busy information externally. Many of us use it now, and it solves a real problem.

Of course you don't win much. I announce the winner via Chatter, and you get to keep the Geek of the Week certificate in your office until the next one is awarded.

I am interested in other ways folks have found to bring thought leadership to the surface.

Come on you Geeks!

Are We Cool Enough?

This question was prompted by this article on "What Motivates Your Top IT Employees". I posted the question to my management team, and ended up with a somewhat livelier discussion than I expected. I do push the team to do cool new stuff, and it often frustrates a good part of the team. While we are not done with this discussion, I have come to some conclusions:

• Cool for the sake of cool is silly. it still needs to enable the business
• What is cool today is status quo tomorrow (or maybe the next day). That doesn't mean it is not good, cutting edge stuff, and something to be proud of, but it does not give you a pass on cool new stuff
• I truly believe that thought leadership can be found anywhere; all levels of the business, customers, partners, etc. In order for us to capitalize on it, people need to bring their ideas forward. Encouraging this has proven to be a challenge
• We are in a major technology shift, specifically the shift of many business functions from traditional on-prem applications to the cloud
• This shift is causing considerable stress on the team, and managing through this change is another big challenge
• Many folks feel they are too busy to spend time finding cool new stuff. I am not completely buying it I find cool new stuff, and I am a pretty busy guy
• In order to give folks some more time to find the clever new solutions, I am trying to pick things we can stop doing. I am shocked at how hard it is to get people to tell me where they spend their time so I can pick stuff we will stop doing, or figure out how to do them more efficiently. If folks really do want to work on the cool stuff, they need to tell me what uncool stuff they spend time on so I can fix it

Of course we are pretty cool. We use our IT technology to enable the business considerably better than most companies I have contact with. Being an IT vendor ourselves, we also spend considerable time showing customers how we leverage our technology, and also upgrade to the latest beta (and sometimes alpha) versions to better support product development.

Another Long-time Vendor Causing Great Pain

This time it is RIM. We have been having sync issues with our blackberries for some time now. We believe it to be somehow related to our Exchange 2010 upgrade, as they started around the same time. RIM support has been no help. They now believe they understand the problem, but don't know how to fix it. They throw a lot of "try this" at us, but it is pretty apparent they don't have a clue as to how to get us relief.

My iOS and Android devices are nearly perfect when it comes to staying in sync, and they are much nicer devices to live with. The only reason we still have blackberries at all is are the slightly better corporate features that some of the users want. However, the most important thing sync, and if you can't get that right, you need to go.

So, I am going to pull the plug. I made and announced the decision to start a slow purge of the blackberries last week, and I am going to use my RIM support dollars on something that actually adds value to the business. I know the loss of my 450 user BES support contract is too small to make much of a difference to RIM, but I'll sure feel better when I am no longer sending them our check.

I really do hate my Microsoft EA

Our Microsoft EA is up this summer. We have started doing a review of our EA agreement, and I am looking to cut it back or eliminate it. Here are my motivations:

• It is the largest single line item in my IT budget, making it a prime target
• We tend to upgrade to the latest and greatest stuff because we own the rights to it. I want to do fewer upgrades moving forward, as we spend a huge amount of time upgrading stuff that could be better spent adding new value to the business
• Speaking of adding value, compared to my cloud apps, the pace of innovation is snail like. For example, we recently finished an Exchange upgrade to 2010. Combined with Office 2010, this gave us maybe half a dozen new features that are visible to our user community. Six features every three years, and you have to spend a few man-months of effort to take advantage of them. Shame on me. By contrast, SalesForce gives my users about 20 cool new features every four months! And I don’t have to do anything, they are just there.  GoodData gives me new stuff at least monthly, if not sooner. Bottom line; the pace of innovation in the cloud is just orders of magnitude faster than what we get from MS (and our other tradition software)
• Microsoft makes the whole thing just too damned hard. The “Product Use Rights” document (PUR) is 138 pages. Really. Only the Government could make it harder

I’m sure I’m forgetting some stuff, but you get the idea. I am even likely to take us to Gmail (from Exchange) later this year. After all, Google has given their users nearly 200 enhancements to messaging in the last year or so. I think I would rather be on that train than run over by it.

And for anyone is having trouble sleeping, here is a link to the MS PUR http://www.microsoft.com/licensing/about-licensing/product-licensing.aspx, and the 26 page document that explains it J

When is a cloud not really a cloud?

...When you stick the word "private" in front of it.

I have a pretty cool data center. State of the art, IP storage, Virtualization, you name it, we are fully buzz-word compliant. When I was describing to some of my peers at a CIO conference not long ago, one of them said "You have a private cloud!" with much enthusiasm. It took me by surprise, as I had never thought of it that way before. I said that I guess you could call it that. Later, after much discussion and wrestling with the idea of a private cloud, I decided there was no such thing. Sure the modern virtualized data center has advantages over the old physical world, but it also comes with its own set of challenges, and my internal IT group still has to deal with physical infrastructure, and more critically, maintain and upgrade apps.

With my cloud applications (the real ones) I never have to worry about the apps, they are just there. Most of them give me cool new features, stuff that adds value to the business, multiple times per year. In contrast, we just spent many man-months upgrading our MS Exchange system. Sure there are a few cool new features, but if I had put that much energy into adding new business value, it would have been much better spent.

I still maintain that I am not moving to the cloud for clouds sake. I am solving problems for the business. Most of the new things we do these days are in the cloud, but we choose them because that seems to be where all of the innovation is these days. When was the last time you really saw something innovative from one of the traditional big software vendors?

And on a similar note, taking you bloated, traditionally in-house application and running it on public infrastructure is not the same thing. Using my Exchange example, you'll still wait three years between batches of new features.

Our IT Road Map

We publish a monthly IT road map. It highlights upcoming changes to our infrastructure or systems, and more importantly, new value we are going to be delivering to the business, and when to expect these things. Here's is a page to give you an idea of what it looks like.

I have been surprised at the response. We publish this via Salesforce Chatter, our internal social media platform, and it goes to all employees. This level of transparency has helped us prioritize, and keeps everyone plugged in to what we are doing. Publishing via Chatter gives the employees an easy way to give us feedback; just reply to the post, and gives us an easy way to track who is looking at it.

It has also helped us be a bit more realistic about what we are going to do. If we haven't done at least basic scoping or allocated resources, it probably doesn't belong on the road map. Setting a date to something that is just a dream at this point just sets false expectations, and leads to us disappointing the business.

We are going to add a "Futures" section that will be a place for us to list the things we are thinking about to give a sense of our IT vision.

In short, keeping the business in the loop with IT initiatives helps keep them in line with the needs of the business, which is a good thing. 

A Short Rant

My wife and I went to the First Night celebration in Portsmouth New Hampshire on New Year's eve. We were enjoying cigars as we walked down the street. For the first time ever, several folks gave us considerable grief about our smokes, including one teenager that was way too young to be so grumpy. What ever happened to New Hampshire? This used to be the Live Free or Die state. It is the main reason I moved here 23 years ago.

It is a bit ironic; if these busy-bodies hadn't lobbied to ban the cigar bars they never went to, I would have been there enjoying a scotch and a cigar.

Why does it seem that folks just can't but the hell out of others lives anymore?