<?xml version="1.0" encoding="UTF-8"?><rss version="0.92">
<channel>
	<title>Performance Matters</title>
	<link>http://www.ktsprocess.com/highperformance</link>
	<description>High performance teams: Lower costs ahead of schedule</description>
	<lastBuildDate>Fri, 11 Feb 2011 22:38:36 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	<!-- generator="WordPress/3.0.3" -->

	<item>
		<title>Are they listening to you?</title>
		<description><![CDATA[Last week as I was discussing objectives with a group of engineering managers, I was reminded how that little voice in our head prevents us from listening. Some context: I look at objectives as having two parts: A purpose ( “why are we doing this work?”) and a Stop Criteria (“ how do we know <a href='http://www.ktsprocess.com/highperformance/2011/02/11/are-they-listening-to-you/'>[more]</a>]]></description>
		<link>http://www.ktsprocess.com/highperformance/2011/02/11/are-they-listening-to-you/</link>
			</item>
	<item>
		<title>Encouragement goes beyond catching people doing things right</title>
		<description><![CDATA[When I was a young manager, I read “The One-Minute Manager” by Blanchard and Johnson.  I learned to “manage by walking-around” and &#8220;catch people doing things right&#8221;. As a motivational tool, catching people doing things right is effective.  But it doesn’t work long term if all you is praise their results. I led the winning <a href='http://www.ktsprocess.com/highperformance/2010/06/11/encouragement-goes-beyond-catching-people-doing-things-right/'>[more]</a>]]></description>
		<link>http://www.ktsprocess.com/highperformance/2010/06/11/encouragement-goes-beyond-catching-people-doing-things-right/</link>
			</item>
	<item>
		<title>Risk Mitigation and the 5 Whys</title>
		<description><![CDATA[When doing risk analysis, engineers have no problem identifying potential problems – answering the “what could go wrong?” question.  The difficulty is with the mitigation plan – “How can we prevent it?” Going over this problem in many coaching sessions, I discovered one reason why this is so Engineers skip the middle step, of this <a href='http://www.ktsprocess.com/highperformance/2010/06/02/risk-mitigation-and-the-5-whys/'>[more]</a>]]></description>
		<link>http://www.ktsprocess.com/highperformance/2010/06/02/risk-mitigation-and-the-5-whys/</link>
			</item>
	<item>
		<title>Embracing Risk</title>
		<description><![CDATA[Most companies have risk management processes.  And most teams follow these processes fairly well.  Why is it, that with same risk management process, some teams succeed at avoiding big problems, and while other teams fail to do so repeatedly? I am sure there are many reasons – but I have noticed one that is not <a href='http://www.ktsprocess.com/highperformance/2010/05/21/embracing-risk/'>[more]</a>]]></description>
		<link>http://www.ktsprocess.com/highperformance/2010/05/21/embracing-risk/</link>
			</item>
	<item>
		<title>You are the leader – but not the master</title>
		<description><![CDATA[I have a received a few “raised eyebrows” comments about my statement that people don’t listen.  A manager said to me: “My people do listen to me”. Do they?  Or are you just lucky? As a young manager I used to think that what I said mattered. But it did not.  Sometimes it looked like <a href='http://www.ktsprocess.com/highperformance/2010/05/11/you-are-the-leader-but-not-the-master/'>[more]</a>]]></description>
		<link>http://www.ktsprocess.com/highperformance/2010/05/11/you-are-the-leader-but-not-the-master/</link>
			</item>
	<item>
		<title>Speaking at IEEE Pitsburgh on May 27</title>
		<description><![CDATA[I will be speaking in Pittsburgh on &#8220;Building High-Performance Engineering Teams&#8220;.  The event is organized by the SSIT section (Society for Social Implications of Technology)  and GOLD section (Graduates Of the Last Decade). The event is held at the Westinghouse Energy Center, Monroeville, PA (map) at 6h30 PM, Thursday May 27. Here&#8217;s a link to <a href='http://www.ktsprocess.com/highperformance/2010/05/05/speaking-at-ieee-pitsburgh-on-may-27/'>[more]</a>]]></description>
		<link>http://www.ktsprocess.com/highperformance/2010/05/05/speaking-at-ieee-pitsburgh-on-may-27/</link>
			</item>
	<item>
		<title>Ask or Judge &#8211; you must choose</title>
		<description><![CDATA[You can ask questions, or you can judge.  But you can’t do both.  You have to choose. I previously suggested asking questions about what your team will do, instead of telling them what to do (see: Ask, Don&#8217;t tell).   But some people find it difficult to get team members to explain their views in <a href='http://www.ktsprocess.com/highperformance/2010/04/28/ask-or-judge-you-must-choose/'>[more]</a>]]></description>
		<link>http://www.ktsprocess.com/highperformance/2010/04/28/ask-or-judge-you-must-choose/</link>
			</item>
	<item>
		<title>Stop looking at the score – stay on process</title>
		<description><![CDATA[On November 9th, 2006, the Rutgers football team was having a bad night – but they just kept “chopping wood”. It had started badly.  Louisville returned the opening kick-off for a touchdown.  Then Louisville could do no wrong getting 25 points before Rutgers would score on the last play before the half.  Going to the <a href='http://www.ktsprocess.com/highperformance/2010/04/25/stop-looking-at-the-score-%e2%80%93-stay-on-process/'>[more]</a>]]></description>
		<link>http://www.ktsprocess.com/highperformance/2010/04/25/stop-looking-at-the-score-%e2%80%93-stay-on-process/</link>
			</item>
	<item>
		<title>Asking leading questions won’t get you there</title>
		<description><![CDATA[Team leaders readily switch to question mode, once I demonstrate that their team does not understand the objective if they simply tell them.  This is why I recommend to Ask – don’t tell. But they raise a valid question: Isn’t it the Team Leader’s role to define the objective?  If we ask questions of team <a href='http://www.ktsprocess.com/highperformance/2010/04/18/asking-leading-questions-won%e2%80%99t-get-you-there/'>[more]</a>]]></description>
		<link>http://www.ktsprocess.com/highperformance/2010/04/18/asking-leading-questions-won%e2%80%99t-get-you-there/</link>
			</item>
	<item>
		<title>Are you responsible or simply accountable?</title>
		<description><![CDATA[The biggest fallacy I have encountered in corporations is the belief that we can assign responsibilities.  Responsibility is by choice – never by assignment. We can assign accountability, duties, even authority – but not responsibility. Think of a parent responsible for her child.  It’s a “no excuses” kind of responsibility. You can’t force this unto <a href='http://www.ktsprocess.com/highperformance/2010/04/09/are-you-responsible-or-simply-accountable/'>[more]</a>]]></description>
		<link>http://www.ktsprocess.com/highperformance/2010/04/09/are-you-responsible-or-simply-accountable/</link>
			</item>
</channel>
</rss>

