Have you ever had problems meeting a schedule because of the nonresponsiveness of people outside your department, outside your division, or outside your company? When your priorities differ from the priorities of the people you depend on, your work and your projects can suffer. Sometimes this can feel like a trap.
When your priorities differ
from the priorities
of collaborators,
projects can sufferI've felt trapped many times. And I've learned that it isn't really a trap, though it can feel like one. Here are some tips for finding your way out of the trap of the recalcitrant collaborator.
- Find out what's happening
- Have a conversation with the noncollaborator, and explain the situation as you see it. Try to find out three things: what's preventing cooperation, when the problem might end, and what it would take to make it happen earlier.
- Sometimes the answers aren't forthcoming, but when they are, the information can be useful and it might even be a basis for joint problem solving.
- Gather intelligence about patterns
- Find out what you can about recent history. Is there a pattern of difficulty between your team and theirs? Or is the pattern more widespread, affecting many others who work with them?
- If some organizational elements get preferential attention, the resolution of the problem will likely involve politics. On the other hand, if your experience is universal, a more mechanical issue might be the cause.
- Give your noncollaborator a last chance
- Have a conversation with the noncollaborator before you inform your boss. Explain that because of the schedule impact, you're compelled to inform your boss of the situation as you understand it.
- Sometimes this helps to persuade the noncollaborator to collaborate. And sometimes, it's seen as a threat, gravely damaging your relationship. If you don't tell the noncollaborator beforehand, though, you also risk damaging the relationship. Be judicious about this tactic.
- Keep you boss informed
- If your boss expects progress, and you're falling behind, keep him or her informed. Without asking for help or advice, explain what you know about the problem in a "heads up" conversation or a series of such conversations.
- When you explain the problem, your boss might offer advice or assistance. Usually, you're free to accept or decline, but unless you have some plan to resolve the problem, accept.
- Ask for advice
- Ask colleagues for advice first, and then ask your boss. Some will have bad advice, some no advice, and some great advice. Caveat emptor.
- Be circumspect about asking your boss for advice — you'll have to follow it.
When everything you know how to do has failed, ask your boss for help, especially if you sense that the problem resides somewhere above you in the org chart. Your boss might decline, or might be unable to help, but if the problem isn't yours, pretending that it is probably won't work. Top Next Issue
Is every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. More info
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:
- Think Before You PowerPoint
- Microsoft PowerPoint is a useful tool. Many of us use it daily to create presentations that guide meetings
or focus discussions. Like all tools, it can be abused — it can be a substitute for constructive
dialog, and even for thought. What can we do about PowerPoint abuse?
- Email Antics: I
- Nearly everyone I know complains that email is a time waster. Yet much of the problem results from our
own actions. If you're looking around for some New Year's resolutions to make, here are some ideas,
in this Part I of a little catalog of things we do that help waste our time.
- Embolalia and Stuff Like That: II
- Continuing our exploration of embolalia — filler syllables, filler words, and filler phrases —
let us examine the more complex forms. Some of them are so complex that they appear to be actual content,
even when what they contain is little more than "um."
- Office Automation
- Desktop computers, laptop computers, and tablets have automation capabilities that can transform our
lives, but few of us use them. Why not? What can we do about that?
- Red Flags: III
- Early signs of troubles in collaborations include toxic conflict, elevated turnover, and anti-patterns
in communication. But among the very earliest red flags are abuses of power. They're more significant
than other red flags because abuses of power can convert any collaboration into a morass of destructive
politics.
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