<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>blog of geewiz &#187; Management</title>
	<atom:link href="http://www.jochen-lillich.de/category/management/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jochen-lillich.de</link>
	<description>You rush a miracle man, you get rotten miracles.</description>
	<lastBuildDate>Tue, 13 Jul 2010 11:23:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Bosses and Leaders</title>
		<link>http://www.jochen-lillich.de/2010/01/10/bosses-and-leaders/</link>
		<comments>http://www.jochen-lillich.de/2010/01/10/bosses-and-leaders/#comments</comments>
		<pubDate>Sun, 10 Jan 2010 14:17:10 +0000</pubDate>
		<dc:creator>geewiz</dc:creator>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[leadership]]></category>

		<guid isPermaLink="false">http://www.jochen-lillich.de/?p=931</guid>
		<description><![CDATA[
  A boss creates fear, a leader confidence. A boss fixes blame, a leader corrects mistakes. A boss knows all, a leader asks questions. A boss makes work drudgery, a leader makes it interesting. A boss is interested in himself or herself, a leader is interested in the group.
  (Russell H. Ewing)

]]></description>
			<content:encoded><![CDATA[<blockquote>
  <p>A boss creates fear, a leader confidence. A boss fixes blame, a leader corrects mistakes. A boss knows all, a leader asks questions. A boss makes work drudgery, a leader makes it interesting. A boss is interested in himself or herself, a leader is interested in the group.<br />
  (Russell H. Ewing)</p>
</blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.jochen-lillich.de/2010/01/10/bosses-and-leaders/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t meet, work!</title>
		<link>http://www.jochen-lillich.de/2009/07/17/dont-meet-work/</link>
		<comments>http://www.jochen-lillich.de/2009/07/17/dont-meet-work/#comments</comments>
		<pubDate>Fri, 17 Jul 2009 08:08:17 +0000</pubDate>
		<dc:creator>geewiz</dc:creator>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[communication]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[meeting]]></category>

		<guid isPermaLink="false">http://www.jochen-lillich.de/blog/?p=866</guid>
		<description><![CDATA[On his blog Remarkable Leadership, Kevin Eikenberry cited an interesting study result in his article &#8220;Leadership and Meetings&#8220;: Almost no manager expects productivity to drop if meetings got banned for one day a week. About half of them even think productivity would increase!

In the OfficeTeam survey, 150 executives were asked &#8220;How would employee productivity be [...]]]></description>
			<content:encoded><![CDATA[<p>On his blog Remarkable Leadership, Kevin Eikenberry cited an interesting study result in his article &#8220;<a href="http://blog.kevineikenberry.com/blog/kevin-eikenberry-group/0/0/leadership-and-meetings">Leadership and Meetings</a>&#8220;: Almost no manager expects productivity to drop if meetings got banned for one day a week. About half of them even think productivity would increase!</p>

<p>In the <a href="http://officeteam.com/">OfficeTeam</a> survey, 150 executives were asked &#8220;How would employee productivity be affected if your company banned meetings one day a week?&#8221; The results:</p>

<p><img src="http://www.jochen-lillich.de/blog/wp-content/uploads/2009/07/expected_productivity_loss.png" class="alignright" alt="Expected Productivity Loss" /></p>

<ul>
<li>No change: 46% (blue)</li>
<li>More productive: 45% (green)  </li>
<li>Less productive: 7% (yellow)</li>
<li>Don&#8217;t know: 2% (red)</li>
</ul>

<p>My subsequent question would be: &#8220;So, why do you think those meetings don&#8217;t add value, and what are you going to do about it?&#8221;</p>

<p>Meetings have the purpose of fostering efficient communication. But just coming together in a room to talk doesn&#8217;t cut it. That&#8217;s the time, money and drive sink we all dread. As always, you have to do things right to reap the benefits.</p>

<p>Brian lists the most important things you should take care of to stop the waste by ineffective meetings:</p>

<ul>
<li>Have clear desired outcomes for every meeting that are communicated before hand.</li>
<li>Use, and follow an agenda (that is focused on those desired outcomes).</li>
<li>Hold people accountable for the action items.</li>
</ul>

<p>So, there are two documents that are crucial for effective meetings: an agenda, sent to everyone in advance, and the meeting minutes (complete with action items and deadlines), sent to everyone after the meeting.</p>

<p>And hey, if you make your meetings really effective, you can have that no-meeting day anyway!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jochen-lillich.de/2009/07/17/dont-meet-work/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How to get the customer off your back</title>
		<link>http://www.jochen-lillich.de/2009/07/15/how-to-get-the-customer-off-your-back/</link>
		<comments>http://www.jochen-lillich.de/2009/07/15/how-to-get-the-customer-off-your-back/#comments</comments>
		<pubDate>Wed, 15 Jul 2009 07:14:18 +0000</pubDate>
		<dc:creator>geewiz</dc:creator>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[communication]]></category>
		<category><![CDATA[customer]]></category>

		<guid isPermaLink="false">http://www.jochen-lillich.de/blog/?p=861</guid>
		<description><![CDATA[Customers become a nuisance whenever they develop a tendency to cling. Suddenly, you find yourself spending a lot of time in meetings and phone calls that you&#8217;d rather use for working on your tasks. It doesn&#8217;t matter if you&#8217;re a freelancer working for several companies or if your customers sit in the same company as [...]]]></description>
			<content:encoded><![CDATA[<p>Customers become a nuisance whenever they develop a tendency to cling. Suddenly, you find yourself spending a lot of time in meetings and phone calls that you&#8217;d rather use for working on your tasks. It doesn&#8217;t matter if you&#8217;re a freelancer working for several companies or if your customers sit in the same company as yourself, you&#8217;ll eventually experience the contact-hungry client.</p>

<p>How should you deal with that need? The request &#8220;Excuse me, but could you please leave me alone and let me do my work?&#8221; doesn&#8217;t seem very effective.</p>

<p>Gitte Härter over at <a href="http://unternehmenskick.de/0/tipps/entry/7-tipps-damit-ihre-kunden-sie-in-ruhe-ihre-arbeit-machen-lassen/">unternehmenskick.de</a> gave that situation a second look and switched to another perspective: that of the customer. She found out that often a heightened need of communication comes from insecurity. In detail, she lists the following causes for insecurity in a professional relationship:</p>

<ul>
<li>The customer doesn&#8217;t yet know you.</li>
<li>The customer made some bad experiences.</li>
<li>The customer himself is insecure.</li>
<li>The customer likes to chat.</li>
<li>The customer wants to dominate you.</li>
<li>You invoke the feeling, that you&#8217;re insecure or maybe understood something wrong.</li>
<li>You failed in posing enough of the right questions, maybe even regarding the core issues that you need to understand to deliver the right solution.</li>
<li>You seem to walk in another (your own?) direction.</li>
<li>You failed another time in the past.</li>
<li>You don&#8217;t respond promptly to phone calls or emails.</li>
<li>You&#8217;re generally too silent.</li>
<li>You communicate too vaguely.</li>
</ul>

<p>Over the years, I learned that customers abhore a communication vacuum. So, if you don&#8217;t communicate the customer expects you to, oftentimes they will take the lead and <em>make</em> you communicate. Unfortunately, this will never be as effective as if you established a steady and controled information flow in the first place.</p>

<p>Gitte has the following suggestions on how you can take the lead and position yourself as a professional partner:</p>

<ol>
<li><p><strong>Create trust.</strong> &#8212; Be present, pose the right questions, show genuine interest in your counterpart. Get all the information necessary to deliver a good job. Also, dare to give honest feedback; for example, explain the customer if his ideas don&#8217;t hit the spot.</p></li>
<li><p><strong>Make clear that you&#8217;ll get in touch when it&#8217;s time.</strong> &#8212; You&#8217;ll rid yourself of control calls as soon as your customer can trust that you work on their issue and will get back to them when questions, showstoppers or delays occur. Make sure you do! Send short receipt acknowledgements, deliver status reports or give a perspective on when you&#8217;ll follow up.</p></li>
<li><p><strong>Be the boss in your area.</strong> &#8212; Your customer gives the order and has the say on goal and conditions, but he isn&#8217;t supposed to interfere on your area of expertise. Stand your ground.</p></li>
<li><p><strong>Lead the conversation.</strong> &#8212; Never be passive in a conversation. Lead the dialogue, show you&#8217;re efficient. Get to the point. Don&#8217;t get lost in endless discussions or waste your time in useless chitchat.</p></li>
<li><p><strong>Summarize what you agreed upon.</strong> &#8212; Everytime you talked (or emailed) about something, at the end summarize the relevant points and what each will do until when.</p></li>
<li><p><strong>Acknowledge &#8220;good&#8221; behaviour.</strong> &#8212; A customer delivers all information in time and doesn&#8217;t question everything? He leaves you especially much freedom? Tell him about your happiness about his behaviour: &#8220;Working with you is great: you send everything so quickly and you&#8217;re open to my suggestions &#8212; thank you!&#8221;</p></li>
<li><p><strong>Always meet deadlines.</strong> &#8212; Always. Meet them without exception. So make them realistic. If there&#8217;s a rare emergency, inform the customer immediately.</p></li>
</ol>

<p>So the summary is: Oftentimes, it&#8217;s not the customer, it&#8217;s you. Drive or be driven.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jochen-lillich.de/2009/07/15/how-to-get-the-customer-off-your-back/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>You&#8217;re not leading when&#8230;</title>
		<link>http://www.jochen-lillich.de/2009/05/31/youre-not-leading-when/</link>
		<comments>http://www.jochen-lillich.de/2009/05/31/youre-not-leading-when/#comments</comments>
		<pubDate>Sun, 31 May 2009 18:10:27 +0000</pubDate>
		<dc:creator>geewiz</dc:creator>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[leadership]]></category>

		<guid isPermaLink="false">http://www.jochen-lillich.de/blog/2009/05/31/youre-not-leading-when/</guid>
		<description><![CDATA[Reading some of the many books on leadership that are out there, you get a picture of how it should look like when you&#8217;re leading. But are you also aware of how it looks when you&#8217;re not in the lead? You better are, because your subordinates certainly do.

Jon Ferguson made an insightful list in his [...]]]></description>
			<content:encoded><![CDATA[<p>Reading some of the many books on leadership that are out there, you get a picture of how it should look like when you&#8217;re leading. But are you also aware of how it looks when you&#8217;re not in the lead? You better are, because your subordinates certainly do.</p>

<p>Jon Ferguson made an insightful list in his blog article</p>

<p><a href="http://jonferguson.typepad.com/lead/2008/01/you-know-youre.html">You know you are not leading when&#8230;</a>:</p>

<ul>
<li>You wait for someone to tell you what to do rather than taking the initiative yourself</li>
<li>You spend too much time talking about how things should be different</li>
<li>You blame the context, surroundings, or other people for your current situation</li>
<li>You choose not to speak the truth in love</li>
<li>You are more concerned about being cool or accepted than doing the right thing</li>
<li>You seek consensus, rather than casting vision for a preferable future</li>
<li>You aren&#8217;t taking any significant risks</li>
<li>You accept status quo as the way it&#8217;s always been and always will be</li>
<li>You start protecting your reputation instead of opening yourself up to opposition</li>
<li>You sleep a little too sound</li>
<li>You procrastinate to avoid making a tough call</li>
<li>You talk to others about the problem rather than taking it to the person responsible</li>
<li>You don&#8217;t feel like your butt is on the line for anything significant</li>
<li>You think what you say doesn&#8217;t matter</li>
<li>You ask for way too many opinions before taking action</li>
</ul>

<p>In short: You&#8217;re appointed the leader, so <strong>act</strong> like one. You&#8217;ll not be judged on your preparations but on your <strong>results</strong>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jochen-lillich.de/2009/05/31/youre-not-leading-when/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Mountaineer Leadership</title>
		<link>http://www.jochen-lillich.de/2009/05/25/mountaineer-leadership/</link>
		<comments>http://www.jochen-lillich.de/2009/05/25/mountaineer-leadership/#comments</comments>
		<pubDate>Mon, 25 May 2009 19:55:50 +0000</pubDate>
		<dc:creator>geewiz</dc:creator>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[leadership]]></category>

		<guid isPermaLink="false">http://www.jochen-lillich.de/blog/?p=852</guid>
		<description><![CDATA[In his German article &#8220;Was ich als Führungskraft durch Bergsteigen gelernt habe&#8221;, Rainer from the HaFAWo blog (&#8220;have fun at work and life&#8221;), describes how the lessons he learned as an alpinist can also be applied to his work as a manager:


Know your goals and their nature, for your job as well as your private [...]]]></description>
			<content:encoded><![CDATA[<p>In his German article <a href="http://www.hafawo.at/selbstmanagement-motivation/was-ich-als-fuhrungskraft-durch-bergsteigen-gelernt-habe/">&#8220;Was ich als Führungskraft durch Bergsteigen gelernt habe&#8221;</a>, Rainer from the HaFAWo blog (&#8220;have fun at work and life&#8221;), describes how the lessons he learned as an alpinist can also be applied to his work as a manager:</p>

<ol>
<li>Know your goals and their nature, for your job as well as your private life. (= Define your goals.)</li>
<li>Have a map and learn to read it right. (= Have a vision.)</li>
<li>Have a compass. (= Have reliable orientation points.)</li>
<li>Make sure to start at the right time to avoid time-dependend dangers. (= Have good timing.)</li>
<li>Expect the worst and be ready to handle it.</li>
<li>Be prepared regarding your shape, food, clothing and equipment. (= Have everything ready you may need.)</li>
<li>Know your skills and with how much of the impossible you can cope. (= Know your limits.)</li>
<li>If there are problems ahead, you maybe have to resort to teamwork. (= Have a supporting team.)</li>
<li>When problems arise, you depend on your equipment. (= Have reliable tools and know how to use them.)</li>
<li>You should know when to turn your back on the mountain and postpone  summit victory. (Admit defeat in time, try again later.)</li>
</ol>

<p>Thanks for the great analogy, Rainer!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jochen-lillich.de/2009/05/25/mountaineer-leadership/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Leadership tips</title>
		<link>http://www.jochen-lillich.de/2009/05/18/leadership-tips/</link>
		<comments>http://www.jochen-lillich.de/2009/05/18/leadership-tips/#comments</comments>
		<pubDate>Mon, 18 May 2009 17:55:38 +0000</pubDate>
		<dc:creator>geewiz</dc:creator>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[leadership]]></category>

		<guid isPermaLink="false">http://www.jochen-lillich.de/blog/2009/05/18/leadership-tips/</guid>
		<description><![CDATA[In &#8220;Ten Top Tips for the Innovative Leader&#8220;, Paul Sloane gives valuable recommendations to everyone who wants to be more of a leader than just being some levels above in the org chart.

He recommends:


Have a vision for change
Fight the fear of change
Think like a venture capitalist
Have a dynamic suggestion scheme
Break the rules
Give everyone two jobs
Collaborate
Welcome [...]]]></description>
			<content:encoded><![CDATA[<p>In &#8220;<a href="http://www.lifehack.org/articles/management/ten-top-tips-for-the-innovative-leader.html">Ten Top Tips for the Innovative Leader</a>&#8220;, Paul Sloane gives valuable recommendations to everyone who wants to be more of a leader than just being some levels above in the org chart.</p>

<p>He recommends:</p>

<ol>
<li>Have a vision for change</li>
<li>Fight the fear of change</li>
<li>Think like a venture capitalist</li>
<li>Have a dynamic suggestion scheme</li>
<li>Break the rules</li>
<li>Give everyone two jobs</li>
<li>Collaborate</li>
<li>Welcome failure</li>
<li>Build prototypes</li>
<li>Be passionate</li>
</ol>

<p>Many of his tips remind me of the concepts explained in &#8220;<a href="http://p.jochen-lillich.de/amazon/0684852861">First, Break All the Rules</a>&#8220;, a great leadership book I read recently (and have to review here ASAP). And looking at the fifth point, this doesn&#8217;t seem like a coincidence.</p>

<p>Especially the first two points resonate with me at the moment because I&#8217;m going to undertake a big change effort myself with my department.</p>

<p>Thanks to Paul for his great summary of important leadership qualities and practices!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jochen-lillich.de/2009/05/18/leadership-tips/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>New read: Leading Change</title>
		<link>http://www.jochen-lillich.de/2009/05/05/new-read-leading-change/</link>
		<comments>http://www.jochen-lillich.de/2009/05/05/new-read-leading-change/#comments</comments>
		<pubDate>Tue, 05 May 2009 09:36:16 +0000</pubDate>
		<dc:creator>geewiz</dc:creator>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[leadership]]></category>

		<guid isPermaLink="false">http://www.jochen-lillich.de/blog/?p=844</guid>
		<description><![CDATA[After listening to the audiobook version of John P. Kotter&#8217;s &#8220;The Heart of Change&#8221;, I decided to also read his book &#8220;Leading Change&#8221;. Kotter is an expert on change management, i.e. the management and leadership skills to lead an organization and make the necessary changes to adapt it to new situations and implement new strategies.

I&#8217;ve [...]]]></description>
			<content:encoded><![CDATA[<p>After listening to the audiobook version of John P. Kotter&#8217;s &#8220;The Heart of Change&#8221;, I decided to also read his book &#8220;Leading Change&#8221;. Kotter is an expert on change management, i.e. the management and leadership skills to lead an organization and make the necessary changes to adapt it to new situations and implement new strategies.</p>

<p>I&#8217;ve read chapter 1, &#8220;Transforming organizations: Why firms fail&#8221;, and I&#8217;m hooked. Kotter explains what errors are common causes of failing change efforts:</p>

<ol>
<li>Allowing too much complacency</li>
<li>Failing to create a sufficiently powerful guiding coalition</li>
<li>Underestimating the power of vision</li>
<li>Undercommunicating the vision by a factor of 10 (or 100 or even 1,000)</li>
<li>Permitting obstacles to block the new vision</li>
<li>Failing to create short-term wins</li>
<li>Declaring victory too soon</li>
<li>Neglecting to anchor changes firmly in the corporate culture</li>
</ol>

<p>Looking at some of the organizational changes I was in some way part of, I can see instances where most or even all eight of those errors were made &#8212; with the appropriate results. I want the changes I&#8217;m about to undertake to be a better success, so I&#8217;m curious what Kotter has in store in the following chapters.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jochen-lillich.de/2009/05/05/new-read-leading-change/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Communicate to lead</title>
		<link>http://www.jochen-lillich.de/2009/04/05/communicate-to-lead/</link>
		<comments>http://www.jochen-lillich.de/2009/04/05/communicate-to-lead/#comments</comments>
		<pubDate>Sun, 05 Apr 2009 20:28:54 +0000</pubDate>
		<dc:creator>geewiz</dc:creator>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[communication]]></category>
		<category><![CDATA[leadership]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Communication is (finally) one of my most important topics at work. Steve Roesler recommends to &#8220;add these four thoughts to your leadership communication kit&#8221;, and I can&#8217;t emphasize his points enough:


Never assume that anyone knows anything.
The larger the group, the more attention needs to be given to communicating.
When left in the dark, people will fantasize [...]]]></description>
			<content:encoded><![CDATA[<p>Communication is (finally) one of my most important topics at work. <a href="http://www.allthingsworkplace.com/2009/04/nothing-happens-until-people-talk.html">Steve Roesler</a> recommends to &#8220;add these four thoughts to your leadership communication kit&#8221;, and I can&#8217;t emphasize his points enough:</p>

<ul>
<li>Never assume that anyone knows anything.</li>
<li>The larger the group, the more attention needs to be given to communicating.</li>
<li>When left in the dark, people will fantasize their own reality. Do you want their fantasy to trump your reality?</li>
<li>Effective leaders are obsessed with accurate, frequent communication.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.jochen-lillich.de/2009/04/05/communicate-to-lead/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing the yuck</title>
		<link>http://www.jochen-lillich.de/2009/03/03/managing-the-yuck/</link>
		<comments>http://www.jochen-lillich.de/2009/03/03/managing-the-yuck/#comments</comments>
		<pubDate>Tue, 03 Mar 2009 17:53:36 +0000</pubDate>
		<dc:creator>geewiz</dc:creator>
				<category><![CDATA[Management]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[If you&#8217;re a manager, you&#8217;ll encounter yuck. What I mean is all the things that you hesitate to tackle, issues that you&#8217;d rather avoid and pretend they don&#8217;t exist.

So you don&#8217;t want to actively engage with the yuck. But you should, says
Allison O’Neill over on Slow Leadership!


  The best leaders constantly seek out the [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re a manager, you&#8217;ll encounter yuck. What I mean is all the things that you hesitate to tackle, issues that you&#8217;d rather avoid and pretend they don&#8217;t exist.</p>

<p>So you don&#8217;t want to actively engage with the yuck. But you should, says
Allison O’Neill over on <a href="http://www.slowleadership.org/blog/2009/02/never-avoid-the-yuck/">Slow Leadership</a>!</p>

<blockquote>
  <p>The best leaders constantly seek out the weakest parts of the business so something can be done about them. Yuck isn’t scary and yuck isn’t terrible. It is powerful and wonderful. It is the kind of stuff that once addressed can totally overhaul workplaces, people and profits.</p>
</blockquote>

<p>Improvement and innovation comes from people that address the yuck despite all the people admiring the emperor&#8217;s new clothes.</p>

<p>That&#8217;s what we did today when we talked about how we can provide 24/7 IT services in a team that suffers from a very unhealthy responsibility-to-headcount ratio. To be honest, I was unsure how much the team was willing to productively work towards a solution instead of just venting frustration and anger about missing growth. But we found some very interesting approaches towards meeting the relevant demands. I&#8217;m glad that I decided to tackle the topic once and for all and gained hope that we&#8217;ll find a solution as a team.</p>

<p>I&#8217;ll keep trying not to hesitate to address the yuck in my job. But I wonder if the &#8217;stupidest thing we do around here&#8217; competition Allison talks about wouldn&#8217;t take us weeks to decide upon a winner. <img src='http://www.jochen-lillich.de/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.jochen-lillich.de/2009/03/03/managing-the-yuck/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Failure is not failure</title>
		<link>http://www.jochen-lillich.de/2009/02/14/failure-is-not-failure/</link>
		<comments>http://www.jochen-lillich.de/2009/02/14/failure-is-not-failure/#comments</comments>
		<pubDate>Sat, 14 Feb 2009 11:32:59 +0000</pubDate>
		<dc:creator>geewiz</dc:creator>
				<category><![CDATA[Management]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[&#8220;That&#8217;s okay, right, I mean, if you&#8217;ve got a boss that&#8217;s telling you to take a chance and if you make a mistake or failure says &#8216;Try not to do it again&#8217; and &#8216;Try to learn from that&#8217;, you know, that&#8217;s a good thing.&#8221;

I like this Hondy documentary video very much:



To make mistakes isn&#8217;t failure. [...]]]></description>
			<content:encoded><![CDATA[<p>&#8220;That&#8217;s okay, right, I mean, if you&#8217;ve got a boss that&#8217;s telling you to take a chance and if you make a mistake or failure says &#8216;Try not to do it again&#8217; and &#8216;Try to learn from that&#8217;, you know, that&#8217;s a good thing.&#8221;</p>

<p>I like this Hondy documentary video very much:</p>

<p><object width="425" height="344"><param name="movie" value="http://www.youtube.com/v/OiaPNlR5A4I&#038;color1=0xb1b1b1&#038;color2=0xcfcfcf&#038;feature=player_embedded&#038;fs=1"></param><param name="allowFullScreen" value="true"></param><embed src="http://www.youtube.com/v/OiaPNlR5A4I&#038;color1=0xb1b1b1&#038;color2=0xcfcfcf&#038;feature=player_embedded&#038;fs=1" type="application/x-shockwave-flash" allowfullscreen="true" width="425" height="344"></embed></object></p>

<p>To make mistakes isn&#8217;t failure. Not to learn from your mistakes is failure.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jochen-lillich.de/2009/02/14/failure-is-not-failure/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
