| April 11, 2001 | Volume 1, Issue 15 |
| Recommend this issue to a friend Join the Friends of Point Lookout HTML to link to this article… |
Archive: By Topic
By Date
Links to Related Articles Sign Up for A Tip A Day! |
| Create a perpetual bookmark to the current issue
| |
by Rick Brenner
For some teams conflict seems to focus around one particular team member. The conflict might manifest itself as either organizational or interpersonal issues, or both, but whatever the problem seems to be, the problem is never the problem.
ill heard a knock at the door. "Come in," she called. It was Troy, and he looked upset. If he felt like he looked, this would be his second "upset" visit in two days. Jill blanked her screen, turned to face Troy, motioned to the chair in front of her desk and said, "Please."
Troy sat. "I'm done," he said. "I'm here to let you know that I've requested reassignment."
Jill had been optimistic at first — Metronome was her team's second project together and Daffodil had been very successful. Well, almost. With hindsight, Jill could see that Rachel and Troy had had some bumps over Daffodil. Now Metronome was becoming a disaster.
Jill had tried everything. She'd worked with Rachel alone, and with Rachel and each of the three others who'd had difficulty with her. Finally she had referred the whole mess up to HR. Nothing worked. Jill wanted to keep Rachel, because she understood the driver software, but not if it meant losing everyone else.
Ironically, Jill's solutions would all lead to the same outcome, because Rachel isn't the problem. For reasons unknown to Jill, transferring Rachel to another team would only create an unfilled conflict role that someone else would then fill. Here's why.
Early in Daffodil, Troy and Jim had been "at war." Jill had separated them by assigning Troy some work that Rachel wanted, but had never asked for, and assigning Rachel some work she hated, but had never objected to. Since Jill stuck with those assignments for Metronome, Rachel had been fuming privately for months. Now she was always irritable, regularly lashing out.
Rachel had placated — she hadn't expressed her discomfort to Jill. Troy and Jim had coped by blaming each other, and Jill had found a super-reasonable "peace" rather than working through everyone's issues, which continued to simmer. Rachel became the focus of the conflict, though she actually contributed only a small piece.
The focus of conflict
is often a role —
it can be filled
by anyoneRachel became the identified patient — the one who exhibited symptoms of pain that was caused by imbalance in the overall system. The team saw the problem as belonging to Rachel, even though four people played roles in creating and maintaining the problem.
Most group interpersonal conflict follows similar patterns. People who seem to be central — especially the identified patient — might only be peripheral to the conflict. People who seem to be peripheral or even helpful can actually be responsible, in part, for igniting and maintaining the conflict.
Eventually, it all came apart for Jill's team. Rachel was reassigned, at great cost to her, to the team, and to Metronome. Jim and Troy were again working more closely together, and resumed their war. Jill was back to Square One — but now Metronome was late.
If you're inside the system, you probably can't tell what's really happening. Seeking outside assistance — from someone with a detached perspective, and the right skills — is your best hope. And the earlier you do it, the easier it will be.
Top
Next Issue
Are you fed up with tense, explosive meetings? Are you or a colleague the target of a bully? Destructive conflict can ruin organizations. But if we believe that all conflict is destructive, and that we can somehow eliminate conflict, or that conflict is an enemy of productivity, then we're in conflict with Conflict itself. Read 101 Tips for Managing Conflict to learn how to make peace with conflict and make it an organizational asset. Order Now!
Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.
Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.
Past issues of Point Lookout are available in four e-books:
Available in early 2009: 2007-2008.
Projects never go quite as planned. We expect that, but we don't expect disaster. How can we get better at spotting disaster when there's still time to prevent it? How to Spot a Troubled Project Before the Trouble Starts is filled with tips for executives, senior managers, managers of project managers, and sponsors of projects in project-oriented organizations. Check it out!
add value to your Web sites quickly and easily. Pick up the HTML to link to this article in a choice of formats.
Are you fed up with tense, explosive meetings? Are you or a colleague targets of a bully? Read 101 Tips for Managing Conflict to learn how to make peace with conflict. Check it out!
Are your projects always late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips & techniques for organizational leaders. Check it out!
A Tip a Day arrives by email each business day. It's 20 to 30 words at most, and gives you a new perspective on the hassles and rewards of work life. Most tips also contain links to related articles. Free!
Save a bundle and even more important save time! Order the Combo Package and download all 21 ebooks and tips books at once, for one low price of USD 161.95 vs. USD 317.97, a savings of over 49% compared to ordering them separately.