Andrew stopped outside Jane's door and knocked on the doorframe. Her back to him, studying her screen, Jane must have somehow recognized Andrew's knock. "Andrew," she said without looking up. "One sec."
She half-stood, still holding the mouse and staring at the screen. Then she clicked, stood up straight, and turned to face him. "OK," she said. "Where to?"
"Courtyard," Andrew replied.
They walked silently to the elevator, rode it to One, crossed the lobby, went out into the brilliantly sunny courtyard, and sat down at an empty umbrella table. Jane still had her coffee mug in hand. She sipped.
"So…" she prompted him.
"This contract bothers me," Andrew began. "I'm a project manager. I don't know much about negotiating contracts. I'll probably do something dumb, but I'm not sure that's what bothers me."
Managing a project for which
you negotiated contracts
presents a conflict of interestAndrew wasn't sure, but Jane was. She'd been there. "Right," she began. "The real problem is that project managers shouldn't be negotiating contracts. It's a conflict of interest."
Jane's insight isn't widely shared, but she does raise a critical point. Project managers who must monitor day-to-day performance of contracts they personally negotiated have a potential conflict of interest. Here are some of the ways this conflict can appear.
- Vulnerability to time pressure
- Especially if negotiations drag on, the organization might apply pressure to the negotiator to bring negotiations to completion. For those project managers who are also the negotiators, this pressure can lead to a temptation to yield, based on a belief that we can "close the gap" through cleverness during project execution.
- When project manager and negotiator are separate people, the project manager can better represent the project's interests, insisting on what is actually required, and compelling more creative negotiation.
- Hidden cost transfers
- During negotiations, it's common to entice the vendor with the promise of work on future projects. But when the negotiator manages both the project at hand and the future project, this tactic amounts to a transfer of resources between the two projects. It distorts the costs of both, invalidating the metrics used to manage projects.
- When the negotiator and project managers are independent, each contract is more likely to stand on its own.
- Concealed contract flaws
- When there are flaws in the contract that become evident only during execution, and when the negotiator has gone on to become the project manager, it is the project manager who must report defects in the contract that he or she produced. It can be tempting to find a way to avoid reporting a flaw of one's own creation.
- When the negotiator and project manager are independent, contract flaws are more likely to be reported, and remedial action is possible.
Even considering whether or not we have a conflict of interest can be problematic. Since we don't want to believe we have a conflict of interest, we do. 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
Is your organization running at peak performance? If not, sometimes the design of its job descriptions could be the culprit? For some novel ideas for elevating performance in your organization, check out my tips book 52 Tips for Leaders of Project-Oriented Organizations.
Your comments are welcome
Would you like to see your comments posted here? rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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 Ethics at Work:
- Virtual Termination with Real Respect
- When we have to terminate someone who works at a remote site, sometimes there's a temptation to avoid
travel — to use email, phone, fax, or something else. They're all bad ideas. Terminating people
in person is not only a gesture of respect. It's good business.
- Approval Ploys
- If you approve or evaluate proposals or requests made by others, you've probably noticed patterns approval
seekers use to enhance their success rates. Here are some tactics approval seekers use.
- Some Truths About Lies: III
- Detecting lies by someone intent on misrepresentation is an important skill for executives, managers,
project managers, and just about anyone involved in knowledge-oriented organizations. Here's Part III
of our little collection of lie detection techniques.
- On Standing Aside
- Occasionally we're asked to participate in deliberations about issues relating to our work responsibilities.
Usually we respond in good faith. And sometimes we — or those around us — can't be certain
that we're responding in good faith. In those situations, we must stand aside.
- 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 Ethics at Work and Ethics at Work for more related articles.
Forthcoming issues of Point Lookout
- Coming December 11: White Water Rafting as a Metaphor for Group Development
- Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies better to development of some groups than to others. We can use a metaphor to explore how the model applies to Storming in task-oriented work groups. Available here and by RSS on December 11.
- And on December 18: Subgrouping and Conway's Law
- When task-oriented work groups address complex tasks, they might form subgroups to address subtasks. The structure of the subgroups and the order in which they form depend on the structure of the group's task and the sequencing of the subtasks. Available here and by RSS on December 18.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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
rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed