Not What I Expected

If life ran like the script we all wrote at age 18, it would be pretty boring, wouldn't it?

More Tips for Carol Bartz

Susan Mernit wrote up "6 tips for Carol Bartz's first 100 days", and it's a good set of tips. I'd like to add 6a, and 7:

"6) Ask--and meet--the rank and file and get their ideas" 6a: And don't rely on your management to decide who amongst the rank and file talk to you.

I've seen this played out too many times--the new exec comes on board, and wants to talk to rank and file to get an idea how things are. They ask for this at meeting with their VPs. The VP of HR is asked to send out the request to the managers.

Big mistake--what happens here is that management decides that there is *no way* the CEO is going to hear from anyone in their organization unless it's someone personally selected by management who already knows the drill (or can be threated or bribed into knowing the drill real damn quick), and can learn the script for the meeting.

What happens? Well, if the CEO is clever, they're going to have a list of every toadie in the organization, and also know that management needs to be cleaned out. If they aren't clever, they go away possibly wondering why everyone they talked to was either a supervisor or tech lead, and they have some really interesting (ie favoring the manager who sent them) ideas on how to fix the organization.

Guess what happens? Either nothing or decisions are made that make no strategic sense to anyone outside of the company, and the corporation continues down the garden path to being bought out or filing chapter 11. The decisions seem to favor a small group of people, who then make out like bandits.

And that segues into:

7) Don't assume management is on your side. In fact assume that entire layers of management are pretty happy with the way things are, and don't want anything to change.

Yes, even though this seems strange in a company that is bleeding from all pores, there are people in these companies who are running their own game, and as long as their fiefdom is doing fine, they're not interested in anything changing, thanks. These people are usually pretty short-sighted, both from a strategic and time sense: they're not interested in what's going to happen in 12-18 months, because their horizon doesn't extend that far. They don't care about the rest of the corporation, except how it helps them achieve their ends.

A fairly quick way to find out if there's an entire layer of management that's a problem is to play a game I call "chase the meme". Remember the rank and file? Ask them to let you know when the directive arrives.

A good directive is something like "managers are requested to spend all their employee relations budget this quarter, and to ask employees at their department meetings how they should spend it. Please communicate this to your organization.". It's bland, and it asks that it be communicated all the way down.

Now, let it loose. The next exec meeting, ask that this be communicated. Enlist HR to get the directive pushed out to the first layer below the execs.

Now wait. When I took part in this, the company in question had a *10%* rate of the directive making it to the first level managers and their staff. It turned out that the director level managers across the entire company were ether dropping it on the floor or asking the HR manager to *not* communicate it.

Armed with that information, the CEO started poking at the director layer, and found that they had effective set up a communications wall, and were cheerfully running their own organizations to their own benefit. I wish I could say that this was dealt with, but it took two more regime changes before that CEO was able to get rid of the lot of them.

Seriously, you don't want to get there. At that point, it took an amazing amount of luck and hard work to get that company out of its death spiral. Others--not so lucky.

January 19, 2009 in biz, computers, management | Permalink | Comments (0) | TrackBack (0)

Hey Bill--here's where your future BSCS students went!

The University of Illinois (remember NCSA Mosaic? remember NCSA anything?) has so many applicants to their undergrad business school that they can pick and choose among the best.

UI isn't the only school that has had their business school applications trend upwards. And why not? That business degree is likely going to command a better starting salary, fewer work hours, and a much smaller chance that a pink slip and offshoring of their job is going to be the reward for their work.

These are the bright students. remember?

March 24, 2006 in biz, computers | Permalink | Comments (3) | TrackBack (0)

ABAP--you can't ignore it

Over in O'Reilly Developer Weblogs Mark Finnern notes that the programming language that had the biggest jump in popularity in the past year is ABAP.

Yup--if what I'm seeing is any indication, we have a bunch of corporations who are swapping out their home-grown internal apps for SAP, and where you have SAP, you have ABAP. Yes, there's Java interfaces into SAP apps, but thee's going to be a lot of ABAP for a long time.

I started looking ar ABAP a year ago, when enough stuff came on line that I needed to know what it looked like and how it acted. Yeah, I may be the program manager, but the program manager still wants to see your code. I also coded in COBOL way too far back when, so I have a general interest in what's being done these days.

Speaking of COBOL, what ABAP reminded me of is what would happen if COBOL and /bin/csh went away for a long weekend. I can understand why it's so popular--you can put things together pretty quickly, and you don't have to have the learning curve for Java. If you're running a "plug and chug" coding shop, that's an important consideration.

If I were packing a portfolio of programming and scripting languages, I'd probably add it to my repetoire. I'd not likely depend on it as a one-trick pony over the long term, though.

And O'Reilly--when are you going to do a book on ABAP? It wouldn't hurt my feelings to see another player in the pool...

March 12, 2005 in computers | Permalink | Comments (0) | TrackBack (0)

Chuqui 3.0

Recent Posts

  • More Tips for Carol Bartz
  • The Web Comics Conundrum, or "Am I paying for past or future performance?"
  • Is retail doing that badly?
  • As Roberto Luongo Feels a Chill
  • Fruits of Summer
  • The "IT Upgrade" for the UK National Health Service that isn't
  • Picking up the prescription: world-class stupid marketing
  • I am seriously unhappy with Sprint
  • "Have Gun--Will Travel" Ages Well
  • Rethinking my position in the metals market
Subscribe to this blog's feed

About

Blog powered by TypePad

Archives

  • January 2009
  • June 2007
  • December 2006
  • September 2006
  • August 2006
  • May 2006
  • April 2006
  • March 2006
  • February 2006
  • January 2006

Categories

  • baseball
  • biz
  • cell phones
  • computers
  • customer service
  • ehlers-danlos
  • Food and Drink
  • foodie
  • hockey
  • IS
  • IT
  • Keenan
  • management
  • marketing
  • medical
  • on the road
  • project management
  • retail
  • sales
  • Sports
  • sports biz
  • stuffage
  • Television
  • Web/Tech
  • Weblogs

Categories

  • baseball
  • biz
  • cell phones
  • computers
  • customer service
  • ehlers-danlos
  • Food and Drink
  • foodie
  • hockey
  • IS
  • IT
  • Keenan
  • management
  • marketing
  • medical
  • on the road
  • project management
  • retail
  • sales
  • Sports
  • sports biz
  • stuffage
  • Television
  • Web/Tech
  • Weblogs