<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: More Disturbing News About HP&#8230;</title>
	<atom:link href="http://www.credoadvisors.com/blog/business-ethics/more-disturbing-news-about-hp/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.credoadvisors.com/blog/business-ethics/more-disturbing-news-about-hp/</link>
	<description>Credo Advisors Consulting Blog: Business Ethics &#038; Corporate Social Responsibility</description>
	<pubDate>Tue, 06 Jan 2009 13:12:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Peter Begley</title>
		<link>http://www.credoadvisors.com/blog/business-ethics/more-disturbing-news-about-hp/#comment-1512</link>
		<dc:creator>Peter Begley</dc:creator>
		<pubDate>Sun, 01 Oct 2006 16:40:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.credoadvisors.com/blog/business-ethics/more-disturbing-news-about-hp/#comment-1512</guid>
		<description>What I find striking is that there are quite a few &lt;em&gt;reasonable&lt;/em&gt; ways in which the "leak" issue could have been dealt with. The most reasonable and ethical, from my perspective, would have been a very open discussion within the board. 

Presumably, if the members were truly taking their fiduciary duties into consideration,  an open investigation, authorized by the board and conducted by an independent committee, would have been a possible outcome. No sneaking. No "pretexting." No slinking around and violating privacy laws. Compare the possible damage that scenario would have caused (short-term bad press) versus the situation HP now faces (pitiful scandal and tons of bad press).</description>
		<content:encoded><![CDATA[<p>What I find striking is that there are quite a few <em>reasonable</em> ways in which the &#8220;leak&#8221; issue could have been dealt with. The most reasonable and ethical, from my perspective, would have been a very open discussion within the board. </p>
<p>Presumably, if the members were truly taking their fiduciary duties into consideration,  an open investigation, authorized by the board and conducted by an independent committee, would have been a possible outcome. No sneaking. No &#8220;pretexting.&#8221; No slinking around and violating privacy laws. Compare the possible damage that scenario would have caused (short-term bad press) versus the situation HP now faces (pitiful scandal and tons of bad press).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Schneider</title>
		<link>http://www.credoadvisors.com/blog/business-ethics/more-disturbing-news-about-hp/#comment-1498</link>
		<dc:creator>John Schneider</dc:creator>
		<pubDate>Wed, 27 Sep 2006 02:04:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.credoadvisors.com/blog/business-ethics/more-disturbing-news-about-hp/#comment-1498</guid>
		<description>One of the more troubling aspects of the HP fiasco is that it points to the absence of trust that exist at the highest level of corporate governance. In this particular case, you have a board president indulging in unethical behavior in order to find out which board member or members were speaking with the press. If I were a shareholder, I would appreciate the fact that board matters are being brought to public light. After all, it wasn't like company secrets were being compromised.</description>
		<content:encoded><![CDATA[<p>One of the more troubling aspects of the HP fiasco is that it points to the absence of trust that exist at the highest level of corporate governance. In this particular case, you have a board president indulging in unethical behavior in order to find out which board member or members were speaking with the press. If I were a shareholder, I would appreciate the fact that board matters are being brought to public light. After all, it wasn&#8217;t like company secrets were being compromised.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
