Phil was feeling frustrated. He and Jake had been at it for two hours, and they had made little progress. From the beginning, Phil felt that Jake hadn't been receptive to his ideas, so after a while he just stopped offering them. Now he felt like little more than a typist and mouse jockey.
Jake was no happier. He was a peer of Phil's boss, which made the collaboration with Phil "diagonal." To Jake, Phil seemed to have his mind on other things. Jake wondered, "Why did Phil agree to work on this, if he didn't really care about what went into it?" Jake had much to do that was more important, and now he was wondering why he was caught in this situation again — spending time on the wrong things with the wrong people.
They were both locked in — by different locks.
When hierarchy is unimportant, diagonal collaborations aren't especially risky, but when hierarchy counts, diagonal collaborations have traps for both partners. Here are some tips for preventing conflict in diagonal collaboration.
- Have a good reason to collaborate
- Perhaps you want to learn something, or to get to know your colleague. Perhaps you have critical skills, knowledge, or talents. These are all good reasons to collaborate. But if your motive is to mentor, to be mentored, to block, to overtake, to justify your existence, or to grab some of (or all of) the glory, don't sign up.
- Take reasonable risks
- When Fun is missing,
the simplest explanation
is that you forgot
to bring the Fun
with you - Anticipating a problem sometimes becomes the problem. Collaborate as if with a peer, until you can tell whether your partner is comfortable with that. It's best if the two of you can discuss this issue openly, but if you can't, assume the best, unless you discover otherwise.
- Focus on content and communication
- Emphasize content instead of the status gap between you and your colleague. Assume that you're working with your partner because somebody thought that you could team up effectively, and because you had something to contribute. Contribute it.
- Work out the kinks
- However difficult you find the collaboration, it can be just as difficult for your partner. Things are unlikely to change for the better if both partners keep their misgivings to themselves. If necessary, ask for help from an impartial third party.
- Enjoy yourself
- Working with the right partner can be fun. Look for ways to create that kind of experience. When Fun is missing, the simplest explanation is that you simply forgot to bring the Fun with you. Take a break, find the Fun, and start again.
- Remember that collaboration is a partnership
- Think of your partner as a peer. Be open to new approaches, and be open to moving in new directions. Let "mistakes" happen — they can lead to exciting, original creations.
You might have a choice that Phil and Jake did not. If you read this page together, right at the start, you'll both have these tips in mind, and that might help keep your collaboration in the safe zone. Top Next Issue
The article you've been reading is an archived issue of Point Lookout, my weekly newsletter. I've been publishing it since January, 2001, free to all subscribers, over the Web, and via RSS. You can help keep it free by donating either as an individual or as an organization. You'll receive in return my sincere thanks — and the comfort of knowing that you've helped to propagate insights and perspectives that can help make our workplaces a little more human-friendly. More
Your comments are welcome
Would you like to see your comments posted here? rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.comSend me your comments by email, or by Web form.About Point Lookout
Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.
This article in its entirety was written by a human being. No machine intelligence was involved in any way.
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.
Related articles
More articles on Personal, Team, and Organizational Effectiveness:
- Working Lunches
- To save time, or to find a time everyone has free, we sometimes meet during lunch. It seems like a good
idea, but there are some hidden costs.
- The True Costs of Indirectness
- Indirect communications are veiled, ambiguous, excessively diplomatic, or conveyed to people other than
the actual target. We often use indirectness to avoid confrontation or to avoid dealing with conflict.
It can be an expensive practice.
- Coping and Hard Lessons
- Ever have the feeling of "Uh-oh, I've made this mistake before"? Some of these oft-repeated
mistakes happen not because of obstinacy, or stupidity, or foolishness, but because the learning required
to avoid them is just plain difficult. Here are some examples of hard lessons.
- How to Foresee the Foreseeable: Preferences
- When people collaborate on complex projects, the most desirable work tends to go to those with highest
status. When people work alone, they tend to spend more time on the parts of the effort they enjoy.
In both cases, preferences rule. Preferences can lead us astray.
- False Summits: II
- When climbers encounter "false summits," hope of an early end to the climb comes to an end.
The psychological effects can threaten the morale and even the safety of the climbing party. So it is
in project work.
See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
- Coming January 22: Storming: Obstacle or Pathway?
- The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.
- And on January 29: A Framework for Safe Storming
- The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout are available in six ebooks:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
- Your stuff is brilliant! Thank you!
- You and Scott Adams both secretly work here, right?
- I really enjoy my weekly newsletters. I appreciate the quick read.
- A sort of Dr. Phil for Management!
- …extremely accurate, inspiring and applicable to day-to-day … invaluable.
- More