TrainingConferencesAbout UsContact UsAdvertiseSQE.comRSS Feed

StickyMinds.com: brain food for building better software

Log In
 Clarify Your Search Criteria

Tips on Using Our Search Feature(s)
 
StickyMinds.com Home
ResourcesTopicsCommunityPowerPass
Home  >  Detail: Mistaken Interpretation



A StickyMinds.com Original
Article Picture
Mistaken Interpretation

By Esther Derby

Send This Content to a FriendGet a Short Link to This ContentPrint This ContentSee User Comments About This Content

Summary: Our brains are wonderful processors capable of making sense of the huge amount of sensory input we receive every day. But sometimes, our first interpretation of sensory data can lead us astray. This week, columnist Esther Derby shows us how assuming our interpretation of events holds the truth of the matter can damage relationships, and how testing our interpretations can help.


Rally Software Development
 

 
"Jim was trying to publicly humiliate me!" Dave asserted, "What a jerk." 
 
"When did this happen?" I asked. 
 
"During the conference call yesterday," Dave responded. "You were there. You heard him. He reamed me in front of the group." 
 
Actually, I hadn't heard him. Or to be more precise, I heard what Jim said, but I didn't hear Jim humiliate Dave, nor had I heard Jim ream Dave.  
 
During the conference call, Jim said "Dave, you haven't been present for our last three calls, and you haven't returned phone calls or emails."  
 
How did Dave get from those words to public humiliation? He told himself a story.  
 
From Point A to Point B, Sometime by a Circuitous Route 
Interactions start with sensory input: some one says something; we hear the words, tone, and inflection; and if we're face-to-face, we see physical posture, facial expression, and gestures. Based on what we've seen and heard, we interpret a meaning. Most of the time, our interpretation is close enough that we catch the (intended) drift and can continue the conversation. 
 
Once in a while, our interpretation is off and our communication becomes tangled. If we've misheard or misinterpreted a word, it's relatively easy to get back on track. But sometimes the interpretation we make causes a rift. Then we need to work harder to get back on track. 
 
Separate Sensory Input from Interpretation 
Our brains are wonderful processors capable of processing vast amounts of data in the blink of an eye. It happens so fast that most of the time we aren't aware that there are two separate steps. But if we learn to separate these steps, we can increase our effectiveness.  
 
I don't mean that in each interaction we need to stop and ask ourselves, "What did I see and hear? What interpretation am I making?" It's just good practice to slow down the process and consciously separate what we have seen and heard from the meaning we make, especially when emotions are high – as in Dave's case. 
 
Once you've separated the data from interpretation, reevaluate your interpretation. Our interpretation can lead us to fabricate specific types of stories, which tend to land us in trouble. 
 
I'm an Innocent Victim 
In Innocent Victim stories, we tell ourselves that we played no part in creating the situation – we're zero percent responsible. When Dave described how Jim humiliated him, Dave conveniently left out facts unflattering to his case – that he had indeed missed three meetings and not returned calls or messages. 
 
He's a Bad Guy 
Like Innocent Victim stories, Bad Guy stories absolve us of any responsibility as well. Bad Guy stories not only let us off the hook, but make the other person 100 percent responsible. Bad Guy stories start by assuming that the other person has evil motives. You can spot a Bad Guy story because it labels the other person as an idiot, vindictive, etc. Once we label someone, it's easy to trash him. And that's where Bad Guy stories go. 
 
Unraveling the Knot 
If you catch yourself in one of these stories, stop. Unravel the knot you are in before you take action or say something you'll regret later. Start by reviewing the sensory input.  
 
What did you see or hear? Don't bleed over into interpretation. When I asked Dave what he'd heard, he replied "Jim told me I'm irresponsible." That's an interpretation. Jim didn't say that at all and may not have meant that. Jim may have been leading up to asking if Dave had been ill. Stick with the facts – just the facts. 
 
If you're telling yourself an Innocent Victim story, ask yourself, "What part did I play? If I asked an impartial observer, what part would he say I played?" Dave conveniently ignored he had in fact missed three calls and gone dark for two weeks.  
 
On the other hand, if you are telling a Bad Guy story, strip off the label. Ask yourself, "What would have to be true for a reasonable person to act this way?"  
 
Once you convince yourself that maybe, just maybe, you are not a victim or the other person isn't a villain, generate at least three possible interpretations, that remind you an interpretation is not a fact. 
 
After Dave and I talked this through, he decided to talk to Jim about what happened during the conference call. Dave realized that he'd been hasty in ascribing motives to Jim, yet he still wanted to convey that he had been embarrassed when Jim publicly recited his absences. Dave approached Jim and shared his interpretation as a hypothesis, not a fact. After listening to Dave, Jim paused for a moment.  
 
"Well," Jim said, "What I was going to say is that it looks like we did a good job covering for you. I was wondering whether I could take some time off and the team could cover for me as well. But when you snapped at me, I decided it meant you didn't think I should take time off." 
 
Dave looked chagrinned. "Sounds like we both jumped to misinterpretations." 
 
Once Dave and Jim realized they had misinterpreted the facts, it didn't take long for them to untangle the conference call interaction. Dave decided that maybe Jim wasn't a jerk. Jim checked with the team and scheduled a few days out of the office. 
 
Isn't it a wonder that human communication works at all?

About the Author
Esther Derby, a regular contributor to Better Software magazine and StickyMinds.com, is one of the rare breed of consultant who blends the technical issues, and managerial issues with the people-side issues. She is well known for helping teams grow to new levels of productivity. Project retrospectives and project assessments are two of Esther's key practices that serve as effective tools to start a team's transformation. Recognized as one of the world's leaders in retrospective facilitation, she often receives requests asking her to work with struggling teams. Esther is one of the founders of the AYE Conference. You can read more of Esther's musings on the wonderful world of software at www.estherderby.com and on her weblog at www.estherderby.com/weblog/blogger.html. Esther is a regular presenter at SQE conferences. Her email is derby@estherderby.com.

Back to Top
 
 


Member Comments
Add Your CommentExpand Comments
 
Comment:    
by Rodger Drabick 7/14/2005

Hi, Esther. Fascinating article, as always. Articles like this always bring me back to the Satir Model of interaction, which basically states that we (as human beings) are always interpreting situations, and that our interpretations aren't always an accurate reflection of the facts in the situation. Your example shows that perfectly.

 
 
Comment:    
by Naveen Samshi 3/10/2005

This is really a good artical to known ourselves.

Author's Response:
3/11/2005    
In my view, the more we know about ourselves -- how we learn, what our blind spots are, our strengths, triggers, etc. -- the more we can choose how we respond to situations, rather than simply reacting. Self-awareness is the cornerstone for personal effectiveness. Thanks for writing.

 
 
Comment:    
by irina green 3/8/2005

Just to back up a step, I think there's a pattern to the misunderstandings: Dave shirks (missing meetings, not returning calls, etc), then Dave reports feeling attacked by Jim. Is there a pattern of causing harm followed by feeling powerless? Did Dave actually turn over the power in this scenario not by proclaiming victimhood ("What a jerk!") but earlier, by causing a loss to Jim (et al.) and **not acknowledging it**? I often can see (often in hindsight, unfortunately) that when I'm not telling the truth (or "coming clean") about causing some harm (real or perceived), I end up on the victim-side ("what a...Read On

Author's Response:
3/8/2005    
Hi, David – You bring up a good point – sometimes we play to victim to avoid facing how we contributed, or where we caused harm. And to unravel a situation, we need to think about what we really want and what we contributed. Your point about loss is interesting, too. The Non-Violent communication folks might talk about in terms of Needs. If we’re talking over the needs of the people we are dealing with, its hard to get very far. Acknowledging the needs with empathy (even when we can’t meet them) allows people to move forward. Thanks for writing. Esther

 
 
Comment:    
by Jan Fincher 3/8/2005

How wonderful to see this topic addressed in a technical setting. I recently read a book, "Crucuial Conversations: Tools for Talking When Stakes are High" by Kerry Patterson, et al. that deals with this very same topic. My reason for picking the book up to begin with is that as technical professionals, we tend to focus more on the product or process at hand, rather than on our relationships with those around us.

Author's Response:
3/8/2005    
Hi, Jan – All project work is social work –relationships are a crucial part of accomplishing most complex tasks. And when we work closely with others, conflict is inevitable. The book you mention, Crucial Conversations has some good advice for how to approach conversations in conflict situations. Thanks for writing. Esther

 
 
Comment:    
by Robert Rose-Coutre 3/8/2005

In many meetings I've heard people start sentences with "No, ..." or "I disagree ..." -- which usually doesn't lead to a productive resolution. What's interesting is that in most cases, I parse the objective statements of two people (person-X and person-Y), and in fact they agree on most everything. Person-X uses negative tones and signals like "No, ..." in response to person-Y -- even while the statement he utters is in perfect accord with person-Y's preceding statement. X and Y have different styles of expression and may even use terminology a little differently, but after parsing the substance of their...Read On

Author's Response:
3/8/2005    
Hi, Robert – The non-verbal parts of communication are fascinating. You can change the way people interpret even a simple sentence by changing which syllables are emphasized. You are late vs. YOU are late or You are LATE. So tone and inflection can give an important clue to what’s going on. On the other hand, I’ve noticed something about when people are repeating a statement by someone they’ve assigned a bad guy role. Often, they use emphasis in a way that connotes that the original speaker is blaming them for something. Thanks for writing. Esther

 
 
Comment:    
by Keith Collyer 3/8/2005

Related to what Dale says, for some people, there is a positive advantage in "Bad Guy" or "Innocent Victim". By making us helpless to do anything about the perceived problem, they also absolve us of any responsibility for solving it. "How can I be expected to fix this, when he won't listen!"

Author's Response:
3/8/2005    
Hi, Keith -- You're right. Abdicating reponsibility for fixing the situaiton is part of the dynamic. It's hard work to admit fix situsations (and sometimes to admit the part we play). These sorts of stories let us off the hook, but usually don't make us any happier or more productive. Thanks for writing. Esther

 
 
Comment:    
by Dale Emery 3/7/2005

Another drawback to my own Bad Guy stories, in addition to confounding the relationship, is that they give all of my power away and leave me helpless. If the problem is that Jim is a jerk, then I'm stuck with the problem until Jim stops being a jerk. Ick. The ideas you give for "unraveling the knot" help me to get out of the helplessness of blame, and focus on what I can do to make things better.

Author's Response:
3/7/2005    
Hi, Dale -- Absolutely! When we have 0% responsibility, there's no place for us to start to improve the sitaution. When I can figure out the part I play - even if its the way I respond - there's something I have control over and can change. Thanks for writing. Esther

 
Back to Top


Marketplace

Web based bug tracking - AdminiTrack.com
AdminiTrack offers an effective web-based bug tracking system designed for professional software development teams.

BugSplat - Automatic Crash Analysis
Fast online exception analysis. Capture customer crash data online.

Six Sigma Certification
100% Online-Six Sigma Certificate from Villanova - Find Out More Now.

Census: Web-based Bug Tracking and Defect Tracking
Track software bugs, defects, enhancements, support calls, and more. Issue tracking software that is scaleable, fully customizable and integrated with VSS. Includes e-mail notifications, role-based workflow, change history, and Crystal reporting.

Check Out IT Certification Preparation Materials
Sign Up With SkillSoft & Get Access to Training Materials for Over 50 Professional Certifications.

Get your product or service listed here.
Subscribe to Better Software Magazine
Subscribe to Better Software Magazine

First Name:

Last Name:

Email Address:


Home   |   Resources   |   Topics   |   Community   |   PowerPass



© 2008 StickyMinds.com. All rights reserved.
StickyMinds.com is a division of Software Quality Engineering.
Privacy Policy    Terms & Conditions    Link to StickyMinds.com    Feedback


Telelogic North America

MKS, Inc.



STARWEST 2008

 
Agile Development Conference 2008