<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.2.1" -->
<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/"
	>

<channel>
	<title>Kim Heldman's Blog</title>
	<link>http://blog.kimheldman.com</link>
	<description>Kim's insights on PM and leadership topics and anything else that strikes her at the moment</description>
	<pubDate>Fri, 09 Mar 2012 02:47:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>
	<language>en</language>
			<item>
		<title>3-Piece Band</title>
		<link>http://blog.kimheldman.com/2012/03/08/3-piece-band/</link>
		<comments>http://blog.kimheldman.com/2012/03/08/3-piece-band/#comments</comments>
		<pubDate>Fri, 09 Mar 2012 02:47:10 +0000</pubDate>
		<dc:creator>Kim</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.kimheldman.com/2012/03/08/3-piece-band/</guid>
		<description><![CDATA[Aligning the stakeholders, project team members, and others related to a project is not an easy task. For example, stakeholders have their hearts set on a blue result, the project team is busy working away on a yellow result, and the CFO redirects the project team toward a green result. What&#8217;s a PM to do?
&#160;
A [...]]]></description>
			<content:encoded><![CDATA[<p style="font-family: Calibri; font-size: 12pt; margin: 0in">Aligning the stakeholders, project team members, and others related to a project is not an easy task. For example, stakeholders have their hearts set on a blue result, the project team is busy working away on a yellow result, and the CFO redirects the project team toward a green result. What&#8217;s a PM to do?</p>
<p style="font-family: Calibri; font-size: 12pt; margin: 0in">&nbsp;</p>
<p style="font-family: Calibri; font-size: 12pt; margin: 0in">A well crafted, agreed upon charter document, scope statement, and change management plan (to handle those inevitable redirects) are critical tools in your PM toolbox. They won&#8217;t solve every question related to changing scope, but they definitely help keep the troops aligned and focused on the goal. Your role as the PM is to educate the stakeholders on the importance of documenting deliverables and keeping them updated on progress. When those changes to scope come along, and they will, the stakeholders or sponsors are responsible for weighing the costs and benefits of a change at this point in the project, and deciding whether the team should be redirected. You, of course, have provided the costs and benefits, and informed them of the level of effort needed for the project team to change direction at this point in the project.</p>
<p style="font-family: Calibri; font-size: 12pt; margin: 0in">&nbsp;</p>
<p style="font-family: Calibri; font-size: 12pt; margin: 0in">In the real world, you may have done all of these things and are still getting misdirects from your illustrious leaders. Here&#8217;s one of the tactics I use in that situation. I tell them a story.<span>  </span>I think people easily relate to stories, especially when it closely matches the situation at hand. I tell them about something I&#8217;ve witnessed<span>  </span>first hand, or something I make up, that helps drive home the point. Here&#8217;s a true situation that I came across just the other day that could help explain to the stakeholders what&#8217;s going on with this project.</p>
<p style="font-family: Calibri; font-size: 12pt; margin: 0in">&nbsp;</p>
<p style="font-family: Calibri; font-size: 12pt; margin: 0in">I live in Denver and like other major cities I&#8217;ve visited, we have a cadre of panhandlers, street entertainers, and vendors. I wasn&#8217;t too far on my lunch time walk the other day, just past Court Pl., soaking up the teaser spring day, when I came upon a three-piece band. They were comprised of a singer, a female holding a stick with a black foam ball glued to the top to simulate a microphone; the drummer, equipped with over turned buckets; and the guitar player whose instrument looked like it had survived a war and sacrificed a couple of strings. The guitar case lay open on the sidewalk in front of the group in the hopes of winning over some loose change from the passers-by.</p>
<p style="font-family: Calibri; font-size: 12pt; margin: 0in">&nbsp;</p>
<p style="font-family: Calibri; font-size: 12pt; margin: 0in">Here&#8217;s the funny thing about this mismatched group, they weren&#8217;t playing the same song. The singer was singing something that was wholly different than what the guitarist was strumming and the drummer was beating away to the tune in his own head. It was a pitiful sight and sound. No coordination, no melody, no end goal in mind. And there were very few coins in the case.</p>
<p style="font-family: Calibri; font-size: 12pt; margin: 0in">&nbsp;</p>
<p style="font-family: Calibri; font-size: 12pt; margin: 0in">Do you see how this relates to our project? Most everyone can imagine three people playing a different piece of music at the same time. It&#8217;s chaos. Carefully bring your stakeholders back from this example and lead them into connecting the story to what is happening on the project. Let them know that the redirection your team is experiencing coupled with unclear expectations lead to poor results. Your team members are all working hard and producing deliverables, just like each of the musicians in the story, but they aren&#8217;t working on the same goal. Hopefully your stakeholders will have that ah-ha moment and ask you how to get them back on track. And you will be prepared with the plan for how to do that, right?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kimheldman.com/2012/03/08/3-piece-band/feed/</wfw:commentRss>
		</item>
		<item>
		<title>A Leadership Test</title>
		<link>http://blog.kimheldman.com/2012/01/23/a-leadership-test/</link>
		<comments>http://blog.kimheldman.com/2012/01/23/a-leadership-test/#comments</comments>
		<pubDate>Mon, 23 Jan 2012 19:13:42 +0000</pubDate>
		<dc:creator>Kim</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.kimheldman.com/2012/01/23/a-leadership-test/</guid>
		<description><![CDATA[Happy New Year to all of you! I hope this finds you raring and eager to go on a new year, new projects, and new adventures.
 I’ve been wondering, why isn’t there a certification test for leaders like there is for project managers? The project management certifications are rigorous and assure that at least you [...]]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal"><span style="font-family: Tahoma, sans-serif; line-height: 18px" class="Apple-style-span">Happy New Year to all of you! I hope this finds you raring and eager to go on a new year, new projects, and new adventures.</span></p>
<p><font class="Apple-style-span" face="Tahoma, sans-serif"> </font><font class="Apple-style-span" face="Tahoma, sans-serif">I’ve been wondering, why isn’t there a certification test for leaders like there is for project managers? The project management certifications are rigorous and assure that at least you understand the principles, terminology, and processes regarding sound project management. I’m proposing a leadership certification test that will help assure our leaders have a heart, have a conscious, and care about their customers and employees. It seems every day I hear about poor leadership, the leadership void, and laments on how our leaders are not leaders at all but dictators. They pay lip service to the “open door policy” and “share your ideas for innovation and efficiencies” and never enact a single suggestion nor really listen when an employee has an idea or an issue to resolve. I think the certification test for leadership positions should go something like this:<o:p></o:p></font></p>
<p><font class="Apple-style-span" face="Tahoma, sans-serif">  </font><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">1.   </span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">Do you believe employees are guilty until proven innocent?</span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px"> </span></p>
<p class="MsoNormal"><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">2.   </span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">Do you often steal ideas from employees and all the while tell them the idea is not worth implementing and then implement it anyway and tell your boss it was your idea?</span></p>
<p class="MsoNormal"><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px"></span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">3.   </span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">Do you take credit for other people’s work?</span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px"> </span></p>
<p class="MsoNormal"><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">4.   </span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">Do you have a lack of concern for customer service and go out of your way to avoid getting their input on our services?</span></p>
<p class="MsoNormal"><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px"></span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">5.   </span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">Do you take credit for the good your work team has accomplished and punish the team when it doesn’t go so well?</span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px"> </span></p>
<p class="MsoNormal"><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">6.   </span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">Do you ridicule and demean your employees in front of others?</span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px"> </span></p>
<p class="MsoNormal"><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">7.   </span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">Do you strip your employees of all ability and authority to resolve problems and make decisions on their own?</span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px"> </span></p>
<p class="MsoNormal"><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">8.   </span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">Do you laugh when employees ask you a genuine question they don’t know the answer to?</span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px"> </span></p>
<p class="MsoNormal"><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">9.   </span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">Do you dance around the answers to difficult questions, particularly questions employees ask about their future in the organization?</span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px"> </span></p>
<p class="MsoNormal"><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px"></span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">10. </span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">Do you actively avoid showing appreciation to your employees?</span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px"> </span></p>
<p class="MsoNormal"><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">11. </span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">Do you believe employees are your greatest liability?</span><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px"> </span></p>
<p class="MsoNormal"><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px">12. Do you believe your company would have a great reputation if it weren’t for your employees?</span></p>
<p class="MsoNormal"><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; line-height: 18px"><br />
</span><font class="Apple-style-span" face="Tahoma, sans-serif"><span class="Apple-style-span" style="line-height: 18px">    <span style="font-size: 12pt; line-height: 115%; font-family: Tahoma, sans-serif">What happens when you work in an environment where leaders not only answer, but act in a way that’s opposite of what these questions suggest? You get employees who feel appreciated and valued, you get meaningful suggestions regarding work processes and customer interactions, and you gain loyalty and dedication to your mission. Being a leader isn’t difficult. But it does take discipline and dedication in putting your employees and customers first. Take the leadership certification test and see how you score. What are your team members and employees saying about you?</span></span></font></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kimheldman.com/2012/01/23/a-leadership-test/feed/</wfw:commentRss>
		</item>
		<item>
		<title>A Three Hour Tour</title>
		<link>http://blog.kimheldman.com/2011/10/10/a-three-hour-tour/</link>
		<comments>http://blog.kimheldman.com/2011/10/10/a-three-hour-tour/#comments</comments>
		<pubDate>Mon, 10 Oct 2011 14:01:00 +0000</pubDate>
		<dc:creator>Kim</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.kimheldman.com/2011/10/10/a-three-hour-tour/</guid>
		<description><![CDATA[      
You may recognize this title from the old Gilligan’s Island TV series. If you haven’t seen it, the show was about seven people who set out on what was supposed to be a three hour tour of some islands. They ended up getting lost and they shipwrecked the boat [...]]]></description>
			<content:encoded><![CDATA[<p><!--[if gte mso 9]><xml>  <o:OfficeDocumentSettings>   <o:AllowPNG/>  </o:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:WordDocument>   <w:Zoom>0</w:Zoom>   <w:TrackMoves>false</w:TrackMoves>   <w:TrackFormatting/>   <w:PunctuationKerning/>   <w:DrawingGridHorizontalSpacing>18 pt</w:DrawingGridHorizontalSpacing>   <w:DrawingGridVerticalSpacing>18 pt</w:DrawingGridVerticalSpacing>   <w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery>   <w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery>   <w:ValidateAgainstSchemas/>   <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>   <w:IgnoreMixedContent>false</w:IgnoreMixedContent>   <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>   <w:Compatibility>    <w:BreakWrappedTables/>    <w:DontGrowAutofit/>    <w:DontAutofitConstrainedTables/>    <w:DontVertAlignInTxbx/>   </w:Compatibility>  </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:LatentStyles DefLockedState="false" LatentStyleCount="276">  </w:LatentStyles> </xml><![endif]-->  <!--[if gte mso 10]><br />
<style>  /* Style Definitions */ table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin-top:0in; 	mso-para-margin-right:0in; 	mso-para-margin-bottom:10.0pt; 	mso-para-margin-left:0in; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin;} </style>
<p> <![endif]-->    <!--StartFragment--></p>
<p class="MsoNormal">You may recognize this title from the old Gilligan’s Island TV series. If you haven’t seen it, the show was about seven people who set out on what was supposed to be a three hour tour of some islands. They ended up getting lost and they shipwrecked the boat and never made it back to civilization.</p>
<p>“A Three Hour Tour” tune was going through my head as I sat through my fourth, three-hour meeting this week. OMG, is there ever a need for a three hour meeting? To add insult to injury, when you work for state government, it’s against the rules to provide water or coffee to state employees at these meetings (because you’re using taxpayer money and that’s not an appropriate use of their dollars). So if you forget to bring your own nourishment, it can be a mighty long three hours.</p>
<p>But I digress, so back to my original question. Three hours, oh my. Most meetings, IMHO, can be conducted efficiently and relay the info needed in much less time than you think. You and I, as meeting facilitators, just need to follow a few simple rules to prevent shipwrecking our next meeting.</p>
<p>1. Always publish an agenda. Ideally, you should ask for input to the agenda a few days prior to the meeting and then you decide what makes the cut. Publish the agenda the day before the meeting.</p>
<p>2. Put time limits on each agenda and item and stick to them. If it’s apparent the topic being discussed needs further discussion, you have a couple of options. First, choose to postpone additional agenda items from this meeting to the next, or, table the issue that’s running over time and add it to the next meeting’s agenda. Or, you could set up a separate meeting to discuss this topic if needed. That seems to defeat the purpose of limiting meetings, but sometimes due to the nature of the issue, you’ll have to use this tactic.</p>
<p>3. Curtail rabbit trails. Keep attendees on track and if new topics come up that need addressing, add them to the agenda for the next meeting.</p>
<p>These three easy steps will help you get control and keep control of your meetings going forward and,hopefully, return you all to civilization in short order.</p>
<p><!--EndFragment--></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kimheldman.com/2011/10/10/a-three-hour-tour/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Dismount</title>
		<link>http://blog.kimheldman.com/2011/09/24/dismount/</link>
		<comments>http://blog.kimheldman.com/2011/09/24/dismount/#comments</comments>
		<pubDate>Sat, 24 Sep 2011 13:56:06 +0000</pubDate>
		<dc:creator>Kim</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.kimheldman.com/2011/09/24/dismount/</guid>
		<description><![CDATA[I attended an event recently where the keynote speaker told us of an old saying I&#8217;d like to share with you. It went like this, &#8220;when your horse dies, dismount.&#8221;It got a lot of laughs. Who wants to ride a dead horse? But how many times in our role as project manager do we continue [...]]]></description>
			<content:encoded><![CDATA[<p>I attended an event recently where the keynote speaker told us of an old saying I&#8217;d like to share with you. It went like this, &#8220;when your horse dies, dismount.&#8221;It got a lot of laughs. Who wants to ride a dead horse? But how many times in our role as project manager do we continue to ride a dead horse of a project all the way to the ground? I know, I know, it&#8217;s a Catch-22. We want to please our customers and we want to deliver results so we&#8217;ll keep riding in the hopes a miracle occurs along the way. I&#8217;d like to offer that we should be the first to dismount and declare the horse, err, project, dead! We should be the first to recognize the signs and then have the difficult, but frank, discussion with the project sponsor. I know this isn&#8217;t an easy thing to do, but is riding a dead horse easy?</p>
<p>Dead projects aren&#8217;t the only reason to dismount. How often as leaders do we hold onto ideas, processes, and structures declaring them good, only because we thought them up and want others to be impressed? We refuse to let the ideas go and don&#8217;t want anyone reporting problems to us about how bad the processes or ideas are because, after all, we know what we&#8217;re doing and don&#8217;t need input from anyone. (Hmm, that&#8217;s rather arrogant isn&#8217;t it?)</p>
<p>When leaders push their ideas onto their team members without getting input from the ground up, they can often create fear in the organization. Instead of gaining momentum and synergy, they create exhaustion. For example, let&#8217;s say our company has decided they need to make some cuts. The proclamation comes down from the ivory tower that 200 people will now do the work that 350 used to do. They don&#8217;t ask the 250 for any ideas on how to make this work, the ivory tower just expects that all work will continue as usual. We all know it&#8217;s not physically possible for 200 people to do the work of 350, nor can those 200 create the synergy that 350 people created. But wait, I take that back. It is possible&#8211;for a while. And here&#8217;s what happens. Team members start operating in fear, perhaps thinking they&#8217;ll lose their jobs if they don&#8217;t pick up the extra work. So they hold the horse up from underneath while their co-workers push the horse from behind and pull it from the front to give the illusion that the horse is alive and well. All the while, productivity decreases, personal lives are impacted because of the increased work loads and stress, and momentum and synergy slowly erode.</p>
<p>Surely a good leader would be able to read the exhaustion and dismay on their faces! But wait, leaders who push ideas down from the top and don&#8217;t bother with input from the ground up don&#8217;t know their workers are exhausted. So they keep enforcing the processes and keep ignoring the recommendations the weary workers are making.</p>
<p>Don&#8217;t let this happen to your teams! If you&#8217;re under the horse, speak up. If you&#8217;re the one riding, dismount and talk to the people holding up the horse and scooping up the poop. You might find some seeds of inspiration and solid ideas to carry your project, or organization, to the next level without killing your staff (and the horse).</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kimheldman.com/2011/09/24/dismount/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Zits and Leadership</title>
		<link>http://blog.kimheldman.com/2011/04/04/zits-and-leadership/</link>
		<comments>http://blog.kimheldman.com/2011/04/04/zits-and-leadership/#comments</comments>
		<pubDate>Tue, 05 Apr 2011 00:17:17 +0000</pubDate>
		<dc:creator>Kim</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.kimheldman.com/2011/04/04/zits-and-leadership/</guid>
		<description><![CDATA[ I recently had the unfortunate experience of having a rather large blemish emerge on the plumpest area of my cheek. It was ugly and it attracted a lot of attention. Oh, people were very kind and didn&#8217;t say anything out loud, but I caught them fighting with themselves to keep their eyes from drifting over and [...]]]></description>
			<content:encoded><![CDATA[<p><font face="'Times New Roman'" class="Apple-style-span"> <!--StartFragment--><span style="font-size: 13pt; font-family: 'Times New Roman'">I recently had the unfortunate experience of having a rather large blemish emerge on the plumpest area of my cheek. It was ugly and it attracted a lot of attention. Oh, people were very kind and didn&#8217;t say anything out loud, but I caught them fighting with themselves to keep their eyes from drifting over and landing on the volcano on my face.  I considered covering it with a bandage, but instead used my tried and true green cover stick. Green is supposed to neutralize the red. Alas in this case, it was so far gone nothing helped no matter the color. Then something interesting happened. The poor souls who were forced to attend a meeting with me or who spent more time than a passing, &#8220;how are you,&#8221; couldn&#8217;t help subconsciously fingering their own cheeks at the very spot my blemish lived. It was as if scratching their own cheek would make the bump on mine disappear. It&#8217;s kind of like people wiping their own nose when you have, well, debris in yours. Anyway, this experience led me to a leadership observation (yes, I&#8217;m tying zits to leadership&#8211;hold on).</span><!--EndFragment-->    </font>
<p class="MsoNormal" style="margin-bottom: 0.0001pt"><span class="Apple-style-span" style="font-family: 'Times New Roman'">Leaders are watched. Their employees, their peers, and others watch them much of the time. Good leaders are imitated, and I mean that in a good way. Much like subconsciously trying to make your zit disappear by picking at their own cheek, your followers will copy your behaviors. If you regularly thank people for a job well done, or keep a smile on your face most of the time, or go out of your way to provide outstanding customer service, your followers will start doing the same. You&#8217;ll notice them thanking each other and making sure they go above and beyond in helping customers. But make no mistake; if you happen to be a not-so-good leader, they&#8217;ll copy those behaviors too. Flying off the handle, accusing people without knowing the facts, dragging others through mud, you name it. </span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt">&nbsp;</p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt"><span class="Apple-style-span" style="font-family: 'Times New Roman'">So the next time you have a prominent zit that others can&#8217;t help noticing (or maybe start now), make sure you&#8217;re demonstrating qualities and behaviors that you&#8217;d like to see your team member&#8217;s display. </span></p>
<p><!--EndFragment--></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kimheldman.com/2011/04/04/zits-and-leadership/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Leadership 101</title>
		<link>http://blog.kimheldman.com/2010/09/27/leadership-101/</link>
		<comments>http://blog.kimheldman.com/2010/09/27/leadership-101/#comments</comments>
		<pubDate>Mon, 27 Sep 2010 23:32:06 +0000</pubDate>
		<dc:creator>Kim</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.kimheldman.com/2010/09/27/leadership-101/</guid>
		<description><![CDATA[     
 
   
In keeping with the theme from my last post on setting up a scenario and asking how you would respond, I have a new, real life scenario for you. I’ve changed the names and the specifics of the incident to protect the guilty party.
Here’s the set [...]]]></description>
			<content:encoded><![CDATA[<p><meta name="Title" /> <meta name="Keywords" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta name="ProgId" content="Word.Document" /> <meta name="Generator" content="Microsoft Word 2008" /> <meta name="Originator" content="Microsoft Word 2008" /></p>
<link href="file://localhost/Users/kimheldman/Library/Caches/TemporaryItems/msoclip/0clip_filelist.xml" rel="File-List" /> <!--[if gte mso 9]><xml>  <o:OfficeDocumentSettings>   <o:AllowPNG/>  </o:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:WordDocument>   <w:Zoom>0</w:Zoom>   <w:TrackMoves>false</w:TrackMoves>   <w:TrackFormatting/>   <w:PunctuationKerning/>   <w:DrawingGridHorizontalSpacing>18 pt</w:DrawingGridHorizontalSpacing>   <w:DrawingGridVerticalSpacing>18 pt</w:DrawingGridVerticalSpacing>   <w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery>   <w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery>   <w:ValidateAgainstSchemas/>   <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>   <w:IgnoreMixedContent>false</w:IgnoreMixedContent>   <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>   <w:Compatibility>    <w:BreakWrappedTables/>    <w:DontGrowAutofit/>    <w:DontAutofitConstrainedTables/>    <w:DontVertAlignInTxbx/>   </w:Compatibility>  </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:LatentStyles DefLockedState="false" LatentStyleCount="276">  </w:LatentStyles> </xml><![endif]--><br />
<style><span> <!--  /* Font Definitions */ @font-face 	{font-family:<span>Cambria</span>; 	<span>panose</span>-1:2 4 5 3 5 4 6 3 2 4; 	<span>mso</span>-font-<span>charset</span>:0; 	<span>mso</span>-generic-font-family:auto; 	<span>mso</span>-font-pitch:variable; 	<span>mso</span>-font-signature:3 0 0 0 1 0;}  /* Style Definitions */ p.<span>MsoNormal</span>, <span>li</span>.<span>MsoNormal</span>, div.<span>MsoNormal</span> 	{<span>mso</span>-style-parent:&#8221;"; 	margin-top:0in; 	margin-right:0in; 	margin-bottom:10.0pt; 	margin-left:0in; 	<span>mso</span>-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:&#8221;Times New Roman&#8221;; 	<span>mso</span>-<span>ascii</span>-font-family:<span>Cambria</span>; 	<span>mso</span>-<span>fareast</span>-font-family:<span>Cambria</span>; 	<span>mso</span>-<span>hansi</span>-font-family:<span>Cambria</span>; 	<span>mso</span>-<span>bidi</span>-font-family:&#8221;Times New Roman&#8221;;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.25in 1.0in 1.25in; 	<span>mso</span>-header-margin:.5in; 	<span>mso</span>-footer-margin:.5in; 	<span>mso</span>-paper-source:0;} div.Section1 	{page:Section1;} &#8211;> </span></style>
<p> <!--[if gte mso 10]><br />
<style>  /* Style Definitions */ table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-ascii-font-family:Cambria; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Cambria; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} </style>
<p> <![endif]-->  <!--StartFragment--></p>
<p class="MsoNormal">In keeping with the theme from my last post on setting up a scenario and asking how you would respond, I have a new, real life scenario for you. I’ve changed the names and the specifics of the incident to protect the guilty party.</p>
<p class="MsoNormal">Here’s the set up. Many of the members of your executive staff don’t communicate well with each other, let alone others beneath…I’m sorry…at lower levels of the organization. Imagine that your employee has received an email from one of these executive managers that begins like this:</p>
<p class="MsoNormal">“Understand that I am way past pissed off on this one.”</p>
<p class="MsoNormal">Point number one: The employee who received this email reports to you. You are not in this executive&#8217;s chain of command, and therefore neither is this employee.</p>
<p class="MsoNormal">Oh, did I mention that this executive copied the entire leadership team, along with others down stream, to spread his good cheer?</p>
<p class="MsoNormal">Point number two: The contents of the email go on to berate this employee for their ignorance in making their request. It also does a good job of making the employee look like an idiot.</p>
<p class="MsoNormal">Point number three: The, dare I call him, gentlemen who sent this email, never bothered to pick up the phone and call the employee to ask any clarifying questions before sending the email. Nor did he call you, his peer, to ask about the situation.</p>
<p class="MsoNormal">Point number four: The facts in the email were WRONG. The executive had not bothered to communicate with other members of the team who already had the information, understood the project, and were well informed of what was happening.</p>
<p class="MsoNormal">Question: What would you do in this scenario?</p>
<p><!--EndFragment--></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kimheldman.com/2010/09/27/leadership-101/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Intuition</title>
		<link>http://blog.kimheldman.com/2010/09/14/intuition/</link>
		<comments>http://blog.kimheldman.com/2010/09/14/intuition/#comments</comments>
		<pubDate>Wed, 15 Sep 2010 01:16:32 +0000</pubDate>
		<dc:creator>Kim</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.kimheldman.com/2010/09/14/intuition/</guid>
		<description><![CDATA[     
 
In preparing for an upcoming presentation, I did some research on the qualities of leaders. Most qualities pop right to mind: integrity, honesty, respect, and so on. These are qualities you never want to compromise. Once you&#8217;ve crossed the bridge and your honesty has been breached or your integrity [...]]]></description>
			<content:encoded><![CDATA[<p><meta name="Title" /> <meta name="Keywords" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta name="ProgId" content="Word.Document" /> <meta name="Generator" content="Microsoft Word 2008" /> <meta name="Originator" content="Microsoft Word 2008" /></p>
<link href="file://localhost/Users/kimheldman/Library/Caches/TemporaryItems/msoclip/0clip_filelist.xml" rel="File-List" /> <!--[if gte mso 9]><xml>  <o:OfficeDocumentSettings>   <o:AllowPNG/>  </o:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:WordDocument>   <w:Zoom>0</w:Zoom>   <w:TrackMoves>false</w:TrackMoves>   <w:TrackFormatting/>   <w:PunctuationKerning/>   <w:DrawingGridHorizontalSpacing>18 pt</w:DrawingGridHorizontalSpacing>   <w:DrawingGridVerticalSpacing>18 pt</w:DrawingGridVerticalSpacing>   <w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery>   <w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery>   <w:ValidateAgainstSchemas/>   <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>   <w:IgnoreMixedContent>false</w:IgnoreMixedContent>   <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>   <w:Compatibility>    <w:BreakWrappedTables/>    <w:DontGrowAutofit/>    <w:DontAutofitConstrainedTables/>    <w:DontVertAlignInTxbx/>   </w:Compatibility>  </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:LatentStyles DefLockedState="false" LatentStyleCount="276">  </w:LatentStyles> </xml><![endif]-->
<p class="MsoNormal">In preparing for an upcoming presentation, I did some research on the qualities of leaders. Most qualities pop right to mind: integrity, honesty, respect, and so on. These are qualities you never want to compromise. Once you&#8217;ve crossed the bridge and your honesty has been breached or your integrity called into question, you will like never have the opportunity to gain the trust and position you once held. It&#8217;s sad, isn&#8217;t it, that we have so many leaders today that don&#8217;t display even these foundational leadership qualities. But I&#8217;ll save that topic for another blog.</p>
<p class="MsoNormal">One of the not so obvious qualities of great leaders I know and have worked with is intuition. There is a strange phenomenon that occurs as you progress up the corporate ladder—you have less and have less information available to make decisions. It isn’t necessarily that the information doesn’t exist, but you now have a broader range of responsibility, a much bigger portfolio of projects, and potentially hundreds or thousands of staff. It isn’t possible for one person to know everything about dozens of projects or hundreds of staff members in their span of control. Many times, decisions are needed quickly without time to perform analysis paralysis. Often, those decisions are snap decisions that are made from the gut.</p>
<p class="MsoNormal">Most good leaders I know and have worked with, have an innate ability to intuitively make good decisions. I have had times when intuition was the only information I had to rely on to make a decision. Practice honing your intuitive skills by thinking back on specific examples in your own life where you just knew something was right. A right answer, a correct choice, the right card to play or number to pick. Anything where you didn’t have sufficient information but you still knew the answer. Think about how you felt and how the intuitive information came about. Was it quick? Did it come from your head or your gut? Was the answer audible? (Okay, we could get into some real funny stories here about psycho leaders, but let’s save that for another day.) Try to use these same experiences when a new situation arises to bring about an intuitive response. One more experiment you can try is make random guesses in benign situations. Guess what kind of car will be in front of you when you enter the highway. Guess which parking space you’ll get before arriving at the store. Guess which commercial is coming up next on your favorite TV program. Intuition is a good skill to have. However, I do recommend using information to help with decision making when it’s available and when you have time to review it. But don’t discount that “feeling” you might have that something just isn’t adding up and learn when to go with your gut.</p>
<p class="MsoNormal">I’m starting a new feature in the blog to spur some discussion. It’s called “Scenario for Discussion.” I’ll set up a scenario and then ask what you would do in this situation. I hope you enjoy it.</p>
<p class="MsoNormal">Scenario for Discussion: Suppose you’re a new leader in a brand new organization. You don’t know anyone on staff yet. One of your employees sets a meeting with you to discuss the poor morale he’s witnessed among his fellow teammates. As you’re meeting with him, something doesn’t sit right. He’s describing scenarios that don’t make sense, and he has performed some questionable actions himself such as contacting a reporter with information about the latest project your company is working on. When you ask him if he’s met with management to discuss his concerns about this project and the poor morale issue, his response is no. He tells you that they wouldn’t listen so why should he waste his time? Since you’re brand new, he’s hoping you aren’t like “them” and will take this situation seriously. Scenario question: What would you do in this situation?</p>
<p><!--EndFragment--></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kimheldman.com/2010/09/14/intuition/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Believing Will Make It So</title>
		<link>http://blog.kimheldman.com/2010/05/25/believing-will-make-it-so/</link>
		<comments>http://blog.kimheldman.com/2010/05/25/believing-will-make-it-so/#comments</comments>
		<pubDate>Tue, 25 May 2010 15:11:43 +0000</pubDate>
		<dc:creator>Kim</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.kimheldman.com/2010/05/25/believing-will-make-it-so/</guid>
		<description><![CDATA[     
 
  
   
I recently watched a TEDTalks podcast titled “Simon Sinek: How great leaders inspire action.” It’s a fascinating talk and I encourage you to give it a listen. Simon’s main premise is, “[People] don’t buy what you do, they buy why you do it.” Ultimately, [...]]]></description>
			<content:encoded><![CDATA[<p><meta name="Title" /> <meta name="Keywords" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta name="ProgId" content="Word.Document" /> <meta name="Generator" content="Microsoft Word 2008" /> <meta name="Originator" content="Microsoft Word 2008" /></p>
<link href="file://localhost/Users/kimheldman/Library/Caches/TemporaryItems/msoclip/0/clip_filelist.xml" rel="File-List" /> <!--[if gte mso 9]><xml>  <o:OfficeDocumentSettings>   <o:AllowPNG/>  </o:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:WordDocument>   <w:Zoom>0</w:Zoom>   <w:TrackMoves>false</w:TrackMoves>   <w:TrackFormatting/>   <w:PunctuationKerning/>   <w:DrawingGridHorizontalSpacing>18 pt</w:DrawingGridHorizontalSpacing>   <w:DrawingGridVerticalSpacing>18 pt</w:DrawingGridVerticalSpacing>   <w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery>   <w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery>   <w:ValidateAgainstSchemas/>   <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>   <w:IgnoreMixedContent>false</w:IgnoreMixedContent>   <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>   <w:Compatibility>    <w:BreakWrappedTables/>    <w:DontGrowAutofit/>    <w:DontAutofitConstrainedTables/>    <w:DontVertAlignInTxbx/>   </w:Compatibility>  </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:LatentStyles DefLockedState="false" LatentStyleCount="276">  </w:LatentStyles> </xml><![endif]--><br />
<style> <!--  /* Font Definitions */ @font-face 	{font-family:Cambria; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;}  /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-parent:""; 	margin-top:0in; 	margin-right:0in; 	margin-bottom:10.0pt; 	margin-left:0in; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-ascii-font-family:Cambria; 	mso-fareast-font-family:Cambria; 	mso-hansi-font-family:Cambria; 	mso-bidi-font-family:"Times New Roman";} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.25in 1.0in 1.25in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;} --> </style>
<p> <!--[if gte mso 10]><br />
<style>  /* Style Definitions */ table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-ascii-font-family:Cambria; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Cambria; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} </style>
<p> <![endif]-->  <!--StartFragment--></p>
<p class="MsoNormal">I recently watched a TEDTalks podcast titled “Simon Sinek: How great leaders inspire action.” It’s a fascinating talk and I encourage you to give it a listen. Simon’s main premise is, “[People] don’t buy what you do, they buy why you do it.” Ultimately, the why is what you believe. People will sign up for projects or follow their leaders to the ends of the earth because they believe what their leaders believe. And as such, this belief becomes personal. The vision becomes their own.</p>
<p class="MsoNormal">So my question for all you leaders out there is this: are you communicating what you believe? It’s difficult for others to follow you if they don’t know what you believe. I know we all hear the “communicate, communicate, communicate,” mantra incessantly. But it’s not just the act of communicating that’s important, it’s what you communicate. You can tell me all day long that we’re going to save significant amounts of time and money by implementing project X. Great. But savings and efficiencies are a result (the “what” in Sinek’s theory), they aren’t a belief. It’s very difficult for those of us in the trenches to use savings or efficiency as a motivator for jumping on the latest project bandwagon and acting as cheerleaders for the doubters around us. Let me give you an example.</p>
<p class="MsoNormal">I recently attended a presentation where an executive from a multi-billion, global company discussed the recent consolidation of their information technology (IT) department.<span>  </span>Up until this project was undertaken, each business unit around the globe had their own IT department with their own procurement rules, governance policies, and so on. This model was inefficient and caused delayed response times, finger pointing, and downright obstinacy when headquarters wanted to implement a standardized IT policy.</p>
<p class="MsoNormal">The why (the belief the CIO and executive IT leaders held) was communicated to the stakeholders and IT staff many times during the course of the project. It went something like this, “We want to become a unified organization able to quickly respond to our customers needs with flexibility, agility, and resiliency while generating savings to our organization.” This company is now two years into their consolidation and it’s a huge success. I believe it was successful because the stakeholders and staff employed by the organization clearly understood the “why” of the project and they made that belief their own. The majority of employees believed that the consolidation would make them stronger, more resilient, and able to act quickly to supply solutions and resolve problems for their customers. That’s a fantastic message. It’s also a message that’s easier for people to believe and make their own than saving money and gaining efficiencies.</p>
<p class="MsoNormal">But what if instead, the message went something like this, “We have the potential to save millions of dollars and gain significant efficiencies so get on board with this project.” Granted, savings and efficiencies are great goals. But are they goals a help desk person or a server technician really cares about? No. Savings and efficiencies are goals executive management is concerned about. Most line staff in an IT organization are concerned about their customer. If they see that being unified will help them be flexible and give them more choices when solving their customer’s problems, they are more likely to believe and support a project that brings about those results.<span>   </span></p>
<p class="MsoNormal">Public speakers are told that you have to tailor the message to the audience. That’s exactly what this global organization did. Now let’s flip the coin. Let’s say you’re selling this idea to executive stakeholders. The CEO, the CFO, and the COO.<span>  </span>I think you see the point. They DO want to hear about cost savings and efficiencies and faster response times as a result. This is exactly the message you want to use with this group in order to gain their buy-in.</p>
<p class="MsoNormal">The success of this global organization’s consolidation hinged on communication that was targeted to the audience. The CIO sold this major project to their executive team using savings and efficiencies as the premise. They sold it to staff and other stakeholders using a unified, flexible model for addressing problems quickly. You can see that both approaches are necessary because both of these groups are thinking about the project from the aspect of how it benefits their department or their day-to-day work on a personal level.</p>
<p class="MsoNormal">Believing in a mission or a project or a new venture is personal. We as leaders have to make the message personal for all of those impacted in order to win the support of the majority. So tell others what you believe about your current project and watch them catch the vision.</p>
<p><!--EndFragment--></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kimheldman.com/2010/05/25/believing-will-make-it-so/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Just Say No</title>
		<link>http://blog.kimheldman.com/2010/01/17/just-say-no/</link>
		<comments>http://blog.kimheldman.com/2010/01/17/just-say-no/#comments</comments>
		<pubDate>Sun, 17 Jan 2010 20:26:40 +0000</pubDate>
		<dc:creator>Kim</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.kimheldman.com/2010/01/17/just-say-no/</guid>
		<description><![CDATA[     
         
 
  
   
My dad always used to tell me that you are who you are when no one else is looking. It’s not what you do when others are watching, it’s what you do when you’re all [...]]]></description>
			<content:encoded><![CDATA[<p><meta name="Title" /> <meta name="Keywords" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta name="ProgId" content="Word.Document" /> <meta name="Generator" content="Microsoft Word 2008" /> <meta name="Originator" content="Microsoft Word 2008" /></p>
<link href="file://localhost/Users/kimheldman/Library/Caches/TemporaryItems/msoclip/0/clip_filelist.xml" rel="File-List" /> <!--[if gte mso 9]><xml>  <o:OfficeDocumentSettings>   <o:AllowPNG/>  </o:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:WordDocument>   <w:Zoom>0</w:Zoom>   <w:TrackMoves>false</w:TrackMoves>   <w:TrackFormatting/>   <w:PunctuationKerning/>   <w:DrawingGridHorizontalSpacing>18 pt</w:DrawingGridHorizontalSpacing>   <w:DrawingGridVerticalSpacing>18 pt</w:DrawingGridVerticalSpacing>   <w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery>   <w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery>   <w:ValidateAgainstSchemas/>   <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>   <w:IgnoreMixedContent>false</w:IgnoreMixedContent>   <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>   <w:Compatibility>    <w:BreakWrappedTables/>    <w:DontGrowAutofit/>    <w:DontAutofitConstrainedTables/>    <w:DontVertAlignInTxbx/>   </w:Compatibility>  </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:LatentStyles DefLockedState="false" LatentStyleCount="276">  </w:LatentStyles> </xml><![endif]-->   <meta name="Title" /> <meta name="Keywords" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta name="ProgId" content="Word.Document" /> <meta name="Generator" content="Microsoft Word 2008" /> <meta name="Originator" content="Microsoft Word 2008" />
<link href="file://localhost/Users/kimheldman/Library/Caches/TemporaryItems/msoclip/0/clip_filelist.xml" rel="File-List" /> <!--[if gte mso 9]><xml>  <o:OfficeDocumentSettings>   <o:AllowPNG/>  </o:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:WordDocument>   <w:Zoom>0</w:Zoom>   <w:TrackMoves>false</w:TrackMoves>   <w:TrackFormatting/>   <w:PunctuationKerning/>   <w:DrawingGridHorizontalSpacing>18 pt</w:DrawingGridHorizontalSpacing>   <w:DrawingGridVerticalSpacing>18 pt</w:DrawingGridVerticalSpacing>   <w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery>   <w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery>   <w:ValidateAgainstSchemas/>   <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>   <w:IgnoreMixedContent>false</w:IgnoreMixedContent>   <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>   <w:Compatibility>    <w:BreakWrappedTables/>    <w:DontGrowAutofit/>    <w:DontAutofitConstrainedTables/>    <w:DontVertAlignInTxbx/>   </w:Compatibility>  </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:LatentStyles DefLockedState="false" LatentStyleCount="276">  </w:LatentStyles> </xml><![endif]--><br />
<style> <!--  /* Font Definitions */ @font-face 	{font-family:Verdana; 	panose-1:2 11 6 4 3 5 4 4 2 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;} @font-face 	{font-family:Cambria; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;}  /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-parent:""; 	margin-top:0in; 	margin-right:0in; 	margin-bottom:10.0pt; 	margin-left:0in; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-ascii-font-family:Cambria; 	mso-fareast-font-family:Cambria; 	mso-hansi-font-family:Cambria; 	mso-bidi-font-family:"Times New Roman";} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.25in 1.0in 1.25in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;} --> </style>
<p> <!--[if gte mso 10]><br />
<style>  /* Style Definitions */ table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-ascii-font-family:Cambria; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Cambria; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} </style>
<p> <![endif]-->  <!--StartFragment--></p>
<p class="MsoNormal"><span style="font-family: Verdana">My dad always used to tell me that you are who you are when no one else is looking. It’s not what you do when others are watching, it’s what you do when you’re all alone and no one knows. I’ve spent my career following that advice and it’s served me well. I have had more than one instance where inappropriate opportunities presented themselves that would have benefited me—but I ran in the opposite direction. </span></p>
<p><!--EndFragment--></p>
<p class="MsoNormal"><span style="font-family: Verdana">There are two qualities I demand of all project team members who work for me—honesty and integrity. You can tell me almost anything, as long as it’s the truth. I worked with a fantastic team member one time who accidentally deleted one of our client’s database of customer records. Every customer, every record, gone. My team member did the right thing. He told me the truth, what he did, and how it happened. Thankfully, after working many long hours by his side, we were able to recover the data. Because he was truthful, we were able to right the situation for our client and he kept his job.<span>  </span><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family: Verdana">What is very disheartening to me are those who are covert and sneaky about their actions but haven’t yet been caught. But I’ve been around long enough to know that most everyone involved in these escapades is eventually found out. I used to work at an unnamed government agency where an employee was caught stealing. She had spent years pilfering tax payer money. And we’re talking millions of dollars! I knew her personally and I have to admit, while I’m a pretty good judge of character, she wasn’t someone I believed could be involved in theft. She’s serving out her thirty-year sentence as we speak. I’m guessing she doesn’t think it was worth it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family: Verdana">As a PMP, we all agree to abide by the PMI Code of Ethics and Professional Conduct. I had a very alert reader inform me that this site: <a href="http://pmptutorial.blogspot.com/">http://pmptutorial.blogspot.com/</a> was plagiarizing some of my material. Sure enough, pages 26 – 30 are posted on this site, word for word, including a figure that I created. I have no doubt my publisher’s attorney will issue a cease and desist order. This person is violating copyright laws and the PMI Code. Again, it&#8217;s disheartening to think that there are project managers, even would be project managers, who could engage in this behavior. It gives us all a bad name. The other saying my dad used to tell me was that if you’re faithful in the little things, you’ll be faithful in the big things. Copying some text and a drawing may seem like a little thing, but where does it stop? How about taking a bonus under the table to approve requirements we know aren’t acceptable? How about a golf trip to Vegas if we assure the vendor that we’ll award them the contract? We know the answer to those questions—just say no.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family: Verdana">My advice is don’t even take the first step. Because little steps can lead us right over a cliff if we aren’t careful. If we begin to justify the little missteps, it’s only a matter of time before the big ones follow. The problem is, as the women who is now serving her thirty-year sentence has found, you continue to gain confidence with each misstep and eventually think you’re invincible. And that’s when it catches up with you. Say no to the little things and the big things will never be a question. <o:p></o:p></span></p>
<p><!--EndFragment--> <!--EndFragment--></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kimheldman.com/2010/01/17/just-say-no/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Please Take Your Seat</title>
		<link>http://blog.kimheldman.com/2009/09/08/please-take-your-seat/</link>
		<comments>http://blog.kimheldman.com/2009/09/08/please-take-your-seat/#comments</comments>
		<pubDate>Tue, 08 Sep 2009 16:32:08 +0000</pubDate>
		<dc:creator>Kim</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.kimheldman.com/2009/09/08/please-take-your-seat/</guid>
		<description><![CDATA[     
 
  
   I took the redeye to Chicago this morning, which means I set the alarm for 3:30 a.m. I thought, no problem, I can catch almost two hours of shuteye on the plane. Wrong!
First, let me start out by applauding American Airlines for enforcing the [...]]]></description>
			<content:encoded><![CDATA[<p><meta name="Title" /> <meta name="Keywords" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta name="ProgId" content="Word.Document" /> <meta name="Generator" content="Microsoft Word 2008" /> <meta name="Originator" content="Microsoft Word 2008" /></p>
<link href="file://localhost/Users/kimheldman/Library/Caches/TemporaryItems/msoclip/0clip_filelist.xml" rel="File-List" /> <!--[if gte mso 9]><xml>  <o:OfficeDocumentSettings>   <o:AllowPNG/>  </o:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:WordDocument>   <w:Zoom>0</w:Zoom>   <w:TrackMoves>false</w:TrackMoves>   <w:TrackFormatting/>   <w:PunctuationKerning/>   <w:DrawingGridHorizontalSpacing>18 pt</w:DrawingGridHorizontalSpacing>   <w:DrawingGridVerticalSpacing>18 pt</w:DrawingGridVerticalSpacing>   <w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery>   <w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery>   <w:ValidateAgainstSchemas/>   <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>   <w:IgnoreMixedContent>false</w:IgnoreMixedContent>   <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>   <w:Compatibility>    <w:BreakWrappedTables/>    <w:DontGrowAutofit/>    <w:DontAutofitConstrainedTables/>    <w:DontVertAlignInTxbx/>   </w:Compatibility>  </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:LatentStyles DefLockedState="false" LatentStyleCount="276">  </w:LatentStyles> </xml><![endif]--><br />
<style> <!--  /* Font Definitions */ @font-face 	{font-family:Cambria; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:3 0 0 0 1 0;}  /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-parent:""; 	margin-top:0in; 	margin-right:0in; 	margin-bottom:10.0pt; 	margin-left:0in; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-ascii-font-family:Cambria; 	mso-fareast-font-family:Cambria; 	mso-hansi-font-family:Cambria; 	mso-bidi-font-family:"Times New Roman";} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.25in 1.0in 1.25in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;} --> </style>
<p> <!--[if gte mso 10]><br />
<style>  /* Style Definitions */ table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-ascii-font-family:Cambria; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Cambria; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} </style>
<p> <![endif]-->  <!--StartFragment--><span style="font-size: 12pt; font-family: Cambria">I took the redeye to Chicago this morning, which means I set the alarm for 3:30 a.m. I thought, no problem, I can catch almost two hours of shuteye on the plane. Wrong!</p>
<p>First, let me start out by applauding American Airlines for enforcing the two-bag carry on rule (okay, one bag and one personal item which can be pretty darn large by the looks of things.) We’ve all heard the rule and then witnessed the business person (or tourist) laden with roller bag, duffel bag, and a brief case or jumbo-sized purse just breeze right on by the attendant and board the plane. What fries me is the poor sucker who brings on <em>one </em>bag and there’s no space left in the overheads to hold it. It won’t fit under the seat so they’re forced to check the bag while Joe and Sally 3-bagger sit smugly in their seats and simply whisk their stuff off the plane upon landing. Yes, I’ve been the poor sucker who had to check a carry-on bag that ended up getting lost, that had my car keys in it because you’re <em>supposed </em>to put your car keys and medicines in your carry-on. But that’s a story for another day. Thank you, AA, for enforcing the two-bag rule.</p>
<p>So, picture this. You’re sitting in the airport holding coral and survey your fellow passengers. If you’re anything like me, I should say if your luck is anything like mine when it comes to flying, scan the scene and pick out the largest passenger you see or the most obnoxious one. Guaranteed, that’s the one who’ll be sitting next to me. And yup, it happened again this morning.</p>
<p>I’m not a big person. I don’t even hit 5’2” and I tend more toward the thinner side of the scale than the heavy side. I mean, I just don’t take up a lot of space. I can sit in the airline seat and have enough room to shove a good size purse between me and the airplane body. I don’t do this, and you’ll see why in a moment, but I could if I wanted to. Don’t get me wrong. I sincerely empathize with the tall and broad among us. My husband tops 6’5” and talk about being crammed packed into an airline seat. His knees are in his chest and he silently prays through the whole flight that the person in front of him does not put his seat back. Truly, I get it.</p>
<p>But for heaven’s sake, my seat is my seat—not your seat. I don’t even mind that all men, and I mean every last one I’ve ever flown next to or between, believes they have a God-given right to the arm rest. If you’re a woman, forget it. Don’t even try to claim it—it doesn’t belong to us. So I gladly relinquish the armrest upon boarding. But OMG. Can I have my seat? I would appreciate not holding your papers in my lap, or having my shoulders bumped fifteen thousand times in flight. A few times is understandable, I get the plight of big folks in a tiny airline seat but after the third or fourth bump, I’ve had enough. The guy this morning could clearly see I was trying to sleep. I crouched myself as close to the window as I could because I knew I was going to have to share my seat. And I did. With his jacket, his thigh, his shoulder, his arm, his phone, his morning paper, and the water bottle. I’m trying to sleep and perhaps out of nervousness (I’ll give him the benefit of the doubt on this one) he squeezed the bottle so it made a popping, cracking sound every time he took a drink. And the guy must have taken his jacket off and put it back on at least six times over the course of two hours. Needless to say, I didn’t sleep.</p>
<p>I just have to resign myself to the fact that even though I can easily fit into the airline seat, I’m by golly going to be just as uncomfortable as those among us who don’t fit into the seats so easily. Sigh. I’ve adjusted my attitude now and I’m packing up the Mac for the connecting flight. I’m surveying my fellow passengers, and, oh, I spot her! She’s the one, jumbo purse and all. Happy flying!<br />
<!--[if !supportLineBreakNewLine]--><br />
<!--[endif]--></span><!--EndFragment--></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kimheldman.com/2009/09/08/please-take-your-seat/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>

