The Business Sensei

Sometimes a Little Inefficiency Can Go a Long Way

This article was originally published in Corp! Magazine.

An efficient system is frequently described as one in which there are no mistakes.

People, however, only learn by making mistakes.

This creates a bit of a problem. In a truly efficient system, there would be no opportunity for people to learn. When there is no learning, the system will eventually fail: either it becomes rigid or it stagnates, but in either case it fails to adapt to changing conditions in the environment.

Shoto Funakoshi, the founder of Shotokan Katate, used to say that in the practice of Shotokan there was no room for error. American students never had the patience for the level of perfection demanded in more traditional Japanese dojos; instead, they made a great many mistakes. Today, Americans win most of the competitions.

Fencing is a very precise sport: a master swordsman can hit a moving quarter with the point of an epee. Yet, the winner of the competition is frequently not the person with the most perfect moves. Instead, the winner is often the person who appears to be making mistakes.

Now, there are certainly situations in which there is no room for mistakes: surgery and landing an airplane are two that come to mind. However, for someone to become a master surgeon or a successful pilot they had to make a lot of mistakes along the way. The goal, of course, is make sure those mistakes occur in settings that do not involve people getting killed. And, although both of them are required to perform potentially difficult operations without error, they are also expected to rapidly recognize and adjust to changing circumstances, for example having both engines of your airplane taken out of action by birds. That ability to adjust can only come from experience in dealing with unexpected or unusual situations: in other words, coping with mistakes without losing your mental balance.

I’ve worked with jujitsu students who completely crumbled when they made a mistake. Their concentration and confidence were shattered and their performance along with them. One minute they’re comfortably demonstrating techniques; the next, they’re frozen or in a panic because something didn’t go as expected. In the business world, I’ve seen CEOs comfortably running their companies, apparently supremely confident, right up until something unexpected happens: revenue misses expectations, there’s an unforeseen problem with the product, a deadline has to be extended, etc. The response is pure panic: in one case, the CEO refused to acknowledge the unexpected problem and insisted on shipping it on schedule anyway… and then couldn’t understand why the customers were so irate. In another situation, the first time revenue came in light, the CEO immediately laid off 20 percent of the company. This was not a particularly well-considered response to the situation. In both of these scenarios, the CEO didn’t stop to think; instead, he took the fact that Something Was Wrong, imagined the most dire of consequences, and took the first action that came to mind.

The problem is that mistakes are not something to fear. They are events that can provide valuable feedback. When something doesn’t work the way you expect, that is often a sign that conditions are not what you expect either. Something has changed or is not what you imagined it was, and it’s critical to understand what that means. Only when you understand exactly what is causing the “mistake” to occur can you design an appropriate solution.

In one company, a researcher was fired because he was clearly making too many mistakes and not committed to his job. How did they know? His experiment wasn’t working. It didn’t work for the next three people either, all of whom quit or were asked to leave. Eventually, it turned out that the experiment couldn’t be performed as designed. The first mistake was made by the person who designed the experiment; the second by management who refused to consider alternative explanations. As a result, they repeatedly executed an inappropriate solution.

When too much focus is placed on being efficient, more and more energy is spent on avoiding mistakes. Eventually, more energy may be spent on avoiding the mistake than on the mistake itself as the company works to solve the wrong problem.

It helps, therefore, to have plan for making use of mistakes and not being frozen by them.

• Start by doing nothing. Take a moment to consider the situation. Look at your own reactions: are you imagining disaster down the road? If you are, try “seeing” that image as a photograph and then imagine crumpling it up and throwing it away. Free yourself to consider alternatives.

• Ask what the mistake is telling you. Consider different ideas. Brainstorm a list of possibilities.

• Look for an opportunity to innovate. Don’t settle for the status quo. Instead of just eliminating the mistake, can you turn it to your advantage? How can you make the system a little, or a lot, better than it was before?

Sometimes, a little inefficiency can go a long way.

BlackBerry Jam

They sit there in the room, their eyes fixed on the head of the table. There stands a man, quite probably the team’s manager. He is speaking, presenting some gem of long-since-forgotten lore. Those watching him seem rapt, focused, intent upon his brilliance. But look again. Notice the strain around their eyes, the sweat upon their brows. See the twitching of the hands, as though each man and woman in that room could keep their hands upon the table only with great effort. Watch longer; see the hands slipping off the table, sliding towards pockets and purses. See realization cross the faces, observe the hands forced jerkily back towards the table, as if their owners were fighting against some horrid, hypnotic compulsion. Over and over again, the hand is pushed back.

But attention is finite, will power limited. Eventually, a hand reaches a pocket. It slips out seconds later, an object tightly clutched in its grip. A flicker of bliss passes across a man’s face as he glances furtively down at the object in his hand: a BlackBerry.

So it was in 2005, in the days when the Blackberries ruled the world. Coming out of the distant north, from a place, or so it is said, far out on the rim, Blackberries quickly came to dominate the corporate world. Everyone had to have one. At the very thought that the Blackbery network might go down, panic would spread across the land. A few months later, in 2006, Webster’s Dictionary proudly proclaimed the new word of the year : “Crackberry.” BlackBerry seemed unstoppable, its spread inexorable. And then, as rapidly as it had grown, BlackBerry shrank, faded, vaninshed away. Of that invincible empire, but a single outpost remains, fighting to not vanish away and be forgotten. What force, what power broke the might of BlackBerry?

Success.

That is correct: what destroyed BlackBerry was its own success. Confident in their power, they forgot that when you build the perfect mousetrap someone will come along with a cat. Unlike a mousetrap, the cat does not need to be reset, it doesn’t need the mouse to come to it, it is fun to play with, and it keeps your feet warm at night. Also, the purr is soothing. While BlackBerry’s co-CEOs were busily dismissing the iPhone as, “a toy,” Apple and Google were busily striking deep into the heart of their empire. iPhones and Android phones are not just business devices. They are entertainment devices and are fun to use. BlackBerry, or to be more accurate, Research In Motion, stood still while those around them kept moving.

One of the challenges in innovation is that what a company becomes good at, it naturally wants to keep doing. Innovation becomes an exercise in perfecting the existing product and building up impenetrable barriers to competitors. The catch, however, is that the wall that keeps others out also keeps you in. Research In Motion kept making better and better “business” phones. They let their product define them until they could no longer change as the world around them moved on. In 2007, the first iPhone arose to challenge the BlackBerry. Much to RIM’s surprise, this upstart “toy” proved surprisingly popular. RIM’s attempt to respond with a touchscreen phone of its own was a dismal failure, and their attempts at an Appstore and at adding an MP3 player to their phones were equally unsuccessful. From owning some 70% of the market in 2006, the BlackBerry is now less than 2%. That was the price of their success.

Real innovation is a messy business. It requires trying a great many different things and being wrong most of the time. Indeed, successful innovators fail far more often than they succeed. When a company does succeed, though, it naturally wants to protect and extend that success: they start thinking about how much more successful they would be if only all those messy, and costly, mistakes could be eliminated. They start looking for reasons why their product is invincible, instead of experimenting with things that might kill it. Your cash cow is sacred only to you; to everyone else, it’s just hamburger waiting to happen. Guided by their successes, Research In Motion focused ever more tightly in making better and better Blackberries. That single-minded obsession caused them to develop corporate tunnel vision: all they could see in the future was their own inevitable triumph. In that, they joined with other great companies such as Polaroid and Kodak, who missed the digital photography boat, IBM which was dethroned by the PCs it invented, Digital Equipment, whose CEO declared the PC, “a toy,” Barnes & Noble, which was successfully Amazoned, and a host of others.

So how does a company remain innovative?

Recognize that the more tightly you focus, the less you see. Sometimes it pays to take your eyes off the ball and look at the big picture. What else is going on? Pay particular attention to those competitors you see as jokes. What are they offering your current customers and, even more to the point, what are they offering your potential customers? Apple and Google didn’t take on BlackBerry in its corporate strongholds; rather, they vacuumed up all the rest of the oxygen and the corporate strongholds followed.

Remember that mistakes are part of the game. You can learn from them or hide from them: it’s your choice whether you are receiving feedback or experiencing failure.

Put your focus on process and strategy, not just on results. When you think strategically, you can start to anticipate the moves others might make. Unlike chess, the rules don’t have to stay the same. If you’re making the rules, someone else will break them. Why wait for them to do it and seize the initiative? And if someone else is defining the rules, you have nothing to lose by breaking as many of them as you can. Who says a business phone can’t play music, videos, and games? Research In Motion, that’s who.

Those meetings are still going on. Hands are still slipping into pockets. Men and women are still furtively glancing down at the objects in their hands. Today, those objects are Droids and iPhones. Tomorrow?

Steve’s new book, Organizational Psychology for Managers, is now available. The initial run sold out in two days at Amazon.com; order your copy now.

International Apple Day +2

Here we are, two days after that moment when Cupertino becomes the center of the universe: International Apple Day. The day when Apple announces its new devices. The day when everyone yawned.

Last year, when Apple announced the iPhone 5, I commented that:

Don’t get me wrong: the iPhone 5 is a beautiful piece of technology. I’ll probably upgrade to one eventually (unless I decide to stick it out and see what the iPhone 6 looks like ). But it’s a lot closer to the iPhone 4s than the iPhone 3g was to the original iPhone. Apple may be growing the box, but it sure isn’t outside it, and they have lots of company in there.

So here’s the thing: Apple’s competitors are looking to find a way out of the box that Steve Jobs created. Is Apple?

Well, as it happened, I didn’t upgrade. I probably will get a 5S though. It’s not the best phone out there, but it’s good enough to make it not worth the effort to switch to another platform. I suppose I might feel differently if I were still doing engineering instead of management consulting. Hacking the phone just isn’t that interesting to me any more.

More to the point, though, is that Apple seems to be stuck in its box, or perhaps Apple Crate would be a better term. Either way, the world is moving past them. Yes, the iPhone 5S is a beautiful piece of technology. Apple put something together that very neatly builds on the previous generations of phones, with nothing out of place. It’s beautiful, it’s powerful, you know exactly what you’ll get. It’s safe.

Two years ago, when the iPhone 4S was announced instead of the i5, I commented that:

Even a bigger question than the i5 was whether or not Tim Cook could fill Steve Jobs’ turtleneck. I, for one, still don’t know.

As a good friend of  mine observed, Apple is turning inward, much as it did the last time Steve Jobs left the company. This time, though, the only way he’s coming back is if they have the services of a really good medium or they manage to build an iSteve gadget, sort of the equivalent of IBM’s Watson but with the personality of Steve Jobs.

Somehow, I suspect that neither of those options are terribly likely to occur. That means it’s up to Tim Cook. He’s got the turtleneck now. When Steve Jobs returned to Apple in the late 1990s, things looked pretty bleak for the company. Jobs took some real risks, and enjoyed some phenomenal successes as a result. So, Mr. Cook, perhaps it’s time to stop playing it safe. Toss the turtleneck, literally and metaphorically, and take a chance. Maybe next time you’ll surprise us.

Problem Solving and Mistakes

This is an excerpt from my upcoming book, Organizational Psychology for Managers

We Can’t Afford That!

“Where are the computers?”

“We can’t afford computers.”

“How can we write software without computers?”

“You’ll figure out a way.”

It’s hard to imagine a conversation like this happening in any company. The truth is, it’s hard to imagine because it basically doesn’t happen. No manager is crazy enough to tell his team to write software without computers. So let’s posit a slightly different scenario:

“Hey, the computers aren’t working.”

“I can’t get the lights to turn on.”

“It’s getting hot in here. What’s going on?”

“Oh, we decided to save money by not paying the electric bill.”

Sorry, that’s still pretty ludicrous. Let’s try another scenario.

I was recently at MIT giving a talk on organizational development. In response to a question about maximizing team performance, I explained that the secret is to have a manager whose job is to be a coach: just like on a top sports team, the manager’s job is to encourage the players, brainstorm with them, push them to achieve more than they thought possible, and make sure they don’t forget to stop and take breaks. It is, after all, the manager’s enthusiasm and sincerity that sets the example for the team, and transforms a team of experts into an expert team.

The immediate response from one member of the audience was, “We can’t afford to have someone just sitting around and watching.”

Now, if they’d left it at that, I would have let it go. Unfortunately, or perhaps fortunately, since it led to this article, they didn’t. They went on to say that the manager needs to do the work of the employees: sales managers should be selling, engineering managers should be doing engineering, and so forth. Resisting the urge to point out that they clearly hadn’t heard a word I’d said to that point, I observed that a manager sits around and watches in the same way that a coach sits and watches. This needs further explanation.

As any Olympic coach can tell you, building a team and keeping it operating at peak performance is a full-time occupation. No one ever says, “These are professional athletes! They shouldn’t need a coach!” If the team wants to compete at a serious level, it needs a coach. If all you care about is playing in the D leagues, well, then perhaps you can get away without the coach. Of course, if that’s what you think of your business, why are you bothering?

When the manager is doing the work of a team member, you have a conflict. Salesmen try to outsell one another; sales success is their currency of respect. Engineers will argue over the best approach to solving a problem; being right is their currency of respect. When the manager is also doing the sales or the engineering or what have you, that shuts down the team. How can the members of the team compete with the manager? While it is a comforting thought to argue that professionals will compete with one another in a respectful manner, and a manager will respect the employee who out-competes him, it just doesn’t work. Comfort thoughts, like comfort foods, may feel good but can easily lead to fattening of the brain.

Athletes trust their coaches in large part because the coach’s job is to make the team successful: the coach is measured by how well he builds the individual athletes and the team. If the coach were being measured on how well he did as an individual competitor, few indeed are the athletes who would trust his advice.

Thus, when a company hires a “manager” who is nothing more than a glorified individual contributor who also signs time sheets, the results are often disappointing. At Soak Systems, it led to constant conflict and eventually to the loss of half the engineering team. If nothing else, the team will never achieve the level of performance that it could reach with a skilled manager.

Further guaranteeing that this problem will occur, most companies hire managers based on their technical, sales, marketing, and so on, skills. They do not hire, or promote, based on their coaching skills. They don’t provide them the training or coaching they need to succeed. Putting someone with no management training into a management role will, at best, produce someone who sits around and watches. More likely, it’ll produce someone who is actively harmful to the team. No wonder companies want “managers” who are also individual contributors: at least they are getting some work out of them and keeping them from causing trouble! Such “managers” really do look like an unnecessary expense. Since most people have never experienced really competent management, they also don’t realize just how much opportunity they are missing.

It’s quite true that you can’t afford to have an untrained manager sitting around and watching. There is also no point in buying computers if you won’t use them or paying for electricity if you don’t have anyone in the office. But if you want to write software you can’t afford to not buy computers. If you have people coming into the office, you can’t afford to not pay for the electricity. If you want to achieve top performance, you can’t afford to not train someone to sit around and watch.

“Author Stephen Balzac has written a terrific book that gets into the realpolitik of organizational psychology – the underlying patterns of behavior that create the all important company culture. He doesn’t stop at the surface level, explaining things we already know like ‘culture beats strategy’ – he gets into the deeper drivers and ties everything back to specific, actionable stories. For example he describes different approaches to apparent “insubordination” by a manager; rather then judging them, he shows how each management response is interpreted, and how it then drives response. Balzac preaches real engagement with one’s own company and a mindful state of operation, especially by executives – who must remember that culture “just happens” unless and until they learn to recognize that their behaviors play a huge part in creating and cementing it. It covers the full spectrum of corporate life, from challenging bad decisions to hiring, training, motivating teams – and the secrets of keeping people engaged and learning – and/or avoiding actions which do the opposite. I highly recommend this book for anyone who wants to participate in creating and steering company culture.”

Attivio – Active Intelligence

Make It Easy

In jujitsu, there are two ways to throw someone: you can make it hard for them to stand up or you can make it easy for them to fall down.

When you make it hard for someone to stand, something very interesting happens. The harder you make it, the more they fight back. Unless your opponent happens to be asleep or under the influence of mysterious hypnotic powers, the very act of attempting to force them off their feet triggers and instinctive and intense resistance. This happens even when training with a cooperative partner who is perfectly willing to be thrown! It is the moral equivalent of standing on someone’s foot while trying to pick them up.

Conversely, when you make it easy for someone to fall down, they naturally follow the path of least resistance. It’s not that they make a conscious effort to fall, rather it’s that if you gently let them have your way, they suddenly discover that they are enjoying an up close and personal relationship with the ground. For the practitioner, this is a much more pleasant and much less effortful experience than trying to make it hard for the other person to stand up. Oddly enough, the fall is also more devastating.

Jujitsu, in short, is about minimum effort, maximum results. In a very real sense, the best practitioners are also the most lazy. They get what they want and they work exactly as hard as they need to get it, no harder.

Now, I’ve rarely seen a manager literally stand on an employee’s foot and try to throw her, but I do frequently see the equivalent behavior over and over.

In one particularly egregious case, a manager at one large and rather well-known technology company told an employee that he wouldn’t get a raise because he made the work look too easy. In a judo match, your throw is not annulled because you made it look effortless. In fact, those judo players who can make throws appear effortless are the best regarded in the sport. Does it really make sense to dismiss the value of an employee’s results in such a cavalier fashion? Is the manager encouraging future productivity or simply future activity?

At Soak Systems, engineers actually wanted to spend time fixing bugs in the software. Management, however, developed an arcane and excessively complex method of prioritizing bugs and scheduling people’s time. By the time the process was complete, the engineers had no say in which bugs were fixed or when they should be worked on. Functionally, that meant that when engineers uncovered serious bugs in the software, they weren’t allowed to fix those bugs: instead, they had to sneak in over the weekend to do the work. After a while, many of the engineers became increasingly discouraged or burned out, and eventually started shrugging and letting management have its way. At least, that way they stayed out of trouble. Management successfully made it so hard to fix the bugs that the bugs didn’t get fixed.

Does it really make sense for the managers to, metaphorically, be standing on employees’ feet so dramatically? After all, management did want to ship a working product! The more management tried to control engineering and force them to fix the bugs in a specific way, the less work actually got done.

In a very real sense, the goal is not to impose your will on people but to make it easy for them to do their jobs, to get them to focus their time and energies to produce the maximum possible return. When you figure out what your actual goals are and then create a path of least resistance to accomplishing them, people will naturally and instinctively move along that path. So how do you do that?

Your first obstacle is the hardest one to overcome. As every martial artist learns, the toughest opponent is the one they see in the mirror. If you find yourself getting angry or falling into a “I’ll show them!” mindset, it’s time to step back and take a break. Give yourself some perspective. Getting an opponent angry is an old martial arts trick and one that never stops working, especially on beginners. Don’t make beginner mistakes.

The next step is to find out if you’re standing on their foot. Ask questions. Understand what problems or obstacles your employees may see. Involve them in brainstorming and discussion. Help them help you to build a picture of the desired outcome and invite their suggestions on how to get there. The more you get them involved, the more you educate yourself. Pay attention to how your actions or the company’s rules are being perceived. Are they pinning people in place or are they making it easy for employees to accomplish the goals of the company?

You may not always like what you hear. Jujitsu students are frequently quite frustrated when their training partner says, “Hey, you’re standing on my foot!” When someone tells you something you don’t want to hear, they’re demonstrating their respect for and trust in you. Appreciate that and build upon it. If you respond harshly or with anger, you only cut yourself off from information; you don’t change anything.

Pay attention to what behaviors you are encouraging and which ones you are discouraging. When you stand on someone’s foot, you are encouraging pointless activity and exhausting, wasteful conflict: what do you suppose that employee at that high tech firm I mentioned earlier did on future projects? When you make it easy for people to do their jobs, you are encouraging constructive argument, innovation, and productivity.

So go ahead and make it easy. What’s stopping you?

The Paradox of Perfection

This article was originally published in American Business Magazine.

“I’ve missed more than 9,000 shots in my career; I’ve lost almost 300 games; 26 times I’ve been trusted to take the game-winning shot— and missed. I’ve failed over and over and over again in my life. And that is why I succeed.”– Michael Jordan

Ask practically any hiring manager if they’d hire someone who never considers alternatives, who refuses to take decisive action, who has never challenged themselves, and the answer will be, “No.”

The odd thing is, however, that those same managers are hiring exactly those people they said they’d never hire. Of course, they say they’re hiring people with strong track records, who don’t have a history of failure, who have never been responsible for something going wrong; the people, in short, with the perfect job histories.

But what they don’t do is take the time to understand just why that person looks so perfect. After all, isn’t it always better to hire someone who has never failed than to hire someone whose background includes unsuccessful projects?

Imagine if Michael Jordan’s coach had said, back when he first missed a game winning shot, “Hey Mikey, you missed that shot! You’re done.”

Far too often, the people who look so perfect are only perfect because they’ve never allowed themselves to attempt anything that would damage their image of perfection. They carefully choose their projects to make sure they’ll be successful, and they never challenge themselves or expose themselves to risk. Unfortunately, when something does go wrong, they also have no ability to cope.

Twelve years ago, I worked with someone who was telling me how he failed his black belt test in the martial art he studied. “It was the first test I’d ever failed,” he told me. “It was devastating.”

“How long ago did that happen?” I asked him.

“Two years.”

“So I assume you passed the second time.”

“What second time?” he asked.

After two years, his failure was still so overwhelming that he hadn’t gotten back on that metaphorical horse. As an engineer, he was not easy to work with because he had to be right all the time.

I was once called in to work with a manager who had a stellar track record, until something went wrong. He couldn’t cope. He kept telling me, “I’m not the sort of manager who allows something like that to happen.”

The resulting disconnect between his (mis)perception of himself and reality was overwhelming. The fellow was so stressed out that he couldn’t sleep, couldn’t eat and couldn’t think straight. The fact that he had never failed meant that he had no resilience. The mere possibility of failure was enough to send him into panic and make the odds of failure more likely. Yes, we did turn things around, and he’s a much more capable manager now than he ever was before.

When you want someone to embark on a risky project or take bold, decisive action, don’t look to the person with the perfect record who has never failed. If they haven’t taken risks or been bold before, why would they change just for you? Clearly what they’ve been doing worked for them—it got them praise, promotions and financial rewards.

Paradoxically, perhaps that person with the checkered past is exactly who you’re looking for. The person who misses that game-winning shot one day, improves their skills, and nails it the next time is the real winner. Success is about trying over and over and accepting the bobbles along the way. Unfortunately, the tendency on the part of many people is to view a mistake as total failure. This deprives them, and their managers, of the chance to improve and seek greater challenges.

Who would you rather trust when the stakes are high? The person with the perfect record, or the one who is the equivalent of Michael Jordan?

Lost in Map Land

The map, as many people know, is not the territory. However, as discussed in a recent NY Times editorial, some iPhone 5 users are finding that the map app doesn’t even do a job representing the territory. I haven’t had that particular problem yet; I’ve been too busy with a different irritating feature of iOS6: podcast management.

In iOS5, I could download my podcasts through the Music app and assemble them into playlists on my iPhone. In iOS6, Apple removed that functionality from the Music app — oh, you can still make song playlists, just not podcasts — and moved podcast management to Apple’s podcast app. Not only is this app slow and buggy, it doesn’t allow users to assemble playlists.

This leads me to wonder if Apple is succumbing to the Creeping Box trap. The Creeping Box trap is something I wrote about in my book, The 36-Hour on Organizational Development, and spoke about in several talks I’ve given on organizational culture and innovation. Fundamentally, it’s what happens when the box you’ve been thinking outside of finally catches up with you. In Apple’s case, the original iPhone created a whole new standard for smart phones. The iPad created a whole new space for tablet computing. Apple blazed the trail, and plenty of other companies followed them or are on the way. They are all in a new box that Steve Jobs built.

Here’s the thing: Apple’s competitors have much less to lose than Apple. They are trying to knock Apple off its perch. Assuming the have the sense to not bet the farm, the worst that can happen to them is that the status quo remains unchanged: “The <new, revised, improved> <Google, Amazon, Samsung, Nosuchco> <Nexus, Kindle Fire, Galaxy, Clay Slab> is really nice but doesn’t live up to the <iPhone, iPad>. Still consumers will like… and so they’ll sell enough of their tablets to make it worthwhile to try again. And, if they beat the iPhone or iPad, the rewards are immense. Indeed, I know many people would argue, with a great deal of justification, that there are plenty of phones out there as good or better than the iPhone 5.

Don’t get me wrong: the iPhone 5 is a beautiful piece of technology. I’ll probably upgrade to one eventually (unless I decide to stick it out and see what the iPhone 6 looks like 🙂 ). But it’s a lot closer to the iPhone 4s than the iPhone 3g was to the original iPhone. Apple may be growing the box, but it sure isn’t outside it, and they have lots of company in there.

So here’s the thing: Apple’s competitors are looking to find a way out of the box that Steve Jobs created. Is Apple?

Flawed Execution — Don’t Lose Your Head Over It

I’m pleased to announce that my next book, “Organizational Psychology for Managers,” will be published by Springer in 2013.

This article was originally published in Corp! Magazine.

There’s an old joke about a lawyer, a priest, and an engineer being sent to the guillotine during the French Revolution.

The lawyer goes first. He kneels, and the blade comes swishing down. Suddenly, it stops just before it hits his neck. The crowd gasps. After a hurried discussion, the executioner announces that since the lawyer survived, it wouldn’t be legal to try again. He’s released.

The priest goes next. Once again, the blade stops just before it severs his head. The executioner declares that clearly it was the divine hand of providence at work, and so the priest is released.

Now it’s the engineer’s turn. Just as he’s about to kneel down, he looked up at the blade and says, “Hey, I see the problem.”

Leaving the engineer aside for the moment, what we have here is a classic case of flawed execution. It’s a fairly common, though less dramatic, event in many businesses. Unlike this particular example of flawed execution, however, when it happens in a business heads often end up rolling.

This, of course, is exactly the problem.

Now, it may seem like flawed execution is a bad thing. In fact, though, what is more important than the execution itself is how the company responds to its success or failure. This is particularly true in organizations that claim to promote innovation or organizational learning.

When a leader takes the view that mistakes mean that heads will role, that sends a very clear message to the rest of the organization: mistakes are something terrible. They are to be avoided at all costs. In other words, always play it safe because if you make a mistake, you’re in trouble. It also means never experiment because your experiment might not work out. In fact, most experiments don’t work; we conduct them to find out what will work.

To put this in perspective, at one software company the engineers on one project had to make some decisions about how users would interact with the program. They had several possible designs, but could not choose between them. Eventually, they made the logical decision to pick one and conduct some user tests. The first few rounds of tests did not go well, but eventually they hit on a design that the users liked. The response from the department head was, “That’s great, but why didn’t you get it right the first time? Your errors cost us a lot of time and money.”

On the next product cycle, the engineers simply picked one alternative and when it didn’t work blamed marketing for not providing them sufficient information. Naturally, marketing responded by blaming engineering, and so it went. Once heads start to roll, the most important thing is to make sure that someone else’s head is the one that goes. This rapidly undermines trust and teamwork.

Conversely, in highly innovative organizations, mistakes are accepted as a necessary part of the game. Indeed, these organizations try to avoid simply jumping to an answer. They recognize, as the engineer in our little joke did not, that jumping to a solution can have fatal consequences. Palm Computing, for example, conducted numerous user tests before releasing the first Palm Pilot. Many of those tests simply involved people walking around with pieces of wood in order to find the right form factor for the Palm devices.

The trick with both innovation and organizational learning is recognizing that you often don’t exactly know what you’re going to build or learn. Learning in particular is a product of making mistakes; when you don’t allow mistakes, you also don’t allow learning. As for innovation, well, it’s very hard to pick the right answer when you’re exploring unknown territory. Rather, getting to a right answer is a process of exploration and experimentation. That process of collaborating with your team, sharing successes and failures along the way, is what truly builds a strong and resilient team, as well as high quality products and services.

In the end, it’s the flawed execution that really gets you what you want, while jumping to the apparently correct answer too quickly can be fatal. No joke.

Stephen Balzac is an expert on leadership and organizational development. He is president of 7 Steps Ahead, an organizational development firm focused on helping businesses get unstuck, and the author of “The 36-Hour Course in Organizational Development.” Contact him at steve@7stepsahead.com.

That’s An Amazing Serve!

One of those little tricks known to certain expert tennis players is saying to an opponent, “That’s an amazing serve! However do you do it?”

They’ll typically do this as they switch sides of the net, and suddenly the opponent’s amazing serve fizzles. By making the other player think about what he’s doing and focus on his body, instead of on the ball, that one question can completely change the course of a game.

Many practitioners of jujitsu and aikido learn the unbendable arm: they are told to extend their arm and imagine water jetting out at high pressure. Their arm becomes incredibly hard to bend. If they try to focus on the muscles, the arm is relatively easy to bend.

A similar trick is used by proponents of medical magnets and various other magic therapies: they’ll ask you hold your thumb and forefinger together on your right hand, and really focus on keeping those fingers together. They’ll then grab your fingers and pull them apart. Next, they have you hold the magnet or the magic herb packet in your other hand, and imagine the strength it’s giving you. Suddenly, your fingers can’t be pulled apart.

It’s a cool trick. I do it regularly by claiming my MIT class ring is magnetic and having the other person hold it in their off hand. Even though people know there’s obviously a trick, it works virtually every time.

So what’s going on? It turns out that when you focus someone on the mechanics of how their body moves, it scrambles their ability to do it. On the other hand, when you focus someone on a particular effect, be that a good serve, an unbendable arm, or keeping your fingers together, the body figures out the best way to achieve the desired result.

To put this another way, we become less capable when we attempt to micromanage ourselves. We become more capable when we learn to trust ourselves to exercise our skills in the ways that make the most sense for us. We do best when we have the freedom to focus on what we want to accomplish and discover the best way of accomplishing it, instead of being locked into one way of doing it.

What is even more interesting is that the behavior of teams mimics the behavior of individuals. The more a manager attempts to control the details of how the team is doing its job, the less capable the team becomes. The expert leader knows how to trust his team and gets out of their way.

The beginning jujitsu player attempts to make every piece of the move perfect: they try to turn their arm at just the right angle, step to just the right spot, and so forth. They are stiff and awkward. The master knows the result she wants and produces it, confident that her body will do the right thing. What is the difference between the novice and the master? Correct practice. Obvious though this point may be, if you practice the wrong things, you’ll do the wrong things.

The team is no different:  a leader learns to trust his team and the members learn to trust the team and the leader through constant practice. Like jujitsu, however, it must be correct practice. The novice who practices incorrectly improves slowly, if at all. He may do more advanced techniques, but he does them with the same awkwardness and wasted energy of a beginner. The team which focuses on the wrong skills may be given more difficult projects, but it does them with the same lack of coordination and poor use of resources as it did when it first got together.

When teams come together and attempt to leap straight into project definition and problem solving, they are focusing on the wrong skills. They haven’t yet learned how to be a team. Before they can define the project or solve problems they have to learn how to make decisions that they can all support. That doesn’t mean they all have to agree with the decision, but every team member must be able to enthusiastically implement whatever the team decides. That won’t happen if the team doesn’t know how to settle disputes and achieve consensus without splitting itself into factions.

Unfortunately, when teams focus on the wrong skills, leaders are unable to trust those teams to make good decisions. The leader, therefore, takes it upon herself to make all the decisions. While this may be a great way to get started, it starts to break down as the problems become more complex. This causes the leader to attempt ever tighter control of the team, with increasingly poor results.

At one major manufacturing firm I worked with, a certain engineering director was the go-to guy. He could solve every problem, and the team knew it. The director often complained that if he was stuck in a meeting, work came to a screeching halt, assuming it ever got moving fast enough to screech as it halted! The idea of taking a vacation wasn’t even in the cards.

The solution was to help him back off and let go of his control. Instead of solving their problems, he started walking the team through his problem solving process. Instead of answering questions, he showed them how he found the answers to those questions. Instead of making the decisions, he helped them develop effective decision making skills. It was pretty uncomfortable at first: the team got it wrong a lot, and he kept imagining what his boss was going to say to him if things didn’t work out. After a while, though, the team started to get the idea. Their problem-solving and decision making skills improved.

One of the very difficult transitions for jujitsu practitioners is discovering that doing very little yields the biggest response. Focusing on what should happen to their partner allows the technique to become effortless. This director had the equivalent experience:  although he felt like he was doing less and less, his team was accomplishing more and more. The less he focused them on the details of getting things done, the more they were able to do. Eventually, he was able to focus his time and energy on long-term strategic thinking, instead of day-to-day minutia.

Trusting yourself, or your team, to do the right thing isn’t magic. It’s the result of hard work and correct practice. The more you control the details, the harder the task becomes. The more you enable your team to deal with the details, the easier it is for everyone, and the higher the quality of the results.

Sometimes less really is more.