
<?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>mcdonaldland &#187; Business</title>
	<atom:link href="http://www.mcdonaldland.info/category/business/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mcdonaldland.info</link>
	<description>A magical discussion of software, economics, and other assorted theories.</description>
	<lastBuildDate>Thu, 15 Jul 2010 00:19:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Culture for the &#8220;A&#8221; Players</title>
		<link>http://www.mcdonaldland.info/2009/04/24/culture-for-the-a-players/</link>
		<comments>http://www.mcdonaldland.info/2009/04/24/culture-for-the-a-players/#comments</comments>
		<pubDate>Fri, 24 Apr 2009 16:49:23 +0000</pubDate>
		<dc:creator>Jason McDonald</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.mcdonaldland.info/2009/04/24/culture-for-the-a-players/</guid>
		<description><![CDATA[Many companies have the concept of &#8220;A&#8221;, &#8220;B&#8221;, and &#8220;C&#8221; players, although GE&#8217;s Jack Welch made this famous in one of his books. The reason there is no classification for a &#8220;D&#8221; player is because companies should ultimately get rid of anyone not performing to the expectations of, at the very least, a &#8220;C&#8221; player. [...]]]></description>
			<content:encoded><![CDATA[<p>Many companies have the concept of &#8220;A&#8221;, &#8220;B&#8221;, and &#8220;C&#8221; players, although GE&#8217;s Jack Welch made this famous in one of his books. The reason there is no classification for a &#8220;D&#8221; player is because companies should ultimately get rid of anyone not performing to the expectations of, at the very least, a &#8220;C&#8221; player.</p>
<p><strong>Characteristics of an &#8220;A&#8221; player:</strong></p>
<ul>
<li>Challenges the status quo in order to drive positive change</li>
<li>Delivers on objectives without having to have someone hold their hand</li>
<li>Will largely succeed in their tasks despite the deadlines, politics, and team involved</li>
<li>Wins</li>
</ul>
<p><strong>Characteristics of a &#8220;B&#8221; player:</strong></p>
<ul>
<li>Does what they are supposed to do</li>
<li>Has a good track record</li>
<li>Needs guidance sometimes but not hand holding</li>
<li>Sometimes goes above and beyond but is not the norm</li>
<li>Has the potential to step up to be an &#8220;A&#8221; player</li>
<li>Wins most of the time</li>
</ul>
<p><strong>Characteristics of a &#8220;C&#8221; player:</strong></p>
<ul>
<li>Sometimes does what they are supposed to do</li>
<li>Has a moderate track record</li>
<li>Rarely, if ever, goes above and beyond</li>
<li>Needs a fair to high level of hand holding</li>
<li>Has the potential to step up to be a &#8220;B&#8221; player</li>
<li>Sometimes wins</li>
</ul>
<p>Most companies are bottom heavy. That is, they spend a large deal of time working with and fostering &#8220;C&#8221; players with the expectation that &#8220;A&#8221; and &#8220;B&#8221; players are already doing a good job and don&#8217;t need attention. Part of what Jack Welch and GE advise is that companies shift their paradigm to focus more on the &#8220;A&#8221; and &#8220;B&#8221; players, thus making them more top heavy. The basic idea is that you give &#8220;C&#8221; players a set goal and opportunity to become &#8220;B&#8221; players. If they don&#8217;t meet the expectations in the given timeframe, send them on their way. This allows management to focus on cultivating &#8220;B&#8221; players into &#8220;A&#8221; players and better supporting the already existent &#8220;A&#8221; players.</p>
<p>Simple enough, right? Just don&#8217;t forget about the culture shift that will happen with this and what it means to the company.</p>
<p>The basic philosophy is going to differ between each class of employee. An &#8220;A&#8221; player will have a different outlook on values, vision, and ethics than a &#8220;B&#8221; or &#8220;C&#8221; player will. Each class of player will have different ideas of what they are looking for, what they can contribute, and what being part of the company means to them. What this means is that as a company shifts its weight from the bottom to the top the overall culture of the organization will change.</p>
<p>Don&#8217;t get me wrong here &#8211; I&#8217;m not talking about the core values or the culture that is transcribed in the mission statement and broadcast to the public. What I am talking about is the basic idea of what is important to employees.</p>
<p>Each class of employee will have distinctly different needs, each of which will typically correspond back to Maslow&#8217;s Hierarchy of Needs. Maslow&#8217;s basic idea is that human needs can be visualized as a pyramid.</p>
<p align="center"> <a href="javascript:void(0)" id="file-link-222" title="400px-maslows_hierarchy_of_needssvg.png" class="file-link image">  <img src="http://www.mcdonaldland.info/wp-content/uploads/2009/04/400px-maslows_hierarchy_of_needssvg.png" /></a></p>
<p align="center"><em> Figure 1: Maslow&#8217;s Hierarchy of Needs</em></p>
<p> Here are the basic steps, from bottom to top, and how they relate to the typical work environment:</p>
<ul>
<li><strong>Physiological</strong><br />
This is the bottom of the pyramid. This typically relates to physical workplace safety. Construction workers are more likely to be focused on this step than are office workers. Likewise, police and soldiers are likely going to be more focused on this step than even construction. The main concern here will be whether something on the job will prove to be harmful or not.</li>
<li><strong>Security</strong><br />
The security of this phase is more related to peace of mind than physical security. Security generally relates to whether or not the job is stable. Do workers worry about being demoted, not getting a stable paycheck, or getting laid off?</li>
<li><strong>Love and Belonging</strong><br />
The idea that an employee can come into work and feel like part of a team falls into this category. Employees worried about this stage will often feel like they are an outside or loner and not fully part of the team. They may feel that they are moving in their own direction, which is incongruent to the direction of the team or company.</li>
<li><strong>Self Esteem</strong><br />
This is the idea that when a worker contributes something he or she feels that it was of value and important to the organization. Workers stuck in this stage will generally be worried about the quality of their work and whether their peers and superiors view their work in the same light and with the same respect that they do.</li>
<li><strong>Self Actualization</strong><br />
This is the top of the pyramid. This step focuses on creativity, morality, philosophy, and other higher level objectives. The concerns of people in this step are going to be whether they are afforded enough leeway to do things like be creative and whether the actions they take are moral and ethical.</li>
</ul>
<p>The basic concept here is that as lower level needs are met the person is then able to shift their focus to higher level and more complex needs.  This means that “C” players may be highly focused on the stability of their job and continuing to get a paycheck while “A” players are more worried about autonomy, the ability to be creative, and doing what they feel is morally and ethically right.</p>
<p>The transition from an “A”, “B”, and “C” player paradigm to an “A” and “B” one will almost always include a cultural shift in order to accommodate the different level of needs required by the majority. As the company shifts away from focusing primarily on “C” players to focusing primarily on “A” and “B” players the hierarchy level at which the collective company’s need is at is raised.</p>
<p>For example, lets say the old company was 50% “C” players. “C” players are worried about security and they make up the majority of the organization so there will be a large portion of management that is devoted to holding hands, regimenting work schedules, and looking over employees shoulders. As this 50% of “C” players is either shifted to “B” players or released the new makeup of the company may be more along the lines of 80% “B” players and 20% “A” players.</p>
<p>If the management that is used to dealing with “C” players continues to focus on the same problems they will inevitably miss the mark and alienate “B” and, especially, “A” players. Without shifting the cultural paradigm along with the performance expectations two things will happen. First, a portion of “B” players will fall into a “C” player category. If they are being treated like “C” players regardless of what they do, why not act like them? Second, “A” players will leave. Regardless of the state of the economy “A” players are always in high demand. Even if they are not able to find a job immediately, they eventually will. Either way, they will leave.</p>
<p>In order to successfully rid a company of “C” players the focus must be two fold: performance and cultural expectations. Without this, companies simply shift the bar higher but ultimately still have “C” players in the mix. In addition, and perhaps most importantly, failure to shift cultural expectations will inevitably result in the loss of “A” players, which is corporate suicide.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcdonaldland.info/2009/04/24/culture-for-the-a-players/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>I didn&#8217;t do it.</title>
		<link>http://www.mcdonaldland.info/2009/03/05/i-didnt-do-it/</link>
		<comments>http://www.mcdonaldland.info/2009/03/05/i-didnt-do-it/#comments</comments>
		<pubDate>Thu, 05 Mar 2009 21:30:44 +0000</pubDate>
		<dc:creator>Jason McDonald</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.mcdonaldland.info/2009/03/05/i-didnt-do-it/</guid>
		<description><![CDATA[Sam was out on a fishing trip with his three buddies and was many miles out to sea. At some point during the trip one of the guys, we&#8217;ll call him John, pulled out a shotgun and started &#8220;skeet&#8221; shooting empty beer cans. Sam didn&#8217;t think it is a good idea and advises against it. [...]]]></description>
			<content:encoded><![CDATA[<p>Sam was out on a fishing trip with his three buddies and was many miles out to sea. At some point during the trip one of the guys, we&#8217;ll call him John, pulled out a shotgun and started &#8220;skeet&#8221; shooting empty beer cans. Sam didn&#8217;t think it is a good idea and advises against it. Many beers later John finally got a little too relaxed (aka careless) and blew a good sized hole in the side of the boat. History tells us that holes and boats don&#8217;t mix well and, as expected, the boat began to sink.</p>
<p>Sam&#8217;s three buddies started to frantically bail water out of the boat using anything they can find &#8211; hats, plastic cups, their hands &#8211; but Sam just sat there. His buddies told him to help them bail and Sam only replied by saying he was against the idea to begin with and that he shouldn&#8217;t have to help clean up their mess.  The water was coming in fast enough that three people need to bail full time to keep the boat afloat. Eventually Sam&#8217;s friends began to tire and the water starts coming in faster than they can keep up.</p>
<p>The boat sinks and Sam drowns. Everyone else lives.</p>
<p>As the boat went down John took out the life preservers only to find that there were only three. Sam&#8217;s three buddies huddled up and decided that they were actively trying to save the boat, and their lives, so they should get the life jackets. As the boat continued to sink Sam held on for a while but eventually found himself treading water. Despite his efforts he couldn&#8217;t keep it up for long and eventually slipped underwater.</p>
<p>What Sam didn&#8217;t realize is that even though he was fundamentally against the idea and even though he played no part in the disaster, he was still on the boat. If the boat went down, so did he. Sam was too caught up in the blame game to recognize that the only way to save himself was to save his friends, regardless of whether he felt they deserved to be in their predicament or not.</p>
<p>There are a lot of Sam&#8217;s in business. Sam&#8217;s eventually drown. Especially when the economy is bad and every life vest is highly coveted. Don&#8217;t be Sam.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcdonaldland.info/2009/03/05/i-didnt-do-it/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Reducing Empowerment 101</title>
		<link>http://www.mcdonaldland.info/2009/02/06/reducing-empowerment-101/</link>
		<comments>http://www.mcdonaldland.info/2009/02/06/reducing-empowerment-101/#comments</comments>
		<pubDate>Fri, 06 Feb 2009 22:12:09 +0000</pubDate>
		<dc:creator>Jason McDonald</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.mcdonaldland.info/2009/02/06/reducing-empowerment-101/</guid>
		<description><![CDATA[All companies should strive to empower their employees. This simply means that all employees should feel that they have the ability to make decisions on behalf of the company. Toyota, for example, gives every employee the ability to stop the assembly line at any time, for any reason. Stopping the assembly line is an extremely [...]]]></description>
			<content:encoded><![CDATA[<p>All companies should strive to empower their employees. This simply means that all employees should feel that they have the ability to make decisions on behalf of the company. Toyota, for example, gives every employee the ability to stop the assembly line at any time, for any reason. Stopping the assembly line is an extremely expensive task for the company, however Toyota realizes that the people on the line have the knowledge, ability, and desire to be able to stop the assembly line if they see a problem. In essence, Toyota empowers them.</p>
<p>Empowerment has prerequisites and consequences though.</p>
<p>The prerequisites are pretty simple to state but harder to live &#8211; empowered employees must be aligned with the goals, vision, and processes of the company. If the employee is expected to act on behalf of the company then he or she must understand what the company wants and needs. Being tightly aligned with the core values of the company and understanding the vision of the firm is essential to this. Using Toyota again, one example may be that a frame on the assembly line is severely damaged, which an employee may realize will damage the assembly line itself. Stopping the line furthers the vision and values of the company by enhancing quality and saving money.</p>
<p>Conversely, if you have a strong alignment with the goals and vision but lack knowledge of the process, empowerment can hurt instead of help. Using the same example as before, if the employee stopped the assembly line because of the bent frame but didn&#8217;t know that there was already a process for handling such things, stopping the assembly line could result in a needless loss of money. If employees are not aligned with the visions and values of a company then the resulting decisions may be out of sync with what is truly good for the company.</p>
<p>The quickest way to reduce empowerment is to not have it evenly distributed. By this I mean that not everyone has an equal understanding of their level of empowerment and the implications of it. This can be for a number of reasons &#8211; everything from poor communication coming down from management to low self esteem of an empowered employee.</p>
<p>When you have varying levels of empowerment a few different forces are at play that reduce the benefit of an empowered company.</p>
<p>First, empowerment is reduced for all because of a reduced understanding by some. If people have varying degrees of what they are entitled to you will ultimately have confusion. This confusion will ultimately lead to a reduction of perceived empowerment by the group. Sticking with the example of the bent frame on the assembly line, if one employee feels they have the right to stop the assembly line but another doesn&#8217;t it is a matter of sheer luck as to which employee notices the defect. If the empowered one notices then they stop the assembly line and set a positive example for the rest of the employees. If the non-empowered one notices then they ignore it, also setting an example for the rest of the employees, albeit a negative one.</p>
<p>Second, people escalate needlessly. When there is confusion over levels of empowerment people will naturally escalate to superiors in order to gain clarification. Continuing our assembly line example, if both the empowered and unempowered employee notice the defect at the same time there will likely be confusion and debate over whether to stop the assembly line or not. Clarification will likely be sought and the line manager will be needlessly pulled in. Had both employees understood their level of empowerment the right thing would have been done and the line manager would have never been pulled in.</p>
<p>Finally, money, time, or other resources are wasted and management locks down the empowerment rights. This is simply a case of management treating the symptom instead of the ailment. If the assembly line is stopped when the employee should not have stopped it then management may incorrectly choose to treat the symptom, the employee wrongly choose to stop the assembly line, instead of the ailment, the fact that the employee doesn&#8217;t understand his or her level of empowerment. Locking down the empowerment instead of increasing awareness results in a loss for the entire company.</p>
<p>This is by no means an exhaustive list but simply the primary ones that are likely to occur when empowerment is not evenly distributed. Empowerment is good and is something that all companies should strive for. However, it is a double edged sword that must be handled with care to prevent inadvertently getting cut.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcdonaldland.info/2009/02/06/reducing-empowerment-101/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Slants and Steps</title>
		<link>http://www.mcdonaldland.info/2009/01/28/slants-and-steps/</link>
		<comments>http://www.mcdonaldland.info/2009/01/28/slants-and-steps/#comments</comments>
		<pubDate>Thu, 29 Jan 2009 01:27:56 +0000</pubDate>
		<dc:creator>Jason McDonald</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.mcdonaldland.info/2009/01/28/slants-and-steps/</guid>
		<description><![CDATA[I had someone that I reported up to at one time that explained the career cycle as a series of steps. The basic idea is that you spend some time at a given level, you learn and assimilate, then you move up to the next step and the process repeats itself. The basic idea is [...]]]></description>
			<content:encoded><![CDATA[<p>I had someone that I reported up to at one time that explained the career cycle as a series of steps. The basic idea is that you spend some time at a given level, you learn and assimilate, then you move up to the next step and the process repeats itself. The basic idea is that there are a virtually unlimited number of steps and that everyone moves from step to step at a different pace. Each step encompasses a variety of factors, all of which are unique to the person, step, situation, and company. Sometimes people walk right up and hit their virtual ceiling while others stagnate at the same step year after year. Others still will find themselves rising quickly only to level out at some point.<a href="javascript:void(0)" id="file-link-217" title="steps.JPG" class="file-link image"> 			</a></p>
<p align="center"><a href="javascript:void(0)" id="file-link-217" title="steps.JPG" class="file-link image"> </a><img src="http://www.mcdonaldland.info/wp-content/uploads/2009/01/steps.JPG" /></p>
<p align="center">Steps &#8211; moving regularly up through a career</p>
<p>The basic idea behind his metaphor is that you should always be moving up. If you look at a given employee (or yourself) and find that the person has spent a long time at a given step, then something is wrong. If a person is stalled out at a step they may need guidance &#8211; or perhaps they are just in the wrong position.</p>
<p><span class="file-link image"></p>
<p style="text-align: center"><img src="http://www.mcdonaldland.info/wp-content/uploads/2009/01/slant.JPG" /></p>
<p style="text-align: center">Slants &#8211; moving very quickly up through a career</p>
<p></span></p>
<p>Throughout my career I have seen three kinds of steppers. There are the people who follow the &#8220;norm&#8221; and step from one step to the next, regularly advancing their career. There are others who seem destined for the top and move almost along a straight line they move up the steps so quickly. Yet others skyrocket at first, only to find themselves slowing down the closer they get to the top. While many would pose that the regular steps are the most common, I would say that the quick ascent, followed by step is.</p>
<p><span class="file-link image"></p>
<p style="text-align: center"><img src="http://www.mcdonaldland.info/wp-content/uploads/2009/01/slantsteps.thumbnail.JPG" /></p>
<p style="text-align: center">Slants and Steps &#8211; moving up quickly, to a point, only to level out</p>
<p></span></p>
<p>The reason is actually quite simple: people will generally excel when they are undertasked and not challenged. Almost everyone falls into this category as they search out the job that is right for them. So what does this mean? It means that if you see yourself, or others, following a trend of very rapid career growth, perhaps they would be better utilized in a different position. This different position doesn&#8217;t necessarily mean that it has to be higher in the reporting chain, but simply more challenging and interesting to the individual charted.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcdonaldland.info/2009/01/28/slants-and-steps/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Lunch Meetings</title>
		<link>http://www.mcdonaldland.info/2008/12/10/lunch-meetings/</link>
		<comments>http://www.mcdonaldland.info/2008/12/10/lunch-meetings/#comments</comments>
		<pubDate>Wed, 10 Dec 2008 17:04:04 +0000</pubDate>
		<dc:creator>Jason McDonald</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.mcdonaldland.info/2008/12/10/lunch-meetings/</guid>
		<description><![CDATA[If you schedule a lunch meeting with people in your office you should supply lunch. Some situations are unavoidable and thus exempt, such as meetings with people in different time zones. However, if the meeting is all local, supply food.]]></description>
			<content:encoded><![CDATA[<p>If you schedule a lunch meeting with people in your office you should supply lunch.  Some situations are unavoidable and thus exempt, such as meetings with people in different time zones. However, if the meeting is all local, supply food.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcdonaldland.info/2008/12/10/lunch-meetings/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Credit Crunch</title>
		<link>http://www.mcdonaldland.info/2008/11/25/the-credit-crunch/</link>
		<comments>http://www.mcdonaldland.info/2008/11/25/the-credit-crunch/#comments</comments>
		<pubDate>Tue, 25 Nov 2008 18:46:26 +0000</pubDate>
		<dc:creator>Jason McDonald</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Economics and Politics]]></category>

		<guid isPermaLink="false">http://www.mcdonaldland.info/2008/11/25/the-credit-crunch/</guid>
		<description><![CDATA[I have been a strong proponent that bank deregulation is at the heart of our current credit issues. While I have always posed the argument that banks deserve a fair level of autonomy, they also need to be watched and controlled very closely. I ran across a video that talks about how money is created [...]]]></description>
			<content:encoded><![CDATA[<p>I have been a strong proponent that bank deregulation is at the heart of our current credit issues. While I have always posed the argument that banks deserve a fair level of autonomy, they also need to be watched and controlled very closely.</p>
<p>I ran across a <a href="http://blog.markturansky.com/archives/108" target="_blank">video that talks about how money is created</a> recently. In the video they site a study that maintains that a large majority of Americans have no clue how money is actually created. This is bad.</p>
<p>If you don&#8217;t know how money is created, <a href="http://blog.markturansky.com/archives/108" target="_blank">watch the videos</a>.  They are a concise overview of how money is created. They bake in a little doom and gloom that, while accurate, isn&#8217;t necessarily an immediate problem (although with credit crunches and bubbles it very well could become an immediate problem). They give a whirlwind tour of what is typically spanned over multiple college business courses. Most importantly, you will be more informed of how the current monetary practices and policies affect you and your fellow citizens.</p>
<p>Please keep in mind as you watch this that &#8220;feeding the beast&#8221;, as they call it, is a <a href="http://www.mcdonaldland.info/2008/07/21/economic-history/" target="_blank">ceteris paribus</a> situation.  They chose to overlook inflation with this scenario. As the amount of outstanding interest rises the numbers are offset by inflation. For example, $10 in interest today is the same actual dollar amount tomorrow, even if inflation has devalued your money such that the <a href="http://en.wikipedia.org/wiki/Real_versus_nominal_value_(economics)" target="_blank">real value</a> of $10 is now actually $20. That is, what cost $10 yesterday now costs $20 for the exact same thing. Without diving down this rabbit hole too deep, just keep in mind that the doom and gloom in the video is not to be taken at face value.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcdonaldland.info/2008/11/25/the-credit-crunch/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tipping the Scales</title>
		<link>http://www.mcdonaldland.info/2008/11/10/tipping-the-scales/</link>
		<comments>http://www.mcdonaldland.info/2008/11/10/tipping-the-scales/#comments</comments>
		<pubDate>Mon, 10 Nov 2008 18:38:56 +0000</pubDate>
		<dc:creator>Jason McDonald</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://www.mcdonaldland.info/2008/11/10/tipping-the-scales/</guid>
		<description><![CDATA[Every organization needs procedures. What needs to happen when I file a bug? How do I notify clients that their feature is in production? Who do I bill this work to? All of these are simplified by procedure. Instead of having to figure out the issue and devise a solution every time the problem arises, [...]]]></description>
			<content:encoded><![CDATA[<p>Every organization needs procedures. What needs to happen when I file a bug? How do I notify clients that their feature is in production? Who do I bill this work to? All of these are simplified by procedure. Instead of having to figure out the issue and devise a solution every time the problem arises, procedures allow us to base our actions on past thought and designs.</p>
<p>Procedures can be good but they can also create more problems than they are worth. When procedures reach a point to where you are spending more time trying to find the right procedure than you would if you just figured out the problem from scratch, they are a burden.</p>
<p>A happy medium should be targeted. This middle ground should ultimately save time &#8211; otherwise it is a wasteful venture. If you have to spend long amounts of time searching for or through documents just to figure out what is supposed to happen then the system is a failure.</p>
<p>Next time you are going to add a procedure you should stop to ask yourself the following:</p>
<p><strong>1. Does this solve a tough problem?</strong><br />
Does this procedure save people an inordinate amount of time or money? Does this procedure address an issue that is difficult to figure out on a case by case basis? If either of these are true then the procedure is likely to be a good addition.</p>
<p><strong>2. Is this going to simplify things or add undue process?</strong><br />
Will people have to take a lot of extra steps just for the sake of procedure? If any part of the procedure is there just for the sake of it and doesn&#8217;t produce a tangible output then the overall process is diminished.</p>
<p><strong>3. How easy will this be to remember?</strong><br />
If a procedure is hard to remember then people will need to look it up each time. This, by itself, doesn&#8217;t necessarily negate usefulness. However, if people have to look it up and it is tough to find then the process becomes much less useful and less likely to succeed.</p>
<p><strong>4. How often is this likely to happen and what is the importance when it happens?</strong><br />
If the item in question rarely happens and/or doesn&#8217;t have a lot of value associated with it then there is likely not a need for detailed procedures. For example, declaring war doesn&#8217;t happen that often but has a high cost so a procedure is needed. Conversely, working showstoppers happens far more frequently but has a relatively low cost.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcdonaldland.info/2008/11/10/tipping-the-scales/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Over the code</title>
		<link>http://www.mcdonaldland.info/2008/10/17/over-the-code/</link>
		<comments>http://www.mcdonaldland.info/2008/10/17/over-the-code/#comments</comments>
		<pubDate>Fri, 17 Oct 2008 14:42:25 +0000</pubDate>
		<dc:creator>Jason McDonald</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Misc]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://www.mcdonaldland.info/2008/10/17/over-the-code/</guid>
		<description><![CDATA[I realized a while back that I have grown tired of writing code. I still enjoy the design aspects of software and enjoy being involved in the software creation process. I just no longer care for the implementation aspect of the business. I haven&#8217;t written a line of code in probably three months. I haven&#8217;t [...]]]></description>
			<content:encoded><![CDATA[<p>I realized a while back that I have grown tired of writing code. I still enjoy the design aspects of software and enjoy being involved in the software creation process. I just no longer care for the implementation aspect of the business. I haven&#8217;t written a line of code in probably three months.  I haven&#8217;t written a significant portion of code in at least six months. And I&#8217;m happy.</p>
<p>My parents were both programmers so I got a very early introduction to software. I began by writing little programs, address books and the like, throughout childhood and high school. I then jumped into a data entry job, which I quickly figured out how to write a script to help automate. From there I never had a job where I didn&#8217;t write code. Until now.</p>
<p>My parents both ended up in management &#8211; my Dad has relatively recently returned to writing code. They both told me the same thing at one point or another: they just got tired of writing code and wanted something new. I believed them and figured that I would follow suit sooner or later.</p>
<p>About five years ago I was still pretty into writing code still but looking to the future I saw myself growing wary in the next five to seven years. My timing ended up being just right. About five years ago I started getting into more leadership roles &#8211; leading software teams while still having my hands in the code. Over that span I have slowly become more and more removed from the code until just a few months ago when I decided I was completely done with it. I am now in a role where I don&#8217;t write any code but still have a high level of involvement in the design and development processes.</p>
<p>I may still write about code and software practices here and there however, as is obvious by my post trends, they will become less frequent. I imagine that the main focus of my writings will continue to be business of software and economics, with a little bit of software sprinkled in here and there.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcdonaldland.info/2008/10/17/over-the-code/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Yurtle the Turtle</title>
		<link>http://www.mcdonaldland.info/2008/10/15/yurtle-the-turtle/</link>
		<comments>http://www.mcdonaldland.info/2008/10/15/yurtle-the-turtle/#comments</comments>
		<pubDate>Wed, 15 Oct 2008 16:50:16 +0000</pubDate>
		<dc:creator>Jason McDonald</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.mcdonaldland.info/2008/10/15/yurtle-the-turtle/</guid>
		<description><![CDATA[One of my favorite books growing up, and now one of my daughter&#8217;s favorite books, is Yurtle the Turtle by Dr. Seuss. The story is of an arrogant turtle king who marvels at how wonderful he is and proclaims that he is the ruler of all that he can see. But things grow stale and [...]]]></description>
			<content:encoded><![CDATA[<p>One of my favorite books growing up, and now one of my daughter&#8217;s favorite books, is <a href="http://www.amazon.com/gp/product/0394800877?ie=UTF8&amp;tag=mcdo-20&amp;link_code=wql&amp;camp=212361&amp;creative=380601" target="_blank">Yurtle the Turtle</a> by Dr. Seuss. The story is of an arrogant turtle king who marvels at how wonderful he is and proclaims that he is the ruler of all that he can see. But things grow stale and Yurtle yearns to rule over more. He orders his turtle subjects to stand on one another&#8217;s backs to form a higher throne for him, allowing him to see and rule more. Throughout the story he keeps forcing more and more turtles to add to his throne so that he gets higher and higher. The entire time a single turtle, Mack on the bottom of the stack, keeps complaining that the turtles are all in pain because of Yurtle&#8217;s greed. Yurtle repeatedly silences Mack until Mack decides he&#8217;s had enough and decides to topple the throne, causing Yurtle to fall into the pond below. The story ends with Yurtle being king of the mud, &#8220;because that&#8217;s all he can see&#8221;.</p>
<p>As a child I vividly remembering this story being a life lesson in not allowing people to boss you around and walk all over you. The message I learned was that people should stand up for themselves and not allow their rights to be violated, no matter who is violating them. As an adult I still see this message but I also see the other side of the equation, especially as it relates to leadership.</p>
<p>As a leader you must keep in mind that people don&#8217;t have to follow you for any reason &#8211; even in business environments. As with Yurtle&#8217;s situation, the lowest person on the team can ultimately bring down the entire structure. Just because someone reports to you on the corporate structure doesn&#8217;t mean that they have to follow you. They can undermine your authority, complain to your superiors or HR, or even leave your team or the company. The relationship between leader and follower is a voluntary one. Always. The only benefit that corporate leaders are given is that they have a mandated reporting structure, allowing them more time to sway their potential followers whereas in non corporate situations the potential followers can leave much quicker if not immediately satiated.</p>
<p>As a leader it is natural to strive for personal and professional growth. However, if that growth comes at the sake of your followers it is just a matter of time before you are in for a tumultuous fall and find yourself being king of the mud.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcdonaldland.info/2008/10/15/yurtle-the-turtle/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Gattaca Effect</title>
		<link>http://www.mcdonaldland.info/2008/10/11/the-gattaca-effect/</link>
		<comments>http://www.mcdonaldland.info/2008/10/11/the-gattaca-effect/#comments</comments>
		<pubDate>Sun, 12 Oct 2008 03:16:50 +0000</pubDate>
		<dc:creator>Jason McDonald</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Philosophy]]></category>

		<guid isPermaLink="false">http://www.mcdonaldland.info/2008/10/11/the-gattaca-effect/</guid>
		<description><![CDATA[The movie Gattaca is about a world where genetic manipulation has reached a level to where unborn fetuses can be genetically modified so that they come out with higher levels of intelligence, physical abilities, and life expectations. In the movie there are two brothers, one who was born after the procedures became available or mainstream [...]]]></description>
			<content:encoded><![CDATA[<p>The movie <a href="http://www.imdb.com/title/tt0119177/" target="_blank">Gattaca</a> is about a world where genetic manipulation has reached a level to where unborn fetuses can be genetically modified so that they come out with higher levels of intelligence, physical abilities, and life expectations. In the movie there are two brothers, one who was born after the procedures became available or mainstream and one who was born before.</p>
<p>There is a pivotal scene, once the boys are adults, that is the basis of my term &#8220;The Gattaca Effect&#8221;. The two men start swimming out to sea, playing a game of chicken. The first one to stop loses. Despite the fact that the genetically altered child always won as children he finds himself unable to keep up with his brother. Stopping, he asks why it is that he, the genetically superior specimen, can&#8217;t keep up. The answer from his genetically natural brother is simple: &#8220;I don&#8217;t save enough energy for the trip back.&#8221;</p>
<p>This has always struck a chord with me. I call it &#8220;The Gattaca Effect&#8221; simply because I have yet to see another term that accurately depicts the trait. &#8220;Heart&#8221; comes close but doesn&#8217;t entirely embody the calculated do or die mentality. Whatever you call it, there is a right time to use it and a wrong time.</p>
<p>Sometimes you have to put it all on the line and risk the loss of everything in order to find success. Other times there are plenty of options available that do not require such a risk. Determining the right time to do each is really an art. Understanding that losing everything is an option <em>and</em> being able to entertain that idea is something that is rare.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcdonaldland.info/2008/10/11/the-gattaca-effect/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
