Take Two Aspirin

As we all know, when we have a cough, the best thing to do is to visit a Cough Doctor. When we have a fever, we visit a Fever Doctor. Also, when our car is making a funny knocking noise in the key of C, we take the car to a mechanic who specializes in funny knocking noises in the key of C. Or maybe we just hope the problem will go away because the only mechanics we know deal with knocking noises in the key of B.

Okay, so maybe this is a bit of an exaggeration. We don’t actually look for Cough Doctors or Fever Doctors and I very much doubt that anyone outside Car Talk would ask if the knocking noise is in the key of C. When we go to the doctor because of a cough or a fever, we go because the doctor understands, or can figure out, why we have that cough or fever. When we take the car to the mechanic because of that weird knocking noise, it’s because we’re hoping that the mechanic can figure out why that noise is happening and what it means. We go to the doctor or the mechanic because of our symptoms, but we don’t go to Symptom Doctors. To be fair, Symptom Doctors are great when all we have is a cold: take two aspirin and call me in the morning.

The fact is, treating symptoms can make us feel a lot better. Having a fever isn’t much fun, and a couple of aspirin can work wonders. Of course, if that fever is because we have the flu, then maybe suppressing it isn’t the best thing to do. That knocking noise from the left rear wheel can be easily tuned out by simply playing the radio loudly enough. Then we don’t have to worry about it until the wheel comes off. Hopefully, this happens while we’re at the gas station and not when we’re traveling at 65 mph on the freeway. Treating symptoms doesn’t make the underlying cause go away, it just lets us feel good. Therein lies the problem.

The symptoms we see are only that: the symptoms. That cough and fever might be a mild cold or it might be the flu. That knocking noise might be nothing or it might be a wheel getting ready to declare its independence from the collective body that is your car. When it comes to fevers and coughs, we can usually tell what’s going on and most of the time the consequences of being wrong are only inconvenient or a bit uncomfortable. With cars, most of us are not quite so good at figuring out what the noise means, while a trained mechanic can do it in minutes or seconds. Not only do they know what it means, they also know the cause, and which parts of the car are affected. The symptoms enable them to identify the problem, and by treating the problem, they also make the symptoms go away. The converse, as we’ve discussed, is not true.

So why would anyone call a Symptom Doctor? Well, just treating the symptoms makes us feel like we’re accomplishing something. We feel better for a brief time. Most important of all, we feel successful. When the symptoms return, we just want them to go away again and we want to feel successful again. So we call the Symptom Doctor back and once again the symptoms go away for a brief period.

In one situation, a certain engineering manager had a team that was always argumentative to the point of being unable to reach agreement on anything. After carefully observing the situation, he decided the problem was that Joe disagreed with everyone too much. Joe had a “difficult personality” and hence was the cause of team’s problems. He fired Joe. Lo and behold, everyone stopped arguing. The manager was very proud of himself for solving the problem. Four months later, a different member of the team had revealed herself to have a “difficult personality.” That’s right, the arguments and lack of agreement had returned in force. Firing Joe hadn’t solved anything; it had simply made the symptoms disappear for a short time. When they reappeared, they were worse than before.

Now, in this particular example, the manager was his own Symptom Doctor. Symptom Doctors can also be brought in from outside: companies hire “Decision Consultants,” or “Consultants For Leaders Who Don’t Listen,” or “Consultants For Leaders Who Listen Too Much,” or “Consultants For Leaders Who Listen With Their Head Cocked At A Funny Angle.” Okay, maybe the last one is a joke. The results of going to a Symptom Doctor, however, are rarely a joke. They are wasted time, wasted energy, and lost resources.

So what do you do instead? Like going to the doctor or the mechanic, you need someone who can understand what is going on. Not a Symptom Doctor, but someone who either knows, or can figure out, what the symptoms mean. It may not be as cheap or as easy as going to a Symptom Doctor, but, unlike the Symptom Doctor, it just might solve your problem.

Fatal Deadlines

“It ships on Monday!”

“We have a deadline to meet!”

“Why did you even set a deadline if you’re going to change it?”

Deadlines. They matter until they don’t. They are far away until suddenly they are right on top of us. Sometimes a deadline is sacrosanct, unchangeable no matter the situation or the quality of the product: one technology CEO I knew released his products on the day he promised them and nothing would change his mind. It was a point of pride for him to always release on schedule. His customers, however, were equally adamant that they wished it would be a point of pride for him to release products that worked. Yes, this particular CEO would release a non-functional product on the chosen date and then deal with fixing it in the field rather than slip the date and deal with the problems. Eventually, the customers won: they went to a competitor.

Other times, deadlines seem to be almost mystical talismans: setting a deadline will magically cause a product to be ready by that date. In one rather dramatic example from early in my career in high tech, the CEO turned to the head of engineering and asked him when the product would be ready.

“September 1st, best case scenario,” was the curt reply.

The CEO nodded, picked up the phone, and said, “We’ll have it ready by July 15th.”

The head of engineering did a very credible job of not exploding.

When July 15th rolled around, the product was not ready. The CEO was shocked. His reaction was, “I set a deadline!”

Sometimes a deadline can spur people to dramatic action. Sometimes it can’t. It’s important to know which situation is which. When I was managing a team, I was once asked why I even bothered to set deadlines if I would then change them. The short answer was that it was because the only deadline that actually mattered was the one at the end, and that one we consistently managed to hit. How?

At the most basic level, deadlines are merely tools. They are powerful tools, but tools nonetheless. As will all power tools, it’s important to know how to use them properly, lest your deadline prove fatal to your success.

At the beginning of any non-routine, non-trivial project, deadlines are basically little more than wishful thinking. Early deadlines exist to give you feedback: how well is your team working? How difficult is this project turning out to be? Will we be able to marshal the resources we need at the times we need them? Are we being aggressive enough? Are we being too aggressive? That feedback provides your roadmap moving forward. Therefore, start with small deadlines: don’t rush forward in giant leaps which give you little information.

Whether you make those initial deadlines or miss them, the key is to be strategic: why did you make them? Why did you miss them? What are you learning about your team and your project? Early stage deadlines can be easily shifted and adjusted as needed, provided you don’t lose sight of the feedback they are generating. Done right, the more flexible your early deadlines, the easier it is to hit your later ones. When you do miss a deadline, recalibrate! Don’t just pile the extra work onto the next deadline; that only triggers a series of failed deadlines, which reduces productivity. Success is not how fast you can move, it’s how smoothly you can accelerate.

As the project continues, you’ll find that your ability to set useful, doable, aggressive deadlines will increase. You want your deadlines aggressive enough to excite and challenge your team, not so aggressive that people look and tell themselves that there’s no point in trying. The secret to maintaining that excitement is simple: strive for deadlines that can be beaten with serious, but not unsustainable, effort. Beating deadlines increases excitement and builds a sense of success. Failing to meet deadlines has just the opposite effect. Quite simply, when people are ahead of schedule, they work harder, are more creative and innovative, and are better at problem solving.

Many a race ends with a final sprint across the finish line. How well you’ve managed the deadlines to that point will determine how hard the sprint is, and how much fuel your team has in its tank when you get there. If the team is exhausted and burned out, your deadline will likely prove fatal to your plans. On the other hand, if the team is excited and energized, they’ll blast through that final deadline.

Effective problem solving

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

 

One of the things that world class successful organizations, the organizations that keep innovating and growing and reinventing themselves, have in common is a remarkably effective ability to solve problems. What is interesting, however, is that they don’t necessarily get it right the first the time; often, perhaps, but not always. What they are extremely good at is knowing how to solve problems in ways that constantly reinforce their cultural beliefs of optimism and success.

To begin with, problem solving is really a question of goal setting. In this case, it is a goal where the outcome is to make the problem go away. Unfortunately, that’s not really enough information to create a specific goal, although plenty of businesses try. There are, however, many ways to make a problem go away at least temporarily. Hence, if that’s all you focus on, you end up with a problem that feels like a boomerang in a Saturday morning cartoon: it keeps coming back and whacking you upside the head. Thus, we need to do a bit more work in order to formulate effective goals around solving our problem.

Before we can solve a problem there is one thing we absolutely have to know. What might that be? Whether I ask this of college students or managers, I always get the same response: puzzled looks and then people start yelling out answers such as, “the solution,” or “the cost of the problem,” or “what resources we need,” or a host of other answers. Eventually somebody says, “Don’t we have to know what the problem is?”

Exactly. Before you can find a solution, you have to identify the problem. As obvious as this may sound, if you don’t know the actual problem, then your solution isn’t likely to fix it. There are a great many solutions out there looking for problems.

A problem can be broken down into three major pieces: there is the actual problem, whatever that may be. We don’t know what the problem is because we can’t actually see it; what we can see are the effects of the problem. That may mean deadlines being missed or angry customers calling to complain or a lack of motivation or difficulty hiring or retaining talent, or countless other things. Those are the symptoms of the problem. Finally, there are the things that occur around the problem, things which attract our attention but which are basically irrelevant to the situation. They look important but they’re not. That’s known as chrome: the shiny stuff that draws our eye and distracts us from what really matters.

 

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

Understanding Hierarchy

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

While I was writing this, I was asked the question, “How important is hierarchy on a team? I’ve been told it’s a problem. I’m responsible for 160 people, and I don’t know what I’d do without a hierarchy.”

Hierarchy is a tool. Whether it works for you or against you depends on how well you understand your tool and the situation in which you are using it. For my friend who has to manage 160 people, some sort of hierarchy is essential: without it, he’d swiftly be overwhelmed.

Hierarchy is a way of organizing and structuring a system. In a typical martial arts school, the hierarchy of belts provides each student a quick visual assessment of who knows what. This can make it easier for students to ask questions or know whom to imitate: learning is enhanced when we can imitate someone we see as similar to us. That person who is one belt ahead is easier to see as “like me” than the person who is many years and belts advanced. The hierarchy also provides visual feedback of the student’s progress, a key component of maintaining motivation.

One of the key roles of the military ranking system is providing a method of coordinating precision operations. It does this by, amongst other things, providing clear rules for whom to listen to and under what circumstances and managing transitions of power should a leader be abruptly removed or cut off from the team. Like the belt system in martial arts, it also provides visual feedback of progress.

In a large organization, hierarchy provides a structured way to know where you are in your career, an easy way to identify nominal skill levels, and a means of coordinating different business activities.

However, when hierarchies become inflexible or bureaucratic, they can easily turn into obstacles. Small companies that attempt to impose rigid, large company hierarchies are asking for trouble: they don’t need the overhead and lack of flexibility that hierarchies can create. A small business’s biggest strength is that it can shift course quickly. A large company, on the other hand, is slower to change but has more resources. It is silly and counterproductive for a small business to impose large company hierarchy and thereby give up its flexibility when it doesn’t have the resources to take advantage of that hierarchy.

Even in larger organizations, the structure needs to be flexible enough to permit good information flow up and down the hierarchy. Too rigid an adherence to hierarchy will reduce productivity and motivation and stifle innovation.

Hierarchy needs to be built out carefully, in accordance with the narrative, goals, and needs of the organization. Make sure you clearly identify what each level of the hierarchy means and how people move up. Periodically review your hierarchical structure and make sure it is still serving you, and not the other way around.

Problem Solving and Mistakes

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

Teams that don’t work when the manager isn’t around are legion. It’s a common problem, and common wisdom suggests that the team members lack motivation or are trying to goof off: when the cat’s away, and all that.

Common wisdom may sound good, but is often wrong. This is no exception.

Groups can get stuck when the leader becomes the chief problem solver. While it may seem efficient for a leader who is also an expert in the domain to quickly solve problems and instruct the team on what to do, this approach again has the drawback of not enabling the team to develop the necessary skills and confidence in those skills. If the team doesn’t think it can do the job, or isn’t willing to try, then it doesn’t matter how skillful they are at decision making and it doesn’t matter how clear the goals are. It’ll merely be that much clearer to them that they cannot do it. It may be necessary for leaders to walk through the problem solving process in front of their team and it will certainly be necessary for leaders to moderate the process.

Basically, teams need to solve problems as a team. This includes making the inevitable mistakes along the way. It is the act of making mistakes, learning from the experience, and moving on that enables the team to truly develop not just confidence in its skills but resilience as well. Without that experience, team confidence is brittle and team members considerably less willing to explore innovative solutions to problems. The broader organization’s cultural attitudes towards mistakes is going to play a significant role here.

Team Development — Stage 1

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

Imagine that first day on a new job working with a group of strangers: there you are, staring at your partners, wondering what to do. You don’t want to admit that you don’t know; after all, perhaps you’re in this group by accident. Sure, they said that the selection process was careful, but they must have made a mistake in your case. If anyone realizes just how little you know, they’ll surely ask you to leave!

The good news is that everyone else feels the same way!

If you’re lucky, a manager or team leader has already been assigned. They’ll clear up your confusion and get things going. If there is no formally appointed manager or leader, however, that can be a problem. It is truly amazing how long it can take to get nothing done. Often enough, though, the mounting pressure of an impending deadline will force someone to take charge or perhaps simply do the project themselves. The latter case, in particular, tends to trigger more than a little resentment!

The dominant characteristics of stage one groups are dependency and inclusion. Members are primarily concerned with their place in the group; the greatest fear is banishment. Consider that exile from the community was, for much of history, seen as a fate worse than death. Indeed, even today with all our technology, survival completely apart from the group which is civilization is extremely difficult!

Thus, members of stage one groups have a very strong focus on appearing competent. Making a mistake is perceived to be tantamount to risking membership in the group. Unfortunately, with many of the companies I work with, that is also the reality (that’s why I’m working with them! It’s not easy to change.). As a result, members are afraid to take risks or admit to mistakes, preventing effective error correction from taking place. The unwillingness to make mistakes or appear less than competent also means that members will often fail to ask questions, leading to confusion about objectives, and are unwilling to accept help lest that be seen as a sign of weakness.

Another characteristic of stage one groups is that the group does not know how its skills match up with the task at hand. Indeed, in a very real sense, the group does not know what its skills are as a group. It takes time and exploration for the group to discover their strengths and weaknesses and how they can support one another to maximize their strengths. There’s a reason the Red Sox have Spring Training, and even then they sometimes never get it together.

Communications in the group will tend to be polite, distant, sometimes appearing formal, or at least extremely careful, in nature. Because group members do not really know how they stand with one another, no one wants to offend anyone else. Conflict is seen as disruptive to the harmony of the group, proof that members are not committed or loyal. There is a great deal of “go along to get along” taking place.

It’s been argued, granted somewhat sarcastically, that to know oneself is the ultimate form of Freudian aggression. By contrast, in a group, the person most people wish they could work with is themselves. Since that’s not actually possible, similarity is the next best thing.

Groups seek common ground. This commonality may be physical, stemming from gender, skin color, size, etc. It may be based on background, nationality, education, or culture. The more diverse the group, the more likely the group will demand conformity as a way of building similarity. The conformity may be based around dress, time spent at the office, where and when to eat lunch, or buying in to some particular ideology. IBM’s blue suit and tie dress code was part of the effort to create similarity in the company and became a cultural icon; a political party’s efforts to require all members to buy into a particular orthodoxy is another way of building similarity. Conformity can also be based around dislike of an outside group or a member of the group who does not buy into the group’s values. Stage one groups are quick to punish such deviants, initially with the goal of bringing them back into the fold. Should that fail, they are usually shunned or exiled. Conformity works best when it focuses on issues that actually help the group get the job done. When conformity focuses on trivial or irritating topics such as requiring everyone to eat lunch together or always show up at the same time, it tends to stifle creativity and individual expression. This causes resentment and reduces group performance.

A strong leader can often be enough to provide the focal point, or at least a focal point, of similarity for the group. Members are usually extremely loyal to the leader, and will rarely question his judgment. When there are questions, they are usually relatively polite and restrained, at least as defined by the cultural norms of the organization. Think of the image of the 1950s manager who takes care of his employees and to whom the employees will go with work or personal problems.

Lacking a strong leader, the group may not coalesce at all. If the group does coalesce, it is often around something trivial or inappropriate: a particular style of dress, eating lunch at a certain restaurant, or in opposition to the schedule, mannerisms, or style of a particular team member. These early attempts at similarity actually produce conformity. Some conformity is necessary for the group to function; too much is stifling. Lacking leadership, the group will not be productive until a leader emerges. As distressing as this fact is for many people, leaderless groups simply don’t function.

The more diverse the group, the greater the need for conformity: the less the members appear to have in common, the more they need to create common ground. On the flip side, the higher the intelligence and self-esteem of the members, the more they resist conformity. As you might imagine, a diverse group of highly intelligent, competent, confident individuals is going to be struggling with two opposing psychological imperatives. Skillful leadership is particularly important here!

Team Development or Growing Wheat in Siberia

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

Once upon a time, the late and unlamented Soviet Union decided to grow wheat in Siberia. Their logic was simple: by growing wheat in the inhospitable conditions of Siberia, the wheat would become stronger. The wheat, however, was indifferent to Soviet philosophy. Despite speeches, threats, and promises from the government, the wheat stubbornly refused to grow.

In 1990s, a group of Nobel Prize winning economists developed some very interesting theories about how the financial markets should work. Their theories were brilliant and attracted billions in investment dollars into the hedge fund they created. Long-term Capital Management almost took down the entire US economy when it collapsed in the summer of 1998.

In both cases, a belief about how the world should work was trumped by the way the world does work.

To bring this a little closer to home, I worked with one high technology company that decided to create a set of coding standards for its software development team. While not an unusual occurrence in software companies, in this case, the manager in charge wrote up a fifty (that’s right, 50) page standards document. Naturally, everyone was overjoyed and memorized everything; at least, that’s what the manager thought. In fact, no one read more than a page or two and most of the engineers ignored even that.

Another company was trying to manage information: design decisions, notes from discussions, and so forth. They had the very good idea that they could manage all their accumulated wisdom as a Wiki. Unfortunately, the Wiki swiftly ballooned into an unmanageable morass of data in which no one could actually find anything useful. The problem wasn’t so much getting people to remember to update the Wiki; it was organizing the information in a manner useful to everyone who needed to use it, and in convincing people to take the time to keep it organized. Indeed, even agreeing on how it should be organized generated controversy and bad feeling.

In both of these cases, beliefs about how people should do their work were trumped by the way people actually do work. Like Soviet wheat, it can be remarkably difficult to motivate or threaten people into doing something that they really do not want to do. Unlike wheat, people can be forced. It’s merely a question of how much time and energy you want to spend: pushing people takes a great deal of effort and tends to result in significant amounts of anger and frustration for all parties involved. Not, in other words, a conducive atmosphere for creating a strong, collaborative team.

Of course, sometimes it is necessary to have people do things they don’t want to do. Code does need to be commented, information needs to be documented, and so forth. Fortunately, unlike wheat, people can be convinced. Instead of pushing them, the key is to get them to pull: the best teams are the ones that know where they should go and will trample anyone who gets in their way.

So what are teams really? Why are some teams a marvel of camaraderie and high performance, while others burn out their members, leaving them exhausted and depressed? Why do people go from loyalty to opposition to the leader? What is the relationship between the leader and the team?

Organizational Psychology for Managers is an insightful book that reminds the business leader of basic principles of leading a successful organization in an engaging style.

Elizabeth Brown
President
Softeach, Inc.