<?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: Assessing and being held responsible for the cost of bad decisions</title>
	<atom:link href="http://blog.tmorris.net/assessing-and-being-held-responsible-for-the-cost-of-bad-decisions/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tmorris.net/assessing-and-being-held-responsible-for-the-cost-of-bad-decisions/</link>
	<description>The weblog of Tony Morris</description>
	<pubDate>Tue, 07 Feb 2012 18:39:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Ivo</title>
		<link>http://blog.tmorris.net/assessing-and-being-held-responsible-for-the-cost-of-bad-decisions/#comment-34661</link>
		<dc:creator>Ivo</dc:creator>
		<pubDate>Mon, 30 Mar 2009 09:28:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tmorris.net/?p=589#comment-34661</guid>
		<description>Warn early and warn often, in writing. 

That way, When you are held accountable, you can point out exactly when you requested more information/clarification/had questions, when you reminded them of that, when you pointed out an answer was insufficient, when you argued against certain decisions, etc. If you need to take the job, either because your boss says so or because you need the money, that is the only way to document the process. An extremely positive side effect is that you stay in constant communication with the parties involved and they see what you are doing and why. They can never feign ignorance that involved company X was being uncooperative, that client-representative Y didn't provide clear answers, etc. Communication takes time, but it is well worth it, even if you are not going to need the records to be able to point out what went wrong.

I've seen a former colleague of mine, that has gone solo, use this approach to great effect.</description>
		<content:encoded><![CDATA[<p>Warn early and warn often, in writing. </p>
<p>That way, When you are held accountable, you can point out exactly when you requested more information/clarification/had questions, when you reminded them of that, when you pointed out an answer was insufficient, when you argued against certain decisions, etc. If you need to take the job, either because your boss says so or because you need the money, that is the only way to document the process. An extremely positive side effect is that you stay in constant communication with the parties involved and they see what you are doing and why. They can never feign ignorance that involved company X was being uncooperative, that client-representative Y didn&#8217;t provide clear answers, etc. Communication takes time, but it is well worth it, even if you are not going to need the records to be able to point out what went wrong.</p>
<p>I&#8217;ve seen a former colleague of mine, that has gone solo, use this approach to great effect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan</title>
		<link>http://blog.tmorris.net/assessing-and-being-held-responsible-for-the-cost-of-bad-decisions/#comment-34652</link>
		<dc:creator>Jan</dc:creator>
		<pubDate>Mon, 30 Mar 2009 05:14:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tmorris.net/?p=589#comment-34652</guid>
		<description>Hi Tony,
those cases are really unfortunate. I have been in such a situation a couple of times and in the end the only thing helped was a) good documentation on the course of the project (and who made which decisions at which point) and b) to escalate the problems with bad desisions early to the project management (and document that).
If you're the last in a chain it's always difficult to prove that you knew the problems all the time and you just tried to comply. Better act early and risk trouble during the project than taking the full blow in the end.
Best regards, --- Jan.</description>
		<content:encoded><![CDATA[<p>Hi Tony,<br />
those cases are really unfortunate. I have been in such a situation a couple of times and in the end the only thing helped was a) good documentation on the course of the project (and who made which decisions at which point) and b) to escalate the problems with bad desisions early to the project management (and document that).<br />
If you&#8217;re the last in a chain it&#8217;s always difficult to prove that you knew the problems all the time and you just tried to comply. Better act early and risk trouble during the project than taking the full blow in the end.<br />
Best regards, &#8212; Jan.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Smart</title>
		<link>http://blog.tmorris.net/assessing-and-being-held-responsible-for-the-cost-of-bad-decisions/#comment-34650</link>
		<dc:creator>Robert Smart</dc:creator>
		<pubDate>Mon, 30 Mar 2009 03:17:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tmorris.net/?p=589#comment-34650</guid>
		<description>Hi Tony, I always enjoy all your comments on a wide range of matters. I can't answer this question but I'm interested in learning about consulting since I might try to do a bit (in the simpler realm of jQuery-JSON-AppEngine development). I used to work in a research organization (though by the time I'd joined they'd changed the spelling to organisation). We had various groups with useful skills and we tried to raise money on the side by consulting. Our clients would look at our research groups and almost invariably say: "Artificial Intelligence: that's what we need". They assumed that this would be able to solve their problem, even though they couldn't describe what their problem was...</description>
		<content:encoded><![CDATA[<p>Hi Tony, I always enjoy all your comments on a wide range of matters. I can&#8217;t answer this question but I&#8217;m interested in learning about consulting since I might try to do a bit (in the simpler realm of jQuery-JSON-AppEngine development). I used to work in a research organization (though by the time I&#8217;d joined they&#8217;d changed the spelling to organisation). We had various groups with useful skills and we tried to raise money on the side by consulting. Our clients would look at our research groups and almost invariably say: &#8220;Artificial Intelligence: that&#8217;s what we need&#8221;. They assumed that this would be able to solve their problem, even though they couldn&#8217;t describe what their problem was&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: trav</title>
		<link>http://blog.tmorris.net/assessing-and-being-held-responsible-for-the-cost-of-bad-decisions/#comment-34649</link>
		<dc:creator>trav</dc:creator>
		<pubDate>Mon, 30 Mar 2009 03:10:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tmorris.net/?p=589#comment-34649</guid>
		<description>If your project is failing you're going to suffer a loss of face, it's unavoidable.

When you say "accept responsibility for this failure" do you mean there is not going to be a post morteim examination to determine what could have been done better?

I'm relatively inexperienced so I haven't had to be the 'head guy' on a failed project yet, but if I was head guy on a project that failed, regardless of who's fault it was, I'd want to figure out if there's any way that it could have been made a success.

Given your above statements that the intermediary was incapable of making correct decisions (or enough of them) then was it possible / will it be possible in future to have someone else make the decisions?
Is it possible to have a successful project while ignoring their decisions?

If the answer to those two questions is no, then it would imply that it's simply not possible for a project undertaken under those circumstances to be successful, in which case everyone who took part is equally responsible in my opinion, but more importantly, you've learned something and can hopefully avoid entering into such doomed propositions in the future.</description>
		<content:encoded><![CDATA[<p>If your project is failing you&#8217;re going to suffer a loss of face, it&#8217;s unavoidable.</p>
<p>When you say &#8220;accept responsibility for this failure&#8221; do you mean there is not going to be a post morteim examination to determine what could have been done better?</p>
<p>I&#8217;m relatively inexperienced so I haven&#8217;t had to be the &#8216;head guy&#8217; on a failed project yet, but if I was head guy on a project that failed, regardless of who&#8217;s fault it was, I&#8217;d want to figure out if there&#8217;s any way that it could have been made a success.</p>
<p>Given your above statements that the intermediary was incapable of making correct decisions (or enough of them) then was it possible / will it be possible in future to have someone else make the decisions?<br />
Is it possible to have a successful project while ignoring their decisions?</p>
<p>If the answer to those two questions is no, then it would imply that it&#8217;s simply not possible for a project undertaken under those circumstances to be successful, in which case everyone who took part is equally responsible in my opinion, but more importantly, you&#8217;ve learned something and can hopefully avoid entering into such doomed propositions in the future.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

