I look around here at SAP, I’d say fighting complexity is our biggest competitor. Sure we have much to learn about simplification, and we must get significantly better at reducing and managing complexity. But if there is one thing that I loathe more than unnecessary complexity it is the oversimplisitic. ERP is complex, so is the Belgian tax code. Many of those that damn SAP and Oracle for its complexity seem to suspend business reality when discussing the next great start up that will blow us away.

This is exactly why customers buy SAP software. We need it to run our businesses. Yes, it costs more then we like but anyone with half a brain realizes that navigating the Brazilian tax code without it would basically put you out of business in Brazil. If you follow my blog at all you realize I think most things are too complex but, this is more on the outside the user facing bits. I don’t want to know anything about the Polish payroll rules all I want to do is pay my employees. If my ERP system makes that easier by guaranteeing compliance then it’s a win.

Just to throw some geeky fuel on the statistical fire counting lines of code to determine “complexity” is dumb. I could reverse a string in 3 lines of confusing recursive C++ code. Or I could write 10 lines that are easier to follow and run at about the same speed and a maintenance programmer would understand it immediately. Which one is better?

I think Google’s next move as Jason, astutely observes is to create “reoccurring revenue” for PC makers like Dell/HP by getting them to install something that isn’t MS Windows, however that something won’t be a Google OS. It will more likely be an Open source OS like, Ubuntu with a revived Google Pack installed on it. I think the simple reason for this is Google has been involved in Linux development for a long time but, in the area of the kernel not on the front end. Why should Google do any work when they can just piggy back on another great initiative.

The pack will have to have some interesting additions to really put the squeeze on MS. I think the obvious choice is “your desktop PC anywhere you are” — the current notion of “your” PC will become irrelevant, meaning, having everything on one piece of hardware you own won’t matter. You can see Google starting to do this now with Google Applications. With the addition of the elusive G-Drive mounted as a “virtual HD” sprinkled into the “Pack” you have a very flexible totally portable desktop environment. Imagine going to any machine in a business and signing in and getting all your preferences, all your documents, installed programs, right there for you! The great part about this it wouldn’t cost Google much, as they would be using currently available OS solutions, FF, Linux, etc. As more people buy PCs with the “Google OS/Pack” on them, more people will reap the benefits of the “anywhere desktop,” creating a runaway snowball effect.

So, I don’t think Google will build an OS in the strictest sense, I think they will extend existing technologies, the Linux desktop out to a their servers and their incredibly powerful data centers down to the desktop.

“If you can’t explain what you are working on to your mom, then you don’t understand it.”

I’ve found this simple rule to be true over many years and many different subject areas. I can still remember my Mom asking me how college was going and what I was working on in a particular class and only being able to explain in the same lifeless math jargon it had been explained to me in. Needless to say after that conversation my Mom didn’t understand that class any better then I did and my grade certainly proved that out.

Maybe this person isn’t your Mom but, you should have them around somewhere — it’s a great check on your understanding level. You can identify this person by when they ask what appears to be an innocuous question, “How does email work?” you end up flailing around for a decent explanation that doesn’t include phrases like, SMTP, POP, sendmail, IMAP, etc. “A football team is a team of football players,” explaining something technical with more techno-babel just means you don’t know what you are talking about. Being able to explain chemistry to another chemistry person is certainly fine and well, and kudos to you as chemistry is a mystery to me, but real in depth understanding is when you can explain chemistry to someone who doesn’t know the meaning of the word titrate.

A somewhat similar idea is talked about in advertising as the “elevator pitch,” but with this it just means you are good at summarizing something down into talking points — which is a different skill distillation. This doesn’t actually mean you really understand what you’re talking about, you’re just very good at crafting a high level, 60 second sound bite, version of what the subject is.

To build a well designed well thought out system you need to have a low level knowledge of the tools and technology but, you also have to be able to stand back and decide if you’ve built a steaming pile of nothing or something truly noteworthy. They both might be technology marvels but, you have to be able to step back and have that “explain it to your Mom” view before you can tell the difference.
To explain email to someone how has no clue what SMTP or even telnet is, is truly a bottom up in-depth understanding of that subject.

I’m still working on explaining REST to my Mom.

1. Agile Development
• Im totally guessing here, but in most IT shops I assume you probably use some locally bastardized version of the Waterfall method. In our R&D team we use an over simplified version of Scrum, the idea is to remove all the unnecessary artifacts from the process and “Shutup and make it work,” to use one of our teams mantras. The basic idea is get testable code in another team’s hands as frequently as possible; this could mean every night or every week.
• The reason this is number one is that it will allow you ( and/or your team ) to prove value instantly. People go nuts when you deliver the 1st version of working code before other teams have even decided who writes the spec
• Using this type of process automatically distinguishes you from your colleagues, it allows you to move fluidly with the ever changing IT landscape, it is a huge win over your normal process and a big key to my team’s success
2. Flatten your Team
• This may seem like a no brainer but odds are there are lots of people between you and your user community. To be successful at delivering code as fast as you will need to justify your spent time you must be as close as possible to your user base. This means you can’t have a rigid structure the person who knows the most about the area needs to make the decisions. Suck up your pride and let them run the show.
3. Get smart people
• I have a really hard time phrasing this statement but, suffice to say, you have to get the cream of your organization. If you want someone to go decide if Ruby on Rails is a good idea you better trust that person’s ability to learn and their ability to judge technologies. In the end it’s better to have fewer people then an army of people you have to micro-manage.
4. Research is failure
• This is one of the hardest concepts for an IT shop to grasp — they mostly deal with uptime and throughput but when experimenting with new ways of doing things you have to be able to deal with a certain amount of risk and this finally brings me to the reason for this blog, a recent post ( really go read it ) by Carmine Coyote at Slow Leadership, really a great job about the fear that makes these teams fail. Which brings me to my last point
  
5. Fear Nothing
• You can’t be a “disruptive innovator” ( thanks Shai ) without risking something every once in awhile
• Make your management understand that fear is costing them $
• “Thrill your users” ( thanks again Shai ) any fears your management has will go away

Good luck, if IT in the US is to stay we must stop being a commodity and start delivering really measurable value to our businesses again. The simplest way to do this in the enterprise space is to simply make those ugly back end systems usable.

btw — this blog was written somewhere south of Greenland at about 33k feet. On board internet is great.