The Business Sensei

Of Cats and Unwanted Prizes

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 McGraw-Hill 36-Hour Course in Organizational Development,” and “Organizational Psychology for Managers.” He is also 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.

Speaking of panic…

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

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. 

It is not a cause for celebration when our arousal spikes up so fast, or is kept high for so long, that we hurtling down the right side of the performance curve. Instead of a more or less gradual decline in performance, we instead experience a very different form of catastrophe.

As we can see, instead of sliding smoothly down the curve, performance can collapse suddenly. Whether this collapse occurs depends on a number of factors, including the overall level of stress, a person’s overall level of fitness, whether or not you’ve had enough sleep, how recently you remembered to eat, and so forth. People who are in good physical condition, are getting enough sleep, and who are remembering to eat despite the stress are less likely to experience catastrophe. They aren’t immune, but at least their odds are better.

When we are sliding down the performance curve, various centering and focus techniques can be used to stop our descent and move us back up toward the peak; we will look at those techniques shortly. Once we fall off the cliff, however, we have to start all the back at the left end of the curve. In other words, we need to rest and recuperate, at least overnight, possibly for a few days, before our performance will return to its precatastrophe peak. Quite simply, when we are sliding down the right side of the curve, we are drawing on our energy reserves more and more rapidly. When we hit catastrophe, we’ve exhausted our reserves and we need to recharge.

If we try to continue performance once we’ve hit catastrophe, we just make things worse. Now we’re into error catastrophe, where mistakes compound upon mistakes, and our efforts to fix them only causes yet more errors. Athletes who hit catastrophe generally don’t have a choice about continuing: they are often physically unable to do so. If you’ve ever seen an uninjured runner or cyclist abandon an endurance race, that’s often what’s going on. In the office, however, we are more likely to get into competitive frog boiling. No one wants to be the first to admit defeat and go home, so everyone keeps pushing on even though productivity is plummeting and we’re actually making the situation worse. When we are feeling stressed, our instincts are to make the stressor go away; taking a break and sleeping seems counter-intuitive, even though it’s exactly what we need. Remember, cognitive short-cuts most often kick in when we’re tired or distracted, and lead us into errors. It is also possible to reach a point of such mental fatigue that it almost becomes too difficult to stop and take that necessary break. This is where it’s particularly important that the team leader has the judgment and presence of mind to chase everyone out of the office.

A final thought here: I’ve seen many companies where the idea of going home and getting a good night’s sleep was viewed as a sign of weakness. Instead, the teams would push on until they dropped from exhaustion, and then force themselves to continue the next day. The results were never worth it. In the infamous Apollo 13 disaster, with oxygen running out for the stranded astronauts in the damaged space capsule, mission controller Eugene Krantz still ordered the crew to get a few hours sleep before attempting the difficult maneuvers necessary to bring the space capsule back to Earth. Running out of air was less risky than the consequences of attempting a difficult operation on no sleep.

Balzac combines stories of jujitsu, wheat, gorillas, and the Lord of the Rings with very practical advice and hands-on exercises aimed at anyone who cares about management, leadership, and culture.

Todd Raphael
Editor-in-Chief
ERE Media