How to make your company sick by treating the symptoms

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

Did you ever notice that doctors who deal with respiratory illness are known as Ear, Nose, Throat doctors, not Achy, Coughy, Sneezy, doctors? You don’t go to a doctor who specializes in coughs; you go to the doctor who understands the system in which coughs occur. Even when you go to a specialist, said specialist usually, or at least hopefully, has enough knowledge of the overall system to recognize when they are not the right person. We might go to a doctor because of our symptoms, but we do not go to Symptom Doctors.

In this case, the company was not addressing what was wrong; they were addressing a symptom. After their Decision Consultant finished working with the team on whatever it is that Decision Consultants do, things really did look better for a short while. It wasn’t long, though, before other decision making problems cropped up. So they brought their Decision Consultant back again, and so it went. The problem never really got better, but the symptoms were periodically alleviated. There was no increase in productivity, but everyone did feel better about the team, particularly the Decision Consultant.

The problem with just treating symptoms is that we end up making ourselves feel better while the problem is constantly getting worse. However, when the solution to the problem is to bring in a Symptom Doctor, that’s what ends up happening. Over time, this approach undermines morale and enthusiasm: not only are there clearly problems, but they must be very big problems because the organization is spending lots of money trying to fix them and they are not going away! Eventually, some organizations come to believe that the problems are simply part of doing business; at that point, the business becomes a very unpleasant place to work!

 

“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.”

 

Sid Probstein

Chief Technology Officer

Attivio – Active Intelligence

How Do You Make Sure You’re in the Right Place at the Right Time?

This article was originally published in Corp! Magazine.

 

“Slow down.”

I can’t count the number of times that my original sensei would say that to me when I started practicing jujitsu. It drove me nuts. I never felt like I was moving fast. Besides, what was wrong with going fast? Now, after twenty years of jujitsu practice, I’m constantly telling my students to “slow down.”

Speed is a funny thing. It appears to be the most important thing in martial arts: being able to block quickly, hit quickly, throw quickly. However, when you move fast, there’s a tendency to overshoot the target, to over-commit. The block is too wide or the punch is over-extended, leaving you vulnerable. It’s easy to miss obvious feints by an opponent, and walk into a fist. Speed also leaves you physically and emotionally exhausted, unable to actually complete a workout. Indeed, the most skilled practitioners never seem to move all that fast. Rather, they become extremely good at always being in the right place at the right time. Speed comes from precision, but precision does not come from speed.

I’m frequently reminded of this phenomenon when I work with my clients. There is a tendency at many companies to try to do more and more in less and less time. The logic seems to be that if people just worked quickly enough, they would be able to get the job done. Instead, though, the error count is increasing even faster than the productivity. The time spent going back and correcting problems and fixing bugs more than makes up for the time saved by moving faster.

In jujitsu, moving fast can appear to work for a while. Eventually, though, you run into someone who knows what they are doing and you get punched in the nose. In a business, moving fast can also appear to work for a while. The major difference is that when you get punched in the nose, it’s not quite as obvious. It still happens though, and usually when you least expect it.

The problem once again is that moving rapidly does not equate to moving precisely. In a corporate setting, that lack of precision translates to instructions not being read closely, exceptions not being recognized, assumptions not being tested, or flat out inaccurate information not being corrected. It can also mean overreacting to a competitor’s product release or to a news story. In jujitsu, you may not have time to stop and think: if you haven’t prepared and trained, then you may just be out of luck. In a business environment, you may feel that you can’t stop and think, but the reality is far different. Unlike jujitsu, decisions don’t need to be made in fractions of a second. There is time to pause and consider the situation: even in the Apollo 13 disaster, NASA’s Eugene Krantz slowed everyone down and collected information before deciding what to do. Knowing when to slow down is what saved the astronauts; moving too quickly would have only compounded the problems beyond recovery.

Fortunately, most of us will never face the kind of life-or-death scenario that Eugene Krantz had to face. That, in turn, only makes the tendency to move too fast even more inexcusable.

The first problem, of course, is recognizing that you are moving too fast. Just as in jujitsu, it is surprisingly not obvious to the person, or team, that they need to slow down. It helps, therefore, to learn to recognize the symptoms of speed.

One of the easiest ones to spot is when the same types of errors just keep cropping up no matter what you do. You fix them in one place, they appear somewhere else. You come up with procedures for reducing the errors and for each mistake that you remove, a new one takes its place. One health related company demanded such a high throughput of patient claims that they were constantly dealing with forms being rejected because of mistakes. So they put in a layer of checklists to make sure the forms were done correctly. Then a layer of paperwork to make sure the checklists were correct. The errors simply kept shifting and the responses only created a slower and steadily more unwieldy system in which the ability to generate billable hours is limited by the need to do paperwork. The company is now one of the leading exporters of red tape. If they had but slowed down a little, they would have finished considerably more quickly.

Another common symptom of moving too fast is feeling like you’ve spent the day on a treadmill: you’re exhausted but it feels like nothing really got accomplished. Items on the to-do list never seem to go away or items that are crossed off keep coming back a few days or weeks later. When problems that were thought solved keep reappearing, that tells you that you need to slow down and put more time into understanding what’s going and devising more robust solutions. Unfortunately, when you’re feeling rushed, a quick solution feels good and creates a temporary oasis of calm. That feeling can be addicting: at one software company, one department developed the habit of simply marking any bugs that had been around for a while as fixed. They knew that it would sometimes take at least two or three weeks before the bugs could be verified. Maybe they’d go away. Maybe they would no longer be relevant. Maybe there’d be more time later to actually look at them. Sure, they almost always came back, but so what? They bought themselves time to relax, and managed to make themselves look good because their bug count was always low. The actual problems with the product, on the other hand, were never addressed.

If you want to move fast, you first have to learn to move with precision. That means starting slowly and learning how to be in the right place at the right time. Otherwise, you spend all your time and energy rushing about overshooting your target and fixing your mistakes.

The Final Frontier

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

 

“Space, the final frontier.”

–          Captain James T. Kirk

 

To be fair, Captain Kirk was talking about a different kind of space than what concerns us here. It may seem a little odd that a book on organizational psychology would be concerned with space; fundamentally, however, we are creatures of our environment. We respond to what is around us and how we perceive the space we are in can affect our moods, our creativity, even our perceptions that our team is worth our time. How people feel about the space they are in can influence whether or not they believe a leader is authentic!

Imagine that you are going to rent an office: you approach the building and see peeling paint and dead trees outside. How does that shape your impression of the building? What will your clients think when they see it? What if you were going to visit a doctor whose office was in that building? Perhaps you’re already beginning to have doubts. Sure, she has great recommendations, but could someone competent really work out of a building like that? Of course, once you step inside you might find a brightly lit, professional office, but first you have to get that far.

Well known psychologist Martin Seligman once observed that as the chair of the psychology department at the University of Pennsylvania, he interviewed many people who went on to become quite famous in the field of psychology… somewhere else. Why were none of the candidates accepted? Reviewing the applications, he and the rest of the faculty found something wrong with each candidate and consistently felt that their strengths just weren’t strong enough. Eventually, Seligman noticed that they were holding all their candidate reviews in a gray, windowless, conference room. When he tried holding the meetings in a brightly lit, colorful space, suddenly the candidates’ flaws didn’t seem so bad and their strengths were considerably more obvious.

Our moods and our environment feed off one another. It’s hard to be discouraged on a bright, summer day, and hard to be excited when it’s cold and gray outside. Similarly, when our work environment is gray or boring, we tend to be less trusting, less creative, less open to new ideas, and less cooperative. We spend more of our mental energy just trying to be vaguely cheerful, and less on actually getting the work done. Conversely, when we are in open, brightly lit spaces, we tend to be more willing to trust and cooperate with others, happier, more energetic, more creative, and considerably more open to new ideas and experiences. If successful innovation and brainstorming requires that we suspend disbelief and open ourselves to off-the-wall ideas – and that is exactly what they do require – then we need to construct our environment to encourage that mindset.

“…[Organizational Psychology for Managers] should be required reading in MBA programs, military leadership courses, and needs to be on the bookshelf of every Fortune 1000 VP of Human Resources.  Steve Balzac is the 21st century’s Tom Peters.”

– Stephen R Guendert, PhD, CMG Director of Publications

What is time?

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

Perhaps the best definition of time is that it is nature’s way of keeping everything from happening at once. Unfortunately, that doesn’t stop us from trying to do everything at once! Even more unfortunately, this approach triggers that feeling of being rushed and reduces our ability to get things done. It helps, therefore, to view time as a framework within which we organize our tasks and plan out how to accomplish our goals. This means adopting more of an event-based view of time rather than the clock-based (or duration-based) view most of us are accustomed to. In this context, a schedule is a way of organizing and viewing time such that people and resources are in the right places at the right times and flowing from event to event.

What is an event-based view of time?

We are accustomed to scheduling ourselves based on the clock:

7:45 pre-meeting meeting
8:00am Project planning meeting
9:00 am Customer meeting
11:30-12:30 –Lunch
12:30 – 2:00 Work on presentation
2:00 – 4:00 Brainstorming meeting

And so forth through the day and week. We learned this in school and we do it at work. The problem, though, is that a lot of work needs to be done in ways that don’t always lend themselves to such precise structures and many activities are not always totally one hundred percent precise in their start and stop times. When you have to coordinate a great many people and resources, you need to have a more precise, structured approach to time: colleges, for example, have to manage student schedules, room utilization, professor availability, etc. But that structure comes with a lot of overhead, and is not always all that useful. While we don’t want to completely eliminate structured time, we also don’t want to be totally controlled by it.

A recent article in the NY Times discussed joint military training between the United States and Japan. When asked what the most difficult part of the training was, the Japanese commander commented that he was initally put off by the fact that the US Marines did not have a set schedule. Japanese military exercises are conducted with, “the precision of a Tokyo subway.” Eventually, the Japanese commander realized that the American troops had learned through real combat experience that things do not always, or often, go according to plan. Flexibility is essential. Rigidity leads to defeat.

Master of Time and Space

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

Where oh where has my little week gone, where oh where has it gone?

It’s Thursday afternoon and that big project is due at 5pm. There’s no way you can finish it in the time you have available. No problem, you can just go to the time bank. All your life, people have been telling you that it’s important to save time. Well, just like you’ve put away money for a rainy day, you’ve saved quite a lot of time. Now you just need to withdraw some of that time and use it to finish the project.

What do you mean that didn’t work? When you save time, shouldn’t you be able to withdraw it when you need it? Unfortunately, that trick never works. Even Doctor Who, the main character of the popular British science-fiction series about a wandering Time Lord, can’t manage that one. That’s the problem with time: no matter how much we save, it’s never there when we go to make a withdrawal. We all get sixty seconds to a minute, sixty minutes to the hour, and 24 hours in a day. Time passes whether we use it or abuse it. The only choice we have is how we use the time, not whether we use it.

We have so many gadgets now for measuring time: clocks, watches, iPhones, the list goes on and on. But measuring time is not experiencing time: we have thermometers that tell us what the temperature is, but whether we feel warm or cold can depend on many factors other than just the number on that thermometer. 45 degrees in January can feel downright warm, and 55 in July might seem blessedly cool. Time is similar. Our experience of time passing is very different from what the measurement of time might tell us; this is why productivity and time are not the same! While we might measure time by the ticks of a clock or the dropping of grains of sand through an hourglass, we experience time as a series of events. When we have nothing to occupy our brains, time seems to stretch endlessly, each second ticking by with the excrutiating slowness of an overwritten sentence. Watching paint dry is so painful exactly because nothing much is happening. Conversely, when we are engaged in something that fills our brains, time seems to race by. When we look back, though, on a day filled with activity, it often seems like a very long time must have passed. Two people can experience the passage of time in the same situation very differently. Some athletes will view their opponents as moving very rapidly, while other athletes, who trained to manage their perceptions in ways that change their sense of time, will see their opponents apparently moving in slow motion. The second are far more likely to win.

What it boils down to is that we do not experience time or perceive time by the passage of seconds on our watches. We perceive time through the passage of external events: day and night, the waxing and waning of the moon, the changing of the seasons, and so forth. Those who have spent time in a windowless conference room or office may have noticed that feeling of disorientation that occurs when you step out at the end of the day and realize just how much time has passed: working for IBM in the late 1980s, in the winter months I would often arrive at the office before it was light and leave after dark. Spending the day in a windowless office meant that by the end of the day, I felt extremely confused about what time it actually was. Spending the day in an office dealing with a constant barrage of interrupts produces a similar disorienting effect.

At the same time, as it were, how we feel about time can change our perceptions of the world around us. In one classic experiment, divinity students about to give a talk on the Good Samaritan had their sense of time manipulated: while still in their dorm rooms, some of the students received a phone call stating, “Where are you? You were supposed to be in the chapel five minutes ago!” Other students received a phone call stating, “Although we have plenty of time, we’d like everyone in the chapel a few minutes early.”
On the route between the dorm and the chapel was an apparently sick or injured person. Those divinity students who thought they were late went by that person, in many cases without even noticing him lying there. Those who did notice assumed that someone else would take care of it or figured that maybe the person wasn’t that sick, or something. Conversely, those divinity students who thought they had plenty of time were far more likely to notice the sick person and take appropriate action. Feeling rushed reduces our ability to see the world.

Just as our perceptions of time influence our behavior and how effectively we work, pursue goals, and interact with others, the physical space we are in matters as well. Space creates associations and triggers for our behavior; the right space can make us feel safe or in danger, critical or creative. The same space at different times can also trigger different reactions. Fundamentally, we humans are creatures of our environment. We can’t completely ignore our surroundings when looking at organizational psychology and behavior. Rather, we need to understand how space matters and how our interactions with the space around us can serve to reinforce or undermine our organizational culture, narrative, learning, motivation, perceptions of fairness and justice, and goal setting. Even our perceptions of leadership can be affected by how space and time are handled.

Do your best…

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

 

I often hear the argument made that the effort involved in effective goal setting is really unnecessary so long as people just “do their best.”

The problem with “do your best” is that “your best” is an arbitrary term. There is no real way to measure it or even know when you’ve arrived. Each person has their own view of what “best” means. Thus, I’ve often heard managers telling employees, “You call this your best work? This is terrible!” Of course, this “feedback” is of absolutely no value as it fails to provide the person with any information that she can use to change or improve her work. Conversely, I’ve also seen many an engineer respond to a deadline by saying to their increasingly frustrated managers, “But it’s not done yet. It could be better!”

For an organization, “do your best” lacks any coherent focus or vision. It produces muddied priorities instead of a common objective. Common goals help bring teams together and provide a means to adjust course when something doesn’t work as expected; “do your best” is more likely to produce argument and blame when the team runs into an unexpected problem. In a “do your best” environment, clearly failure is the result of someone not “doing their best!” Everyone should just “try harder!” This is a sure recipe for overwork, exhaustion, burnout, and low productivity. Of course, since everyone is busy running around in circles frantically trying to “try harder” and “do their best,” it looks like a lot is getting done: remember that motion does not equal progress. Accomplishing goals equals progress.

The whole point of goals is that they give us a way to decompose a task into logical pieces, organize those pieces, and attack them in a systematic fashion. Goals provide us feedback so that we know how far we’ve come, how much is left to do, and when we’ve arrived at our destination. “Do your best” does none of these things. Overall, people, and businesses, with clear goals out-perform those who are simply attempting to do their best roughly 99.9% of the time. But, since autonomy is an important motivating factor, you should feel free to bet against those odds if you really want to.

Goal decomposition

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

 

I’ve mentioned several times the concept of creating subgoals and how large goals generate a great many smaller goals. This process is known as goal decomposition. Goal decomposition is critical if we’re going to accomplish anything large or significant: a black belt in a martial art, a college degree, shipping a product, building an innovative organization, or implementing successful organizational change, are all large goals that must be broken down into pieces in order to have any reasonable chances of success.

When breaking goals down, it helps considerably to start at the end and work backward to the starting point, rather than work forward from the starting point to where you want to go. Working backward, a technique known as reverse goal chaining, does two things:

First, working backward creates implicit agreement for each step. As you define a step, it’s clear how that step moves you forward; after all, you just stepped backward to define the step! If you can’t see how to move forward from a given step, that alerts you that you’re taking too big a step. You can address that issue immediately, or at least put in a goal that when you get to point X you need to evaluate how to move to point Y. Because you are working backward, the logical progression is easier to see and there is less debate about whether that step will get you where you want to go. Instead, the implicit agreement that you’re building makes it easier to generate overall agreement to the entire goal chain; this is extremely valuable when you need to convince your team to buy in to the goals! People are more likely to listen with an open mind instead of arguing the validity of each step in the process.

Second, reverse goal chaining is a very elegant way to transform your goals into a well thought-out strategy for accomplishing those goals. Strategy is, in a very real sense, the art of looking to your end point and then reasoning backward. As you work your way backward, insetad of fighting over the validity of the step, you can instead consider how each step influences or changes the world around you and how those affected by your actions might respond. In what way might a competitor react to your actions? How can you anticipate and prevent that? A chess master builds his strategy often at an almost unconscious level, but they do work backward. They are then playing toward various board positions that they know will move them to victory. Intervening board positions are the subgoals along the way to the final board position. At the same time, the other player is seeing and responding to each move, potentially forcing the strategy to evolve and adjust. Fencers do the same thing, leading their opponents into patterns of moves so that the opponent becomes predictable. Smart businesses try to force their competitors into untenable positions as well.

As you work your goals backward, you also need to address the question of close and distant deadlines. Technically speaking, we are looking at Proximal Goals and Distal Goals.

Proximal goals are the goals that are right in front of us. Those are the goals we are doing today.

Distal goals are further off in time. Those are the goals we are working toward tomorrow.

Proximal goals build upon one another to bring us to our more distal goals. At any given moment, our proximal goals tend to be the most relevant since, after all, they have the most immediate deadlines. Sometimes, though, a proximal goal is just not that interesting or personally relevant by itself. In that case, our distal goals help remind us of the importance of those proximal goals: the proximal goal of practicing falling feeds the more distal goal of learning to throw, which feeds the goal of passing a belt test, which feeds the goal of learning the next set of techniques toward the ultimate goal of a black belt. Even a student who doesn’t much care to practice falls will still do so if they value that end point sufficiently. Because the path to the end point is broken down and visible, it’s easier to imagine achieving it.

When a business tells me that their employees have no sense of urgency, one of the first things I look at is how they’ve broken down their goals: are milestones all big and distant? Quite frequently, the problem is that the goals, and rewards, are all distal and there are no proximal goals to get people started.

 

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

 

What are goals?

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

 

We talk about goals a great deal. Every January I receive numerous articles touting the benefits of setting goals, and assuring me that if I just set goals then everything will magically work out Just Fine ™. I’ve lost track of the number of times I’ve walked into a company and asked people, “What are your goals?” only to receive blank looks in return. Occasionally, I’m told that the goal is to make money. At least they have an answer; it’s not a very good answer, but it’s a starting point for discussion.

Let’s start by recognizing that making money is not a goal. It’s not even an outcome. Making money is a form of feedback: it’s one of several measures that can tell you if your strategies are working and your company is producing valuable goods or services. Focusing on the measurement instead of on the goals and approaches that enable you to make money leads to poor strategy and short-term optimization at the expense of long-term growth. That’s not to say that making money isn’t important: for many organizations and individuals it is a vital component of continuing to do what you want to be doing. It’s merely not the overall goal and, as we’ve already discussed, it’s also a terrible way to produce long-term motivation.

What about those New Year’s resolutions that everyone talks about at the beginning of the year? Sadly, those are not goals either. They are, at best, good intentions. The problem is, an intention is not a goal; an intention is a statement of desire or a wish or a dream, but it is not a goal. As we will discuss later in this chapter, intentions can be used to help execute goals, but they are not goals. Intentions are too vague, too hard to measure, and too lacking in structure to be effective goals.

Rather, we need to think about goals as a combination of desired outcomes, processes or strategies to achieve those outcomes, and learning and discovery. Indeed, like Gaul, goals can be divided into three types:

  • Outcome goals – these are our desired results.
  • Process goals – goals set to produce behaviors that will lead us to our desired outcomes.
  • Learning goals – developing new skills and obtaining new information to help us with our process, outcome, and learning goals.

Let’s look at each of these goals in more depth.

The Efficient Light Bulb: A Productivity Fable

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

 

Once upon a time, there was a light bulb. This light bulb was quite a remarkable light bulb: it was praised far and wide for its incredible efficiency. This light bulb gave off no waste heat. This light bulb did not contribute to global warming. It had no carbon footprint.  It did not rely on fossil fuels. Truly, it was an amazing light bulb and visitors came every day to see this remarkable light bulb.

One day, though, a traveler coming to see the light bulb in action was delayed by an unfortunate flood that closed several roads. He did not arrive until well after night had fallen. Much to his surprise, he found the light bulb sitting in a pitch dark room.

“Why aren’t you giving light?” asked the traveler.

“Give light!” replied the light bulb in shocked tones. “You must be joking. If I did that, I would use fossil fuels. I would have a carbon footprint. I would give off waste heat. I would no longer be efficient.”

“But isn’t the purpose of a light bulb to give light?” asked the traveler.

“I’ve always been told to be efficient,” replied the light bulb with a shrug. If you have never seen a light bulb shrug, it is truly a wonder to behold. The traveler would have been amazed, except, of course, that the room was too dark for him to see the miraculous event.

Once upon a time, there was a software company named “Soak, Inc.” Soak’s product relied upon a very complex database server. One day, the VP of Engineering stormed into the office and declared, “The server is too slow. We need to speed it up.”

From that day forth, every effort was focused on improving the speed of the server. Other issues were deemed insignificant beside the one, critical, goal of performance. Engineers who dared to raise other issues were publically humiliated for wasting the company’s time. Bugs that did not relate to performance issues were deemed “optional.” People who spent time reviewing the optional bugs and trying to fix them were warned that their insubordination would cost them their jobs if it did not cease immediately.

Eventually, Soak developed an amazingly efficient server. It was fast. It was robust. It was ready to demonstrate to potential clients.

The demo started out remarkably well. The server did not crash, causing some to believe that this couldn’t actually be a demonstration of a software product. Indeed, the server performed flawlessly. All would have gone well indeed for Soak had not someone noticed that the data being delivered by the server didn’t make sense. Yes, what the server had gained in performance it had lost in accuracy. In other words, it was incredibly good at very rapidly delivering useless or incorrect information.

When the engineers were questioned about this unfortunate oversight, they shrugged and replied, “We were told to be efficient.”

While it is not nearly as amazing to see an engineer shrug as it is to see a light bulb shrug, the effects are much the same.

At Soak, a goal was set, a metric for success was defined, and that metric became the sole determinant of progress. Goals are extremely powerful tools: the best thing about them is that you accomplish them. Unfortunately, sometimes the worst thing about goals is that you accomplish them. At Soak, they accomplished their goals. A dead light bulb is extremely efficient, but not useful. Similar observations can be made about the server.

Before leaping into setting a goal, especially a goal to solve a problem, it helps to understand the actual problem and to understand what the actual symptoms are. Rather than create useful goals, they fixated on a symptom. That did not, however, actually change anything.

At Soak , the VP stated that they were trying to solve the problems his company was facing as rapidly and effectively as possible. They were setting goals. They were Taking Action! Taking action is certainly helpful, but it is even more helpful to be taking the correct action. Since it’s not always possible to determine just what the correct action is, it becomes even more critical to listen to the feedback and questions from the people who are charged with actually executing the action. The engineers knew that something was wrong, but no one was willing to listen to them. As we will discuss shortly, a key aspect of successful goal setting is understanding the feedback you’re getting.

I realize that many of you reading this are probably chuckling to yourselves and thinking that this scenario could never happen at your companies. The folks at Soak said the same before, during, and even after it happened to them. The light bulb had no comment.

Productivity seems like such a simple thing. Somehow, though, it never is. As we have already discussed, cognitive shortcuts such as the Halo Effect can influence how productive we perceive someone to be. Ultimately, the only real way to measure productivity is through understanding goals and knowing how to construct goals so that they will actually get you what you want. Otherwise, you may just end up with a dead light bulb.

 

After it was released, Organizational Psychology for Managers sold out in two days at Amazon.com. Order your copy now.

 

Goal Apocalypse

It’s a new year. That means two things: one, the world didn’t end in the so-called “Mayan Apocalypse” of 21 December 2012; and two, since the world didn’t end it’s time to figure out some resolutions for the New Year. Perhaps a good one is not worrying about Mayan Apocalypses or Aztec Apocalypses or whatever the next apocryphal apocalypse might happen to be! At least that one has a chance of being kept.

Of course, as we all know the problem with New Year’s resolutions is that they never last long anyway; indeed, in most cases a New Year’s resolution has about as much likelihood of coming true as the latest predicted Apocalypse. Even when we move from the realm of resolutions, which tend to be fairly vague, to the more specific area of goals, we don’t see a significantly greater success rate.

Why not?

The major problem most people have with setting goals is that they don’t take the time to really think through what they want to accomplish. They fall back on the SMART (Specific, Measurable, Achievable, Relevant, Time-bound) formula, and then wonder why it didn’t work. While the formula is a good mnemonic, the mnemonic doesn’t really tell you how to use it.

The trick is to start at the end: what are you *really* trying to accomplish? When someone says they want to “get in shape,” do they mean run 2 miles? A marathon? Bicycle? Play tennis? Lose weight? When a business says it wants to ship a product, again, what is the outcome they are seeking? Who will buy it? Why would they want it?

It’s important, therefore, to describe how the world will be different if you accomplish your goal. By fleshing out that description, you can then identify which pieces you can control and which ones you can’t. You can write a novel, but you can’t force any given publisher to accept it. However, you can engage in behaviors that will make it more likely (researching appropriate publishing houses, investigating agents, getting advice from published authors, researching the steps to get a novel published in the first place!, etc). This will develop into your strategy: a series of steps that move you toward your goal. Those strategic steps will often turn into smaller goals along the way. That’s great: it helps you manage and track your progress.

The time element comes in when you start planning how and when you will execute the steps. You can also define trigger conditions that will cue you to work on your goal: “on Monday after I finish my coffee I will…”

Don’t try to keep all your goal directed behavior in your head: calendar entries, checklists, etc, are all good tools for keeping track of what you should be doing when. Indeed, just the act of writing out your goals at the start of the year can help you focus on them. Silly as it sounds, we tend to not believe ourselves if we don’t write down the goals. The act of writing is what moves us from dreaming to doing. While the complexity and number of people involved will vary depending on whether you are writing out an individual or a business goal, the process is fundamentally the same.

It’s important, by the way, to not set too many goals. If you overload yourself with goals, you will fragment your attention, and that may well make it hard to focus on work or make you short-tempered: you’re using your brain power to manage all your goals and have nothing left to resist the urge to snap at that irritating co-worker. 3-4 large scale goals are usually as much as you want: remember that the process of designing your goal strategy means that a few big goals can generate a lot of little goals!

The challenge is thinking big and simultaneously being realistic about the commitments on your time and energy. The best goals strike a balance between the two.

 

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.” Steve’s latest book, “Organizational Psychology for Managers,” is due out from Springer in 2013. 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