The Business Sensei

Seven Habits of Pointy-Haired Bosses

Scott Adams, of Dilbert fame, routinely features tales of bumbling managers. The popularity of Dilbert, and the degree to which it resonates with people, are a testament to his accuracy; indeed, Dilbert’s pointy-haired boss has become an iconic figure. Dilbert aside, however, I have observed that very few leaders are intentionally like the pointy-haired boss depicted in the comic strip. Rather, they engage in pointy-haired behaviors without realizing the effect they are having on the organization as whole. Let’s explore some examples of such behaviors and their unintended consequences.

1. Pointy-haired bosses break their own rules and figure either no one will notice or no one will mind because they are in charge. In one company, the CEO called everyone together to talk about the importance of really working hard and putting personal needs to one side in order to ship a product. At the end of the talk, he announced he was leaving for a two week vacation in Hawaii and wished everyone good luck. This did not go over well. One vice-president, who had apparently not been warned, almost choked on his coffee. When the CEO came back, two people had quit and the rest were up in arms.

2. The pointy-haired boss believes that he is separate from the group he leads. In fact, leaders are also group members, with a very important and well-defined role. Through their actions, leaders set the norms for their group. For example, the manager of a team at a large software company imposed a $.25 penalty for being late to meetings. When he was subsequently late himself, the team gleefully demanded he pay up. After a brief stunned moment, he tossed a quarter into the pot. No one complained about the fine after that. What the leader does is directly mirrored in the organization. When leaders find that employees are not living up to the standards of the organization, they often need to look in a mirror and see what example they are setting.

3. Pointy-haired bosses fail to recognize the culture they are creating. To be fair, it’s hard to see your own culture from the inside, and despite what many managers and CEOs believe, culture is formed not from what you say but from what you do. As MIT’s Ed Schein observes, “Culture is the residue of success: success in dealing with external challenges and success in internal advancement.” What behaviors are successful in the organization? What behaviors are rewarded? The very behaviors that people tell me they want to change are frequently the ones they are encouraging.”

4. Pointy-haired bosses lack an understanding of group/team dynamics. They like to say that their organization is “different,” and the research on group dynamics doesn’t apply. That’s like the people in early 2000 who said about the stock market that “This time, it’s different.” If you’re dealing with people, patterns repeat. It pays to recognize the patterns and understand how they are manifesting in your specific situation.

5. Pointy-haired bosses are often unable or unwilling to create a clear, compelling vision for their organization that gets everyone involved and excited. The best way to attract and retain top talent is to make people care about what the company is doing. That’s best done through painting a vivid picture of the outcome and creating clear goals.

6. Pointy-haired bosses motivate through short-term rewards and/or intimidation. They assume they know what their employees want, rather than taking the time to ask or to observe how people are responding. Short-term rewards and intimidation generate short-term spikes in performance, but build neither loyalty nor the desire to go the extra mile. Unfortunately, far too many people are willing to sacrifice the longer-term performance of their team for a short-term gain . In one company, the head of engineering “motivated” employees by inviting them to join him for happy hour in a bar on Friday nights. Had he asked, he would have realized that what the team wanted on Friday nights was to go home and have dinner with their families. Instead of motivating the team, he made them feel imposed upon.

Finally,

7. Pointy-haired bosses do not believe in asking for or accepting help. It’s not about asking for help, it’s about investing time and money to enable the company to accomplish its goals. The boss’s time is a resource; skilled leaders invest their time and the time and money of their business where that will produce the best return. Sometimes the best return is obtained by investing in an employee, sometimes by investing in a contractor.

Very few leaders deliberately engage in these Pointy-haired boss behaviors. Rather, their behaviors are the result of their own corporate success story. Therefore, for all that even one or two Pointy-haired boss behaviors can derail an organization, behaviors acknowledged to be counter-productive are very difficult to eradicate. Nevertheless, the ability of a manager or CEO to recognize these failings and invest in changing themselves is the true test of “great” leadership.

Published at FreudTV.

Yankee Swap Rorschach

The holidays are the season for Yankee Swaps. Now, a Yankee Swap would seem to be a fairly simple and straightforward activity: each person either chooses a wrapped gift or steals an opened gift from someone else. This latter activity can, of course, trigger a chain reaction, but that’s part of the fun. At the end, everyone feels like they had at least some measure of control over the outcome. One would think it difficult, if not impossible, to mess up a Yankee Swap.

However, all things are possible. In this case, one company held a Yankee Swap with incredibly detailed and complicated rules which had as its most salient feature that no gifts were opened until the very end. In other words, the experience was transformed into the equivalent of a very slow grab bag: a long, frustrating, totally random process at the end of which people felt that they had no control over the outcome. Ironically, the most common complaint from employees at this company is that many of the rules are complex, time consuming, and leave them feeling like they have very little control over how they get their work done.

Now, a Yankee Swap is a pretty insignificant event, little more than an amusing party game. However, how a business goes about designing a small process says a lot about how it goes about designing larger, more significant processes: process design is strongly influenced by institutional habits and beliefs. With a small process, it’s easy to see the results of that belief in action because the entire event can be seen at one time; with larger processes, cause and effect may be separated by weeks or months, and the process is often so big that no one ever views it as a whole. The company ends up wondering why their results are poor, but can’t figure out the reasons. Those small processes can provide valuable insights into the company’s methodology and assumptions; recognizing consistent causes of small problems can enable you to avoid large ones. Ultimately, more important than improving one process is improving how the company designs all its processes.

In designing a process, it helps to clearly understand what you are trying to accomplish. Why did this particular company choose to redesign the Yankee Swap? Was there an actual problem that someone was trying to solve? Clearly, someone felt a need to come up with something, although their motives are impossible to fathom. As a result, they got a process that rather missed the point, but did end up reflective of the organization as a whole. However, it’s generally more successful to focus on results:

·        Clearly define the objective. If the objective is to solve a problem, take the time to look at the symptoms and consider what they mean. When do they come up? Under what circumstances? Remember, the symptoms are not the problem, they’re just the symptoms. Generate a list of hypotheses and then test them to see if they lead to the observed symptoms. Solving the wrong problem will generally make things worse, not better.

·        Describe what a successful outcome will look like. What will have changed? What behaviors will be different? Make this concrete. If success is, “people will have more fun,” how will you know? If the picture isn’t clear, identify the questions you need to answer to bring clarity. This may be an iterative process.

·        Identify what you can change and what you can’t. You probably can’t change the economy, but you can change how you deal with it. Tom Watson Sr., founder of IBM, used the Great Depression as an opportunity to build up a highly trained, extremely loyal workforce and a stockpile of equipment. When WWII started, IBM was in an excellent position to capitalize on the reawakening economy. If everything falls into the “can’t change” category, you need to revisit your goal or problem formulation.

·        Brainstorm possible solutions or approaches. Record ideas and do not evaluate any of them until you have a significant number of possibilities. Don’t worry if some ideas are silly or off-the-wall: innovative solutions come from the most unlikely sources.

·        Will your solutions really get you where you want to go? Do research. Don’t rely on opinion and conjecture.

·        Define your action steps.

·        Execute and evaluate. Did it work? If not, check your problem formulation and try again.

If you’re not getting the results you want, what steps are you missing?

Why Teams Fail

In today’s high-tech workplace, it is virtually impossible to not be part of a team. Projects are too big, too complex, too involved for a single person to do it all. Yet far too often people find teamwork to be frustrating and exhausting. Even when the team successfully ships a product, team members often feel burned out, frustrated, or surprisingly unhappy with their accomplishment.

Many managers have heard of the four stages of team development: Forming, Storming, Norming, and Performing. What is not as well known is the importance of that early, forming stage. During this phase, team members determine whether or not they feel emotionally and intellectually safe working with one another; they develop a sense of group identity, or remain a collection of individuals.

There’s an old saying that a couple isn’t really married until they’ve had their first fight. The same is true of teams. Part of working together involves arguing with coworkers: put any group of people together, and they are bound to have their own approaches and solutions to problems. If team members feel unable or unwilling to argue with one another, they avoid any conflict. If they are forced to argue but haven’t developed effective means for conflict management, the argument can quickly turn personal. In either case, the exchange of thoughts and ideas is blocked, anger builds, tension mounts, and the ability of team members to work together is severely compromised. Instead of developing group identity, team members may become convinced that their best strategy is maximizing personal gain instead of team performance.

The problems are exacerbated when the leader’s expertise is not management but engineering. There is a persistent, and ultimately painful, myth that engineers will only respect another engineer. Unfortunately, the very personality traits and skills that make someone a good engineer are often exactly the wrong skills to be a good manager. A team leader needs to have the social skills and empathy to manage the evolving dynamics of his team, and the interpersonal knowledge to apply those skills.

Of those people who do possess both sets of skills, even fewer can do both simultaneously. A good manager spends his time building the team. If he’s busy writing code, designing circuits, or what have you, then he’s not building the team. If he’s like most people thrust into a new situation and tasked with doing something he’s really good at, and something he’s not good at, he’ll gravitate toward the former.

Another problem faced by team leaders is that the storming phase can get, well, pretty stormy. The focus of that storm is often the leader. If the leader feels attacked, she’s likely to respond accordingly. This is a perfectly natural reaction. It’s also counterproductive. Managing conflict effectively means not getting enmeshed in the conflict in the first place: team progress can be set back weeks, months, or longer. Once conflict is joined, replacing the leader may improve things in the short-term, but can often make things worse long-term. The fundamental team dynamic needs to be repaired.

Unfortunately, more than half the teams in businesses become stuck in conflict or avoidance. When a team becomes stuck, it is stressful and exhausting to the team members. The company pays for this in lower productivity, reduced product quality, increased illness and absenteeism, and higher staff turnover, all of which can be fatal to a business.