Slashdot Mirror
Ballmer Turns To Geeks For Salvation
jfruhlinger writes "One of the critiques of Steve Ballmer as Microsoft CEO is that, as someone who came up through sales, he doesn't really get what running an innovative tech company is about. With the company board starting to question his performance — he didn't get his bonus last year because of the Kin debacle, for instance — it appears that Ballmer is planning to install engineers in high places to turn the company around."
Microsoft is dominated by high-end market-consuming business strategists at the top. Bill could do both; Ozzie stepped down because he couldn't replace Bill in that role. There's just no way that there's an internal tech person with the force of will to push the business guys around and all he or she needed was Ballmer's okay to make more impact.
Much less five of these folks. I just don't see it -- in my opinion, Microsoft needs to acknowledge it's becoming IBM, and move on gracefully to another stage in its corporate development.
If I was on the board, I would have screamed for Ballmer's dismissal in September 1999, when he drove the MS share price down by 3.8% in a single day by saying "There is such an overvaluation of technology stocks that it is absurd. I would include our stock in that category." Ballmer might be a good business person, but as far as setting the corporate culture, he is an epic fail. The big question is, who should replace him as CEO?
I've abandoned my search for truth; now I'm just looking for some useful delusions.
That's been my experience with 25+ years in a major IT player. What engineers want, is someone that will listen to them. And someone who will grab them under the arms and pull them up and support them when things get ugly, and they get knocked out cold. It's quite simple actually, but it's quite amazing how few managers can do it right. I have seen a few cases exemplary performance. When I was in southern France, doing some firefighting on a project where the shit had hit the fan, and knocked the damn thing over. A couple of the employees there told me that they were coming in on the weekend to work on problems. This was not an order from the management there. Their attitude so impressed me, that I said, "I'll be in with you guys!" The second line manager got wind of the renegade action and showed up in the lab on the weekend. She didn't ask any questions about progress, but just discretely sat at a terminal, and did manager email stuff. And brought pastry snacks for the folks. But you had the feeling that she was there for us, in case we needed anything. One manager did a great job of filtering us from nasty emails about bad management decisions, that would be reversed anyway. Some folks in another department asked us, "Hey, did you see the email about capping our overtime pay?" There was another email a week later, that it was retracted. So our manager had tried to shield us from some unnecessary stress.
On the other hand, my manager left the company. A manager from another department was appointed as his successor. He did nothing for a month, aside from forwarding management and policy notes that he received to us. He didn't even come by to introduce himself. Well, duh! I started the rumor that he didn't exist, but was actually some kind of ELIZA type forwarding engine. Then he invited is to a meeting.
One brilliant engineer colleague of mine had excellent people skills, but declined to be put in the manager career path. He told me, "I don't want to explain to employees all day, why they can't have a bigger monitor."
So, back to the point, Ballmer has a very aggressive ego. I'm not sure if he will be able to take advice from a "mere" engineer. And I'm not sure that good engineers will be able to take his abuse for long.
Schroedinger's Brexit: The UK is both in and out of the EU at the same time!
"Software engineers suffer from the same basic issue. They tend to be so extremely technology oriented that they get completely lost in all the features that should be included, all the bells and whistles, and seem to regard an interface as something you paste on afterwards (inter-face, something which is the area where the user rubs against the technology), when the interface is the personification of the whole system, as well as the public face of the program and the company itself."
I think this perspective is heavily colored by the rise of software engineering as a mainstream career, and the youth-dominance of the late 90's early 00's. When I was a 28 year old code cowboy in 1998 NYC, working with other late 20's code cowboys, I would have heartily agreed with you. Now, however, those same cowboys (and I) are significantly more focused on ROI, usability, and discovering the customer's desires. Software engineering is maturing, and so are software engineers.
Frankly, I have had as hard a time -- if not harder -- getting the sales people to put together a credible revenue projection to justify a new project as with getting engineers engaged in considering value for dollar. The engineers are interested in solving the problem once you show them it is just math and measurement. The sales people want to run with their gut and tend to be optimistic (admittedly; because that is important to successfully engaging a customer) about the probable revenue.
Stop-Prism.org: Opt Out of Surveillance
Like it or not, computers are becoming appliances, so everything in the future needs to be designed with a UX in mind... which is why Apple places UX and OS designers in the top position, while all the engineers and salespeople work below them.
Parent is right - an empty executive chair would be funny on so many levels. Balmer's MIA business strategy, defecting MS executives, the CIO purchasing logic that keeps the company profitable, and of course it's the weapon of choice in the MS executive suite.