﻿<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title>Don Bloom's Web Log</title>
	<updated>2012-02-14T13:10:01Z</updated>
	<id>http://weblog.dbaconsult.com/atom.aspx</id>
	<link href="http://weblog.dbaconsult.com/atom.aspx" rel="self" type="application/rss+xml" />
	<link href="http://weblog.dbaconsult.com" rel="alternate" type="application/rss+xml" />
	<generator uri="http://app.onlinequickblog.com/" version="2.6.6">Quick Blogcast</generator>
	<entry>
		<title>The Force of Technology in Business – The Dark Side</title>
		<link rel="alternate" href="http://weblog.dbaconsult.com/2007/07/17/the-force-of-technology-in-business--the-dark-side.aspx?ref=rss" />
		<id>tag:weblog.dbaconsult.com,2007-07-17:170bf584-8c4b-48d5-9c74-d415163400aa</id>
		<author>
			<name>Don Bloom</name>
		</author>
		<category term="Risk Management" />
		<category term="Productivity" />
		<updated>2007-07-17T17:11:00Z</updated>
		<published>2007-07-17T17:11:00Z</published>
		<content type="html">&lt;FONT size=2&gt;
&lt;P&gt;At least part of running a business requires attention to detail. Thankfully we live in a world where there’s no shortage of technological tools available to keep track of everything. With the right set of computers, networks and related tools, including portable computing and communications gadgets, we can keep our business – and our life – under control. &lt;B&gt;But wait!!&lt;/B&gt; If you think everything is under control … Well, as the old saw goes, "… you’ve probably overlooked something!"&lt;/P&gt;
&lt;P&gt;There are some issues to consider before you can even hope to claim a measure of control over the technology in your business (let alone your life!) It’s not just getting everything to work and play well together. One important consideration is the dependency relationship you develop with each of the tools you use and how you would function if one or more of them failed in some way. The risk of having a single failure is compounded when you consider that it’s not just you that develops the dependency. The very act of getting things to work together to enhance productivity creates a chain of dependencies within the collection of tools you use. That doesn’t even account for all of the people that depend on you and your tools and the people &lt;I&gt;you&lt;/I&gt; depend on!&lt;/P&gt;
&lt;P&gt;As an example, if you’ve ever suffered a loss of data because of a computer failure, you have good sense of where I’m going with this. Was all the lost data also stored on a backup? Even if it was, how long did it take to recover the failed computer? … and what did it cost? The most common answers I hear are &lt;B&gt;"No," "a lot longer than I expected" &lt;/B&gt;and&lt;B&gt; "way too much!"&lt;/B&gt; But everybody gripes about their computers. Let’s try another example.&lt;/P&gt;
&lt;P&gt;Consider your cell phone and what would happen if suddenly it was unavailable to you. What’s the risk of that you ask? As it turns out, it’s quite likely – in the form of a dead battery among numerous other possibilities. But because this is a common and relatively easy to predict event, we all have solutions and practices to mitigate the risk of suffering any real harm. We consider ahead of time what we’ll do if our cell phone is unavailable. We might carefully check the power level every morning; we probably make sure we have our car charger or an extra battery; we’ve learned to make use of voice mail so we can use another phone, just in case …. If we have a plan for coping and managing the risks, we can get along fine without a cell phone for a while. If we haven’t planned, things might get a little more hectic, but we’ll probably do alright since this is after all, a comparatively simple problem.&lt;/P&gt;
&lt;P&gt;So let’s complicate things, shall we? What if the lost tool is your Palm Pilot or other handheld computing device, aka PDA or "personal digital assistant"? What if it isn’t just a dead battery? What if it gets lost or even damaged beyond repair? Now, imagine you’re returning from a successful marketing trip or conference; where you’d entered dozens of new contacts to update your computer-based sales management system; and you had some great ideas that you jotted down in your PDA.&lt;/P&gt;
&lt;P&gt;How much potential value &lt;I&gt;did&lt;/I&gt; you actually create that’s now gone? How much business &lt;I&gt;could&lt;/I&gt; you have gotten from those new contacts? Which of your ideas &lt;I&gt;could&lt;/I&gt; have led to great products or services for customers, clients or prospects? We’re &lt;U&gt;not&lt;/U&gt; talking about getting rid of technology tools! After all, you can just as easily lose a paper notepad. The right question should be, "W&lt;I&gt;hat would it cost to put a backup and recovery strategy in place?&lt;/I&gt; When your productivity and your business is dependent on the tools you use, you need to invest enough in them to limit the risk of failure or at the very least reduce the potential business impact of a failure.&lt;/P&gt;&lt;/FONT&gt;</content>
		<summary>Much has been written about the use of technology as a force for significant productivity improvement in businesses large and small. But once you’re dependent on it, what do you do when it’s not available? 
</summary>
	</entry>
	<entry>
		<title>Software Updates and the Small Business</title>
		<link rel="alternate" href="http://weblog.dbaconsult.com/2006/10/23/software-updates-and-the-small-business.aspx?ref=rss" />
		<id>tag:weblog.dbaconsult.com,2006-10-23:7bc30c80-2185-4617-b332-703647ce1d37</id>
		<author>
			<name>Don Bloom</name>
		</author>
		<category term="Risk Management" />
		<category term="Productivity" />
		<updated>2006-10-23T19:18:00Z</updated>
		<published>2006-10-23T19:18:00Z</published>
		<content type="html">&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"&gt;To minimize the risk of software updates, larger companies actually set up test environments to apply them and review the impact on daily operations. The smaller the business, the less practical this approach is since it requires significant expenditure for IT and Human resources. So how can a small company reduce the risk of applying the software patch that comes with its own problems, making things worse, rather than better?&lt;?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"&gt;I don’t know of any software company – Microsoft and McAfee included – that has worked out a fool-proof mechanism for determining beforehand every side-effect a specific update could have on any given computer.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;U&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"&gt;Their&lt;/SPAN&gt;&lt;/U&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"&gt; problem leaves the typical small business and their computer users without a solution for dealing with difficulties encountered because of updates that are &lt;I&gt;supposed&lt;/I&gt; to make the software they sold you &lt;U&gt;better&lt;/U&gt; in some way – more capable, more efficient, faster or safer.&amp;nbsp;If you're&amp;nbsp;someone who has suffered through difficulties caused by just such an incident, it doesn’t help you to know that they’re not that common. It just seems like they are because you don’t hear about the millions of successful updates, only the hundreds (OK,&amp;nbsp;sometimes more like thousands) that don’t work!&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"&gt;Working with small companies, I’m inclined to recommend and implement procedures where updates for all software are only downloaded, but not installed. On a regular schedule, sometimes as often as weekly, someone either sends in the list of pending updates and they’re checked against known problems, or a technician actually applies the appropriate updates. This is typically done along with other regularly scheduled maintenance&amp;nbsp;like system performance tuning (e.g. disk space management) and security reviews (e.g. virus and spyware checking.) The cost for that regular maintenance keeps things running smoothly and is viewed more or less like vehicle maintenance – think “100 hours of computer usage or 30 days, whichever comes first.”&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"&gt;Smaller organizations or individuals who don’t feel they have the funds to keep up with a maintenance program, need a different approach, one that within the industry is quaintly referred to as “break – fix” work. Essentially, you wait for something to break then spend money to fix it. This is not per se a bad approach. It’s just a trade-off of the risks associated with possibly spending too much on regular monthly maintenance to prevent some problems, versus spending very little or nothing on maintenance and suddenly having a serious problem with attendant high cost to fix. But, as is often said, “That’s a management decision!” &lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"&gt;Maybe I should also say &lt;U&gt;explicitly&lt;/U&gt; that it is &lt;U&gt;not&lt;/U&gt; a technical decision. There are certainly technical risks, but like all business risk, management has to make the decision as to which course of action to follow. Bad things &lt;U&gt;can&lt;/U&gt; happen. Computer hardware &lt;U&gt;will&lt;/U&gt; fail. Computer software &lt;U&gt;will&lt;/U&gt; fail. No simple answer can suffice to tell a business owner which risk is worth taking and which should be avoided. Given all the facts about a business, it’s not difficult to come up with reasonable estimates of the potential cost trade-offs among statistically probable computer failures: the costs of waiting for a failure and then fixing it; the costs of a regular maintenance program; and the costs of fixing the problems that will occur anyway given the level of maintenance you’ve decided on, including “none.”&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;There may not be a way of preventing all of the potential problems, but there are certainly ways of planning for them, managing your response to them and recovering from them without your business being disrupted any more than absolutely necessary. (… and without spending so much to do it that your business &lt;U&gt;is&lt;/U&gt; disrupted … more than necessary!)&lt;/SPAN&gt;</content>
		<summary>To minimize the risk of software updates, larger companies actually set up test environments to apply them and review the impact on daily operations. The smaller the business, the less practical this approach is since it requires significant expenditure for IT and Human resources. So how can a small company reduce the risk of applying the software patch that comes with its own problems, making things worse, rather than better?</summary>
	</entry>
	<entry>
		<title>Evaluating Risk: Lottery Tickets and Business Decisions</title>
		<link rel="alternate" href="http://weblog.dbaconsult.com/2006/09/21/evaluating-risk-lottery-tickets-and-business-decisions.aspx?ref=rss" />
		<id>tag:weblog.dbaconsult.com,2006-09-21:af2e894d-cac8-4610-9d84-7e88999342f8</id>
		<author>
			<name>Don Bloom</name>
		</author>
		<category term="Risk Management" />
		<updated>2006-09-21T17:29:00Z</updated>
		<published>2006-09-21T17:29:00Z</published>
		<content type="html">&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"&gt;&lt;SPAN style="FONT-SIZE: 10pt"&gt;&lt;FONT face="Times New Roman"&gt;What is it about “risk” that&amp;nbsp;makes it so hard for&amp;nbsp;people to evaluate?&lt;BR&gt;&lt;?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"&gt;&lt;SPAN style="FONT-SIZE: 10pt"&gt;&lt;FONT face="Times New Roman"&gt;&lt;BR&gt;I've thought about this for a long time, but it came to head recently while listening to a conversation about, of all things, lottery tickets. Here's the simple scenario – People pay for a lottery ticket in the hopes of winning prizes, even though the probability of winning is extremely low. &lt;o:p&gt;&lt;/o:p&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"&gt;&lt;SPAN style="FONT-SIZE: 10pt"&gt;&lt;FONT face="Times New Roman"&gt;&lt;BR&gt;Let's deal with this question by introducing a&amp;nbsp;concept many people may not be familiar with -&amp;nbsp;"Expected Value." &lt;/FONT&gt;&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt"&gt;&lt;FONT face="Times New Roman"&gt;If something costs a dollar, a rational consumer should expect at least a dollar of value from it. Often, the object purchased is one where&amp;nbsp;the rational consumer applies some personal judgment in establishing the value. For example, one person might feel that a dollar for a small chocolate bar at the local quick-mart is too costly and refrain from purchasing it; whereas, another person might be in the throes of an irresistible urge for a chocolate fix and happily pays the price. The same thing applies to just about any purchase of this kind, from a loaf of bread to an SUV. (This is not an appropriate time to discuss the difference between a necessity and a luxury. In principal, this applies to anyone with any money to spend, even if deciding between food and prescription drugs.)&lt;BR&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"&gt;&lt;SPAN style="FONT-SIZE: 10pt"&gt;&lt;FONT face="Times New Roman"&gt;&lt;BR&gt;Sometimes though, the value may be intrinsic, that is integral to the object such as a readily exchangeable commodity like gold or silver (though that would usually cost more than a dollar.) Another type of purchase that may be considered to have an intrinsic value is the “significant” business purchase or investment, where various aspects of the purchase and use of the object can be analyzed and quantified, then presented in a way that helps the rational consumer (business owner, in this case) make a decision about the purchase.&lt;o:p&gt;&lt;/o:p&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"&gt;&lt;SPAN style="FONT-SIZE: 10pt"&gt;&lt;FONT face="Times New Roman"&gt;… which brings us back to the lottery ticket. &lt;BR&gt;&lt;BR&gt;Lotteries usually have clearly stated conditions and procedures that make the probabilities of winning equally clear. As an example, the multi-state Mega-Millions game in the &lt;?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" /&gt;&lt;st1:country-region w:st="on"&gt;&lt;st1:place w:st="on"&gt;United States&lt;/st1:place&gt;&lt;/st1:country-region&gt; offers a grand prize with the odds of winning fixed at about 175 million to one. By way of contrast, given that on average 1,000 people in the &lt;st1:country-region w:st="on"&gt;&lt;st1:place w:st="on"&gt;United States&lt;/st1:place&gt;&lt;/st1:country-region&gt; are struck by lighting each year, then the odds of an individual getting hit by lightning on a given day is approximately 109 million to one. So, on the day they do the lottery drawing, you’re more likely to get hit by lightning than to win the grand prize.&lt;o:p&gt;&lt;/o:p&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"&gt;&lt;SPAN style="FONT-SIZE: 10pt"&gt;&lt;FONT face="Times New Roman"&gt;&lt;BR&gt;The neat thing about the lottery though is the fact that you can actually work out the actual – or I should say the “expected” value of a one dollar selection of numbers (with of course some margin for error.) Let’s keep it simple for the moment and think about flipping a coin, where the odds are two to one for either heads or tails. Without going into all the theory behind it, if you were to make bets of one dollar on each flip, you would want to be paid two dollars for every win so that over time you’d at least come out even. You get paid two dollars, but there are two possible outcomes or odds of two to one. Divide the prize ($2) by the odds (the 2 outcomes) and you get one dollar – the “expected value” of any given flip of the coin.&lt;SPAN style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;BR&gt;&lt;BR&gt;&lt;/SPAN&gt;The same logic holds for the lottery. If the odds of winning the Mega-Millions grand prize are 175 million to one, you would want the grand prize to be at least 175 million dollars! (Beyond this simple analysis, it gets really complicated. For example, would you want to add in the “expected values” of all the other smaller prizes? Or, what if you decided to consider that as the prize gets larger more people will play? How many people have to play before the probability of more than one person choosing the winning numbers becomes significant and you would have to share the prize?)&lt;o:p&gt;&lt;/o:p&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"&gt;&lt;SPAN style="FONT-SIZE: 10pt"&gt;&lt;FONT face="Times New Roman"&gt;&lt;BR&gt;&lt;STRONG&gt;The Issue of Rational Decision Making&lt;o:p&gt;&lt;/o:p&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"&gt;&lt;SPAN style="FONT-SIZE: 10pt"&gt;&lt;FONT face="Times New Roman"&gt;&lt;BR&gt;If it’s only rational to buy a lottery ticket if the expected value equals or exceeds the cost, why is it that people buy lottery tickets when prizes are much too small to justify on an expected value basis? More to the point of this discussion: Why wouldn’t a business owner make all purchase decisions based on an “expected value” approach? One reason, which probably applies more to a lottery ticket than a business decision is the emotional component of the decision. Dreams of becoming an overnight multi-millionaire can have a way of affecting your decision making process. Alternatively, it’s probably more likely that the cost of the investment has an impact on the decision. At a dollar a chance, the bargain seems so cheap compared to the possible payoff (not the expected value!) that people will play the game. &lt;BR&gt;&lt;BR&gt;A parallel business decision might be the relatively minimal costs of say, office supplies. Getting involved in every decision to buy a box of paper at the best price would cost more than the possible savings. The decision process allows for some leeway in minimizing every cost because of the possibility you’d incur additional unexpected costs somewhere else in the business, like the loss of productive time of highly paid resources (supervisors, managers, the owner, …)&lt;BR&gt;&lt;o:p&gt;&lt;BR&gt;Then the questions become: How do you balance the need to make important decisions vs. the unknown costs of getting too deeply involved in every decision? The answer lies in&amp;nbsp;the&amp;nbsp;science/art of Risk Management, another subject I've thought about for a long time, though&amp;nbsp;that will have to wait for another entry at another time.&lt;/o:p&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;</content>
		<summary>What is it about “risk” that makes it so hard for people to evaluate?
I've thought about this for a long time, but it came to head recently while listening to a conversation about, of all things, lottery tickets. Here's the simple scenario – People pay for a lottery ticket in the hopes of winning prizes, even though the probability of winning is extremely low. </summary>
	</entry>
	<entry>
		<title>A note about measuring IT investment performance</title>
		<link rel="alternate" href="http://weblog.dbaconsult.com/2006/07/10/a-note-about-measuring-it-investment-performance.aspx?ref=rss" />
		<id>tag:weblog.dbaconsult.com,2006-07-10:8e244903-f62d-4335-8b82-17af2f8204f2</id>
		<author>
			<name>Don Bloom</name>
		</author>
		<category term="Productivity" />
		<updated>2006-07-10T19:55:00Z</updated>
		<published>2006-07-10T19:55:00Z</published>
		<content type="html">&lt;P&gt;&lt;FONT face="Times New Roman" size=3&gt;&lt;FONT size=2&gt;(Originally entered 5/25/2006)&lt;BR&gt;&lt;/FONT&gt;I don't think very many business owners would disagree that when you hire an employee you expect them to do or produce something of value. In effect, as a business owner you are &lt;U&gt;investing&lt;/U&gt; in the new employee and want a return on your investment. You evaluate employees on a regular basis and so &lt;U&gt;are&lt;/U&gt; in fact evaluating the return on your investment.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Times New Roman" size=3&gt;But most businesses do &lt;STRONG&gt;NOT&lt;/STRONG&gt; think that way when they buy technology assets - computers, networking and communications equipment, telephones, software, etc.&amp;nbsp;The asset&amp;nbsp;is purchased, and typically written off, if not on the books then at least in the minds of owners and management. Very rarely is a formal review made of the return on the investment of technology assets! Worse, since it is essentially people, the aforementioned &lt;U&gt;employees&lt;/U&gt;, that use the computers and other technology, &lt;EM&gt;their evaluation has buried within it an implicit evaluation of the technology&lt;/EM&gt; - the tools that the employee is using to do the job you hired them to do.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Times New Roman" size=3&gt;Consider the following scenarios and ask yourself if any of them might be occurring in your organization.&lt;/FONT&gt;&lt;/P&gt;
&lt;OL type=1&gt;
&lt;LI class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list .5in"&gt;&lt;FONT face="Times New Roman" size=3&gt;The employee is performing well and the technology is performing well. You rate the employee highly and give them a raise, possibly promote them ... performance has been improved even from what it would have been ... Promotion may lead to a position where the employee will no longer have access to the technology tools they were using. Should some of the money used to give the employee a raise be used to improve the technology or extend its use to more employees?&lt;/FONT&gt; 
&lt;LI class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list .5in"&gt;&lt;FONT face="Times New Roman" size=3&gt;The employee is performing well, but the technology is a problem. The result could be:&lt;/FONT&gt; 
&lt;OL type=a&gt;
&lt;LI class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l0 level2 lfo1; tab-stops: list 1.0in"&gt;&lt;FONT face="Times New Roman" size=3&gt;The employee's performance still looks good to you and you rate them highly, not knowing that they could be doing a better job if not for the computer or communication problems.&lt;/FONT&gt; 
&lt;LI class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l0 level2 lfo1; tab-stops: list 1.0in"&gt;&lt;FONT face="Times New Roman" size=3&gt;The employee's performance doesn't look so good. Worse, they're probably getting frustrated by the technology or other problems. You have a good employee, but you don't know it ... and you may not care when they decide to leave your company.&lt;/FONT&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;LI class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list .5in"&gt;&lt;FONT face="Times New Roman" size=3&gt;The employee is only average and the technology is great. You give the employee a high rating and give them a big raise, not knowing that you should have taken some of those investment dollars (the raise!) and put it into more technology to help more employees.&lt;/FONT&gt; 
&lt;LI class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list .5in"&gt;&lt;FONT face="Times New Roman" size=3&gt;The employee is just average and the technology causes problems, too. Things are probably a mess and you may fire the employee. You go through an expensive hiring process and end up with at best a good employee that gets frustrated with the bad technology ... and then leaves. (See #2a)&lt;/FONT&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;&lt;FONT face="Times New Roman" size=3&gt;The only solution is doing an evaluation of the technology directly. Obvious, but not so easy!&lt;/FONT&gt;&lt;/P&gt;</content>
		<summary>I don't think very many business owners would disagree that when you hire an employee you expect them to do or produce something of value. In effect, as a business owner you are investing in the new employee and want a return ...</summary>
	</entry>
	<entry>
		<title>Amazing Communications</title>
		<link rel="alternate" href="http://weblog.dbaconsult.com/2006/07/10/amazing-communications.aspx?ref=rss" />
		<id>tag:weblog.dbaconsult.com,2006-07-10:a6eb1f78-6967-4460-9b79-140dc10298de</id>
		<author>
			<name>Don Bloom</name>
		</author>
		<category term="Telecommunications" />
		<updated>2006-07-10T19:48:00Z</updated>
		<published>2006-07-10T19:48:00Z</published>
		<content type="html">&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;FONT face="Times New Roman" size=3&gt;&lt;FONT size=2&gt;(Originally entered 5/25/2006)&lt;BR&gt;&lt;/FONT&gt;A&amp;nbsp;few of months ago was the 130th anniversary of Alexander Graham Bell's first successful experiment with the telephone. On&amp;nbsp;that fateful day in&amp;nbsp;1876 &lt;?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" /&gt;&lt;st1:City w:st="on"&gt;&lt;st1:place w:st="on"&gt;Bell&lt;/st1:place&gt;&lt;/st1:City&gt; spoke into the mouthpiece of his as yet unproven invention and called to his assistant, Thomas A. Watson using the now famous words, "Mr. Watson. Come here. I want to see you." Watson heard and understood him. Though subsequent experiments weren't as clearly understood, that was the beginning of an incredible change in the way we communicate. But now, instead of over a metal wire strung from one room to another, our wires circle the globe. The "wires" much of our communication now travels through are in fact strands of glass thinner than a human hair. And a lot of our telephone conversations now take place traveling through no wires at all!&lt;/FONT&gt;&lt;/P&gt;</content>
		<summary>A few of months ago was the 130th anniversary of Alexander Graham Bell's first successful experiment with the telephone. On that fateful day in 1876 ...</summary>
	</entry>
</feed>
