It looks like nothing was found at this location. Maybe try a search or browse one of our posts below.

What’s the difference between culture and stereotypes?

Bear with me.

In Bananas, Woody Allen plays Fielding Mellish, a nebbish from Brooklyn (maybe it was Queens) who finds himself leading a Latin American revolution.

For one reason or another (and, given the source, probably no reason at all), Mellish finds himself back in the United States. His hosts helpfully provided a translator. But because he was a schlimazel from Brooklyn who only spoke English, the translator listened to the welcomer’s English-language statements and repeated them, in English, to Mellish, and then repeated Mellish’s response, also given in English, back to the other conversant.

It’s funnier on screen.

Mellish’s hosts decided to provide a translator based on their expectations. Doing this isn’t wrong, although validating our expectations improves our outcomes even more.

But what we all-to-often do is invert the sequence, basing our expectations on our decisions. That’s when we start to ignore the facts that are right in front of us.

Stay with me. We’ll get to the point soon.

Back when IT was Data Processing, business managers had conversations with programmers about what computers could do. The conversational template went like this:

Business Manager: “Can you get the computer to do x?”

Programmer: “Sure,” after which the programmer got the computer to do x.

A slightly different template went like this:

Business Manager: “Can you get the computer to do y?”

Programmer: “No, computers don’t work like that. But I can get the computer to do z. Will that help?” After this, and a few more back-and-forths, the programmer got the computer to do a. And after quite a few of these exchanges, programmers had the computer doing abcdefghijklmnopqrstuvwxyz.

These conversational templates and their results worked well enough to create the first-generation of legacy applications that businesses ran on for decades. And if you think it all sounds a lot like Agile you aren’t wrong.

Anyhow, someone decided programmers couldn’t be expected to converse with Regular Ordinary People. And so they invented the business analyst to, very much like the translator in Bananas, translate between Geek English and Business English. In the process they convinced both business managers and programmers that they must have been fooling themselves when they thought they’d been having productive conversations.

Which (finally!) brings us to this week’s topic – the difference between stereotypes and cultural norms.

They certainly do resemble each other. A stereotype creates an expectation that all members of some identified group will behave the same way when faced with a given situation.

A cultural norm, in contrast, is the approved response to a given situation exhibited by all members of a self-identified group that’s enforced by the group through peer pressure.

And yet, most of us, most of the time, consider stereotyping to be a bad idea, especially when they are guilty of stereotyping us.

At the same time most of us, most of the time, consider our culture to be one of our strengths and sources of strength.

What’s the difference? First of all, stereotypes tend to be disparaging, used to describe something about them that makes them inferior to us. That’s as opposed to cultural traits, which tend to be complimentary, describing something about us that makes us superior to them.

Bob’s last word:

Still too subtle a difference? Let’s try this: When we deploy a stereotype we rob members of the group we’re stereotyping of their individuality. When we express a cultural trait we’re usually trying to achieve coherence, trust, and membership. Culture preserves our individuality while establishing that we’re part of a larger whole.

Bob’s sales pitch: And on an entirely different subject, hop on over to CIO.com to read my latest article there. It’s about Lifecycle Management and I think you’ll find it useful. Whatever else, I think it will give you a practical take on how to handle one of IT’s most significant architectural challenges.

Work hard and keep your nose clean.

That’s good advice if you want a sweaty proboscis. For career advancement, hard work and an unsoiled schnoz give you a stable place to stand while you get your bearings and plan your strategy. At best. At their worst they stereotype you as cannon fodder — trustworthy, reliable, and useful, but ultimately disposable.

Unless you work for a well-run company. If you do, a reputation for integrity and going the extra mile or three is the best way I know to rise to executive ranks.

Which brings us to this week’s question: Lots of people would like to achieve executive rank. Many are smarter and more talented than the relatively few who succeed. What’s the difference?

Since there are as many answers as there are types of executive, answering the question requires a list of the various types of executive you’re likely to find (and, perhaps, be). Did I say types? Think of these as archetypes — styles of leadership in a pure form. Real executives blend one or more of the archetypes that follow:

Visionary: The Visionary has, or has adopted, a new idea and wants passionately to turn it into reality.

The Visionary’s best path to the executive ranks is entrepreneurship. Excellent at selling their vision, Visionaries build a business around themselves, surrounded by managers and employees who buy into the vision, and the possibility of making it happen.

Visionaries are usually better at defining what has to happen than at making it happen. The successful ones, through luck or skill, have a second-in-commands to do that.

More don’t. The world has no shortage of unfulfilled visions.

General: Generals view every situation as a battlefield, and everyone else as a soldier or officer who is with them or against them. As a result, Generals are likely to be ruthless. Winning is the measure of all things.

Some are Generalissimos — in charge. Generalissimos are often better at achieving and holding onto power than at leading a successful organization. Among the reasons: Generalissimos see everyone in the world as being either friend or foe and treat every foe as a threat to be neutralized. All that’s required to be classified as “foe” is to disagree.

Other generals accept civilian leadership — perhaps from a visionary — and see their role as making sure their side wins.

The best generals are excellent strategists, tacticians, and logicians, and recognize the value of smart, well-trained, disciplined men and women throughout their organization.

The worst fight unnecessary battles because fighting battles is what they know how to do.

And because winning battles builds loyalty among the troops, whether or not the battle was worth fighting.

Head Coach: Head coaches have a lot in common with generals. Highly competitive, they build organizations that are good at winning, and know how to choose winning strategies and tactics.

Head coaches share a limitation with generals — they see the world as a zero-sum game, where if they want to win, someone else has to lose. Head coaches are, however, less ruthless than generals. They are more likely to recognize and accept the rules of the game, and know that losing a game doesn’t mean losing a season.

The best aspect of Head Coaches is that, as is the case in football and basketball, they recognize that they aren’t the stars. The worst is their fondness for illustrating every conversational point with a sports metaphor.

Prairie Chickens: Every spring, male prairie chickens congregate in acre-or-so areas called “leks.” In each lek they carve out small territories and do the prairie chicken dance to attract females. The male in the center of the lek is most successful. Females ignore those at the periphery entirely.

The center males aren’t, as you might think, the meanest, toughest prairie chickens around. My former colleague in ethology, Henry McDermott, proved this through years of careful observation: Those male prairie chickens that don’t die from disease or being eaten move closer to the center by taking the territories of the dear departed.

Many corporate executives achieve high rank in much the same way: They avoid failure rather than achieve success, drifting upward by filling the holes left by bolder executives who slipped up and were asked to vacate the premises.

Visionaries, generals, head coaches and prairie chickens. See yourself anywhere on the list?

If you don’t, never fear. You still have a chance. Seven, really.

That’s how many C-archetypes are left … assuming I don’t think of any more.