<?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 on: The UnLeadership Manifesto &#8211; making of the 21st century leader &#8211; part 1</title>
	<atom:link href="http://www.sastwingees.org/2008/07/26/the-unleadership-manifesto-making-of-the-21st-century-leader-part-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sastwingees.org/2008/07/26/the-unleadership-manifesto-making-of-the-21st-century-leader-part-1/</link>
	<description>Knowledge is Scrumptious</description>
	<lastBuildDate>Sun, 05 Feb 2012 13:13:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Sukumar</title>
		<link>http://www.sastwingees.org/2008/07/26/the-unleadership-manifesto-making-of-the-21st-century-leader-part-1/comment-page-2/#comment-4524</link>
		<dc:creator>Sukumar</dc:creator>
		<pubDate>Wed, 13 Aug 2008 11:48:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.sastwingees.org/?p=578#comment-4524</guid>
		<description>Ashutosh,
Thanks for the detailed response to Ranjit&#039;s 4point formula.  Upon rereading the whole thing again, you are right, we do need to involve the person who committed the mistake. However, to Ranjit&#039;s point, you may want to consider the nature of the mistake and the nature of the mistake-maker to decide whether to include him/her in the discussion.  A one-size-fits-all may not work. 

As for this point no.4, i don&#039;t think Ranjit meant it to be taken literally. his tip no.4 is just to make it clear that ultimately it is the leader who is responsible for the mistakes committed by the team members.  Again, this should be done based on the type of mistake and who has made that mistake.</description>
		<content:encoded><![CDATA[<p>Ashutosh,<br />
Thanks for the detailed response to Ranjit&#8217;s 4point formula.  Upon rereading the whole thing again, you are right, we do need to involve the person who committed the mistake. However, to Ranjit&#8217;s point, you may want to consider the nature of the mistake and the nature of the mistake-maker to decide whether to include him/her in the discussion.  A one-size-fits-all may not work. </p>
<p>As for this point no.4, i don&#8217;t think Ranjit meant it to be taken literally. his tip no.4 is just to make it clear that ultimately it is the leader who is responsible for the mistakes committed by the team members.  Again, this should be done based on the type of mistake and who has made that mistake.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashutosh Didwania</title>
		<link>http://www.sastwingees.org/2008/07/26/the-unleadership-manifesto-making-of-the-21st-century-leader-part-1/comment-page-2/#comment-4454</link>
		<dc:creator>Ashutosh Didwania</dc:creator>
		<pubDate>Thu, 07 Aug 2008 13:55:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.sastwingees.org/?p=578#comment-4454</guid>
		<description>@ Ranjit


I completely agree with your thoughts when you say that a leader must prepare the ones under him to replace him some day. 

However, when it comes to making way for a junior to replace you, I feel it should be done in very well thought-out manner. You talk about working under your team-member because you feel he is smarter than you but don&#039;t you think with the kind of experience you would have already gained by then, you might well prove to be far more useful to the organization in a leadership role rather than working just as a team-member. In such a scenario, the best option would probably be to move on to tougher leadership roles (of course if approved by the ones senior in the hierarchy), roles where you would further be able to test your leadership mettle against the very best and roles where you would be facing far more challenging situation than in your previous stint. This approach should not be misunderstood as one of ego, prestige or selfishness rather all I want to convey is that moving up a notch could probably be the way to go. After all at the end of the day its all about the extent to which you are able to contribute to the organization.

Out of the four tips that you&#039;ve mentioned, point 1 and 2 are simply superb and could do wonders if followed sincerely. However, I don&#039;t quite agree with point no. 3 which says that the &#039;why&#039; of the problem should be postponed for at least a week. If all the issues related to the problem are solved then and there, don&#039;t you think it would help avoid further confusion? Moreover, not involving the person who committed the mistake might not go down well with someone who is seriously dedicated towards his work. This would make the person dwell on whether the leader has lost confidence in him and there couldn&#039;t be anything worse for someone than the feeling that the leader doesn&#039;t find him capable enough of rectifying his own mistakes. Even a hint of this would completely shatter the individual. Instead it would be better to tell him on the face &quot;Hey, you could have done better.&quot; The ones who think logically would take it in a very positive manner. In the end its all about how well you have been able to judge the one under you. If you are able to find out the pulse of the ones working under you and deal with them accordingly instead of dealing with one and all with the same approach, team management would be far more effective.

I also beg to differ on point no 4 which states that a leader should forget that he has a team when things go wrong. I guess this would be like being too good for no reason. Yes, a true leader should definitely take the entire responsibility when things go wrong but not in exchange of losing everything everything he has. Being too good might be an excuse for the ones under you who are not very sincere towards their work. There is a thin line between creating an open work environment and providing excess freedom.</description>
		<content:encoded><![CDATA[<p>@ Ranjit</p>
<p>I completely agree with your thoughts when you say that a leader must prepare the ones under him to replace him some day. </p>
<p>However, when it comes to making way for a junior to replace you, I feel it should be done in very well thought-out manner. You talk about working under your team-member because you feel he is smarter than you but don&#8217;t you think with the kind of experience you would have already gained by then, you might well prove to be far more useful to the organization in a leadership role rather than working just as a team-member. In such a scenario, the best option would probably be to move on to tougher leadership roles (of course if approved by the ones senior in the hierarchy), roles where you would further be able to test your leadership mettle against the very best and roles where you would be facing far more challenging situation than in your previous stint. This approach should not be misunderstood as one of ego, prestige or selfishness rather all I want to convey is that moving up a notch could probably be the way to go. After all at the end of the day its all about the extent to which you are able to contribute to the organization.</p>
<p>Out of the four tips that you&#8217;ve mentioned, point 1 and 2 are simply superb and could do wonders if followed sincerely. However, I don&#8217;t quite agree with point no. 3 which says that the &#8216;why&#8217; of the problem should be postponed for at least a week. If all the issues related to the problem are solved then and there, don&#8217;t you think it would help avoid further confusion? Moreover, not involving the person who committed the mistake might not go down well with someone who is seriously dedicated towards his work. This would make the person dwell on whether the leader has lost confidence in him and there couldn&#8217;t be anything worse for someone than the feeling that the leader doesn&#8217;t find him capable enough of rectifying his own mistakes. Even a hint of this would completely shatter the individual. Instead it would be better to tell him on the face &#8220;Hey, you could have done better.&#8221; The ones who think logically would take it in a very positive manner. In the end its all about how well you have been able to judge the one under you. If you are able to find out the pulse of the ones working under you and deal with them accordingly instead of dealing with one and all with the same approach, team management would be far more effective.</p>
<p>I also beg to differ on point no 4 which states that a leader should forget that he has a team when things go wrong. I guess this would be like being too good for no reason. Yes, a true leader should definitely take the entire responsibility when things go wrong but not in exchange of losing everything everything he has. Being too good might be an excuse for the ones under you who are not very sincere towards their work. There is a thin line between creating an open work environment and providing excess freedom.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rajagopal sukumar</title>
		<link>http://www.sastwingees.org/2008/07/26/the-unleadership-manifesto-making-of-the-21st-century-leader-part-1/comment-page-2/#comment-4449</link>
		<dc:creator>rajagopal sukumar</dc:creator>
		<pubDate>Thu, 07 Aug 2008 03:16:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.sastwingees.org/?p=578#comment-4449</guid>
		<description>Thanks Ramesh. Long time no hear. Welcome back. 

Those are great points from the Hindu article. I agree with all of them. 

As for the independence, i think leaders need to be empowered by their management. Without that it is hard to excel as a leader. But then you have to play with the hand you are dealt. Sometimes your management may not be supportive of what you are trying to do. It is still incumbent upon the leader to manage the management in such a way that it does not infringe on the team&#039;s ability to get things done. I know this is easier said than done. Hope you agree?</description>
		<content:encoded><![CDATA[<p>Thanks Ramesh. Long time no hear. Welcome back. </p>
<p>Those are great points from the Hindu article. I agree with all of them. </p>
<p>As for the independence, i think leaders need to be empowered by their management. Without that it is hard to excel as a leader. But then you have to play with the hand you are dealt. Sometimes your management may not be supportive of what you are trying to do. It is still incumbent upon the leader to manage the management in such a way that it does not infringe on the team&#8217;s ability to get things done. I know this is easier said than done. Hope you agree?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rajagopal sukumar</title>
		<link>http://www.sastwingees.org/2008/07/26/the-unleadership-manifesto-making-of-the-21st-century-leader-part-1/comment-page-2/#comment-4448</link>
		<dc:creator>rajagopal sukumar</dc:creator>
		<pubDate>Thu, 07 Aug 2008 03:13:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.sastwingees.org/?p=578#comment-4448</guid>
		<description>Sairaj,
You are absolutely right. Vision or as Shoba puts it - Purpose is a critical success factor. The only mod i would make in the context of unleadership is that the vision/purpose is a shared one - developed jointly by the team.</description>
		<content:encoded><![CDATA[<p>Sairaj,<br />
You are absolutely right. Vision or as Shoba puts it &#8211; Purpose is a critical success factor. The only mod i would make in the context of unleadership is that the vision/purpose is a shared one &#8211; developed jointly by the team.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rajagopal sukumar</title>
		<link>http://www.sastwingees.org/2008/07/26/the-unleadership-manifesto-making-of-the-21st-century-leader-part-1/comment-page-2/#comment-4447</link>
		<dc:creator>rajagopal sukumar</dc:creator>
		<pubDate>Thu, 07 Aug 2008 03:12:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.sastwingees.org/?p=578#comment-4447</guid>
		<description>Ashutosh,
Those are great insights. I saw the first one in response to Meenaks&#039; ch1b post on this subject. I really liked the first rule you have - let the team members rule the roost. The 2nd one is also a good one. The third one has been covered by Ranjit nair above already.  he has also gone one better giving some specific tips on how to make that happen. Please let us know if you agree with Ranjit&#039;s tips or not?</description>
		<content:encoded><![CDATA[<p>Ashutosh,<br />
Those are great insights. I saw the first one in response to Meenaks&#8217; ch1b post on this subject. I really liked the first rule you have &#8211; let the team members rule the roost. The 2nd one is also a good one. The third one has been covered by Ranjit nair above already.  he has also gone one better giving some specific tips on how to make that happen. Please let us know if you agree with Ranjit&#8217;s tips or not?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

