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
- 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 welcomeWould you like to see your comments posted here? rbrenJcUAhAcbDBsYTyQbner@ChaccDykMXwCRgGUsqeLoCanyon.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.
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.
More articles on Personal, Team, and Organizational Effectiveness:
- Excuses, Excuses
- When a goal remains unaccomplished, we sometimes tell ourselves that we understand why. And sometimes
we do. But at other times, we're just fooling ourselves.
- When Stress Strikes
- Most of what we know about person-to-person communication applies when levels of stress are low. But
when stress is high, as it is in emergencies, we're more likely to make mistakes. Knowing those mistakes
in advance can be helpful in avoiding them.
- One Cost of Split Assignments
- Sometimes management practices have unintended consequences. To reduce costs, we keep staff ranks thin,
but that leads to split assignments for those with rare skills. Here's one way split assignments can
lead to higher costs.
- Decisions: How Looping Back Helps
- Group decision-making often proceeds through a series of steps including forming a list of options,
researching them, ranking them, reducing them, and finally selecting one. Often, this linear approach
yields disappointing results. Why?
- Solutions as Found Art
- Examining the most innovative solutions we've developed for difficult problems, we often find that they
aren't purely new. Many contain pieces of familiar ideas and techniques combined together in new ways.
Accepting this as a starting point can change our approach to problem solving.
Forthcoming issues of Point Lookout
- Coming May 31: Unresponsive Suppliers: III
- When suppliers have a customer orientation, we can usually depend on them. But government suppliers are a special case. Available here and by RSS on May 31.
- And on June 7: The Knowledge One-Upmanship Game
- The Knowledge One-Upmanship Game is a pattern of group behavior in the form of a contest to determine which player knows the most arcane fact. It can seem like innocent fun, but it can disrupt a team's ability to collaborate. Available here and by RSS on June 7.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenOwVoBuAnCnLUXrufner@ChacZVaPOFaQguhOkpfaoCanyon.com or (617) 491-6289, 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, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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 words in your inbox in one hour. License any article from this Web site. More info
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's an upcoming date
for this program:
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- The Race to the South Pole: Ten Lessons for Project Managers
- On 14 December 1911, four men led by Roald
Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen
had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished.
As historical drama, why this happened is interesting enough, but to organizational leaders, business
analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read
more about this program. Here's an upcoming date for this program:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street, Rocky Hill, CT 06067: September 20, Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- 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.