The Business Sensei

Help Star Performers Ramp up the Whole Team

Originally published in Corp! Magazine.

Do basketball players have hot hands? A hot hand in basketball is when a player is shooting better than normal. A star player with a hot hand is, therefore, going to be shooting incredibly well. Many players claim that it happens, and many statisticians point out that it doesn’t. The argument against basically says that when you look at the frequency that a missed shot follows a successful shot, you find that the whole “hot hand” thing is just an illusion. It may feel like something is happening, but the results don’t match.

The statisticians, however, are missing a key point: a basketball player is not on the court by himself. In other words, he’s not playing in isolation. When a player is shooting extremely well, the other team is going to put more effort into guarding him. Of course, if that’s correct, the extra effort expended guarding that star player should leave less available to guard other players on the team. In other words, the increased performance of a star should have the effect of increasing the performance of the entire team.

Once someone actually thought to ask that question and look at star performance in that context, the answer turned out to be that hot hands exist and that true star performers don’t just perform well on their own –they increase the performance of everyone on the team.

Star performers in a business setting are the same, or at least they can be. The trick is to set up your team so that star performers increase everyone’s productivity rather than just their own.

To begin with, what are your incentives? If you’re only rewarding team members for their individual performance, you’ve got a problem. You’ve told your star performer to make herself look as good as possible, even at the cost of other team members: Imagine a basketball team where each player was only concerned about his own personal record and not about whether the team won or lost. The fact is, such a team wouldn’t be all that successful. I’ve seen any number of software development teams, for example, structured in just that way, with exactly the expected results.

Part of what enables a star to be a star is the strength of the team. While it can be comforting to argue that focusing on individual incentives will weed out the weaker performers and leave you with the star players, that’s a bit like arguing that your basketball team only needs Michael Jordan. He’s a fantastic player, but even he can’t be everywhere on the court. Jordan is so good in part because he has a strong team supporting him. Conversely, the team is so good in part because of Jordan.

This brings us to the next point: how do people communicate on the team? This can be tricky: everyone sends emails around, but that doesn’t mean they are communicating. It’s important to look at the patterns of conversation and communication in the group: quite often, one person is the center of the wheel; even when a team member is ostensibly addressing the group, he’s really talking to that one person, and no one responds until that one person weighs in.

Related to communication is the question of how well your teams argue and makes decisions. A team which never argues is also incapable of making good decisions. Sure, they may get lucky once in a while: a blind basketball player might also sink the occasional basket. Effective decision making requires being able to debate issues, ask pointed questions, disagree strongly, and eventually come to a consensus that everyone can work with. Teams that can’t do that tend to not benefit from star power.

What is the boss’s attitude toward giving and receiving help? At one company, the manager who took over a particularly high performing team had the attitude that, “you do your job, and let the other guys take care of themselves.” Although the star performers continued to do relatively better than everyone else, overall productivity dropped off rapidly after that manager took over the team. People stopped helping each other. Conversely, in a different department, the manager who came in with the “we’re all in this together” attitude saw his team performance skyrocket. Although the best performers on his team were not as individually strong as the best performers on the first team, on the second team the stars really brought everyone else up, and everyone else really supported the stars. In basketball, five people working together will beat five people working apart.

Hot hands exist, in basketball and in virtually all other areas of team performance. It’s only a question of whether or not your team is set up to take advantage of them when they occur.

My Hovercraft is Full of Eels

Originally published in Corp! Magazine.

“Is the product done?” a certain manager asked during a product review meeting.

“It is done,” replied the engineer building the product.

“Are there any problems?”

“There are problems.”

“What is the problem?”

“It does not work.”

“Why doesn’t it work?”

“It is not done.”

I will spare you the transcription of the subsequent half hour of this not particularly funny comedy routine. The manager and the engineer managed to perform this little dance of talking past one another without ever seeming to realize just how ludicrous it sounded to everyone else in the room. It was rather like Monty Python’s classic Hungarian-English phrasebook sketch, in which translations in either direction are random. In other words, the Hungarian phrase, “I would like to buy a ticket,” might be translated to the English phrase, “My hovercraft is full of eels.”

It was extremely funny when Monty Python performed it. As for the manager and the engineer, well, perhaps they just didn’t have the comedic timing of Python’s John Cleese and Graham Chapman.

[SYSTEM-AD-LEFT]As it happens, “my hovercraft is full of eels” moments come about far too often. What was unusual in this situation is that it involved only two people. Usually, considerably more people take part. Thus, instead of a not particularly amusing exchange between two people, there is an extremely frustrating exchange involving several people. The most common failure to communicate is the game of telephone: as the message passes along the line, it becomes increasingly distorted.

What I hear from teams over and over is, “We are communicating! We send email to everyone.” This is where the hovercraft starts to fill with eels. Broadcasting is not really communicating: effective business communications require a certain amount of back and forth, questioning and explaining, before everyone is on the same page.

Who talks to whom? When you send out an email, do questions come back to you? Or do people on the team quietly ask one another to explain what you meant? While it’s comforting to believe that every missive we send out is so carefully crafted as to be completely unambiguous, very few of us write that well. Of that select few, even fewer can do it all the time. Particularly in the early stages of a project, if there are no questions, then there are certainly problems.

When someone else asks a question, either via email or in a meeting, does everyone wait for you to respond? Even worse, does Bob only jump into a thread if Fred jumps in first? Who is Bob responding to at that point, you or Fred? Are you still addressing the main topic or is the hovercraft starting to become eel infested?

It can be extremely frustrating to ask, “Are there any questions?” and receive either dead silence or questions about something trivial. It can easily become tempting to assume that there are no questions and just race full speed ahead. However, until employees figure out how much each person understands about the project and how you will respond to apparently dumb questions, they will be cautious about what they ask. Their curiosity is as much about one another and about you as it is about the project. How that curiosity gets satisfied determines whether you have productive conversations or a hovercraft that is full of eels. In the former case, you get strong employee engagement; in the latter case, you don’t.

If you’ve been working with a team for some months, or longer, and people are still not asking questions then there are really only two possibilities: either your team is composed of professional mind-readers or you are about to find a room full of those pesky eels. No project is ever perfectly defined from the beginning. Questions and debate should be ongoing throughout the development or production cycle. A lack of questions tells you that there is a lack of trust between the team members and between the team members and you. When trust is lacking, so is engagement.

Now some good news: remedying that lack of trust isn’t all that complicated. It does, however, require a certain amount of persistence and patience.

Start by highlighting each person’s role and contribution to the project. Why are they there? What makes them uniquely qualified to fill the role they are in? Be specific and detailed. If you can’t clearly define their roles, you can rest assured that they can’t either.  Questions come when people are clear about their roles. Disengagement comes when people are not clear about their roles.

Prime the pump with questions. Demonstrate that you don’t have all the answers and that you need the help of the team to find them. Give each person a chance to play the expert while you ask the dumb questions. When you set the tone, the others will follow. Communications start with the person in charge.

Separate producing answers from evaluating answers. Collect up the possibilities and take a break before you start examining them and making decisions about them. Brainstorming without evaluating allows ideas to build upon one another and apparently unworkable ideas to spark other ideas. Pausing to examine each potential answer as it comes up kills that process.

Encourage different forms of brainstorming: some people are very analytical, some are intuitive, some generate ideas by cracking jokes, others pace, and so on. Choose a venue where people are comfortable and only step in if the creative juices start to run dry or tempers start to get short. In either case, that means you need to take a break.  Intense discussions are fine, heated discussions not so much.

Initially, you will have to make all the decisions. That’s fine, but don’t get too comfortable with it. As trust and engagement build, the team will want to become more involved in the decision making process. Invite them in: that demonstration of trust will further build engagement and foster effective communications. Effective communications, in turn, builds trust and engagement.

Having a hovercraft full of eels isn’t the real problem. The real problem is what a hovercraft full of eels tells you about the trust, engagement, and communications in your company.

Don’t over commit to start the new year!

Why do so many people end up overcommitted at work, in volunteer activities, or socially?

The tendency to say “yes” to any request stems from several sources.

First, most of us like to think of ourselves as the type of person who helps others. Thus, when a friend or colleague (or boss) asks for help, that request immediately triggers us to think, “But if I don’t help, what does that say about me? I’m not <selfish/mean/self-centered/uncaring/etc.” So, we agree to help in order to protect our self-image.

Second, and related, is what’s known as social theater: in certain environments, there are certain role expectations that are taken for granted. Helping others is often one of those expectations. Therefore, when someone asks, we agree almost automatically, without really thinking through the consequences, or even the wisdom, of the decision. Essentially, behaviors that we learned at some point in our lives without really thinking about them become automatic behaviors later when the right trigger presents itself.

Third, many businesses foster a culture of obedience and pressure to always get more done in less time. Although this cultural baggage is ultimately destructive to the business, as it leads to burnout and corner-cutting, in the short-term it appears to be very rewarding. Thus, it gets repeated and hailed as an emblem of the dedication and productivity of the employees. It is, in reality, a sign of a company with relatively low functioning teams: high performance teams know their limits and are willing to stand up for them. Low functioning teams, and the members thereof, routinely bite off more than they can chew.

Fourth, when we over promise and fail to deliver, we frequently assume that the problem lies within us: if we’d just worked harder, if we were just a little more skilled, if we just a little smarter, and so forth. Thus, we become even more determined to “get it right” the next time around. In truth, the problem was not that we weren’t working hard enough, or weren’t smart enough, etc. The problem was that we simply tried to do too much, not some personal failing that can be corrected by working harder.

So how do you prevent this from happening?

There are several techniques, which can be used singly or in combination.

One trick is to identify the thought or image that pops into your head the moment someone asks you for help. It can be hard to catch this, but with a little effort, most people will discover that some image flashed across their brain and that they are reacting to that image instead of the request for help. That image might be a thought about how important it is to help others, or a belief that other person can’t succeed without your help, or an image of being fired for not helping, etc. This is one of those situations where if you ask 99 people to describe their image, you’ll get 99 responses :). Once you catch the image, you can look at it and ask yourself if it’s actually realistic. Do they really need your help that badly? If you’re a productive employee, do you honestly think you’ll get fired for saying “no?”

Another thing to recognize is that boundary testing is a normal part of all relationships: we instinctively attempt to understand our environment, and that includes understanding what we can and cannot expect from the people around us. Not knowing the boundaries is anxiety producing. Children do this sort of boundary testing all the time, and when they don’t find a boundary their behavior only gets worse until they get a reaction. Adults are different only the sophistication (and even that is arguable!) of their boundary testing. Thus, saying “no” is a form of setting boundaries. Setting boundaries actually helps make other people feel more secure because they now know what to expect from you, and also establishes you as a peer of the person making the request. Consider, the only people who are, in our society, nominally prohibited from setting boundaries are children. Children are typically expected to comply with most adult requests (how often did you hear, “When your mother asks, it’s not a request!” when you were growing up?). Thus, it’s important to recognize boundary testing and also recognize that setting limits is beneficial for everyone.

Another approach is to reverse the question: “I’d love to help you, and I’m not sure how I can fit this into my schedule. Let me go through with you what I have to get done over the <time> and you can help me figure it out.” Frequently, people ask for help without realizing the degree of imposition. Going through your constraints and asking them to help you figure out how to fit in their request is often a good technique to get them to realize just how much they are asking of you. If, in the end, you still decide to accept the request, you’ve at least enabled them to recognize just how big a favor they’re asking.

Note that if your boss is making the request, you can still apply this approach, with a slight modification: “I would love to do this, and I’m concerned that if I agree, these other projects will suffer. Please let me know your thoughts on how I should prioritize these different tasks.”

By the way, it can help to block out chunks of time on the calendar representing the total amount of time you expect a task to take (when you estimate how long a task should take, add 25%… most of us underestimate!). Tasks never seem that big when you’re thinking about them abstractly, but when you create a visual representation, you’ll be amazed how much time you’ve allocated.

All right, so  you’re already over-committed, what do you do? The best thing is to take an honest look at your tasks, prioritize, and then start contacting people. You can start with either your lowest priorities or your most recent “Of course I’ll do that!” Either way, you need to say, “I’m sorry. I know I told you I would help you, and I’ve discovered that these prior commitments are going to take much longer than expected.”

No, the other person won’t be happy. However, they will be a lot happier that you told them early on, not at the last minute. The longer you wait, the more painful the conversation becomes, the angrier they’ll be, and the worse you’ll feel. Moreover, you’ll be that much more likely to give in when they start complaining, leaving you feeling overworked and bullied.

Of Cats and Unwanted Prizes

Originally published in Corp! Magazine

I have three cats. Cats being the creatures that they are, I have only to sit down to read a book and instantly there is a cat on my lap. Regardless of which cat it is, a familiar pattern ensues: first, the cat carefully positions itself in front of my book. Once I adjust to move the book, the cat then carefully positions itself on one of my hands. This continues until I give the cat the attention it’s seeking. At that point, it first butts its head against me and then, purring loudly, turns and sticks its behind in my face.

I am sure that there are people who find this end of a cat absolutely fascinating. I’m even quite sure that there are contests in which cats win awards for having the most beautiful behind. For cat breeders and cat fanciers, it can be a big deal to win one of these cat trophies. It is a cause for great celebration.

In an office environment, however, a catastrophe is anything but a cause for celebration.

The worst thing about catastrophes is that they happen about as often as a cat sitting down on top of the book you’re reading. At least, to listen to some managers, it certainly sounds that way. Somehow, every little thing, every small problem, was magnified until it had the aura of impending doom. In short, every setback was becoming a prize for the cat with the most beautiful behind. At one company, the conversation went something like this:

“We’ve found a major bug in the software.”

“We can’t delay the ship.”

“We can’t ship with this bug.”

At that point, the manager started screaming that the product would go out on schedule, or else. When he finally calmed down and I was able to talk with him privately, he told me that he knew that if the company didn’t ship on time, the customers would abandon them and they would go out of business. He was happy to ship non-functional software to avoid that fate.

When he calmed down still further, he agreed to delay the ship.

I am sure that most readers are chuckling to themselves right now. After all, delays in software are legendary. Obviously, this manager was overreacting. True enough; the question is, why? Why would a perfectly sensible, intelligent man react so negatively to something which is, frankly, a common event in the software business?

It turns out that this particular company prided itself on holding to very aggressive schedules. The schedule was so aggressive that they were virtually always running behind. Therein lay the problem.

Time is a funny thing. We react very differently depending on how we perceive it. Being behind schedule all the time had the effect of generating a certain sense of urgency, which was the stated intent of the aggressive schedule. Unfortunately, the urgency generated in this situation was of the slightly breathless, heart-pounding sort similar to what one might experience if being chased by a very large cat of the “has a big mane” variety.  A cat which, I might add, is looking to do more than just sit on your book.

The problem with aggressive schedules is that, in fact, being behind schedule can generate the same panicked response in people that they would feel in a situation which actually was dangerous. While in those situations, we’re very good at running away or fighting desperately, but we’re not good at making cool, rational decisions or developing innovative solutions to problems. Each pebble encountered along the road becomes a giant boulder. When we do finally get to the end of the project, rather than feeling a sense of accomplishment and success, there’s more of a sense of relief that at last it’s over. What’s missing is the thrill of victory that energizes people for the next project. That feeling of success is the key to getting, and keeping, people excited and motivated.

In short, instead of the team beating the schedule, the schedule was beating them.

Conversely, when a team is running slightly ahead of schedule, something very different happens. Running ahead of the game means that the team is feeling a constant sense of success. When people feel successful, they work harder, they are more creative, and they look forward to coming into work each day. Teams that are running ahead of schedule are more likely to develop innovative new solutions to problems rather than just slap on band-aids. Feeling that you have the time to stop and think is critical: just think about how easy it is to miss the obvious when you are feeling rushed.

The trick is to view your schedule as a living document. It’s something that you will constantly adjust according to the situation, especially at the beginning of a project. The less you know about potential difficulties down the road, the harder it is to plan: so don’t. Instead, plan to plan. As you move forward, you can revise and project the schedule further and further into the future.

If you find yourself running behind, that’s feedback. Pay attention to what it’s telling you. Is something more complicated than expected? Is someone overwhelmed with a task that turned out to be significantly more time-consuming than you thought? Did something go wrong? Is a vendor habitually late with parts? Is your schedule just plain too aggressive?

If you’re running ahead, that’s also feedback. It might mean that the schedule is too easy and your team isn’t being challenged. Be willing to become more aggressive. It could mean that you need to slow down: are people rushing and cutting corners? At one company, pressure on QA engineers to rush product inspections led to some very expensive and embarrassing recalls and some very irate customers. Moving way ahead of schedule could also mean that your team is working too hard too soon: success is a marathon, not a sprint. Burn out early and you won’t reach the finish line.

Leave the catastrophes to the cats.

Stephen Balzac is an expert on leadership and organizational development. A consultant, author, and professional speaker, he is president of 7 Steps Ahead, an organizational development firm focused on helping businesses get unstuck. Steve is the author of “The 36-Hour Course in Organizational Development,” published by McGraw-Hill, and a contributing author to volume one of “Ethics and Game Design: Teaching Values Through Play.” For more information, or to sign up for Steve’s monthly newsletter, visit www.7stepsahead.com. You can also contact Steve at 978-298-5189 or steve@7stepsahead.com.

My Hovercraft is Full of Eels

As published in Corp! Magazine

“Is the product done?” a certain manager asked during a product review meeting.

“It is done,” replied the engineer building the product.

“Are there any problems?”

“There are problems.”

“What is the problem?”

“It does not work.”

“Why doesn’t it work?”

“It is not done.”

I will spare you the transcription of the subsequent half hour of this not particularly funny comedy routine. The manager and the engineer managed to perform this little dance of talking past one another without ever seeming to realize just how ludicrous it sounded to everyone else in the room. It was rather like Monty Python’s classic Hungarian-English phrasebook sketch, in which translations in either direction are random. In other words, the Hungarian phrase, “I would like to buy a ticket,” might be translated to the English phrase, “My hovercraft is full of eels.”

It was extremely funny when Monty Python performed it. As for the manager and the engineer, well, perhaps they just didn’t have the comedic timing of Python’s John Cleese and Graham Chapman.

As it happens, “my hovercraft is full of eels” moments come about far too often. What was unusual in this situation is that it involved only two people. Usually, considerably more people take part. Thus, instead of a not particularly amusing exchange between two people, there is an extremely frustrating exchange involving several people. The most common failure to communicate is the game of telephone: as the message passes along the line, it becomes increasingly distorted.

What I hear from teams over and over is, “We are communicating! We send email to everyone.” This is where the hovercraft starts to fill with eels. Broadcasting is not really communicating: effective business communications require a certain amount of back and forth, questioning and explaining, before everyone is on the same page.

Who talks to whom? When you send out an email, do questions come back to you? Or do people on the team quietly ask one another to explain what you meant? While it’s comforting to believe that every missive we send out is so carefully crafted as to be completely unambiguous, very few of us write that well. Of that select few, even fewer can do it all the time. Particularly in the early stages of a project, if there are no questions, then there are certainly problems.

When someone else asks a question, either via email or in a meeting, does everyone wait for you to respond? Even worse, does Bob only jump into a thread if Fred jumps in first? Who is Bob responding to at that point, you or Fred? Are you still addressing the main topic or is the hovercraft starting to become eel infested?

It can be extremely frustrating to ask, “Are there any questions?” and receive either dead silence or questions about something trivial. It can easily become tempting to assume that there are no questions and just race full speed ahead. However, until employees figure out how much each person understands about the project and how you will respond to apparently dumb questions, they will be cautious about what they ask. Their curiosity is as much about one another and about you as it is about the project. How that curiosity gets satisfied determines whether you have productive conversations or a hovercraft that is full of eels. In the former case, you get strong employee engagement; in the latter case, you don’t.

If you’ve been working with a team for some months, or longer, and people are still not asking questions then there are really only two possibilities: either your team is composed of professional mind-readers or you are about to find a room full of those pesky eels. No project is ever perfectly defined from the beginning. Questions and debate should be ongoing throughout the development or production cycle. A lack of questions tells you that there is a lack of trust between the team members and between the team members and you. When trust is lacking, so is engagement.

Now some good news: remedying that lack of trust isn’t all that complicated. It does, however, require a certain amount of persistence and patience.

Start by highlighting each person’s role and contribution to the project. Why are they there? What makes them uniquely qualified to fill the role they are in? Be specific and detailed. If you can’t clearly define their roles, you can rest assured that they can’t either.  Questions come when people are clear about their roles. Disengagement comes when people are not clear about their roles.

Prime the pump with questions. Demonstrate that you don’t have all the answers and that you need the help of the team to find them. Give each person a chance to play the expert while you ask the dumb questions. When you set the tone, the others will follow. Communications start with the person in charge.

Separate producing answers from evaluating answers. Collect up the possibilities and take a break before you start examining them and making decisions about them. Brainstorming without evaluating allows ideas to build upon one another and apparently unworkable ideas to spark other ideas. Pausing to examine each potential answer as it comes up kills that process.

Encourage different forms of brainstorming: some people are very analytical, some are intuitive, some generate ideas by cracking jokes, others pace, and so on. Choose a venue where people are comfortable and only step in if the creative juices start to run dry or tempers start to get short. In either case, that means you need to take a break.  Intense discussions are fine, heated discussions not so much.

Initially, you will have to make all the decisions. That’s fine, but don’t get too comfortable with it. As trust and engagement build, the team will want to become more involved in the decision making process. Invite them in: that demonstration of trust will further build engagement and foster effective communications. Effective communications, in turn, builds trust and engagement.

Having a hovercraft full of eels isn’t the real problem. The real problem is what a hovercraft full of eels tells you about the trust, engagement, and communications in your company.

Sir CEO and the Green Knight

As published in the CEO Refresher

One fine day, Arthur, the CEO rode forth upon his trusty steed. At his side hung his magic sword, Expostfacto. Expostfacto was widely considered to be a sword with a sharp legal mind. Arthur had made his fortune renting camels, which he parked every day in a large camel lot.

The sun was shining. The birds were singing. Suddenly, a dragon came roaring out of the sky, heading straight for Arthur. Flame billowed from the dragon’s mouth. Arthur drew his sword and with one swift blow, buried the dragon in a shower of subpoenas.

So it went, as Arthur spent many days enjoying the freedom of facing foes instead of sitting in stultifying board meetings, where, regretfully, it was seen as déclassé to employ the full might of Expostfacto upon annoying board members or customers. Against the power of Expostfacto, each foe swiftly fell under a massive pile of paperwork.

So it went until the day that Arthur encountered Maldive, the Green Knight.

“None shall pass!” quoth Maldive.

Many blows were exchanged, with Expostfacto screaming its legendary battle cry, “Lorem ipsum dolor sit amet,” a phrase which has become familiar to all internet users. Eventually, though, with a mighty blow, Arthur struck Maldive’s head from his shoulders. That should have ended the fight right then and there, but Maldive was an internet marketing scheme. He simply put his head back on and continued the fight. Eventually, Maldive knocked Expostfacto to one side, and placed the point of his sword at Arthur’s throat.

“I could slay you now,” said he. “But on your honor, I will spare you if you can answer this question: What does every engineer desire? Swear on Expostfacto that you will return in a month. If you have the answer, you will live. If not, you die.”

Ignoring Expostfacto’s muttered comments on possible loopholes and the inadvisability of signing anything, Arthur took the oath to return in a month with the answer or without it.

Arthur rode across the land searching for an answer to the question. He called together all his senior managers and asked them, to no avail. He even posted the question on Twitter and Facebook, leading to some very interesting answers and suggestions, particularly from certain ex-politicians in New York and California. However, since Maldive had asked about engineers, Arthur knew those answers couldn’t be true because an engineer wouldn’t know what to do with one even if he found someone willing to go on a date.

By day 29, things were looking quite bleak for Arthur. As he rode through the frozen lands of Nadir, he encountered a strange looking man. The strange thing was that the man did not appear to be in a rush. As a CEO, Arthur was quite used to people rushing around following his orders. He could always tell when things were getting done by how much people were rushing.

“Who are you?” asked Arthur, puzzled at the sight of someone so calm and relaxed.

“Merlin,” was the reply.

“Merlin the Magician?” asked Arthur.

“No, Merlin the consultant. What seems to be a problem?”

“Nothing, nothing at all,” said Arthur who, like most CEOs, became very cautious at the sight of a consultant.

“Good,” said Merlin, who turned back to whatever he was doing, completely ignoring Arthur. This was a very unusual experience for Arthur, who was not used to being ignored by anyone.

After several minutes, Arthur said, “Well, I guess I’ll be on my way.”

There was no response.

“I’m going now,” said Arthur.

There was no response.

Arthur started to ride away. There was still no response from Merlin, who seemed quite happy to let Arthur leave. Arthur had not ridden very far before he stopped and turned back.

“Do you know what every engineer wants?” asked Arthur.

“Why do you ask?” replied Merlin.

Before long, Arthur was telling Merlin exactly why he wanted to know and what would happen if he didn’t find out. I wasn’t long before a price was agreed upon and Arthur had his answer.

“That’s it?” exclaimed Arthur. Reflecting on it further, he said to himself thoughtfully, “But that’s what everyone wants!”

The next day Arthur showed up at the appointed time for his meeting with Maldive.

“Well?” said Maldive.

“Is it money?” said Arthur.

“No.”

“Is it a fast car?”

“No.”

“Sex?”

“We’re talking about engineers,” responded Maldive. “If that’s the best you can do, then prepare to die.”

“Wait,” said Arthur. “What engineers want is the freedom to make their own decisions.”

There was a long silence.

“I see you encountered Merlin,” growled Maldive. “Very well. But I doubt you will learn from this experience!”

And so Maldive turned and rode away.

Arthur, meanwhile, departed for home in a very thoughtful mood. What, indeed, did it really mean that people want to make their own decisions? Obviously, if he allowed all his employees to make their own decisions, surely chaos would result. No one would know what anyone else was doing! There would be no coordination between departments.

The moment Arthur returned to his office, he discovered the true meaning of chaos. Thousands of emails needing his attention; projects stalled because he hadn’t been around to tell people what to do; irate customers complaining about badly maintained camels (even camel renters have some expectations!); employees angry and frustrated because they couldn’t get anything done in his absence.

“I knew I should never have taken a vacation,” Arthur thought ruefully to himself. “This happens every time! It’s even worse than when I’m in a meeting or on a call.”

As Arthur dove into sorting out the confusion that came about from his taking his guiding hands off the corporate reins, he kept wondering how much worse it could really be if he allowed his employees to make their own decisions. Would it really be worse than what he dealt with every day? Arthur decided to experiment: instead of solving the problems in one department, he gave them limited decision making power. They could approve all expenditures, including customer returns or gifts, up to a fixed amount. After a couple of false starts as everyone got used to the new arrangements, Arthur found that that department was suddenly taking up much less of his time and energy. Moreover, the increased productivity of his employees more than made up for the occasional decisions that Arthur might have made differently. Indeed, simply by building some structure, Arthur found he could permit much more freedom and limit the downside of the occasional mistake, and create almost unlimited upside. At the same time, he also found that he could now focus much more on the strategic direction of his company instead of spending all his time putting out fires.

Best of all, as Arthur spread these changes throughout his company, he found that work didn’t come to a halt whenever he wasn’t available. Productivity increased because employees no longer needed to look busy in order to appear to have a purpose; instead, they could actually engage in purposeful activity. Sure, there were still moments of frustration, but on the whole, employees were happier and more motivated than he had ever seen them. Motion does not equal progress, Arthur realized. Progress equals progress.

In the end, the ability to give people the freedom to work as they would like to work comes from building the structure to enable them to know what to do. Without structure, there may a lot of motion, but very little progress. What will you do to change that?

Stephen Balzac is an expert on leadership and organizational development. A consultant, author, and professional speaker, he is president of 7 Steps Ahead, an organizational development firm focused on helping businesses get unstuck. Steve is the author of “The 36-Hour Course in Organizational Development,” published by McGraw-Hill, and a contributing author to volume one of “Ethics and Game Design: Teaching Values Through Play.” For more information, or to sign up for Steve’s monthly newsletter, visit www.7stepsahead.com. You can also contact Steve at 978-298-5189 or steve@7stepsahead.com.

The Corporate Culture Conundrum

I get asked a lot about corporate culture. In this case, I ended up responding to a very detailed query at such length that I decided to include it here since I doubt the person interviewing me will be able to use all of what I wrote (I’m also posting this after the article comes out, so I don’t upstage anyone).

Let’s start by defining culture. At root, culture is nothing more than the residue of perceived success. In other words, it is the accumulated knowledge of how to be successful at a particular company and how the company is successful in the marketplace.

Why success and not failure? Simple. We tend to repeat the behaviors that appear to bring us success, and discontinue those that do not. Moreover, cultures based on failure simply do not survive. At some point, there have to be successes in order for the culture to remain viable.

I focus on perceived success because what really matters is not whether a behavior is really successful so much as our belief that it is successful. For example, in the 1990s, Nokia firmly believed that its success was due to its innovative management style. The reality was that they had a hot product, cell phones, in an exploding market. When the market saturated, their revenues dropped off along with every other cell phone provider in 2000. Today, Nokia is increasingly irrelevant. If everyone at the company had come to work wearing Groucho Glasses every day, their product would still have sold and they might very well have ascribed their success to their innovative dress code. The results would have been pretty much the same, although people might have been inspired to tell better jokes.

Because culture contains within it the memory of success, it is very hard to change. No one likes to change what’s working! What’s worse is that a behavior rarely succeeds all the time: when something doesn’t work, we ascribe the failure to “not trying hard enough” and resolve to do better. The resulting semi-randomness to the success produces a response similar to playing a slot machine: random success is highly addicting.

This phenomenon becomes particularly important when we realize that the business environment changes more rapidly than the culture. A once successful behavior gradually stops working. However, because it fades out slowly, intermittent successes along the way serve to make the behavior stronger and stronger even as its usefulness is decreasing. When it comes to not changing a behavior, it takes only the occasional success to make up for an awful lot of getting kicked upside the head.

This also means that there are two key aspects to culture: what we do and why we do it. Most organizations focus purely on the “what” and ignore the “why.” Even when an organization attempts to change culture, they almost always focus on what they are doing. Unfortunately, when you only change the what, you are changing the superficial. The underlying why will rapidly pull the new behavior back into alignment with the original behavior; although cosmetic changes may persist, the new “what” will be fundamentally identical to the old.

The “whys” of culture also interlock: there is rarely one reason for a particular behavior. As a result, attempting to change one “why” can also be quite difficult because a) it’s hard to identify it precisely, and b) the rest of the interlocking structure of beliefs pulls it back. It is quite possible for a CEO or senior management team to simply chop off a piece of a corporate culture, but it can be quite unpredictable what else they’ll lose: for example, when IBM dropped its traditional full-employment policy, they also lost a great deal of employee loyalty and their historic “IBM takes care of me and my family, I take care of IBM” employee mindset.

With that said, let me jump over to your questions:

1. How do you know when there's something wrong with your corporate culture (what are 2-3 signs), or how do you know if things need improving just a bit?

Something is “wrong” with a corporate culture when the culture can no longer obtain resources, that is to say clients and revenue, from its environment. The early symptoms can manifest in several ways before the revenue drop really hits. The most common is a persistent feeling of being stuck: more and more effort is expended for less and less success. Previously successful revenue generating behaviors are losing their effectiveness, but doing so in fits and starts.

Another common symptom is increasing defensiveness on the part of management: executives don’t want to hear why something isn’t working, and attempts to address problems are met with denial. At exactly the point where the executive team should be bringing in outside help, they become increasingly unwilling to do so. An outsider is far too likely to grind the sacred cows into hamburger. IBM’s decision to bring in Lou Gerstner in 1992 is an example of a company overcoming that fear of outsiders and actually addressing their problems.

A third symptom of culture problems is a persistent inability to make and keep decisions. When teams within the company, or the company as whole, continually revisits discussions and can’t seem to follow-through on goals, that’s a major warning sign that you need to take action.

2. Where do generational differences among staff and colleagues come into play?

Let’s start with the elephant in the living room: the Gen Y myth. This whole concept that Gen Y’ers are somehow less dedicated, less motivated, or less <insert here> than Gen X or Boomers is, quite simply, a myth. Indeed, the whole idea that the younger generation is less respectful, dedicated, hard-working, and so forth, than their elders is itself a cultural belief that goes back at least to Socrates.

What is different, however, is that Gen Y’s do not share the cultural belief that you graduate from college, work at one job for 40 years, and retire to enjoy your “golden years.” While this was, or at least appeared to be, a valid cultural belief at one time, it is no longer valid in the current environment and shows no signs of regaining validity. However, for those who grew up with it, it is very difficult to put it aside.

Within an organization, what matters first is not the generational differences but the degree of immersion in the culture of the organization. Younger employees are less deeply immersed in the culture; they’ve had less time to absorb it and to assume its values. Thus, they are more likely to propose ideas and approaches that older employees view as violating cultural values and hence are more likely to reject. Note, by the way, that I’m referring less to chronological age than to amount of time with the company. Since the older employees typically have more authority, younger employees are more likely to be frustrated. How they cope with that will, however, be strongly influenced by their generational cultural values: a Boomer or X’er might decide that if they stick around and pay their dues, they’ll get a voice in due time; a Gen Y’er is probably more likely to go somewhere else. One solution is not inherently better than another.

3. How do you cultivate a creative and collaborative team (what 2-3 three things can really build that team culture)?

Culture is whatever is seen as successful. If you want people to collaborate, reward collaboration. Sounds simple, but it just doesn’t happen. Companies focus on individual performance and individual reward. As a result, they get a bunch of individuals often competing for a limited pie. While it is important to acknowledge and reward individual contributions, that cannot be all that you reward and it should never be set up in a way that creates competition between team members.

4. It's all about innovation, how best to encourage creative brainstorming for service/product innovation (what works and what doesn't and why)?

There are four culture traps to avoid and four cultural beliefs to build. The four traps are:

Perfection — We must make the perfect mousetrap… which works until someone comes along with a cat.

Protection — We must not hurt our existing products. Pity our competitors don’t feel that way…

Identity — We’re an X not a Y. IBM was a serious business company in the 1980s. They didn’t “do games.” Now they’re heavily involved in serious gaming.

Creeping Box — We’re so far outside the box no one can catch us. Just ask Yahoo… Once you move outside the box, the box grows and suddenly you’re just one of the pack.

The cultural values to foster

Continuous education — Keep people learning. Don’t limit people to taking classes in their areas of expertise; rather encourage employees to study whatever interests them. Innovation comes from putting together apparently disparate pieces of information.

Making mistakes — How do you respond to mistakes? Innovation is a messy business. If mistakes are punished, no one will risk making them and innovation will falter. Thomas Edison famously said that he’d learned a thousand ways to not make a light bulb. Easy to say, hard to live.

Strategic breaks — Allow the breakthrough to happen. The “eureka” moment doesn’t happen when we’re exhausted from banging our head against the wall. It comes when we take a break and do something different. Learn how to take breaks strategically.

Patience — Don’t wait for a crisis to force your hand. Necessity may be the mother of invention, but waiting for the last minute to start innovating is the number one cause of premature death amongst new ideas.

5. How do intangibles like volunteerism, office greening, impact corporate culture?

Intangibles matter to the extent that they reflect the corporation’s values, beliefs, and aspirations. Volunteerism can be very important in a company that views itself as a good citizen of the community. However, to be effective, intangibles have to be worth the time and energy expended on them. If employees who volunteer their time end up being paid less or promoted less frequently than those who don’t volunteer their time, volunteerism will fade out. The behavior that is rewarded will become part of the culture, and the culture will attract those who believe in the values manifested through the behavior.

6. What are other intangibles that are important but corporations may not be keen about their importance?

How meetings are conducted, whether employees are permitted to work from home, how much freedom and autonomy versus direction employees are given, how mistakes are handled, how disagreements are managed, how permissible it is to question authority, are just a few of the intangibles that shape cultures.

7. How important is culture today and why?

Organizational culture is probably the most important most powerful force in any corporation. Because culture is the lessons of the past, it provides the template for how to behave in the future. Once a corporation loses sight of its culture, it’s only a matter of time before it slams into a brick wall.

8. Is your sense that most firms are focused on their culture, why or why not?

While many firms focus on their culture, they focus on the wrong aspects of it. Most companies focus purely on the “what,” those superficial artifacts that are easy to see but which have the least significance. It’s hard to focus on the “why.” Indeed, really delving into the “why” of your culture is rather like performing open heart surgery on yourself. In other words, you need the assistance of a trained outsider who is not immersed in your culture to see the elements you take for granted.

9. Any interesting, stats, surveys or other data about corporate culture?

Let me point you my book, “The 36-Hour Course in Organizational Development.” Chapter one is about culture and the entire book discusses how organizational development shapes and is shaped by culture.

10. If a company can make only one change in it's culture, how to determine what should be that priority?

The biggest priority is changing the belief that you can change only one thing… Seriously, culture change is not a precise, surgical operation. Sure, if you’re only after changing the “what,” you can pick one thing, but for anything non-trivial you have to go after the “why.” That requires taking the time to really understand what values and assumptions that are taken for granted are no longer valid, and then building up a new set of values and assumptions. Most culture change fails because it tries to focus too narrowly on one thing. Corporations go through a lot of pain and spend a lot of money only to experience a fleeting success before the culture reverts back to the way it was: when you seek to change only one thing, everything connected to that one thing acts to pull it back to its original form.

What Big Picture?

As published in The CEO Refresher

Using the Force: What Every Exec Can Learn from Darth Vader

As published in the Worcester Business Journal

My 6-year-old son is seriously into Star Wars. As we were watching the movies recently, he turned to me and asked, “Why is Darth Vader such a mean leader?”

Coming from a kid who thinks the Sith are kind of cool, the question took me by surprise. On the other hand, it’s rather heartening to see that even a small child can recognize bad management. Of course, the real question is not what makes Darth Vader such a bad leader. After all, when you’re the Dark Lord of the Sith, you don’t really need a reason. More aptly, the question is: What does it take to be a good leader?

No Intimidation

First, we have to dispense with the primary weapon of the Sith: fear. Darth Vader rules through terror, but the fact is, you don’t need to have the power to choke people to death using the Force to create a climate of fear. Fear is very effective at getting people to move away from something. In the practice of Jujitsu, fear of injury is often quite sufficient to convince an attacker to dive headfirst into the ground or into the nearest wall. Some mistakes are a natural part of doing business. When people are shamed for making mistakes or threatened with loss of their jobs if they don’t measure up, they become less creative, less dedicated and errors are not corrected.

Team Spirit

To be a positive leader, the first step you need to take is to focus on affiliation. You might also think of it as team spirit. When people come together to form a team, the first thing they do is look for common ground. To really create affiliation, the leader needs to actively get to know his team members and encourage them to get to know one another.

Independence

Next is building autonomy. Perhaps counter-intuitively, autonomy is the result of having structure. Structure lets each team member know what the others are doing well enough to trust them when they aren’t visible. That trust is what permits autonomy.

Lack of structure is chaos. Too much structure is stifling. For example, when an employee comes up with a good idea and your response is to ignore them, that is too little structure. When you say, “Good idea! Here’s how we can make it better!” that’s too much structure. Appropriate structure is to say, “Great idea! How did you come up with it?”

Great Expectations

Competence is not just hiring competent people. It’s creating an atmosphere of competence. Nothing succeeds like the expectation of success.

Managers can motivate employees in one of two ways: you can focus on failures, and make dire predictions about what will happen if employees screw up; or you can focus on success, and remind the employee of the things they did well.

The keys to great leadership are: get away from fear, build affiliation, create structure to enable autonomy, and craft an atmosphere of competence.

The hard part is finding the right balance for your team and your company. Start slowly and let yourself accelerate as you learn to use these techniques effectively. You’ll soon be amazed at how fast you’re going.

Make a New Plan, Stan

As published in Corp! Magazine

Jesse Livermore, the legendary stock trader of the early twentieth century, was famed for his ability to keep his cool no matter what the market was doing. He neither became discouraged when he lost money or exhilarated when he made money, and he made a lot of money. His greatest triumph was making $100 million (no, that’s not an error) on Oct. 29, 1929, the day of the market crash that preceded the Great Depression. He was one of only two people to make money that day. As people were panicking around him, he calmly covered his short positions into the chaos. What was his secret?

It was simple: Jesse Livermore had a plan. Over the course of his trading career, he developed a plan for when to buy and when to sell. When the plan didn’t work, he stepped back, analyzed the failure, and adjusted his plan. Jesse Livermore’s plan failed many times, especially during his early days as a trader. He went broke more than once and, in 1915, was a million dollars in debt. But Jesse Livermore never failed.

Now this may look like sophistry: he created the plan and the plan led him into bankruptcy. Isn’t that a failure? Sure: it was a failure of the plan. By creating an external construct, a plan, Livermore was able to prevent his emotions from dominating his trading. More broadly, he was able to place the failure outside himself. It’s much easier to change one’s plan than it is to change oneself. On the flip side, when things went well, he could enjoy the fruits of victory without allowing the excitement to color his perceptions and cost him his profits. Each day, he knew that he had followed his plan.

This lesson can be easily applied to the business world, especially today. The news is a steady drumbeat of economic disaster after economic disaster, bankruptcies, shrinking sales, and so forth. It’s extremely difficult to not become discouraged; I regularly hear from business owners that they are no longer listening to the news. It’s simply too depressing. Unfortunately, restricting information only reduces a business’s ability to act when the opportunity presents itself; you won’t even know that the opportunity is there! Tom Watson, the founder of IBM, was reputed to read the papers every day all through the Great Depression. He had a plan, and part of his plan involved staying aware of what was happening around him. He was waiting and watching for his moment of opportunity. That moment came, and the rest, as they say, is history.

So how do you go about making a plan?

• Start by defining a broad vision of what your business wants to accomplish. What will the world look like if you’re successful?
• Identify the steps needed to bring that vision into reality.
• For each step, identify how you will recognize whether or not it is working. It pays to decide upon your metrics before the pressure is on, and to identify the signs of trouble as early as possible. Jesse Livermore never bought a stock without deciding in advance the conditions under which he’d sell it, whether for a profit or a loss. As a result, his losses were small and his profits large.
• Break those steps down into activities that can be done on a daily, weekly, and monthly basis.
• Define appropriate checkpoints where you can evaluate progress and determine whether or not your plan is working. Remember to allow sufficient time to collect enough data to make a good decision. Evaluating before you have enough information is an excellent way to abandon a successful plan before it has time to pay off.
• Execute your plan, day in and day out. You measure your own success or failure by whether or not you stuck to the plan.
• Constantly review and revise your plan as you learn more. Failures of the plan are simply an opportunity to evaluate and adjust.

When we fail, it can be difficult indeed to get up and try again. But when the plan fails, it’s relatively simple to modify it and keep going.

What’s your plan?

Stephen Balzac is an expert on leadership and organizational development. A consultant, author, and professional speaker, he is president of 7 Steps Ahead, an organizational development firm focused on helping businesses get unstuck. Steve is the author of “The 36-Hour Course in Organizational Development,” published by McGraw-Hill, and a contributing author to volume one of “Ethics and Game Design: Teaching Values Through Play.” For more information, visit www.7stepsahead.com or contact steve@7stepsahead.com.