<?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>Chad Sturtz &#187; People</title>
	<atom:link href="http://chadsturtz.com/category/people/feed/" rel="self" type="application/rss+xml" />
	<link>http://chadsturtz.com</link>
	<description>A Journey Through Software</description>
	<lastBuildDate>Wed, 04 May 2011 15:45:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
		<item>
		<title>The Two Types</title>
		<link>http://chadsturtz.com/2011/01/the-two-types/</link>
		<comments>http://chadsturtz.com/2011/01/the-two-types/#comments</comments>
		<pubDate>Thu, 13 Jan 2011 17:23:24 +0000</pubDate>
		<dc:creator>Chad</dc:creator>
				<category><![CDATA[Motivation]]></category>
		<category><![CDATA[People]]></category>
		<category><![CDATA[teamwork]]></category>

		<guid isPermaLink="false">http://chadsturtz.com/?p=132</guid>
		<description><![CDATA[There is a line that separates the people around you.  Depending on how you look at it, it may be blurry or clear, but you still know it&#8217;s there.  On the left side you have people that you want to invest in, do everything possible to keep at your organization, watch and learn from, and [...]]]></description>
			<content:encoded><![CDATA[<p>There is a line that separates the people around you.  Depending on how you look at it, it may be blurry or clear, but you still know it&#8217;s there.  On the left side you have people that you want to invest in, do everything possible to keep at your organization, watch and learn from, and let drive the direction of your team or business.  While those on the right side may be intelligent and hard working, you know they&#8217;re not the type of people to grow an organization around.</p>
<p>What separates these groups?  It&#8217;s the presence of four traits: vision, desire to learn, passion, and value of teamwork.</p>
<p>Vision is what keeps these people focused on the big picture in addition to their immediate tasks and surroundings.  They consider long term effects, understand how individual roles fit together, and are able to look at a single issue from many perspectives.  Passion keeps them motivated and always performing at their best.  It&#8217;s the excitement and reward they feel every day and is visible in their actions.  The desire to learn makes them ask &#8220;why?&#8221;.  They want to be taught to fish rather than given a meal.  They work to consume new information every day and grow from it.  Their value of teamwork encourages them to assist others and share information and responsibility.  They wear whatever hat is necessary, and often wear several hats at the same time.  They know that the most ambitious goals are possible with the right group of people.</p>
<p>Focus on creating teams with a majority of people from the left side.  Provide an environment and culture that encourages innovation and risk taking, does not treat change negatively, and invests in its people.  From this you will get processes that work well for your organization, an army of intelligent, productive, and efficient people, and an organization considered successful by any measure.</p>
]]></content:encoded>
			<wfw:commentRss>http://chadsturtz.com/2011/01/the-two-types/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>So much for that idea</title>
		<link>http://chadsturtz.com/2011/01/so-much-for-that-idea/</link>
		<comments>http://chadsturtz.com/2011/01/so-much-for-that-idea/#comments</comments>
		<pubDate>Fri, 07 Jan 2011 08:40:08 +0000</pubDate>
		<dc:creator>Chad</dc:creator>
				<category><![CDATA[Misc]]></category>
		<category><![CDATA[Motivation]]></category>
		<category><![CDATA[People]]></category>
		<category><![CDATA[presentations]]></category>

		<guid isPermaLink="false">http://chadsturtz.com/?p=128</guid>
		<description><![CDATA[9 months ago my daughter was born and since then I&#8217;ve had trouble finding much time for career development outside of the office.  One of my solutions to the problem was to form a sort of user group in my office that would meet over brown-bag lunch presentations.  I had already given a few brown-bag [...]]]></description>
			<content:encoded><![CDATA[<p>9 months ago my daughter was born and since then I&#8217;ve had trouble finding much time for career development outside of the office.  One of my solutions to the problem was to form a sort of user group in my office that would meet over brown-bag lunch presentations.  I had already given a few brown-bag lunch presentations myself, trying to set an example, but only one other person ever did a presentation.  I thought that if I wrote out what it was I wanted to do and how I expected to to be valuable to our team, maybe there&#8217;d be more buy-in.  Plus, if I could get everyone to do just 1 or 2 presentations a year, we could have a meeting every other week.</p>
<p>I approached the entire office with this proposal and was very thrilled to get buy-in from a large percentage of my coworkers.  I volunteered to do the first presentation and asked 2 of my more active coworkers to take care of presentations 2 &amp; 3 just to get things rolling.  Presentation number 3 is next week and after several emails, no one else in the office has volunteered for presentation #4 (or any other future slot).</p>
<p>I found out that for 2 people, the problem was coming up with something to talk about.  I have provided topic ideas as well as offered to brainstorm with anyone that was willing to present but unsure of a topic.  Still&#8230; no one has offered to present.</p>
<p>At this point I&#8217;m assuming it won&#8217;t pan out.  I felt it was acceptable to send a few emails stating that we needed people for upcoming presentations seeing as how I got a large amount of buy-in before this whole thing started, but I&#8217;m not going to push it.  If no one comes forward, I&#8217;ll just continue giving presentations when I can hoping that maybe someone else will jump in every once in a while.</p>
<p>I have to admit, I&#8217;m a little confused as to why so many people thought it was a good idea but then won&#8217;t participate.  I even found out that for presentation #2 (I was out sick), no one set up a virtual meeting or conference call for the few remote people assigned to our office.  Furthermore, those remote people never IM&#8217;d, emailed, or called anyone asking what number to call in on or for an invitation to the virtual meeting.  Maybe I&#8217;m the only one that feels there&#8217;s value here&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://chadsturtz.com/2011/01/so-much-for-that-idea/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Why I need Yammer</title>
		<link>http://chadsturtz.com/2010/07/why-i-need-yammer/</link>
		<comments>http://chadsturtz.com/2010/07/why-i-need-yammer/#comments</comments>
		<pubDate>Fri, 02 Jul 2010 20:48:44 +0000</pubDate>
		<dc:creator>Chad</dc:creator>
				<category><![CDATA[People]]></category>
		<category><![CDATA[teamwork]]></category>

		<guid isPermaLink="false">http://chadsturtz.com/?p=122</guid>
		<description><![CDATA[Q: Why do I need Yammer? A:  It&#8217;s simple&#8230; I want access to my fellow software engineers and technologists that live on the other side of boundaries that get created around other Departments, Products, Business Units, and Acquisitions. True story. I had to quickly come up to speed on a technology I had not been introduced [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Q</strong>: Why do I need Yammer?</p>
<p><strong>A</strong>:  It&#8217;s simple&#8230;<strong> </strong>I want access to my fellow software engineers and technologists that live on the other side of boundaries that get created around other Departments, Products, Business Units, and Acquisitions.</p>
<p>True story. I had to quickly come up to speed on a technology I had not been introduced to previously.  I took the normal approach of aggressively searching online to find examples, white papers, blogs, anything to help.  Time was running out, and while I had learned a lot in a short amount of time, I wanted a little help connecting all of the dots and selecting what I needed to focus on to complete my task in a timely manner.  I needed 15 minutes with an expert in this technology to guide me down the right path, because I didn&#8217;t have time to go down the wrong one.</p>
<p>I jumped on Yammer and put out a call for help.  A development manager responded with the name of a person who he knew to be experienced with this technology.  He introduced us over email and a few minutes later, I was getting exactly what I needed.</p>
]]></content:encoded>
			<wfw:commentRss>http://chadsturtz.com/2010/07/why-i-need-yammer/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Why you&#8217;re not ready for Agile: The real top 10 list</title>
		<link>http://chadsturtz.com/2010/07/why-youre-not-ready-for-agile-the-real-top-10/</link>
		<comments>http://chadsturtz.com/2010/07/why-youre-not-ready-for-agile-the-real-top-10/#comments</comments>
		<pubDate>Thu, 01 Jul 2010 19:25:38 +0000</pubDate>
		<dc:creator>Chad</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[People]]></category>

		<guid isPermaLink="false">http://chadsturtz.com/?p=115</guid>
		<description><![CDATA[The real 10 reasons your organization isn't ready for Agile.]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve all seen too many blogs and articles along the lines of &#8220;10 reasons you&#8217;re organization isn&#8217;t ready for Agile&#8221;.  I believe that buried under all of those &#8216;reasons&#8217; are fundamental problems that will keep your organization from reaching any high level of productivity.  Here it is, the real top 10 list:</p>
<p>1. you&#8217;re not hiring the right people</p>
<p>2. you&#8217;re not hiring the right people</p>
<p>3. you&#8217;re not hiring the right people</p>
<p>4. you&#8217;re not hiring the right people</p>
<p>5. you&#8217;re not hiring the right people</p>
<p>6. you&#8217;re not hiring the right people</p>
<p>7. you&#8217;re not hiring the right people</p>
<p>8. you&#8217;re not hiring the right people</p>
<p>9. you&#8217;re not hiring the right people</p>
<p>10. you&#8217;re not hiring the right people</p>
<p>Hopefully this comprehensive list will help you and your organization.  Cheers.</p>
]]></content:encoded>
			<wfw:commentRss>http://chadsturtz.com/2010/07/why-youre-not-ready-for-agile-the-real-top-10/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Problem Solvers</title>
		<link>http://chadsturtz.com/2009/11/problem-solvers/</link>
		<comments>http://chadsturtz.com/2009/11/problem-solvers/#comments</comments>
		<pubDate>Tue, 17 Nov 2009 20:47:19 +0000</pubDate>
		<dc:creator>Chad</dc:creator>
				<category><![CDATA[People]]></category>

		<guid isPermaLink="false">http://chadsturtz.com/?p=8</guid>
		<description><![CDATA[Over the past 5 years, I&#8217;ve had the opportunity to work with many people who were very knowledgeable in many different areas.  However, one thing I&#8217;ve come to realize all too often is that when it comes to solving difficult problems, knowledge is, at most, half the battle.  Time and time again I have seen people [...]]]></description>
			<content:encoded><![CDATA[<p>Over the past 5 years, I&#8217;ve had the opportunity to work with many people who were very knowledgeable in many different areas.  However, one thing I&#8217;ve come to realize all too often is that when it comes to solving difficult problems, knowledge is, at most, half the battle.  Time and time again I have seen people struggle at solving a problem they did not immediately know the answer to.  Without a suite of problem solving skills, the value of their knowledge of the problem domain quickly diminishes.  These are the times when the Problem Solvers step in and get the job done.</p>
<p>So, who are the real problem solvers?</p>
<p><strong>Visionaries &#8211; </strong>The greatest Problem Solvers can very quickly identify a clear path to success.  From this vision they are able to generate a plan of attack that will strategically expose the root problem and find the correct solution(s).</p>
<p><strong>Leaders &#8211; </strong>As a leader, the Problem Solver is able to coordinate the effort.  They break the the plan of attack down into individual tasks that can be executed in parallel by the resources at hand.</p>
<p><strong>Enablers &#8211; </strong>Possibly the most important skill a Problem Solver has is the ability to remove roadblocks or find alternative paths.  The key to solving a problem quickly is to never stop.  The Problem Solver recognizes this and focuses on getting himself/herself and others whatever it is they need to identify and fix the issue.</p>
<p><strong>Communicators &#8211; </strong>Solving problems requires that the right people have the right information.  The Problem Solver is able to recognize important data and ensure that the information is shared.  Furthermore, they identify all available communication channels and use them effectively.</p>
<p><strong>Adaptive -</strong> The Problem Solver knows that any new discovery can change everything.  At a moment&#8217;s notice, they are able to shift resources, open new communication channels, and devise an entirely new plan of attack.</p>
]]></content:encoded>
			<wfw:commentRss>http://chadsturtz.com/2009/11/problem-solvers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

