The Business Sensei

Slush in the Schedule

It’s snowing as I write this. Of course, these days that means I could be writing this article almost anytime. In the last three weeks, we’ve had some 7 feet of snow, or maybe 8, in the Boston area. That makes for a lot of snowmen! It also makes for a lot of slush in people’s schedules. It’s no wonder that the police in one New Hampshire town issued an arrest warrant for Punxsutawney Phil.

In fact, this sort of weather really makes a dramatic point about just how hard it can be to plan and schedule just about anything. A couple of blizzards and it’s amazing how disrupted everything becomes.

Schedules are a funny thing. When I was giving a workshop a few years ago on project management, one of the people in the audience became quite irate when I suggested that the point of a schedule is not to make sure that you optimize every minute, but rather that a schedule exists to prevent us from trying to do everything all at once.

This person insisted that it was possible to precisely calculate the amount of time that each step of the schedule would take and thus there was no need to waste any time. Had this actually worked for him? Well, it turns out that he was (in)famous for missing deadlines and burning out his teams trying to hit arbitrary targets. No matter how precisely he tried to calculate the schedule, something would always derail it: the flu has no respect for precision. Once a tight schedule is disrupted, it can easily become a game of falling dominos.

In the end, the goal is to beat the schedule, not create a schedule that beats you. It’s quite amazing: when we’re ahead of schedule, we are simultaneously more relaxed and more energized. We focus better and come up with more creative solutions to problems. Unexpected obstacles are fun challenges. When we are behind schedule, we feel rushed. Every delay feels like a crisis. We take shortcuts and make more mistakes, which, in turn, only further disrupts the schedule.

The secret, it turns out, to effective schedules is not to try to be extremely precise, but rather to recognize that your schedule will need some slush. Things do not always happen when they are supposed to: some things will go faster than expected, and others will go more slowly. The goal is to be able to adapt to that: when the US military started conducting war games with the Japanese, the hardest thing for the Japanese military was that US forces wouldn’t attack on time. Sometimes they were early, sometimes they were late. This was very frustrating for the Japanese, who were used to extreme precision in their war games. Eventually, they figured out the lesson: warfare doesn’t happen on a clock.

When you’re building your schedule, don’t just estimate how long something will take. Break down each task, think about the different moving pieces involved. Consider which pieces can be disrupted by someone getting the flu or by a freak storm. Where are you implementing a known and tested solution and where are you trying something new and different? Exploration will always take longer if only because you don’t know ahead of time what you’re getting into: Boston’s famous Big Dig certainly had its share of bad planning, but it also had its share of discovering that the problems being solved were much bigger and more difficult than anyone expected.

As I explained to someone very recently, always put breaks in the schedule. As every endurance athlete learns, mostly by ignoring this advice, you need to stop and rest periodically. When you decide to skip a rest or a meal break, you set yourself up for failure. Just as the silence between the notes is what makes the music, it is the breaks in the schedule that enable the team to maintain high productivity over the long term.

Take time in your schedule as well to put in checkpoints to evaluate progress. That doesn’t mean fighting about why something didn’t get done, but rather to understand what is working and what is not. Make adjustments and shift resources as necessary: part of good scheduling is the ongoing process of refining the schedule.

But what about 8 feet of snow? Surely no one can plan for weather conditions like that! Of course not, but that’s not the point. When we are used to the idea that schedules need regular tune-ups and adjustments, when we recognize that unexpected obstacles are just part of the job, then it becomes easier to role with whatever storms arise. The blizzard isn’t a crisis, it’s just a more dramatic version of business as usual.

Are you beating the schedule or is the schedule beating you?

Hidden Assumptions

We’ve been hearing a lot about how it now appears that two nurses working with Ebola patients in Dallas have contracted the disease. The big question is, of course, how did it happen? What was the mistake or violation of medical protocol that led to them getting infected?

When I ran a pandemic flu simulation exercise (essentially, an experiential assessment) in Washington DC, part of the exercise involved doctors coming down with the deadly flu strain. I received some very interesting feedback from one of the doctors. He told me about all the different simulations that they do: natural disasters, terrorist attacks, accidents, radiation poisoning, etc. Then he said, “But we’ve never done one where we get sick.”

Hidden assumptions: the things we so take for granted that we don’t even consider them. Doctors and nurses are used to working with sick people, and they are used to working through a lot of minor discomforts. They just don’t think about getting sick. Apparently, though, no one ever told that to the Ebola virus.

And that’s the key point: our hidden assumptions are great until they’re not. It’s like the old slapstick routine where the comic steps on a rake: it seems to pop up out of nowhere and smack him in the face.

The problem, though, is that hidden assumptions are just that: hidden. We don’t even realize they’re there until we trip over them. At that point, the damage is done.

It’s far better to find them ahead of time. Unfortunately, we can’t just ask about them: what are we not considering? Hidden assumptions are hidden; they are, by definition, the things we are not thinking about or even considering. They are the box we don’t even know we’re in. Experiential assessment can change that by forcing us into experiences that reveal the box.

Real opportunity comes when we realize what we’re taking for granted.

To Succeed, Plan to Fail

I’m getting tired of hearing people say, “Oh I get it. We didn’t plan to fail, we failed to plan.”

When I’m working with a business to help them understand why their process is failing or their projects are off course, sooner or later someone comes out with this little gem. At that point, everyone nods sagely as though they’ve actually solved something. They are missing the point. If that was all that was wrong, they wouldn’t need help.

Sure, it’s certainly true that if you fail to plan, you’re far more likely to fail, but knowing that doesn’t actually address the real problem: they are taking the “failure is not an option” mindset. This is a fantastic line in a movie, but has some problems in reality.

When we take the mindset that failure is something that cannot be accepted, we are implicitly stating that failure is a terrible thing, something so terrible that we cannot even consider it. It’s an attitude similar to that taken by many martial artists, who teach their students that they must never allow themselves to be taken off balance. All their training is then based on the idea of never being off balance. As a result, when they are off balance, they freeze.

A youthful student once watched Morehei Uyeshiba, the founder of Aikido, sparring with a much younger, stronger opponent. After Uyeshiba defeated the guy, the young student said to him, “Master, that was amazing. You never lose your balance!”

Uyeshiba’s reply: “You are mistaken. I frequently lose my balance. My secret is that I know how to regain it quickly.”

Uyeshiba recognized that loss of balance is a normal part of any fight. By training to rapidly regain his balance, he stripped the experience of its emotional content. It was merely something that happened, and something which he well knew how to recover from. As a result, not only were his opponents unable to capitalize on taking him off balance, when he took their balance, they didn’t know what to do.

Failure is the same. When failure becomes something we fear, it can cause us to freeze. At one company, the first hiccup in a string of successes led to panic by the CEO. He wasn’t used to failing, and he didn’t know what to do about it.

The problem is that fear of failure causes us to avoid risk and not experiment with new ideas. When something goes wrong, as it inevitably will, we figuratively lose our balance and become momentarily stuck. If we think that failure means something terrible will happen, we opt for the safe course. Unfortunately, the safe course is often not the best course or the wisest course. It’s merely the one that minimizes the short-term risk to us, potentially at the cost of long-term risk to the team. That, of course, is just fine: if the entire team fails, no one is to blame.

Conversely, when we accept that along the route to success there will be many failures along the way, and when we practice viewing failures as a form of feedback, the negative emotional component of failure is eliminated. Instead, we simply have information: something we attempted did not work the way we expected. What does that mean? What is that telling us about our plan? About our process? About the competitive landscape?

Failure is a way of calibrating our efforts and focusing our energy. Particularly early in a project, small failures are, or should be, common. The less defined the project, the more exploration needs to occur in order to adequately and accurately define the milestones. Indeed, early milestones are best thought of as little more than wishful thinking: opportunities to put stakes in the ground and see what happens when we get there. It’s the chance to see how well the team members are working together, how effective the leader is being, how effectively the team can make decisions and implement a course of action.

When we fear failure, the fear itself is often more damaging than the failure! The key to succeeding at large, important projects is to recognize that failures will happen along the way. By accepting the information that failure gives us and cultivating the mindset that failures are recoverable and useful, failure truly does make us more, not less, likely to succeed.

Plan to fail

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

I have to confess to being very tired of the old aphorism, “If you fail to plan, you are planning to fail.” Planning to fail is actually a worthwhile exercise, while failing to plan is simply a good way to waste time and energy without any benefit at the end. Failure is a surprisingly useful tool, at least for those who are not afraid to use it.

Seeing how your plan is failing can give you vital information on how to shift focus, allocate resources, and generally adjust your strategy. On a more subtle level, we won’t fully trust a plan that fails to consider failure: we need to have confidence that our plans or our feedback systems will alert us to something going wrong in order for us to believe it when things are going right. I’ve frequently seen companies abandon working plans simply because they had never determined how they’d know if something was going wrong and therefore concluded that something must be going wrong no matter how much evidence they had that their plans were working!

More broadly, though, the difficulty is often a misunderstanding of what it means to plan. I’ve worked for companies that tried to plan projects out 2-3 or more years. While this is possible in a very broad sense, details matter, and you can’t plan details that far in advance. Instead, you have to plan the steps in front of you. Part of the plan is to pause periodically and review the plan. What worked? What didn’t work? What are the next steps? Developing an effective strategy is not something you do once and then execute blindly; you have to constantly adjust as circumstances change. The beginning chess player tries to play out a sequence of moves and is paralyzed when the opponent doesn’t respond as expected; the chess master has a plan and constantly adjusts his strategy in response to his opponent.  You need to plan far enough, but not too far: This may sound like it contradicts the concept of reverse goal chaining; not at all. It is simply the case that the more distal steps are going to be vague until you get close enough to see the details. Good strategy requires a certain comfort with ambiguity and the ability to periodically evaluate, adjust, and adapt any plan.

Interestingly enough, the beginning chess player usually can’t explain his plan, while the master can. The beginner’s plan sounds like, “I have a plan: I’ll do this, and this, and this, and that’s how I’ll win.” The chess master, on the other hand, is likely to treat you to a detailed discussion of his thinking processes and chess strategy. The first is easy to say and easy to listen to, but is fundamentally useless. The second is hard to articulate and takes a lot of effort to follow, but actually does have a chance of working. Part of the reason it works is that the chess master has contingencies built into his strategy: he’s already considering that his opponent might do something unexpected and is mentally prepared to handle that. The beginner, by assuming that each step simply needs to be executed in the proper sequence, is locking himself into a rigid mindset. Chess strategy or business strategy, the results are same.

Fundamentally, failure is a form of feedback. In fact, this is exactly what you want failure to be: a means of testing out different strategies and figuring out which ones work best. Used this way, failure can be very helpful. Indeed, without such productive failures learning and strategy development is impossible.

However, sometimes the cost of failure can be somewhat higher. If Billy’s goal is to cross the street safely 75% of the time, what about the other 25%? Even if we raise the expectation to 99%, that one failure can negate all the successes: getting hit by a car can ruin your whole day.

It’s all too easy to confuse the two types of failures and businesses do it all the time. They are afraid to fail when that failure would give them valuable information and they take risks that sound good but where one slip causes you to lose everything.

How do we tell the two types of failure apart?

“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. I highly recommend this book for anyone who wants to participate in creating and steering company culture.”

 

Sid Probstein

Chief Technology Officer

Attivio – Active Intelligence

Eye of the Hurricane

I was lying on my back. Standing around me were four people who, only two weeks before, had been teaching a class on appropriate emergency response in jujitsu.

The fact that I was flat on my back on the ground was not, in one sense, unusual. A friend of mine was taking his black belt exam and I had volunteered to let him demonstrate his throws on me. Things went slightly off the rails when he threw me, lost his balance, and ended up kicking me in the head.

The “thwock!” echoed through the gym.

One of the instructors was supposed to take charge. They stared down at me. I stared up at them. Eventually, I said, “Someone get me an ice pack.”

One of the men jumped slightly, turned, and ran out of the room. A moment later, he ran back in with one of those first aid kid chemical cold packs in his right hand.

“It’s not cold,” he yelled.

“You have to squeeze it,” came a voice from somewhere in the room.

In case you were ever curious, yes, it is possible to squeeze one of those cold packs too hard.

For such a small cold pack, the contents covered a remarkably large area.

I looked at my now soaking gi. I got to my feet.

“I’m fine now. Please don’t help me any more.”

Fortunately, in this situation, there was no permanent harm done and the fact that several people froze at the moment of crisis was merely embarrassing. My gi wasn’t even stained.

Unfortunately, many businesses are not so lucky. Even more unfortunately, it’s not the actual disasters that freeze them: handling the rare fire or power failure is barely a blip in the proverbial routine. Rather, the “disasters” that throw everything off balance and freeze decision making in its tracks are those that could have been anticipated or for which management thought that they had prepared.

Despite all their training, when the accident occurred, the four jujitsu instructors metaphorically lost their balance by focusing on the image of how bad it could be. That prevented them from acting immediately to determine how bad it actually was.

At Lacunae Software, the ship date was two days off when QA found a major bug in the software. Rather than stop, investigate the severity, and determine an appropriate course of action, the CEO announced that delaying the ship would clearly doom the company. He castigated QA for disloyalty and ordered the product to ship on schedule. Customers were not happy, costing the company more than the delay would have. Acting out of fear of how bad it could have been made the situation worse.

When things are going well and something suddenly goes wrong, it can be very easy to focus on all the potential negatives. That doesn’t help. Successful companies have the habit of focusing on what can go right. Developing that mindset takes practice:

Take a deep breathe and recognize that you have more time than you think. This is quite probably the hardest step.

• Remind yourself of the vision for your product and company (you do have a vision, right?).
• Review the steps necessary to manifest that vision. It can help to write them down as you go through them.
• List the things that can go right to move you forward from where you are. Be realistic, and also optimistic.
• Any time you find yourself focusing on what can go wrong, stop and shift back to what can go right. Evaluate the problems later.

Far too many companies never define their vision nor do they map out the path to success. The secret to success is staying on balance. The secret to not losing balance is knowing where you’re going, reminding yourself how you’ll get there, and focusing on the positive.

Where Did The Time Go?

There is nothing quite like that warm feeling you get at the end of the day when you look back and wonder where the time went. There is nothing quite like realizing that an entire day has gone by and nothing got done. Unfortunately, this happens far too often, especially when the day holds meetings.

Meetings have a bad reputation for consuming a great deal of time while producing little of substance. That reputation is well deserved. Despite this, meetings remain extremely popular in many companies. Unfortunately, in addition to potentially wasting a great deal of time, meetings often tend to leave people drained and unable to focus. As a result, they use up even more time getting back on track after the meeting.

Read the rest at FreudTv.com