Archive for August, 2010

Microsoft’s Ballmer – Lessons on Dealing with Poor Performers

August 18th, 2010

I’ve worked at a couple of large companies – IBM & Microsoft. Dealing with poor performers has and always will be a challenge for new as well as experienced managers. Did you know that management expends more effort protecting and advocating for poor performers than it does trying to get a simple salary increase, bonus, or modest promotion for our most outstanding performers? Sad, but true – and if you think this is not true please ship me an ounce of whatever it is you’re smoking – I obviously need it more than you do.

Every manager and every company has a different way of dealing with performance issues. The most popular method is to simply pretend it’s not happening – you know, the denial thing. I mean after all this method is successfully employed in our daily lives with alcoholism, drug abuse, and a host of other behavioral problems, so why not apply this practice to poor performers in the workplace?

At IBM, in the early days, the method was promotion – yes – this is no typo – promotion. If someone was not doing a good job you simply promoted them to get them out of the way. This was a great system – and counter intuitively quite ingenious. Before long, some of the most inept individuals in the company quickly rose to the top, and ultimately it became quite a liability to your career if you held too high a title. In the late 80’s early 90’s an IBM VP wouldn’t have a chance in hell of getting a job outside the company.

Microsoft, during the Ballmer era, had a different method of dealing with performance issues that I observed. There was what I would call the “process” method and then there was the “Steve” method. By the way, this was just my observation and I don’t know if this was documented anywhere but I did observe it on enough occasions for it to make an impression on me.

The “process” method was based on former GE CEO Jack Welch’s book Straight from the Gut. I think Steve really liked this book and admired Jack. Jack was like the quintessential CEO. He was a really disciplined, process oriented guy, who laid out in tremendous detail how GE should be run, at every level, and executed flawlessly in my opinion (good thing he left prior to the big 2002/03 recession and 2008/09 great depression II). Jack imbued this mentality throughout the entire company and created a corporate culture around process-oriented thinking and execution. To me, Steve liked this concept, but unfortunately only one single property from Jack’s book was inherited and Steve applied it to the entire Microsoft culture. This property was – Get rid of the bottom 15%.

Damn right! This is the ticket to dealing with poor performers – you get rid of the bottom 15%. The problem is that this was the ONLY property Steve would carry over from Jack and GE. This is like saying, “I’m going to be a world famous physicist, and Einstein is going to be my model”. The problem is that I have never studied physics, am not good at math, and not very smart – so in lieu of these minor details, the property I choose to inherit from Einstein is simply his funny hair.

ballstein Microsoft’s Ballmer – Lessons on Dealing with Poor Performers

So the 15% thing is still commonly used in big business.  But Steve has another practice that I’d like to point out – the “Steve” method for dealing with poor performers. I recall a meeting Steve invited me to when he first became CEO. He wanted to get people’s opinions, to listen. I guess it’s “new job” behavior – you put on your best behavior for the first month or so to impress everyone and then ultimately migrate to your natural point of equilibrium – that’s where Steve probably is now, but I think it only took him about two days to get there.

What I noticed at this meeting had nothing to do with what we talked about. In fact, I don’t remember a word of the conversation – I didn’t remember it when I left his office. I’m not sure he even asked my opinion about anything. I did however notice two other things: first, what the hell was he doing in this dinky little office? I mean he’s the CEO of this massive company and he had an office the size of a small utility closet. Second, why did he keep yelling to his admin about how late the VP in the office next to his was?  After all, Steve was meeting with me and the fact that this VP was late was irrelevant.

I didn’t make a connection at the time, but a week later the VP was shot (spun as a retirement of course). Later, I noticed something else.  Steve moved to another building and shortly thereafter the EVP of Worldwide Sales and Services was shot. He was moved into one of those nondescript fofo jobs that don’t allow you to do any damage and gives you enough time to plan your “retirement”. The sad thing is that if you’re at all astute (and I just mean breathing), you don’t understand the intent of this “opportunity” and everyone around you is just depressed to talk to you. This story played out again to an EVP-level development exec.

As a joke I started to think that if Ballmer wanted to shoot someone he’d just move into the office next to them and execute. I think this was his conscious plan, and I think it’s a good plan – it’s bold and direct, no pussy footing around.  When Steve moves into the office next to you, put together your “retirement” plans immediately.

I mentioned this theory to a former high level Microsoft exec, whose name I’d prefer not to mention, (Paul Maritz), who also has a very small office, and he laughed, but then quickly turned to the person in the office next to his and shouted out a warning. This unnamed exec is very bright, but I don’t really know if he believed my theory or just wanted to give me the impression that he came up with the idea first and was demonstrating adroitness in the art.

So what about Steve? Check this out:

October 2009 – Newsweek “The Lost Decade: Why Steve Ballmer is no Bill Gates.

May 2010 – The Economist “APPLE has overtaken Microsoft to become the world’s largest technology company by market capitalization.

June 2010 – San Francisco Chronicle “Sorry, Steve. We think it’s getting to be time for you to move on.”

July 2010 – The Economist “Rumours persist that a coup is brewing to oust Steve Ballmer” “…Microsoft is behind… Should the firm fail to catch up fast, Mr. Ballmer will surely be tossed through a window.”

August 2010 – Seattle Post Intelligencer –”Is it time for Microsoft’s Steve Ballmer to go?

The writing is not just on the wall – I think it’s dripped onto the floor. Steve has somehow gotten himself into the bottom 15%. What does a guy like this do? He can’t wait around for his board to give him the message.  Can we really expect all eight board members to move into the office next to him?

I hope to blog again.

P.S. on Steve. I don’t know Steve well. My interactions with him were few, but significant enough that if he saw me today, he would know who I am. Steve’s a brilliant guy, and, as I point out frequently to many people I speak with, managing a company the size of Microsoft is a daunting undertaking that few in the world could handle for a month let alone 20+ years. It is a human impossibility to wrap your brain around a challenge of this magnitude, and I accordingly have a high degree of respect and admiration for anyone in this position regardless of what I may think of them. In my blog I allude to Steve having sat in many offices over the years that have resulted in someone going out the door. There’s a good lesson and moral here: bad things happen to the best and most capable of individuals – even a person like Steve can get munched – it’s like Pac Man.

linkedin Microsoft’s Ballmer – Lessons on Dealing with Poor Performersfacebook Microsoft’s Ballmer – Lessons on Dealing with Poor Performerstwitter Microsoft’s Ballmer – Lessons on Dealing with Poor Performersgoogle buzz Microsoft’s Ballmer – Lessons on Dealing with Poor Performerstechnorati Microsoft’s Ballmer – Lessons on Dealing with Poor Performersslashdot Microsoft’s Ballmer – Lessons on Dealing with Poor Performersmsdn Microsoft’s Ballmer – Lessons on Dealing with Poor Performersdigg Microsoft’s Ballmer – Lessons on Dealing with Poor Performersreddit Microsoft’s Ballmer – Lessons on Dealing with Poor Performersstumbleupon Microsoft’s Ballmer – Lessons on Dealing with Poor Performersdelicious Microsoft’s Ballmer – Lessons on Dealing with Poor Performersmixx Microsoft’s Ballmer – Lessons on Dealing with Poor Performerssphinn Microsoft’s Ballmer – Lessons on Dealing with Poor Performersspaces Microsoft’s Ballmer – Lessons on Dealing with Poor Performersbuzz Microsoft’s Ballmer – Lessons on Dealing with Poor Performersshare save 256 24 Microsoft’s Ballmer – Lessons on Dealing with Poor Performers

Posted in Management | Comments (0)

SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sails

August 13th, 2010

My last Blog dated 8/3 had to do with my theory on why SAP acquired Sybase. The post was largely based on Oracle’s Lawsuit and the SAP/TomorrowNow allegations. I was really surprised to read the Wall Street Journal article on 8/5 that SAP accepted liability in the Oracle lawsuit. Great timing!

I wanted to say a few words about this. I thought the Oracle lawsuit had tremendous merit. My sense was that even if Oracle was 10% right about the allegations, SAP was screwed. I was just imagining all the depositions, the trial with a bunch of SAP witnesses, appearing one by one telling their story about allegation after allegation, having to concede to wrong doing upon wrong doing. What a mess!  And what a victory for Oracle. What an interesting setting for the jury to deliberate upon and a great set up for a huge hunk of the $1 billion Oracle claim. Imagine the jurors going for the full amount just on principal and of course, for the sport of it.

Well – SAP’s acceptance of liability was a brilliant move – it totally sucked the wind out of Larry Ellison’s sails. All the drama is over, just like that. No stream of witnesses testifying of wrong doing. No long drawn out endless diatribe of unwilling, extracted admissions of misconduct on the part of SAP.

It’s over – all there is to talk about now are the damages. Larry claims a billion, SAP claims tens of millions, and it’s up to Oracle to demonstrate damages. There’s no talk about “…corporate theft on a grand scale…” It’s just about damages, and Oracle will be hard pressed to demonstrate a billion in damages.

Great chess move SAP! However, you won’t be able to sit around dreaming that you’ll get away with a “tens of millions” slap on the wrist. My prediction in my last blog was that you’re in for a quarter billion dollar citation – so get the checkbook out.

I hope to blog again.

linkedin SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sailsfacebook SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sailstwitter SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sailsgoogle buzz SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sailstechnorati SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sailsslashdot SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sailsmsdn SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sailsdigg SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sailsreddit SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sailsstumbleupon SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sailsdelicious SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sailsmixx SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sailssphinn SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sailsspaces SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sailsbuzz SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sailsshare save 256 24 SAP sucker II – Larry Ellison Gets the Wind Knocked Out of His Sails

Posted in Business Intelligence | Comments (0)

SAP Sucker

August 3rd, 2010

sap sucker SAP Sucker

I’ve been meaning to write about this – SAP’s $5.8B acquisition of Sybase that is.  There’s been a good bit written about it – excellent and relevant comments as well. Look at the excerpts:

Forrester: “With Sybase Unwired, the mobile apps can be written once and deployed on multiple mobile platforms.” This “…gives SAP the opportunity to develop new types of business applications for mobile devices… .”

Yankee: “…the fusion of cloud computing, application mobility and social media to transform the enterprise mobility space.”

A Software Insider’s Point of View:  SAP “…also gains access to the financial services and public sector markets.  On the geographic front, Sybase has strong presence in the China market, an area where SAP sees future growth.”

Forbes: “Sybase is not enough to make SAP entirely relevant in scope and scale (and it goes without saying that in this land of giants, Sybase was not large enough to survive on its own). But it picks up a solid asset, with businesses in financial modeling and mobile databases that are essential for SAP to stay in the game.”

Good stuff – very relevant and right on the mark from my perspective.

I have another theory. I’m sure all of the above is true, but an interesting side thought occurred to me. I kept thinking about the Oracle lawsuit against SAP involving the alleged inappropriate downloading of Oracle proprietary data by SAP. I took a glance at the Oracle complaint. It’s amazing. Take a look at some of the allegations:

“This case is about corporate theft on a grand scale…”

“Oracle brings this lawsuit after discovering that SAP is engaged in systematic, illegal access to…Oracle’s computerized customer support systems.”

“Through this scheme, SAP has stolen thousands of proprietary, copyrighted software products and other confidential materials that Oracle developed to service its own support customers.”

“In late November 2006, there occurred unusually heavy download activity on Oracle’s password-protected customer support website. …The access and download activity Oracle observed on its systems…did not resemble the authorized, limited access to which its customers were entitled. …SAP employees using the log-in credentials of Oracle customers with expired or soon-to-expire rights had, in a matter of a few days or less, accessed and copied thousands of individual Software and Support Materials.”

“…using one customer’s credentials, SAP suddenly downloaded an average of over 1,800 items per day for four days straight (compared to that customer’s normal downloads averaging 20 per month.”

“Other purported customers hit the Oracle site and harvested Software and Support Materials after they had canceled all their support with Oracle in favor of SAP TN (TomorrowNow).”

“…a user on an SAP TN computer signed on as Oracle customer Honeywell International…to access Oracle’s support system and copy literally thousands of Oracle’s Software and Support Materials in virtually every product library in every line of business.”

“…Oracle to date has indentified more than 10,000 unauthorized downloads of Software and Support Materials relating to hundreds of different software programs.”

“…some users logged in with user names of “xx” “ss” “User” and “NULL”. Others used phony email addresses like test@testyomama.com…”

“…one user…appears to have logged in using the credentials of seven different customers in a span of just 15 days – all from SAP computers in Bryan, Texas. All of these customers whose IDs SAP appropriated had one critical fact in common: they were, or were just about to become, new customers of SAP TN – SAP AG’s and SAP America’s software support subsidiary whose sole purpose is to compete with Oracle.”

WOW! This is heavy duty. I’m not a lawyer. I don’t know if all or any of this is true or accurate, but it would seem that if there were even a small degree of accuracy, it would be a big problem for SAP. We do know however that as a result, SAP announced in mid 2008 that it would shut down its TomorrowNow division.

I find this really interesting. SAP requires access to Oracle products and code to develop their products. SAP is actually Oracle’s biggest ISV. SAP Business Apps drag a lot of Oracle DB along with it. So SAP needs access to the Oracle Database Technical Reference material to build its product. A division of SAP, Business Objects, needs access to Oracle Applications to build their products. You can’t build worthwhile SAP BusinessObjects Rapid Marts without knowing intimately, at a programmatic level, what the Oracle Application is doing.

Think about this as well. A year ago or so you could go to the Oracle Partner Network site and see SAP and Business Objects products listed. If you go to that site today you see products from other companies like Teradata and IBM/Cognos that compete with Oracle but you do not see SAP or Business Objects.

If you’re SAP and you’re dealing with a major lawsuit alleging inappropriate and illegal access to proprietary data and you need access to Oracle to build your products, what do you do? Well – perhaps two things:

Plan A) You work with Oracle and try to negotiate some limited access agreement. After all, Oracle does make a ton of money, probably close to a billion a year, from SAP apps customers that use the Oracle database.

Plan B) You have to have a Plan B and it better be better than plan A. Is it possible that Plan B is figuring out how to no longer rely on the Oracle database?  That’s what I’d be doing. You acquire Sybase. You embed it in your cloud offerings. It’s the store for mobile applications. You sell it to every new customer. You bundle it in SMB and mid-market channel sales. You try like hell to convert Oracle database customers (impossible for a ton of technical reasons, performance concerns, and the conversion expense mountain you have to overcome, but nonetheless a noble effort that will rest on the shoulders of some unknowing SAP sales exec who will get shot in less than 12 months.)

I think this $5.8B Sybase acquisition was a great idea. SAP needs this to survive, but it’s not enough to win. I also think it was worth paying the huge premium.

Total cost of the TomorrowNow acquisition: TomorrowNow acquisition cost + $5.8B for Sybase + $.25B to $1B to settle illegal access suit = about $6.2-$7B.

From that perspective what is the big deal in SAP spending a quarter billion to a billion or so to overcome this issue? The problem is gone.  They further cut, or limit, their reliance on Oracle, they access and open new markets and revenue streams, and most importantly they make themselves more attractive as an acquisition target to IBM, whose mutual mission in life is to kick Oracle’s ass. This is two mints in one – a great idea and a dream come true!

I hope to blog again…

…and, I would really like your thoughts on this theory.

PS:  My personal opinion of SAP:  SAP is a good company. They didn’t, and wouldn’t, engage in the activities alleged by Oracle. However, the company they acquired, TomorrowNow, would. Unfortunately for SAP, they own TN and the liability and potential consequences of the poor judgment on the part of TN.

linkedin SAP Suckerfacebook SAP Suckertwitter SAP Suckergoogle buzz SAP Suckertechnorati SAP Suckerslashdot SAP Suckermsdn SAP Suckerdigg SAP Suckerreddit SAP Suckerstumbleupon SAP Suckerdelicious SAP Suckermixx SAP Suckersphinn SAP Suckerspaces SAP Suckerbuzz SAP Suckershare save 256 24 SAP Sucker

Posted in Business Intelligence | Comments (0)