The Business Sensei

The Peter Principle of the Thing

As published in Corp! Magazine

A good many years ago, I was working at a small software company. For various personal reasons, the VP of Engineering abruptly left the company and one of the senior engineers was promptly promoted to take this place. Now, this guy was an excellent engineer and I learned a great deal from him. He was a fun person to work with and someone who was always enthusiastic. He was picked for the job exactly because of those qualities and because of his engineering prowess. However, as a manager of engineering, he never appeared to have the same joy and excitement about his job. Indeed, he often gave the impression that he’d rather be writing code than managing other people who were writing the code. After the company folded, as far as I know, he went back to engineering.

At another company, Jim was a star researcher. He was brilliant. He was the person who came up with idea after idea. He did so well that eventually he was put in charge of the lab. At that point, things went downhill. Working through other people drove Jim up the wall. He wanted to be in the lab, not arguing about the best way to do things. He couldn’t go back, though, without being viewed as a failure. At the same time, he couldn’t get promoted until he “shaped up” and “made his lab more productive.” He was trapped doing a job he didn’t particularly enjoy and wasn’t particularly good at.

Both of these stories are examples of a hypothesis first proposed in the 1960s by psychologist Lawrence J. Peter. Today, the “Peter Principle” is spoken about with a certain amusement and a smug “yeah right” attitude. Unfortunately, “yeah right” is the only construction in the English language in which a double positive makes a negative. In other words, the Peter Principle is popularly seen as a joke. In fact, it’s not. Moreover, it turns out that when you have an environment in which someone can be promoted into a job that is significantly different from what they’ve been doing, the Peter Principle is virtually inevitable. The key point lies in recognizing what constitutes “significantly different.”

Well, as it happens, managing engineers is significantly different from being an excellent engineer. Managing researchers is significantly different from being a top researcher. Managing salesmen is significantly different from being a top salesman. However, being a top engineer, researcher, salesman, or whatever is exactly what brings that person to the attention of senior management. If this isn’t disturbing enough, in the study confirming this phenomenon, authors Pluchino, Rapisarda, and Garofalo also found that the best way to avoid it was to either promote people randomly or promote the best and the worst performers equally.

As Monty Python might say, “This is getting silly!” After all, how can it possibly be true that random promotion would work better than promoting the best performers into management?

Consider how much time, effort, and training is required to become a top engineer, researcher, salesman, doctor, or just about anything else. Nothing in the training these people receive prepares them to manage others. In fact, good management is, in many ways, the antithesis of being a successful solo performer: instead of doing the work yourself, you are now doing it through others. Motivating others is a different experience than motivating yourself. Helping others stay focused and on track is different from keeping yourself focused and on track.

So, without resorting to promoting people randomly, what could be done to prevent the Peter Principle from taking over in your company?

Well, if it were possible for someone to both be a manager and not be a manager at the same time, you would be able to see if they could do the job, and allow them to continue along the track they’re on if they don’t shape up. Unfortunately, literally attempting this is pretty hard on the person and the business; someone who tries to be both a manager and an individual contributor at the same time usually ends up doing one, or usually both, badly.

An alternative, though, is to take a page from sports and provide practice space for people. Just as a sports team might rotate players through different roles before figuring out what each one is best at, companies can use predictive scenario leadership games and exercises not just to train existing leaders, but to find leaders. Quite simply, when people don’t know what to do, they do what they are most comfortable doing. In predictive scenarios, people have the opportunity to demonstrate talents that might not be obvious or which may never come up in their regular jobs. For example, the best managers create order in chaotic or ambiguous situations and know how to build employees’ confidence. When you enable an entire department to participate in a predictive scenario, you can see who is actually doing those things. Rather than promote randomly, you can pick the people who most strongly demonstrate the desired skill set for the position you are looking to fill!

Is this easy? Not necessarily. It takes some serious effort to avoid the Peter Principle. I suspect that many of you reading this are thinking that you simply can’t afford do anything about it. The real question is, can you afford not to?

Stephen Balzac is an expert on leadership and organizational development. A consultant, author, and professional speaker, he is president of 7 Steps Ahead (www.7stepsahead.com), 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.” Contact him at steve@7stepsahead.com.

Death of a Thousand Knives

As published in Corp! Magazine

Very few companies are ever driven out of business by their competitors.

I’ve found that this statement upsets a great many people, all of whom are quick to jump up and start providing examples of companies that were, in fact, driven out of business by their competitors. This is missing the point. Indeed, it’s rather like a detective in a murder mystery concluding that the cause of death was that the victim’s heart stopped. It matters whether the heart stopped due to lead poisoning, for example in the form of a bullet, or due to some other cause. Indeed, understanding exactly what led to that heart stopping moment is a key part of solving the mystery.

Similarly, while it’s not so unusual for a failing company to have the coup de grace administered by a competitor, how they got to that point makes all the difference. Focusing only on the end point provides a very simple, comfortable solution, but not necessarily a particularly useful one.

Robotic Chromosomes, for example, was a company that dominated a particular niche in the bioinformatics market. They were an early entrant into the field and their products were initially the best on the market.

Over the course of several years, though, they developed a view of their clients as idiots. The fact that their clients were all highly educated research scientists did not enter into the equation. If they had trouble using the software, they were idiots. As a result, the company became increasingly less open to feedback from either clients or the market. While their market share was increasing faster than the market itself, they could get away with that attitude. Eventually, though, their growth started lagging the growth in the market. Phrases like “law of large numbers” and “temporary aberration” were batted about. When their market share started shrinking, phrases like, “temporary aberration” became even more popular. The view of the clients as insanely stupid for buying competing products became more common.

Today, they no longer exist. Were they driven out of business by their competitors? Only in the sense that they put themselves in a position to allow their competitors to drive them out of their dominant position in the market. Sure, their competitors may have pushed them over the cliff, but they were the ones who chose to walk to the edge and lean over.

Now, it may reasonably appear from the preceding description that Robotic Chromosomes was taken down by a clearly defined event, that is, viewing clients as idiots. That is not, however, quite correct. While it may appear that way in retrospect, the reality is that Robotic Chromosomes suffered from a series of cascading errors. Each mistake was small, easily overlooked or ignored. Each mistake led to more mistakes until eventually the company was suffering from so many small cuts that it eventually had no strength left to resist when its competitors moved in. So how does a company avoid this death of a thousand knives?

The obvious answer is that they needed better communications. While true, it again misses the point. Communications is where problems show up, but the communications are rarely the problem. Rather, the dysfunctional communications are the symptom of the problem. It’s critical to look beyond the symptoms to identify the real problem. Otherwise, you spend all your time looking at the wrong things, as Robotic Chromosomes so eloquently demonstrated.

Avoiding that fate requires a willingness to accept negative feedback; it means being willing to hear what people are saying about your product, your service or your management style. If you aren’t willing to listen, or if you structure the way in which you listen to negate the feedback, you’re setting yourself up for failure, one step at a time. For example, creating a culture that mocks and demeans your clients is not a recipe for success, and closes you off from valuable feedback from those clients.

Being willing to accept feedback is only a first step though. You have to create a context in which employees are not afraid to give you that feedback, and in which they believe that providing feedback is worthwhile. If people believe they’ll be punished for being critical or regarded as “not a team player,” it’ll be hard to get them to provide feedback.

Next, you need to clearly define your goals and also define how you’ll know whether you’re succeeding or failing. Robotic Chromosomes had very fluid definitions of success, definitions that shifted regularly to avoid facing unpleasant results. It’s important to separate the evaluation of the feedback you’re getting from the testing to see if the criteria for that evaluation are valid. In fact, verifying the validity of your criteria should be done before you then evaluate your feedback: otherwise, it’s too easy to redefine success and give yourself a few more cuts. None of them seem all that bad at the time.

Step by step, over the course of several years, Robotic Chromosomes successfully created an environment where any negative feedback could be ignored because that feedback was always coming from idiots. Their competitors didn’t drive them out of business. They drove themselves out of business; their competitors simply put them out of their misery. How will you avoid the death of a thousand knives?

Stephen Balzac is an expert on leadership and organizational development. A consultant, author, and professional speaker, he is president of 7 Steps Ahead (www.7stepsahead.com), an organizational development firm focused on helping leaders grow their businesses. 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.” Contact him at steve@7stepsahead.com.

The Accidental Leader

As published in Corp! Magazine

Does this sound painfully familiar?

The team leader left the company or was transferred elsewhere. No one knows anything about the new person coming in. Everything is up in the air. It’s almost impossible to get any work done because everyone is too busy wondering what’s going to happen next. Is the team going to be kept together? Will the project be cancelled?

Or how about this situation:

You were just assigned to take over a strong team. The former leader, well-respected by the team, is leaving. When you get there, there is a marked lack of enthusiasm. Everyone smiles and nods, but the suspicion is palpable. No sooner do the first words leave your mouth when you have a sinking feeling that whatever it was you said, it was exactly the wrong thing.

Although it may seem that the difference is which side of story you happen to be on, in reality, the situations aren’t really any different at all. In both cases a once functional team is tossed into a state of chaotic uncertainty. From feeling comfortable and secure, suddenly everyone is wondering if there’s another shoe about to drop.

Oddly enough, when the new leader comes in, the situation often gets worse. Rather than allaying people’s fears, too often those fears are increased. It’s not that the new leader is trying to scare people; it’s just that whatever she says, it just doesn’t seem to come out quite right.

At one company, the new executive director was welcomed with great fanfare. Thus, she was totally unprepared when her modest proposals to improve how the company delivered products ignited a firestorm of protest and resistance. This was a very painful situation, although I was able to help them work things out in the end. Still, though, perhaps we might want to look at a more upbeat scenario.

At another company, the new president decided to try something different. When he took over, he didn’t tell people how things would be; rather, he asked them how things should be. Rather than set deadlines, he asked employees what deadline the previous, successful president would have set for their projects. Rather than set new rules, or even focus on existing rules, he asked people what sort of structure would most help them. Rather than try to Impose His Mark on the organization, he took the time to understand what mark was already there. Rather than fight the natural resistance people have to change, he invited the rest of the company into the change process. The transition ended up going remarkably well. What was even more interesting was that along the way he took a fair bit of heat from his board that he was not “acting like a leader.”

He ended up being one of the best leaders the company ever had. Despite initial beliefs to the contrary, it was no accident. By now, you might even recognize the company.

Most leaders respond to a chaotic situation by trying to impose order. This isn’t necessarily a bad idea, at least in theory. Chaotic situations are unpleasant and without some sort of structure, nothing is going to get done. Despite this, when order is imposed too rapidly, suddenly everyone is fighting for chaos.

The secret to taking over a new team, indeed, to dealing with any team or company in a chaotic situation, is to move slowly. Speed comes from being in the right place at the right time, not from rushing to get things done. When you take the time to find the most serious pain points, the places where people are most scared or most upset, and you resolve those situations, you build the trust you need to succeed.

How do you find those points? Ask the team. Involve them in the process. Don’t impose order; rather, create order.

Are people concerned about deadlines and how changes in product schedules might impact them? Invite them to help set the deadlines. Is product quality an issue? At one training company, the fear was that the changes would compromise the quality of the training being offered, which would, in turn, drive away clients. The solution was to stop fighting about it and instead identify the metrics currently being used to determine quality: both the official ones and the ones that staff members used privately. Once those metrics were brought to everyone’s attention, then the new CEO could help the staff members see how the new training would actually surpass the old training. Sounds simple, but the experience was anything but!

You impose order when you walk into the situation and tell everyone what to do. You create order when you find points of maximum leverage and invite people to suggest the order they want you to provide. The second may be slower, but, paradoxically, it gets you to where you want to go a lot sooner. How will you create order in your organization?

Storming the Black Gate

Near the end of the award winning movie, Lord of the Rings: The Return of the King, Aragon leads his pitifully small army to the Black Gate of Mordor, realm of Sauron the Dark Lord. Sauron’s forces outnumber Aragorn’s by easily a hundred to one. On the surface, there appears to be little chance of success. Indeed, during the planning of the assault, Gimli utters the famous line: “Certainty of death, small chance of success… What are we waiting for?”

As those familiar with the story know, the attack is diversion. Its goal is to draw the attention of Sauron so that Frodo can destroy the Ring of Power. Aragorn, however, cannot let on that the attack is anything but an all-out assault on Sauron’s fortress. To fool Sauron, indeed, even to convince his soldiers to follow him, he must act and speak as though he has complete confidence that his badly outnumbered army can win. Aragon must not just be confident, he must be so confident that people will be inspired to follow him to almost certain death. That act of confidence is what makes it possible for Frodo to succeed and for Sauron to be defeated.

Read the rest in the Journal of Corporate Recruiting Leadership

On KKZZ 1400 AM Tuesday 1pm ET

I’ll be interviewed tomorrow at 1pm ET on KKZZ Radio. I’ll be speaking on organizational culture and innovation: the two-edged sword.

The call-in number for the studio is (805) 639-0008.

The interview streams over the Internet at BrainstorminOnline.com.

Feel free to call in and ask questions, talk up my book, etc 🙂

Smell Test

As published in Corp! Magazine

The door opens onto a room filled with equipment: banks of computers, spectrometers, air and tissue samplers and things that you cannot even recognize. The hum of electronics fills the room and there is a definite odor of fish. As you look around, you can see dozens of fish waiting to be analyzed for oil contamination. The purpose of all this machinery is to determine if seafood is safe to eat after the Gulf oil spill.

Sounds like something out of a science-fiction movie. That’s because it is something out of a movie: reality is not nearly so visually impressive. It turns out that the most sophisticated instrument for determining the safety of seafood is the trained human nose. With remarkably little training, the human nose can do something that all the expensive and elaborate electronic equipment cannot do: figure out whether a fish is contaminated or not.

About 20 years ago, a Japanese business decided to conduct a thorough chemical analysis of fine wine. They used sophisticated equipment and complex computer analysis to determine the chemical composition of the perfect bottle of wine. They then produced a wine that perfectly matched their profile.

In the ensuing blind test, tasters had no trouble recognizing the Japanese wine: it was universally described as “having the taste of dishwater and a bouquet of dirt.”

Once again the human nose proved superior to all the fancy equipment that was brought to bear on the question.

When speaking to a group of managers, I asked them to describe their company’s goals. The response was a rather confusing medley of Gantt Charts, Microsoft Project, comments on the latest decision support software and so forth. What was their approach to management? Once again, the same cacophonous medley ensued.

Fish, wine and management have a couple of things in common.

First and foremost, all those fancy tools and gadgets are tools, nothing more. There is nothing inherently special about them, any more than there is anything inherently special about a hammer. In the hands of a master craftsman, a hammer can be a very useful and versatile tool; in the hands of someone without that skill, a hammer is little more than a device for making sure that every problem looks like a nail.

By the same token, the value of management support software, or whatever other power tools are being used, is only as great as the skill of the manager using it. Tools leverage skill; if there is no skill, there is no leverage. There is also a strong possibility of cutting yourself off at the knees: power tools can be dangerous. In other words, all the management support tools in the world won’t help someone who doesn’t know how to manage. More to the point, just as a trained human nose is the best tool for detecting contaminated fish, the best leaders and managers are those who have actually learned how to lead and manage.

From a very practical perspective, the best leaders are those who can connect with their followers. It’s not about Gantt charts or other fancy tools. It’s about building trust and enabling people to feel that they can count on you.

Wait, isn’t that backwards? Doesn’t the leader need to be able to count on his followers? Sure. And the way you get there is by demonstrating that they can count on you, that they can trust you.

In a sadly familiar tale, at Soak Systems, no trust exists between different departments, between marketing and engineering, between engineering and the CEO. Why is there a lack of trust? The CEO constantly visits clients and makes promises that engineering can’t possibly fulfill. Even worse, he regularly changes direction and priorities: one day project X is vital to the future of the company, even when it fails to ship on time or when it ships and doesn’t work. The next day, it’s project Y. Each prediction of impending doom is followed by another prediction of impending doom if the project doesn’t work.

At this point, no one believes the CEO. No matter how important or unimportant his pronouncements, they are all greeted with the same level of skepticism. All his charts and graphs are failing to convince anyone. Is it possible for the CEO to reverse the trend and actually build credibility? Sure! The easiest way is for his prediction of doom to come true just once. Granted, that’s not particularly useful, but it is the easiest approach.

A more difficult approach is to put aside all the shiny tools and actually pay attention to the people. If he is willing to learn how to build trust and establish connection with his followers, then there’s a good chance he can turn things around. But he has to be willing to learn instead of being distracted by all the pretty toys.

I said earlier that there are two things that wine, fish and management have in common. We’ve discussed one. The other is pretty simple.

They all stink when they’re bad.

When the Fat Tuesday Sings

As published in the CEO Refresher

Recruit Confidently

As published in ERE.Net

Recently, I heard a hiring manager comment that she would “Prefer not to hire anyone at all.”

Her company is growing. They are actively looking for people. At the same time, this manager who has been tasked with building up her team is openly telling candidates that if she has her way, not one of them will be hired. Indeed, given the choice, it’s hard to imagine candidates accepting an offer if they did get one, compared, say, to an offer from an enthusiastic and confident employer.

While making the observation that this woman lacked confidence might be something of an understatement, it is only a start.

Confidence begets confidence, just as lack of confidence begets lack of confidence. This manager was demonstrating a lack of confidence in herself, her company, its hiring process, and in the candidates. That, in turn, makes it extremely difficult to attract top people: if the hiring manager doesn’t seem confident, what does that tell the candidate about the company?

While most businesses viewed the Great Depression as a time to hunker down, cut everyone possible from the payroll, and hide under the bed until things got better, one CEO took a different perspective. He saw the Depression as an opportunity to find the best people, build their loyalty and commitment, and stockpile equipment and material against the day the economy turned. Tom Watson’s confidence that things would get better propelled IBM into becoming the global powerhouse it remains to this day.

In another example, a recent news report featured an economist claiming that hyper-inflation and total social collapse is just around the corner. Is that likely? I’m no economist, but I have to wonder how many people today remember Dow 36,000? James Glassman’s book was published at the height of the Internet boom: in October 1999, just a few short months before the market crashed in March 2000. The predictions of a rosy future stretching into forever were loudest, and most believable, at the top; what does that say about the news today?

In the end, though, while this woman’s lack of confidence may have been made obvious by the economy, and helping her reframe the news was an important step, further investigation revealed the economy wasn’t the actual cause. The actual cause was both more immediate and less obvious: she fundamentally didn’t trust the hiring process her company used. If you don’t trust the process, it’s hard to have confidence in it, and the more vulnerable you are to surrounding influences such as the news. In a strong economy, her lack of trust could easily go unnoticed simply because the positive news flow would allay her fears; without the positive backdrop, however, her fear and her lack of confidence in the system were fully exposed. Sadly, this lack of confidence appears to be the case in a great many different companies.

It’s a topic I write about in the next Journal of Corporate Recruiting Leadership. In that article, I specifically get into some ways to address the problem. While it’s certainly true that we don’t control the economy, we can control how we react to it. We control as well how well our recruiting systems are designed and how well trained we are in using different parts of it. Understanding what we control and how to exercise that control well is the key to true confidence.

Mousetrap Company

As published in Corp! Magazine

Remember the classic kid’s game, Mousetrap? In this historic tribute to the legendary Rube Goldberg, players have to assemble an exceedingly convoluted and baroque mechanism that will supposedly catch a mouse. As I have young kids, I recently had a refresher course in the game. What was interesting was the debate about which part of the trap is the most important: the crank turn at the beginning? The shoe that kicks the bucket, the ball bouncing down the stairs, the diver that flies into the washtub or the trap itself falling down the pole? In the end, most of the kids decided that it must be the trap, since without that you can’t actually catch the mouse.

Listening to the debate, I had the rather disturbing experience of being reminded of a certain software company. A similar debate occurred there as well: the engineers who were supposedly designing and implementing the software were being raked over the coals because they hadn’t successfully produced a workable product by the deadline. At first glance, it was clearly their responsibility to build the product, and their failure was costly indeed to the company.

The first glance is not, however, always the most accurate one.

In the game of Mousetrap, a number of things have to happen correctly in order for that all important trap to fall. If the shoe doesn’t kick the bucket, the ball won’t go bouncing down the stairs. If the crank doesn’t turn, the gears won’t rotate and the shoe won’t move. Indeed, while a failure at any point in this wonderfully elegant mechanism will derail the whole thing, failure at the start means that it won’t even get going.

At this software company, the process for getting a release out the door was, unfortunately, even more elaborate than the mousetrap. The biggest problem, though, was the crank at the top. The company had several products, and competition for resources was fierce. What the CEO seemed to be paying attention to was what received the time and energy of the engineers. Although the CEO kept saying that this particular release was critical to the future of the company, he made no effort to organize the company around that release, nor did he delegate that task to anyone else. Thus, the assumption from the top down was that this release couldn’t really be as important as all that.

By the time engineering got involved, the engineers were focused on multiple tasks. Without any direction from above, they took their best guess on which direction to go. Being engineers, that meant that they pursued the interesting technical problems, not the serious business priorities: when not given direction, most people will do the thing they are best at doing, whether or not that is the thing that really needs to be done at that moment.

When it came time to ship the product, the best that could be said about it was that it didn’t crash too often. The customer was not pleased.

What happened here was that there was no logical flow of control or means of prioritizing tasks. Superficially, an unhappy customer was the fault of the engineers; certainly, they took the blame. However, was that really accurate? The engineering team did their job as best they could with the information they had available. The real failure was in the leadership: when no one is leading, people follow the path of least resistance. That may not get you where you want to go. Although the failure did not manifest until the very end, the seeds of that failure were sown long before the engineers ever started working on that particular product.

Fundamentally, it is the job of the leader to set the direction for the company and keep people moving in the right direction.

It is the job of the leader to build the team so that the employees will follow him in that direction. It is the job of the leader to build up his management team so that he does not become the bottleneck.  It is the job of the leader to make sure that the technical problems and the business problems are in alignment and that the biggest contracts are the ones that get priority. This seems obvious, but for something obvious, it certainly fails to happen in far too many situations.

In this particular situation, the company’s mousetrap didn’t work very well. The trap didn’t fall. The rod didn’t move. The diver didn’t dive. The crank might have turned, but it didn’t turn particularly well. Indeed, the company really only got one part of the mousetrap process to work well.

They did manage to kick the bucket.

Stephen Balzac is a consultant and professional speaker. He is president of 7 Steps Ahead (www.7stepsahead.com), an organizational development firm focused on helping businesses to increase revenue and build their client base. Steve is a contributing author to volume one of “Ethics and Game Design: Teaching Values Through Play,” and the author of “The 36-Hour Course in Organizational Development,” published by McGraw-Hill. Contact him at steve@7stepsahead.com.

When the CEO Meets Frankenstein

As published in Corp! Magazine

Horror movies follow some fairly predictable tropes: the monster slowly awakens; someone sees it happening, but no one really believes him. As the story unfolds, people go to investigate and are captured, killed, driven mad and so forth. There’s always something terrible going on, and there’s always some helpless innocent caught up in it, acting the way helpless innocents generally act.

Of course, when the helpless innocent doesn’t act as expected, well, that can cause the whole story to change. The classic comedy, “Abbott and Costello Meet Frankenstein,” is a traditional period horror film, complete with the legendary Bela Lugosi, in which the helpless innocents are Bud Abbott and Lou Costello, acting like, well, Bud Abbott and Lou Costello. This, of course, causes the plot to go flying off the rails, at least as far as Count Dracula’s dastardly plot to reawaken Frankenstein’s monster is concerned.

The key element of a horror film is that our helpless innocents are put into a situation in which they have no idea what to do. As in most situations, when we don’t know what to do, we do what we know how to do. Indeed, successful horror relies on that phenomenon: the terror comes from seeing how our ordinary actions lead deeper and deeper into trouble. Alternately, if those ordinary actions are slightly askew, the horror becomes comedy. In that case, the humor comes from seeing Abbott and Costello responding to a deepening horror by doing what they normally do.

The movie works because the tendency to do what we know how to do is both powerful and universal. Most people, confronted by novel situations, react that way. When there is truly nothing they can do, they attempt to exert control anyway by doing something that they can do. The results are often comedy or horror, depending on perspective and circumstance.

At one nonprofit, the founder of the organization was a man who had started out working in a stockroom. When the organization hit a financial crisis, he fixated on doing inventory. There was simply nothing useful he could do. Rather than feel helpless, he did the thing he could do. This made his board very happy as it kept him busy while they raised money for the organization.

At a high-tech company, a product deadline was threatened by a vendor not delivering a critical software component on schedule. There was nothing that could be done: the entire product was designed around that deliverable. The department head responded to the situation by demanding his employees work long hours, before the vendor delivered. After it was delivered might have made some sense, as the company would need to make up the lost time, but before? The department head had no control over the vendor, so he dealt with the situation by controlling the people around him.

Comedy and horror might be quite enjoyable when viewed from a safe distance, like a movie screen, but are much less fun to be in the middle of. How, though, does a leader avoid having her actions turn the situation into a comedy of errors or frustrating, painful experience for her employees?

The key is to practice dealing with chaos. Consider successful athletes: they learn all the moves and drills of their particular sport. Then they practice by competing against other athletes in order to become comfortable with the unexpected actions of their opponents. Indeed, Judo competition is referred to as “randori,” or “seizing chaos.” Because it’s not possible to predict what strategies people will employ or control what an opponent does, the successful athlete learns to adapt to the situation. Rather than becoming stuck on one response, they become adept at switching strategies to counter their opponents.

Successful leaders need to develop the same skill. It’s not enough to just know the theory of leadership; you also must practice in a chaotic or ambiguous scenario. Sadly, for many leaders, that means practicing on the job. As most athletes learn the hard way if they move straight from drilling to competition, getting used to chaos takes its own practice.

Fortunately, just as athletes have multiple training tools at their disposal to learn to deal with chaos before they enter competition; tools are available for business leaders as well. Predictive scenarios, a type of live action serious game, provide the sort of detailed, ambiguous situations that enable a leader to become comfortable with chaos. Unlike traditional leadership training exercises, there is no one, right answer. Participants need to motivate others, win deals, provide feedback, and execute strategies in a constantly shifting environment. Rather than just talking about leadership, participants need to display leadership and do it well enough to convince others to follow them.

Like the athlete, the leader becomes adept at switching strategies and at managing unpredictable situations. Rather than being trapped by doing what they can, they become able to apply what they know. Instead of comedy or horror, they achieve success. Now, that is something you do want to be in the middle of!

Stephen Balzac is an expert on leadership and organizational development. A consultant, author, and professional speaker, he is president of 7 Steps Ahead (www.7stepsahead.com), an organizational development firm focused on helping businesses to increase revenue and build their client base. 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.” Contact him at steve@7stepsahead.com.