Friday, February 26, 2010

Unraveling a workplace mystery: Why is your employee snapping at you?

In this post, we’re going to tell the story of a real-life incident that happened several months ago in a local office. We’d like you to put yourself in the position of the supervisor, trying to figure out what’s going on with his employee. As you read, ask yourself what you can conclude about the employee’s personality and mindset.


The Problem
One afternoon last fall, this supervisor (call him Brian) was working closely with one of his employees (Amanda) to complete a straightforward, if somewhat tedious task — identifying, labeling, and sorting a long series of electronic files. The files were photographs, and only Brian could determine what they were and where they needed to go. Amanda’s job was to bring the files up on the screen for the supervisor to see, and then label and organize them as directed.

For the first hour things seemed to go smoothly. They managed to organize about 20% of the images before taking a break for Brian to attend a meeting. But the next time they met, after just 10 minutes Brian started noticing a change in Amanda’s attitude. Her answers to his requests (“Can you make this image larger?” “Can you show me that last one again?”) became increasingly curt and abrupt. When he tried to give her suggestions (“How about making a new folder for that?”), she snapped back, “I know!” or “Okay, I’m doing it.” After about an hour of this, Brian started becoming quite irritated himself. He suggested taking a break and went back to his office to try to figure out what might be happening. He had never known Amanda to be so rude, but then again, she did much of her technical work independently, without anyone telling her what to do.

Before we tell you what came next, try for a moment to consider what might account for Amanda’s behavior. What might she be thinking about this task or about Brian? What type of personality traits might lead her to respond so harshly in this situation? What might her intention be here? And how should that affect the way Brian responds?

Finding Answers
Do you have some thoughts? Good. If you followed our suggestions in thinking about this issue, you may have come up with some interesting hypotheses about Amanda — maybe she resents being told what to do; she thinks this task is beneath her; or she’s edgy in general and doesn’t work well with others. Maybe she wants to get Brian to be less directive, or even wants him to get so irritated that he’ll go away and get out of her hair. What should Brian do? Find a way to let her do this project more independently? Give her feedback about her attitude? Offer a stern warning?

Let’s look at what Brian actually did. First let’s look at what he didn’t do. He had some guesses about what might be happening with Amanda (based on his experiences working with her for a number of years), but he did not assume that any of them were true. Instead, he decided to engage Amanda in a conversation about what was happening. Also, he did not focus his attention solely on what was going on with Amanda; rather, he asked her to help him figure out what was happening in their interaction — which was a product of both of their actions. (Of course, this is the exact opposite of what we asked you to do; we wanted you to be able to compare the different sorts of conclusions these two methods produce.)

Talking together in this way, these two people came up with answers that surprised both of them. Initially, Amanda couldn’t explain what was going on. She was aware of feeling very irritated, but didn’t know why. It was only by thinking through the events together that they identified the factors that had led to her irritation — and there had been quite a few:
  • Technical slowdowns: There were several steps to manipulating the files, and they took longer than Brian realized. As a result, he would often give instructions on a new task before Amanda had completed the previous one, so she had to rush to get both of them done.
  • Perceived time pressure: Amanda interpreted Brian’s rushed instructions as an indication that he was in a hurry, which increased her level of stress.
  • Actual time pressure: The second time they got together, they only had 30 minutes to work before Brian had to leave for another meeting.
  • Phone interruptions: Several times, Brian answered the phone in the middle of the organizing work. When he was finished, it took them both some time to get re-oriented to exactly where they’d left off. This added further to the stress of the real and perceived time pressures.
  • Startling interruptions: Periodically, as Amanda was scrolling through images, Brian would reach over to point at the screen and say, “Wait!” or “That one there!”, which startled Amanda and kept her stress level climbing.
This was a wonderful realization, because it pointed so easily to solutions — solutions much more effective (and pleasant) than a stern warning. For instance:
  • Technical slowdowns could be anticipated. Instead of jumping ahead, Brian learned to wait until Amanda said she was ready to move on.
  • Perceived time pressure was reduced by Brian explaining that he was not actually in a hurry. (In SAVI terms, Amanda learned that her Mind-read of him was inaccurate.)
  • Actual time pressure was minimized by waiting until they had a longer stretch of time to work together.
  • Phone interruptions were eliminated by simply ignoring the phone during this period of work.
  • Startling interruptions were minimized by Brian holding back, keeping his interruptions quieter and less intrusive. (Just gaining some awareness helped; he hadn’t realized what he’d been doing.)
With these changes, the irritability problem was solved. Amanda apologized for being curt and rude, Brian apologized for unknowingly creating a stressful situation, and they easily moved on.

We like this story because it provides a good illustration of the value of a collaborative problem-solving approach (What’s wrong here?), as opposed to a solely person-focused approach (What’s wrong with her?). It also has some personal meaning for us. As we mentioned earlier, this is an entirely true story. Brian and Amanda are yours truly — Ben Benjamin and Amy Yeager.

5 comments:

  1. Great example of a common occurrence. I particularly liked: "he asked her to help him figure out what was happening in their interaction — which was a product of both of their actions." The focus is on the behavior in their dyadic system, as opposed to the people, and looked at improving the environment (ignore telephone, find a better time) to support the goal.

    Thanks.

    ReplyDelete
  2. I really like that ... as I have seen that happen before. I also think there is something about "technology" in general that creates this kind of situation. It is kind of like the invisible "third person" in the relationship.

    (Consider how exasperating it is when someone is surfing the web to show you something ... I always want to jump in and take over ... because I hate watching the weird way that someone might find a file or information ...).

    This use to happen all the time in web development .. and part of it is a lack of understanding of how difficult it might be to say, manipulate an image, etc. I think people over-estimate the 'human' element that is necessary ... photos just don't re-size themselves ... and very few processes are totally automated.

    ReplyDelete
  3. Thanks for your comments; you both make really good points. Looking at the whole system -- including behavior, environment, and whatever technology is being used -- can be a great way to take conflicts less personally. (Not to mention resolving those conflicts more effectively!)

    ReplyDelete
  4. Amy and Ben,
    Nice to think systems instead of attribution!Since I have no employees, I'll try it at home. Thanks for the personal touch.
    Elaine

    ReplyDelete
  5. Glad you enjoyed this. And yes, try it at home! (As someone in the process of moving -- with all the up-ending of previously established systems that entails -- I can attest to the benefit of looking beyond attribution in the personal context as well.)

    ReplyDelete