<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ProcurementAlert.com &#187; personnel</title>
	<atom:link href="http://www.procurementalert.com/tag/personnel/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.procurementalert.com</link>
	<description>Strong partnerships forge strong companies</description>
	<lastBuildDate>Fri, 22 Jul 2011 00:19:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>Procurement&#8217;s role in working out common problems</title>
		<link>http://www.procurementalert.com/procurements-role-in-working-out-common-problems/</link>
		<comments>http://www.procurementalert.com/procurements-role-in-working-out-common-problems/#comments</comments>
		<pubDate>Thu, 08 May 2008 15:09:12 +0000</pubDate>
		<dc:creator>Charlie Walker</dc:creator>
				<category><![CDATA[In this week's e-Newsletter]]></category>
		<category><![CDATA[Latest News & Views]]></category>
		<category><![CDATA[Procurement trends]]></category>
		<category><![CDATA[goal]]></category>
		<category><![CDATA[personnel]]></category>
		<category><![CDATA[procurement]]></category>

		<guid isPermaLink="false">http://www.procurementalert.com/?p=45</guid>
		<description><![CDATA[Butting heads: It&#8217;s happened to all of us, at one time or another. And the company or department is too small to avoid crossing paths. But who wants to spend the foreseeable future growling at each other? Well, there is a solution. It&#8217;s not waiting for the problem to go away or work itself out. [...]]]></description>
			<content:encoded><![CDATA[<p>Butting heads: It&#8217;s happened to all of us, at one time or another. <span id="more-45"></span>And the company or department is too small to avoid crossing paths. But who wants to spend the foreseeable future growling at each other?</p>
<p>Well, there is a solution. It&#8217;s not waiting for the problem to go away or work itself out. That ain&#8217;t gonna happen.</p>
<p>There is a way to confront the problem &#8212; and the person &#8212; in a calm, let&#8217;s-settle-this-now manner. You both have something in common: Seeing this matter resolved. That&#8217;s a good starting point. Use that starting point to open the door to sensible conversation. Then, there&#8217;s a seven-step plan for handling (and hopefully working out) the problem.</p>
<ol>
<li><span style="text-decoration: underline;">Fly solo</span>. It&#8217;s just you and the other person; no one else needs to be at the table.</li>
<li><span style="text-decoration: underline;">Define your goal</span>. Going into this, know what your problem is, and your goal for this interaction.</li>
<li><span style="text-decoration: underline;">Prepare yourself</span>. Make a list of what you&#8217;ll say to support your view of the problem. You don&#8217;t want to be fumbling for this in the middle of the meeting.</li>
<li><span style="text-decoration: underline;">What&#8217;s the worst that can happen?</span> Spend a few minutes jotting down how you expect the other person to react and what he or she might say. Writing out these concerns reduces the impact they can have on you.</li>
<li><span style="text-decoration: underline;">Making preparations</span>. Review your notes; write down examples of the behavior you&#8217;re going to talk about.</li>
<li><span style="text-decoration: underline;">Plan for privacy</span>. Choose a spot where neither of you will be interrupted.</li>
<li><span style="text-decoration: underline;">Begin the meeting</span>. Keys: Look the person in the eye; explain your view of the problem; give the other person a chance to speak and pay attention; have a back-and-forth discussion until you&#8217;ve both settled on a solution.</li>
</ol>
<p> Nobody said it would be easy. But you get better with practice. You also improve your own job performance by doing this, because you&#8217;ve &#8220;cleared the decks&#8221; and made it easier to focus on your procurement duties.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.procurementalert.com/procurements-role-in-working-out-common-problems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

