Archive for the ‘Leadership and Management’ Category

Airline Metrics

Tuesday, March 2nd, 2010

I was on a flight the other day. Which airline doesn’t matter because this story applies to any of them. The flight was scheduled to depart at 1:30pm. The aircraft was an Embraer ERJ-145 which only holds about 50 passengers. At the request of the flight attendant we hurriedly boarded and shut down our electronic devices so at 1:29pm the door was shut and the jetway was pulled back from the plane. Thus chalking up another “on time departure” for this airline’s metrics. We then sat there for 20 minutes while the pilots recalculated their weight and balance. At one point they reattached the jetway in order to deplane an airline employee who was jump seating. After a few more calculations, they reconsidered and allowed him to re-board. Just as a side note, if we’re voting and the choice is between an extra 200lbs of fuel and allowing an airline employee to jump seat, my vote is on the fuel. After modest delay of about 25 minutes we were on our way.

The thing that irked me was that while they technically might have “departed” on time, from a customer’s perspective they didn’t come anywhere close to that. Teams fall prey to this all the time. The first thing an operations team puts in place is something like Nagios to monitor the CPU, memory, and disk of all the servers. As we discuss in our post Monitoring Strategies, the first measurement to put in place should be something to measure from the customer’s perspective and answer the question “Is there a problem?” The most important thing to know is are my customers being impacted and how. The answer to that will determine who gets paged, how you should react, etc. After answering that then you need to figure out “Where is the problem?”, “What is the problem?”, and “Why is there a problem?”.

Failure to heed this and you’re at risk of falling into the airline metrics trap. You’ll be satisfied that you’ve kept all the servers up and running 99.99% of the time but your customers may have only been able to access the site 95% of the time because of software, networking, database contention, etc. The result is unhappy customers despite you meeting all your stated performance metrics.

Stop Doing Annual Reviews

Wednesday, February 24th, 2010

It’s annual review season again and lots of you managers are probably swamped trying to write pages of feedback, both positive and negative, for your employees. My advice for the coming year is to stop doing annual reviews. Workers today, millennials especially, don’t want to wait for a review or feedback once per year. This cycle was fine back when employees worked for a company for 30 years and could take twelve months to work on last year’s deficiencies. Today’s world is one of instant updates (Twitter, Facebook, etc) and a career comprised of stops at many different employers.

A BLS news release published in June 2008 looked at the number of jobs that people between the ages of 18 and 42 held. On average, men held 10.7 jobs and women held 10.3 jobs. Both men and women held more jobs on average in their late teens and early twenties than they held in their mid thirties. Holding 11 jobs over 24 years averages to holding each job slightly over 2 years each. If you wait for an annual review to provide feedback the employee is likely half done with their tenure at the company.

We argued in a recent post Lower your standards and build a better team that the standards for hiring should be lowered. The reason is that we are unable to predict future success based on past performance in a different environment (different employer, different culture, etc) and academic prowess isn’t likely to be a good indicator of job performance. A couple hour interview doesn’t net a better result. Said more simply, we should hire more people but make the cuts way faster. This is especially true when employees, great or poor performers, are likely to leave in 2 years.

Give feedback and rewards quickly. Why should salary increases occur only once per year? When someone performs well or takes on additional responsibility, give them positive feedback and reward them. Today’s employment environment calls for fast hires, fast feedback, and fast cuts.

Firefighting

Tuesday, February 9th, 2010
Who are the heroes in your organization? They are probably the ones who come in during the crisis, find the bug, fix it, and bring the site back. It’s natural for all of us to consider the people who rescue us as heroes. The reality is that the real heroes are the ones who never get recognized because they fix things before they break, not afterwards. Firefighters get medals, safety inspectors do not, but I think they should.

The people in your organization that you should be finding and smothering with praise are the ones who stay late at night or over the weekends making sure things are right. These are the real heroes and should be treated like it. The ones you have to call in to put out a fire are great but they are more opportunist than heroes in my book. Additionally, what message would you rather send, put out a fire and get rewarded or prevent a fire and get rewarded? I’d chose the latter.

There is one thing way worse than the opportunist who waits for fires so they can be the hero, that is the firefighters who are arsons. This phenomenon is known as “Hero Syndrome” in which people crave heroism by creating situations that they can solve. The people who write sloppy code or let junior engineers write bad code and let it get into production so they can be the hero and fix it, they suffer from the Hero Syndrome. Someone who ignores preventative maintenance and waits for things to break should not be rewarded, they should be counseled.

Go find your safety inspectors and reward them. And while your firefighters might have earned a pat on the back, ask the hard questions of why the problem wasn’t found earlier before it impacted your customers.

Team Conflict – Part 1

Monday, February 1st, 2010

Our December article in GigaOm had a brief nod to the myth that conflict in teams is bad.   In fact, practitioner experience and scholarly research agree that there are good forms of conflict and bad forms of conflict.  The good conflict, often referred to as cognitive conflict, is the healthy debate that teams get into regarding what should be or why something should be done and involves a wide range of perspectives and experiences.   Bad conflict, often referred to as affective conflict, is role based and often involves how to do something or who should be doing something.  This of course isn’t to say that all discussions over roles are “bad”, but rather that lingering role based discussions that are perceived as political or territorial can be unhealthy for an organization if not handled properly.

Good, or cognitive conflict, helps teams open up the range of possibilities for action.  Diverse perspectives and experiences work together to attack a problem or an opportunity from multiple angles.  Brainstorming sessions and properly run post mortems are all examples of controlled cognitive conflict with the intent of generating a superior set of alternatives and actions.  Team norms have been shown to have a positive effect on developing cognitive conflict; a culture of acceptance and respect for diverse opinions is more likely to generate more alternatives.   Emotionally and socially intelligent leaders also may help create positive cognitive conflict within teams.  But research shows us that cognitive conflict if left unresolved can escalate to affective (bad) conflict.

Bad (or affective) conflict results in physical and organizational trauma.  Physically, it can leave us drained as the sympathetic nervous system (the same system partially involved in the fight or flight syndrome kicked off by the hypothalamus) releases the stress hormones epinephrine and norepinephrine.   Our blood pressure and heart rate increase, and the adrenal cortex releases 30 different hormones to deal with threats.  Over time, constant affective conflict leaves us drained.  Organizationally, teams fight over ownership and approaches.  Organizations become fractured, and scholarly research shows that the result is a limiting of our options from a tactical and strategic perspective.  The fighting closes our minds to options, meaning we sub-optimize our potential results.

Why is all of this important?  By understanding the sources and results of conflict, we as leaders can drive our teams to have healthy debates and we can quickly end value destroying affective conflict.  Our job is to create a healthy environment suitable to the maximization of shareholder value.  By creating an open, caring and respectful culture we can both maximize cognitive conflict and minimize affective conflict.  By setting clear roles and responsibilities we can limit the sources of affective conflict.  And by hiring a diverse group of people with complementary skills and perspectives we can minimize group think, maximize strategic options and grow quickly!

Speak in Terms of Objectives – Not Actions

Thursday, January 14th, 2010

Have you ever been in a position where a project you were managing was late or over budget? Have you ever supported an application that had a customer impacting service outage? How did your boss respond to these issues? Did she say something like “I want a review of our quality strategy” or “I’d like to see our application rollout strategy”? Maybe they asked for something even more nebulous and less connected to the issue at hand like “Show me our site and product integration strategy”. Huh? What does that mean?

It’s easy for managers to react to incidents and problems by requesting that certain actions be taken by a person or team. The problem with such an approach is that it feels like a punitive action to the people from whom the action is being requested. Maybe the group or person needs to receive performance feedback, but by asking them to take an action you are not really giving them feedback. If your goal is to both provide feedback and ensure the underlying issue is corrected then provide candid performance feedback and explain the desired goal of the corrective action.

Great leaders understand intuitively that they should speak in terms of desired end states and then ask for plans to achieve those end goals or states. Another approach is to use the Socratic Method and ask your team what an appropriate end goal should be, whether they’ve achieved it and how they should correct their approach to achieve that goal. The first is probably the best approach when the team is overwhelmed or you are in the middle of a crisis. The latter approach is best for higher performing teams who have simply hit a “bump in the road”.