<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for JT Pedersen</title>
	<atom:link href="http://jtpedersen.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://jtpedersen.net</link>
	<description>Innovative Business Leadership</description>
	<lastBuildDate>Thu, 10 May 2012 22:33:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Do You Artificially Constrain Yourself? by Constraints Add Color to Your Life &#124; JT Pedersen</title>
		<link>http://jtpedersen.net/2012/04/11/do-you-artificially-constrain-yourself/comment-page-1/#comment-666</link>
		<dc:creator>Constraints Add Color to Your Life &#124; JT Pedersen</dc:creator>
		<pubDate>Thu, 10 May 2012 22:33:45 +0000</pubDate>
		<guid isPermaLink="false">http://jtpedersen.net/?p=3864#comment-666</guid>
		<description>[...] month, I wrote about the topic of constraints (Do You Artificially Constrain Yourself?).  The topic&#8217;s not discussed that often, so I was mildly surprised today, when I came across [...]</description>
		<content:encoded><![CDATA[<p>[...] month, I wrote about the topic of constraints (Do You Artificially Constrain Yourself?).  The topic&#8217;s not discussed that often, so I was mildly surprised today, when I came across [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Deadlines By Fiat, Agile, &amp; Disaster! by JT</title>
		<link>http://jtpedersen.net/2012/05/03/deadlines-by-fiat-agile-disaster/comment-page-1/#comment-656</link>
		<dc:creator>JT</dc:creator>
		<pubDate>Tue, 08 May 2012 17:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://jtpedersen.net/?p=3996#comment-656</guid>
		<description>&lt;p&gt;&lt;strong&gt;Hello Bruce,&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Thank you for your note.&#160; I can appreciate the practical reality you outline, such as managers doing &#039;bad math.&#039;&lt;/p&gt;

&lt;p&gt;I did like your point about constraining projects as well.&#160; Sometimes you do need to simply limit the amount of resource you&#039;re prepared to invest in a given effort.&#160; Failure to realize the importance has led to way too many never-ending projects.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p><strong>Hello Bruce,</strong></p>
<p>Thank you for your note.&#160; I can appreciate the practical reality you outline, such as managers doing &#8216;bad math.&#8217;</p>
<p>I did like your point about constraining projects as well.&#160; Sometimes you do need to simply limit the amount of resource you&#8217;re prepared to invest in a given effort.&#160; Failure to realize the importance has led to way too many never-ending projects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Deadlines By Fiat, Agile, &amp; Disaster! by JT</title>
		<link>http://jtpedersen.net/2012/05/03/deadlines-by-fiat-agile-disaster/comment-page-1/#comment-655</link>
		<dc:creator>JT</dc:creator>
		<pubDate>Tue, 08 May 2012 17:11:55 +0000</pubDate>
		<guid isPermaLink="false">http://jtpedersen.net/?p=3996#comment-655</guid>
		<description>&lt;p&gt;&lt;strong&gt;Hello Deb,&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Thank you for your note.&#160; Reading it, you helped underscore another observation many seem to miss: Agile&#039;s principles in many ways can be applied to disciplines &lt;em&gt;beyond&lt;/em&gt; software development.&lt;/p&gt;

&lt;p&gt;Glad it had some take-aways for you.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p><strong>Hello Deb,</strong></p>
<p>Thank you for your note.&#160; Reading it, you helped underscore another observation many seem to miss: Agile&#8217;s principles in many ways can be applied to disciplines <em>beyond</em> software development.</p>
<p>Glad it had some take-aways for you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Deadlines By Fiat, Agile, &amp; Disaster! by Deb Nystrom, (@RevelnConsults)</title>
		<link>http://jtpedersen.net/2012/05/03/deadlines-by-fiat-agile-disaster/comment-page-1/#comment-654</link>
		<dc:creator>Deb Nystrom, (@RevelnConsults)</dc:creator>
		<pubDate>Tue, 08 May 2012 16:35:37 +0000</pubDate>
		<guid isPermaLink="false">http://jtpedersen.net/?p=3996#comment-654</guid>
		<description>Cool JT.  I love hearing about the Agile group discussions as it is informative to learn of the Iron Triangle and your perspective on Agile &amp; communication.   The continuing intrigue I have with Agile is the capacity for adapting, flexing while staying focused on a clear goal, that itself may even change.  Living productively in responsive tension, is also what I like to call it.

From my org. development systems side, dealing with traditional management efficiency thinking can be one of the big wrenches in the works, with some rigidity that can lead to disaster.  In fact, managers can create their own silos of &quot;being managerial&quot; when what is needed is leadership.

A built in culture of flex (like Michigan Steelcase focused on an idea culture), that is respectful of those who do the work, two way feedback, and experience with what works (no phone ringing on software problem, via our local Menlo Innovations) - is one take away from mulling over your post.  I like that I&#039;ve heard Rich Sheridan rattle off the typical problems of new specs, changing expectations and THEN how Menlo has become so very clear about the boundaries and guidelines to deal with such project buster behaviors.   Such behaviors are also legion within large organizations who are internal customers of each other.   Boundaries and guidelines, mutually agreed upon, are still important, even more so.

I like that smart teams DO create  checklists.  Pilots use them.  They ARE useful to check our ego and blind spos.  They help create better boundaries and guidelines conversations = communication = which can evolve to thinking systemically &amp; just being team smart.    In a VUCA* world, that means agility with good communication to me.   Thanks again for getting me thinking about agility and what it really means.

*VUCA = volatile, uncertain, complex and ambiguous, a term coined by the US Army War College in the weeks before September 11, 2001.</description>
		<content:encoded><![CDATA[<p>Cool JT.  I love hearing about the Agile group discussions as it is informative to learn of the Iron Triangle and your perspective on Agile &amp; communication.   The continuing intrigue I have with Agile is the capacity for adapting, flexing while staying focused on a clear goal, that itself may even change.  Living productively in responsive tension, is also what I like to call it.</p>
<p>From my org. development systems side, dealing with traditional management efficiency thinking can be one of the big wrenches in the works, with some rigidity that can lead to disaster.  In fact, managers can create their own silos of &#8220;being managerial&#8221; when what is needed is leadership.</p>
<p>A built in culture of flex (like Michigan Steelcase focused on an idea culture), that is respectful of those who do the work, two way feedback, and experience with what works (no phone ringing on software problem, via our local Menlo Innovations) &#8211; is one take away from mulling over your post.  I like that I&#8217;ve heard Rich Sheridan rattle off the typical problems of new specs, changing expectations and THEN how Menlo has become so very clear about the boundaries and guidelines to deal with such project buster behaviors.   Such behaviors are also legion within large organizations who are internal customers of each other.   Boundaries and guidelines, mutually agreed upon, are still important, even more so.</p>
<p>I like that smart teams DO create  checklists.  Pilots use them.  They ARE useful to check our ego and blind spos.  They help create better boundaries and guidelines conversations = communication = which can evolve to thinking systemically &amp; just being team smart.    In a VUCA* world, that means agility with good communication to me.   Thanks again for getting me thinking about agility and what it really means.</p>
<p>*VUCA = volatile, uncertain, complex and ambiguous, a term coined by the US Army War College in the weeks before September 11, 2001.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Deadlines By Fiat, Agile, &amp; Disaster! by Bruce McCarthy</title>
		<link>http://jtpedersen.net/2012/05/03/deadlines-by-fiat-agile-disaster/comment-page-1/#comment-651</link>
		<dc:creator>Bruce McCarthy</dc:creator>
		<pubDate>Fri, 04 May 2012 00:48:02 +0000</pubDate>
		<guid isPermaLink="false">http://jtpedersen.net/?p=3996#comment-651</guid>
		<description>Hi JT,

I have certainly seen my share of managers who seem to forget basic math: that you can&#039;t, for example, take a team with the capacity to handle two projects at once and ask them to handle another without either eliminating one or slowing them all down. As you say, this usually stems from a lack of communication.

Corporate management is typically bad at communicating so it&#039;s up to us as leaders in product development to keep telling them what we&#039;re doing, why, and when we expect to be done. Then we&#039;ve provided all the necessary facts for a conversation where they want something more or sooner. We can always respond with some variation of &quot;ok, to provide that, what do you NOT want to do?&quot;

Separately, I think it&#039;s worth noting that there is nothing wrong with an arbitrary deadline. Sometimes they are just a business reality. We have to ship for a public event or a customer deadline. It can also be useful to set a deadline to avoid over-engineered solutions. Sometimes it just makes sense to allocate some specific number of person-weeks to a project and no more. 

It&#039;s not arbitrary deadlines per se that lead to disaster. It&#039;s setting them without acknowledging that the other parts of the triangle have to adjust in concert. You can pick a deadline, you just can&#039;t also dictate the budget and the scope.</description>
		<content:encoded><![CDATA[<p>Hi JT,</p>
<p>I have certainly seen my share of managers who seem to forget basic math: that you can&#8217;t, for example, take a team with the capacity to handle two projects at once and ask them to handle another without either eliminating one or slowing them all down. As you say, this usually stems from a lack of communication.</p>
<p>Corporate management is typically bad at communicating so it&#8217;s up to us as leaders in product development to keep telling them what we&#8217;re doing, why, and when we expect to be done. Then we&#8217;ve provided all the necessary facts for a conversation where they want something more or sooner. We can always respond with some variation of &#8220;ok, to provide that, what do you NOT want to do?&#8221;</p>
<p>Separately, I think it&#8217;s worth noting that there is nothing wrong with an arbitrary deadline. Sometimes they are just a business reality. We have to ship for a public event or a customer deadline. It can also be useful to set a deadline to avoid over-engineered solutions. Sometimes it just makes sense to allocate some specific number of person-weeks to a project and no more. </p>
<p>It&#8217;s not arbitrary deadlines per se that lead to disaster. It&#8217;s setting them without acknowledging that the other parts of the triangle have to adjust in concert. You can pick a deadline, you just can&#8217;t also dictate the budget and the scope.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Been Quiet Recently&#8211;Here&#8217;s Why by Andrew Stein</title>
		<link>http://jtpedersen.net/2012/04/28/been-quiet-recently-heres-why/comment-page-1/#comment-650</link>
		<dc:creator>Andrew Stein</dc:creator>
		<pubDate>Sun, 29 Apr 2012 22:23:25 +0000</pubDate>
		<guid isPermaLink="false">http://jtpedersen.net/?p=3927#comment-650</guid>
		<description>Jeremiah Johnson:       Just where is it I could find bear, beaver, and other critters worth cash money when skinned? 
Robidoux:       Ride due west as the sun sets. Turn left at the Rocky Mountains. 

Bear Claw Chris Lapp:       You&#039;ve come far pilgrim. 
Jeremiah Johnson:       Feels like far. 
Bear Claw Chris Lapp:       Were it worth the trouble? 
Jeremiah Johnson:       What trouble? 

Bear Claw Chris Lapp:       Can you skin Griz? 
Jeremiah Johnson:       I can skin&#039; em as fast as you can catch&#039; em. 
[Bear Claw runs through the cabin with a huge grizzly bear close behind and jumps out the back window] 
Bear Claw Chris Lapp:       Skin that one, pilgrim, and I&#039;ll get you another! 

Andrew:       JT, rule number one..., go west, and never look back!  avoid the &quot;griz.&quot;</description>
		<content:encoded><![CDATA[<p>Jeremiah Johnson:       Just where is it I could find bear, beaver, and other critters worth cash money when skinned?<br />
Robidoux:       Ride due west as the sun sets. Turn left at the Rocky Mountains. </p>
<p>Bear Claw Chris Lapp:       You&#8217;ve come far pilgrim.<br />
Jeremiah Johnson:       Feels like far.<br />
Bear Claw Chris Lapp:       Were it worth the trouble?<br />
Jeremiah Johnson:       What trouble? </p>
<p>Bear Claw Chris Lapp:       Can you skin Griz?<br />
Jeremiah Johnson:       I can skin&#8217; em as fast as you can catch&#8217; em.<br />
[Bear Claw runs through the cabin with a huge grizzly bear close behind and jumps out the back window]<br />
Bear Claw Chris Lapp:       Skin that one, pilgrim, and I&#8217;ll get you another! </p>
<p>Andrew:       JT, rule number one&#8230;, go west, and never look back!  avoid the &#8220;griz.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Not Comfy, Feeling Uncomfortable? by JT</title>
		<link>http://jtpedersen.net/2012/04/17/not-comfy-feeling-uncomfortable/comment-page-1/#comment-641</link>
		<dc:creator>JT</dc:creator>
		<pubDate>Wed, 18 Apr 2012 18:40:51 +0000</pubDate>
		<guid isPermaLink="false">http://jtpedersen.net/?p=3892#comment-641</guid>
		<description>&lt;p&gt;&lt;strong&gt;Andrew, Alan,&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I appreciate your both sharing your insights.&#160; Your comments help expand the base premise in productive directions.&#160; Andrew, your comment on the Leader being stable externally, the guidepost for those around them regardless their internal turmoil, is important.&#160; It becomes easier as one becomes more experienced dealing with uncertainty.&lt;/p&gt;

&lt;p&gt;Alan, the need to see beyond ourselves is important.&#160; Reflecting on your comment, I have to agree.&#160; I think one&#039;s ego is definitely an impediment. Viewing one&#039;s self as a pinnacle of achievement, precludes the desire, the necessity to go beyond.&lt;/p&gt;

&lt;p&gt;Thank you both,&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;JT…&lt;/strong&gt;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p><strong>Andrew, Alan,</strong></p>
<p>I appreciate your both sharing your insights.&#160; Your comments help expand the base premise in productive directions.&#160; Andrew, your comment on the Leader being stable externally, the guidepost for those around them regardless their internal turmoil, is important.&#160; It becomes easier as one becomes more experienced dealing with uncertainty.</p>
<p>Alan, the need to see beyond ourselves is important.&#160; Reflecting on your comment, I have to agree.&#160; I think one&#8217;s ego is definitely an impediment. Viewing one&#8217;s self as a pinnacle of achievement, precludes the desire, the necessity to go beyond.</p>
<p>Thank you both,</p>
<p><strong>JT…</strong></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Not Comfy, Feeling Uncomfortable? by JT</title>
		<link>http://jtpedersen.net/2012/04/17/not-comfy-feeling-uncomfortable/comment-page-1/#comment-640</link>
		<dc:creator>JT</dc:creator>
		<pubDate>Wed, 18 Apr 2012 18:40:48 +0000</pubDate>
		<guid isPermaLink="false">http://jtpedersen.net/?p=3892#comment-640</guid>
		<description>&lt;p&gt;&lt;strong&gt;Andrew, Alan,&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I appreciate your both sharing your insights.&#160; Your comments help expand the base premise in productive directions.&#160; Andrew, your comment on thee Leader being stable externally, the guidepost for those around them regardless their internal turmoil, is important.&#160; It becomes easier as one becomes more experienced dealing with uncertainty.&lt;/p&gt;

&lt;p&gt;Alan, the need to see beyond ourselves is important.&#160; Reflecting on your comment, I have to agree.&#160; I think one&#039;s ego is definitely an impediment. Viewing one&#039;s self as a pinnacle of achievement, precludes the desire, the necessity to go beyond.&lt;/p&gt;

&lt;p&gt;Thank you both,&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;JT…&lt;/strong&gt;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p><strong>Andrew, Alan,</strong></p>
<p>I appreciate your both sharing your insights.&#160; Your comments help expand the base premise in productive directions.&#160; Andrew, your comment on thee Leader being stable externally, the guidepost for those around them regardless their internal turmoil, is important.&#160; It becomes easier as one becomes more experienced dealing with uncertainty.</p>
<p>Alan, the need to see beyond ourselves is important.&#160; Reflecting on your comment, I have to agree.&#160; I think one&#8217;s ego is definitely an impediment. Viewing one&#8217;s self as a pinnacle of achievement, precludes the desire, the necessity to go beyond.</p>
<p>Thank you both,</p>
<p><strong>JT…</strong></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Not Comfy, Feeling Uncomfortable? by Alan Shelton</title>
		<link>http://jtpedersen.net/2012/04/17/not-comfy-feeling-uncomfortable/comment-page-1/#comment-639</link>
		<dc:creator>Alan Shelton</dc:creator>
		<pubDate>Wed, 18 Apr 2012 18:16:12 +0000</pubDate>
		<guid isPermaLink="false">http://jtpedersen.net/?p=3892#comment-639</guid>
		<description>To me the important recognition in this piece is that there comes a time where growth is harder to come by. Once we have learned our skill sets and our leadership becomes more internal. We trade the discomfort of not knowing our stuff for the discomfort of not knowing ourself. Many never recognize this distinction. But if we do, as JT did, we begin to seek to stand in the unknown. For we see that our ego definition, the who we thought we were, is now an impediment. Our wisdom needs to come from a bigger version of ourself that includes the unknown.

And this is where Andrew Stein hits it on the head. Great leaders are confident. Not just in their content knowledge, but in their ability to stand in the unknown and lead with that vulnerability fully embraced. So on the inside they are indeed uncomfortable, but much like all who charge into the unknown they actually have been there before.</description>
		<content:encoded><![CDATA[<p>To me the important recognition in this piece is that there comes a time where growth is harder to come by. Once we have learned our skill sets and our leadership becomes more internal. We trade the discomfort of not knowing our stuff for the discomfort of not knowing ourself. Many never recognize this distinction. But if we do, as JT did, we begin to seek to stand in the unknown. For we see that our ego definition, the who we thought we were, is now an impediment. Our wisdom needs to come from a bigger version of ourself that includes the unknown.</p>
<p>And this is where Andrew Stein hits it on the head. Great leaders are confident. Not just in their content knowledge, but in their ability to stand in the unknown and lead with that vulnerability fully embraced. So on the inside they are indeed uncomfortable, but much like all who charge into the unknown they actually have been there before.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Not Comfy, Feeling Uncomfortable? by Andrew Stein</title>
		<link>http://jtpedersen.net/2012/04/17/not-comfy-feeling-uncomfortable/comment-page-1/#comment-638</link>
		<dc:creator>Andrew Stein</dc:creator>
		<pubDate>Wed, 18 Apr 2012 12:09:59 +0000</pubDate>
		<guid isPermaLink="false">http://jtpedersen.net/?p=3892#comment-638</guid>
		<description>For me, there are two factors to managing the stress that being uncomfortable creates is to realize two things. The first factor is that it is really the other guy&#039;s issue. Whether it&#039;s a hiring manager, an HR screen, or your boss doing it to you. One&#039;s uncomfortable feeling is a function of worrying that the other guy is thinking, grading, judging you. If you have made the right choice or decision, go forward, execute, learn, and if you fail, learn from that. Forget about the judging, that will happen no matter what decision or choice you make.

The second factor is confidence, and this is key. The difference between an average leader and a great leader is the confidence they have in their direction, the trust around them that builds from that confidence, and the willingness to course-correct as soon as necessary - and fully accepting the responsibility for the course correction.  Average is to be tentative, make excuses and pretend that failure didn&#039;t/doesn&#039;t ever happen. 

Great leaders and people are always confident and never tentative. They appear to others as being comfortable, with being wrong, unsure, or uncomfortable. Inside, they may be deeply uncomfortable, but on the outside, they know that people are looking at them for leadership. Their confidence is what sets them apart when in an uncomfortable situation.</description>
		<content:encoded><![CDATA[<p>For me, there are two factors to managing the stress that being uncomfortable creates is to realize two things. The first factor is that it is really the other guy&#8217;s issue. Whether it&#8217;s a hiring manager, an HR screen, or your boss doing it to you. One&#8217;s uncomfortable feeling is a function of worrying that the other guy is thinking, grading, judging you. If you have made the right choice or decision, go forward, execute, learn, and if you fail, learn from that. Forget about the judging, that will happen no matter what decision or choice you make.</p>
<p>The second factor is confidence, and this is key. The difference between an average leader and a great leader is the confidence they have in their direction, the trust around them that builds from that confidence, and the willingness to course-correct as soon as necessary &#8211; and fully accepting the responsibility for the course correction.  Average is to be tentative, make excuses and pretend that failure didn&#8217;t/doesn&#8217;t ever happen. </p>
<p>Great leaders and people are always confident and never tentative. They appear to others as being comfortable, with being wrong, unsure, or uncomfortable. Inside, they may be deeply uncomfortable, but on the outside, they know that people are looking at them for leadership. Their confidence is what sets them apart when in an uncomfortable situation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

