The Business Sensei

For Want of a Rubber Band

The other day, my DVD player stopped working. Naturally, this happened the night I was sitting down to watch a movie I’d been looking forward to. Quite simply, the tray wouldn’t open (presumably, it wouldn’t close either, but there was no way to test that). As we all know, a feature of modern electronics is that there are “No user serviceable parts inside.”

Nonetheless, I decided to open it up anyway. If nothing else, I figured I could at least recover the trapped DVD one of my kids had left in the machine.

Opening it up was an interesting experience. Inside was mostly empty space with a tray and a circuit board. Apparently the major difference between a portable player and a non-portable one is the amount of wasted space.

There was also one user serviceable part: the rubber band.

Yes, in the midst of the electronics there was a broken rubber band. That rubber band acted as the “drive train” to open and close the DVD tray. Just think about that: all this high tech electronics rendered completely useless by the failure of a sixty cent rubber band. How much is that rubber band really worth? Sometimes the value is not the cost of the item but what it makes possible. Sometimes the critical problem that is blocking us from moving forward turns out to be something small and simple, but only if we know where to look and what to look for. While I could have replaced the DVD player, that would have been a much more expensive solution than replacing the rubber band. Knowing the real problem enabled me to pick the best possible solution.

I was asked recently about my opinion on attendance point systems.

“Why?” I replied.

The person explained her company was having problems with absenteeism and people changing shifts without notifying anyone in authority. Based on this, she wanted my opinion of attendance point systems, presumably on the logic that implementing one would solve her problem. Unfortunately, without knowing exactly why people are not showing up for work on time and without knowing why they’re constantly switching shifts, implementing an attendance point system is as likely as not a solution in search of a problem. Sure it might work; on the other hand, it might not work. It’s basically a roll of the dice.

So why jump to that solution? Simple. It’s easy. Faced with a problem without an obvious solution, the natural response is to impose a solution that fits the symptoms. Symptoms, unfortunately, are not the problem; they’re just the symptoms. Like taking an antibiotic for the flu, it doesn’t help and may make you feel worse.

Instead, we need to work backward from the symptoms to understand the underlying problem. With my DVD player, the symptom was that the tray wouldn’t slide out. Had I assumed the problem was that the electronics were fried, I would have tossed it and bought a new one. By investigating the problem, I had a working DVD player in less than fifteen minutes.

Investigating the problem, however, requires a certain amount of effort and frequently appears overwhelming and expensive. The lure of an obvious, easy, and, above all, cheap solution is very strong. The fact is, there are a lot of obvious, inexpensive solutions to many problems. In a business, it’s particularly easy to find an easy solution particularly if you don’t care if it actually works. If you want a working solution, though, the choices become somewhat more limited.

Investigating a problem is rarely as overwhelming as it first appears. With the DVD player, it was easy to open it up and see what was going on inside. With human systems, on the other hand, taking them apart in that way can be a bit problematic. Putting them back together again is even more tricky. The real key is to see how often the symptoms appear and under what conditions. What other symptoms are there? What do people say when you ask them about their experiences and their observations? As you put together a picture of the symptoms and when they appear, you can start brainstorming about possible causes. Does your organization have a cold? The flu? Is it suffering from growing pains?

At one company, everything was going great until they went public, had a huge influx of cash, and began a rapid expansion. Suddenly, all sorts of symptoms appeared: increased conflict, passive-aggressive behavior, confusion, inability to follow through on decisions, and so forth. Fixing the problem required first identifying what was really going on, and then crafting a solution appropriate to that organization. None of the problems were that big, but, like that rubber band, they were in critical places.

In a sense, it’s not how big the problem is that matters most. What matters most is what that problem is preventing you from doing.

How much was that rubber band worth again?

My Hovercraft is Full of Eels

Originally published in Corp! Magazine.

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

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

“Are there any problems?”

“There are problems.”

“What is the problem?”

“It does not work.”

“Why doesn’t it work?”

“It is not done.”

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Make Believe Can Really Help Business

I was very pleased to see that Lizzie Stark’s new book, “Leaving Mundania: Inside the World of Grownup Make-Believe” is now available. Lizzie’s book is an excellent explanation of live-action roleplaying (larping) and how it works.

But  wait? Isn’t larping just a game? How can it help my business? I’m glad you asked.

All businesses need to provide leadership to their members, motivate employees, and negotiate with individuals and organizations. The problem is practicing those skills in an environment that doesn’t feel artificial. A well-designed, serious larp provides an engrossing, entertaining training experience. Players are able to get into the game and as a result deal with the problems that come up much as they would in real life. Whether a player gives up in frustration after encountering an obstacle or comes up with a creative out of the box solution, that tells you they’ll likely do the same thing on the job. Conversely, when someone shines in the game, but is a mediocre performer on the job, that alerts employers to untapped potential.

In sports, teams practice their skills over and over to deal with every conceivable scenario. Businesses rarely have that luxury. When I design a serious larp for a business, the experience of playing in the scenario enables employees to practice and hone skills before the critical situation in which they are needed. Employees also have the opportunity to experiment and make mistakes in an environment in which there are no financial consequences to the business. Finally employees who need additional skill training can be identified before they fail on the job.

If you want an academic treatment of larping, click here. Otherwise, I encourage you take a look at “Leaving Mundania,” and think about how you can use the games she describes to help your business (and have a good time!).

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.

North Korean Rocket Change

I was listening to a news report this morning about North Korea’s latest rocket launch. It was quite the show, with hordes of journalists invited to watch and report on North Korea’s military might. According to one report, North Korea was also showing off for potential buyers of its military equipment.

As anyone who has ever given a software demo might suspect, North Korea’s rocket demo had similar results: it crashed. Unlike software, you don’t get to reboot the rocket and try again.

Although the news report wasn’t entirely clear on what happened, it appears that just before the first stage of the rocket finished its burn and dropped away, stages two and three both tried to ignite.

This did not go well.

Although perhaps less visually spectacular, the results are much the same when a business attempts to implement a “North Korean Rocket” approach to organizational change.

Organizational change is never easy, and on top of that, most companies make it considerably harder than it needs to be.

Change is a process: like launching a rocket, each stage needs to fire in turn. Attempting to fire the stages all at once or out of order only leads to a spectacular boom.

At least with a rocket, you might get some visually stunning fireworks.

The first stage of organizational change is getting your employees comfortable with the idea of making a change in the first place! This is one situation where focusing on what’s wrong is the right thing to do. You want your employees talking about why the status quo isn’t so hot, and how things really could and should be better. After all, if they’re all happy with the status quo, why would they want to change? As many a manager has learned, the more force you apply to make people change, the slower they go and the more likely your change initiate will fail.

Once people are in the mood for change, it’s time for the second stage: building some excitement. Rather than grumbling about how bad things are, it’s time to ask how things could be better. What would the company be like if we did make a change? How would that feel? What would working at that changed company be like? Look at both benefits to the company and benefits to the individual: no one wants a change that will leave them worse off.

In stage three, it’s time to focus on creating the confidence to change successfully. No matter how excited people may be at the idea of change, if they don’t believe they can do it, they won’t really try. It’s time to get them talking about previous successes, especially successful changes they’ve made in the past.

Finally, in stage four, it’s time to get people contributing ideas for change. Getting everyone involved dramatically increases the odds of success. The more confident and excited people are, the better the ideas they’ll come up with. The more involved they are in the idea generation process, the harder they’ll work to make the changes happen.

I worked with one client who would say to me, “Okay, I get it. I should do this, and then this, and then this.”

About then, I’d stop him, and say, “No, just do this one thing.”

He didn’t like that: it was too slow.

Every week, he’d complain that the project wasn’t moving forward. Every week, I’d ask him what he’d done, and he’d list off “this, and this, and this.”

Eventually, he decided to try going through the stages in order and one at a time. Suddenly, he saw progress.

Like the rocket, ignite the stages in the right order, and you make very rapid progress. Try to ignite them all at once or in the wrong order and you have a North Korean rocket launch: straight up in the air and then straight down into the ocean.

If they’re lucky, they might still be able to sell arms to Pottsylvania.

Happy Groundhog Day!

In the movie Groundhog Day, Bill Murray finds himself reliving the same day over and over again. Great movie, and solid proof of the old adage that adventure is something really dangerous and exciting happening to someone else. As much as watching Groundhog Day can be lots of fun, actually experiencing it is something else again. Thus, it never fails to amaze me when organizations willingly enter the Groundhog Zone.

No, I don’t mean that they are afraid of their own shadows, although that sometimes happens too! Rather, they are trapped in a cycle that is at best non-productive, at worst, downright destructive to the organization. Worst of all: everyone knows its happening and yet no one does anything about it. Unlike Bill Murray, though, they aren’t actually trapped. They just think they are.

For example, I worked with one two thousand person organization on some serious leadership issues. The first time the organization ran into this particular problem was decades ago, and it nearly destroyed the business. Many of the top people stormed out to found a competing company. The same thing happened again some twenty years later. The third time around, we made some progress: there was no fissioning of the business. Everyone stayed put and the first steps were taken to resolving some of the long-standing structural problems that were causing this cycle to repeat. It wasn’t easy and it wasn’t necessarily pleasant, but it happened.

Okay, that’s an old business. Should we really be concerned with problems that only come up every twenty years? That’s up to you; I suppose it depends on when the next time the cycle rolls around. But Groundhog moments are not limited to older companies. Younger companies can have the same problems.

At one company, the engineering teams are unable to make decisions. The same issues come up week after week: every Monday is Groundhog Day! While there is a lot of talking and a great deal of motion, there is no progress. Running around in circles may feel good, but doesn’t exactly get you anywhere. Management regularly gets involved in various ways, and always with the same results: there’s some yelling, some threats, maybe a few people get fired, and there’s a brief flurry of forward motion. After a few weeks or a couple months, though, they are right back to where they started. Even though many members of the management team know there’s a problem, even though they keep talking about the problem, they take no action despite the cost to the organization: on the order of six figures per month. Groundhog Day indeed!

So what do you do when you realize that you are trapped in Groundhog heaven? Since every company’s Groundhog Day is uniquely theirs, the key is to know how to generate possible solutions, rather than find a one-size fits none approach.

First of all, don’t be afraid of your own shadow. Recognize that something isn’t working the way it should. The longer you pretend the problem doesn’t really exist or the longer you just hope it’ll go away, the worse it will get. As Einstein famously said, doing the same thing over and over and expecting a different result is the very definition of insanity. Whatever you’re doing to change things isn’t working. It’s time to try something else.

In Bill Murray’s case, Groundhog Day just happened overnight. In the real world, you didn’t get into Groundhog mode overnight and you won’t break out of it overnight. Stop looking for quick fixes: if they haven’t worked yet, they aren’t likely to in the future. You’ll spend more time and money trying quick solutions that don’t break the cycle than you will in committing to one solution that may take some time to implement. Organizational change, even beneficial change that everyone claims they want, is still difficult. If it wasn’t, Groundhog Day would be over by now.

Look outside the company for ideas. Let’s face it, you’ve got some really smart people working at your company (if that’s not true, you have bigger problems!). If they haven’t managed to change things, it might just be because they either don’t know how or they are too busy doing their jobs to devote the time and energy necessary to driving the changes necessary, or both. Whatever the reason, recognize that if they could, they would. Look at other companies and adapt their solutions to your specific culture and situation and bring in the resources you need to actually break the cycle.

Bill Murray has no choice but to repeat Groundhog Day over and over. Fortunately, you aren’t Bill Murray. What choice will you make?

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

Take a Future Retrospective

Originally published in Corp! Magazine.

Once upon a time there was a staircase. Although it wound its way up from floor to floor in the manner traditionally associated with staircases, this was no ordinary staircase. Although it stood in a courthouse in Franklin, Ohio, in a fashion much like other staircases, yet it was not like the other staircases. With most staircases, those who look down see stairs beneath their feet. With this staircase, however, those who looked down saw the floor below and those people walking up the stairs. They saw those who stood at the bottom of the staircase, for this staircase, you see, was made of clear glass. While we have no information as to whether those climbing the staircase felt a sense of vertigo when they looked down, we do have definitive information about what they said when they looked down: “Hey, those people at the bottom of the stairs are staring up my dress.”

Although the news report was slightly vague on this point, we may safely assume that this comment was made only by those who were, in fact, wearing a dress.

But yes, it seems that people on the staircase made an observation that had eluded the architects who designed the staircase: that if you can look down through the glass, you can look up through it as well.

When questioned on this point, the architects responded by saying that they had naturally assumed that no one would be so inappropriate as to stand at the bottom of a glass staircase in a courthouse and look up women’s dresses.

When this insightful observation was relayed to the judge, he replied that, “If people always exercised good judgment and decorum, we wouldn’t need this building.”

The architects had carefully considered their building material. They had thought about how to make the glass durable and resilient. They had considered the problems involved in building a glass staircase in such a way that it would continue to look good even after having hundreds of people walking up and down it each day. They had, in fact, solved each one of these problems.

What they had not considered was how the customer, to wit, the people in the courthouse, would actually use the product. They were so fixated on the concept that a staircase is for walking on, not staring through, that they failed to consider the ramifications of their architectural decisions. To be fair, architects are hardly unique in making this type of mistake. It can be very easy to let your assumptions about how something should work or how it will be used to blind you to how it will actually work or be used. Consider the example of the business school competition to design a helicopter. The contest was judged on a number of factors, including the weight of the finished product. The winner was the helicopter without an engine. Apparently, no one had included “able to fly” in the criteria for success. The assumption that, of course, a helicopter should fly was so taken for granted that no one thought to see if it was included in the rules.

On the bright side, it had considerably less severe consequences than the situation involving the helicopter that flipped upside down while in flight. Or the data analysis software package that looked like it had crashed the computer, causing users to reboot shortly before the calculations were complete. Or the organizational improvements that led to a massive talent exodus.

In each situation, the people designing the end result honestly believed they were giving the customers, including the employees in the final case, what the customers had requested — and that belief prevented them from considering any other possibilities.

“We asked!” the designers protested. “That’s what they said they wanted.”

Were the customers really asking for a helicopter that flipped upside down or an expensive glass staircase that had to be subsequently covered? Of course not. But somehow, that’s what the designers heard.

The problem was that they asked the wrong questions, further leading them into their one, narrow, view of the result. Thus, no one ever stopped to imagine how the end product, be it staircase, contest rules, helicopter, software, or organizational procedures would actually be used.

In each situation, rather than seeking information, the people asking the questions sought validation. They already had an idea in their heads, and any inquiries they made were aimed at confirming that idea, not testing it.

When you say, “This is what you wanted, right?” or “What do you think of this approach?” odds are you aren’t requesting information; you are requesting validation. Indeed, even if you are seriously trying to get information, such questions usually get you validation instead. This is because the client assumes that you, as the expert, know what you’re talking about.

So how do you ask for information? One answer is to change the time frame. Instead of asking them to imagine the future, pretend it’s the future and imagine the past: “If we went with this approach, and six months from now you weren’t happy, what would have gone wrong? If you were happy, what would have gone right?”

This small change causes people to actually imagine using the product or living with the new procedures. Now, instead of validation, you’ll get information. That information may shake up your carefully constructed vision of the future, but that’s fine. Better now than after the sightseers congregate at the bottom of that glass staircase. A future retrospective also forces you to be more honest with yourself and to address the issues in front of you.

What challenges is your business facing? If, six months from now, you had successfully addressed your most persistent problems, what would you have done to make that happen?

Don’t over commit to start the new year!

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

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

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

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

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

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

So how do you prevent this from happening?

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

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

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

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

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

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

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

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

New Year’s Resolutions? Forget it!

It’s barely the start of the new year, and I’ve already received half a dozen identical articles touting the benefits of SMART goals as the solution to all my New Year’s resolutions.

Now, to be fair, they have a point as far as it goes: New Year’s resolutions have a shorter half-life than champagne at a New Year’s party. However, that’s about as useful as these articles get.

Specific, Measurable, Achievable, Relevant, and Time-bound, SMART goals are often touted as the secret to personal and business success. Unfortunately, it’s a pretty safe bet that most of these goals will go the way of all New Year’s resolutions. Why? Because none of these articles actually tell you how to make SMART goals work. In fact, most people who try the SMART approach for any but small and relatively easy goals frequently find themselves frustrated and disillusioned.

Well-constructed goals are extremely powerful tools for getting things done, increasing concentration and motivation. Successfully completing a well-constructed goal builds self-confidence. Unfortunately, creating a well-constructed SMART goal is not quite so simple as the average article makes it out to be.

To begin with, a specific goal is only useful if it’s something you can control. Although this may seem obvious, the fact is that far too many people set goals that appear to be under their control, but really are not. For example, consider the athlete who sets the goal of winning an upcoming tournament: it’s specific, it’s measurable, it has a time of completion associated with it, and presumably it’s highly relevant to the athlete. Is it achievable? Depending on the athlete’s level of skill, very possibly. However, the athlete has no control over the difficulty of the competition. He may simply be outplayed by a more skilled opponent.

Furthermore, although the goal is measurable, in that the athlete will know whether or not he accomplishes it, the measurement is not particularly useful. At no time will he know how close he is to accomplishing the goal, where he needs to focus his energies, or what else needs to be accomplished. The athlete is far better served by setting the goal of exercising certain key skills in the competition, skills that have a high probability of leading to a victory. Not only will he gain the self-confidence boost of accomplishing his goal, he may just win the tournament. Whether your goal is winning a competition, selling a product to a particular customer, or getting a specific job, focusing mainly on outcomes only gets you in trouble.

Another problem is that a goal may simply be too big. If a goal takes years to accomplish, it can be extremely difficult to maintain motivation. Big, ambitious goals are wonderful, but they need to be carefully structured. It is vital to break them down into subgoals that can be accomplished in a much shorter period of time. The perception of progress is critical to maintaining motivation, whether for an individual or a team.

Having too many goals is another common problem. Well constructed goals are great, but if you have too many of them at once, they become a distraction. Many people can focus on three to five unrelated goals without a problem, but not ten or twenty. Keeping in mind that each goal might generate numerous subgoals along the way, it’s easy to see how having more than a few key goals can easily balloon out of control.

Is the goal something you really care about? Many people have goals that they don’t really care about. Perhaps they’ve been told it’s something they ought to do or they believe they should do, but they don’t really care about the outcome. If you don’t care whether or not you accomplish a goal, it’s hard to find the motivation to do it.

Used properly, SMART goals can be a very powerful and effective tool. Well-constructed goals can increase motivation, improve focus, and build self-confidence. Used improperly, they can decrease motivation, and destroy self-confidence. If you’re using SMART goals, here are some questions to ask yourself:

Do I control the outcome?

Can I measure progress in a meaningful way?

Is my goal too big? How can I break it up?

Do I have too many goals? Is there enough time in the day/week/month to work on each one?

When will I work on each piece of my goal? How will they chain together?

Do I really care about my goal? Is this something I genuinely want to accomplish?

Good luck!

Of Cats and Unwanted Prizes

Originally published in Corp! Magazine

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

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

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

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

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

“We can’t delay the ship.”

“We can’t ship with this bug.”

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

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

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

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

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

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

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

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

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

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

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

Leave the catastrophes to the cats.

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