<?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>Perspectives &#38; Strategy &#187; Time Management</title>
	<atom:link href="http://cio-perspectives.com/category/time-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://cio-perspectives.com</link>
	<description>By Peter B. Giblett - The eZine for Corporate Leadership. Investigating strategic issues-corporate change-Social Media</description>
	<lastBuildDate>Thu, 22 Dec 2011 01:32:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Management, Leadership and the Art of Delegation</title>
		<link>http://cio-perspectives.com/2011/04/management-leadership-and-the-art-of-delegation/</link>
		<comments>http://cio-perspectives.com/2011/04/management-leadership-and-the-art-of-delegation/#comments</comments>
		<pubDate>Wed, 13 Apr 2011 04:27:40 +0000</pubDate>
		<dc:creator>Peter B. Giblett</dc:creator>
				<category><![CDATA[Leadership & Business Effectiveness]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Time Management]]></category>
		<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Strategic Problem Solving]]></category>

		<guid isPermaLink="false">http://cio-perspectives.com/?p=1398</guid>
		<description><![CDATA[Much of this article was originally published on bizcovering.com and is part of a series of articles about leadership and management, with an intention of advising the new manager &#8211; the problem solver that has recently been promoted. This is advice based on personal experience over many years in a leadership position. Learning to delegate [...]]]></description>
			<content:encoded><![CDATA[<p>Much of this article was originally published on <a href="http://bizcovering.com/management/leadership-and-the-fine-art-of-delegation/">bizcovering.com</a> and is part of a series of articles about leadership and management, with an intention of advising the new manager &#8211; the problem solver that has recently been promoted. This is advice based on personal experience over many years in a leadership position.</p>
<p>Learning to delegate is a skill that every new manager must learn, and usually learn it fast. Yet all share one thing in common, they want to jump in and get the task completed, yet delegating correctly is actually better for the business unit, it develops the skills of the whole team and that is important for the success of the manager.</p>
<p>The art of delegation is largely about breaking each job into achievable tasks and entrusting that a group of competent individuals will be able to complete that assignment. Ultimately this depends on having a competent team involved in delivering the project at hand. In this context a project is defined as any block of work requiring more than a simple task to complete it. Projects can last anywhere between an hour and several months or years; typically they last several days and involve any business discipline, even those not typically associated with project work.</p>
<p>Delegation arguably requires a mutual level of understanding of all the things that need to be completed and when they should be completed. It can be postulated that delegation skills are rarely well understood, one of the problems being that an effective problem solver can be that they are ineffective at assigning responsibilities to members of a team that they now run. In part this is because they consider themselves as the only person capable of delivering results. Yet we all know that effective delegation helps reducing the process time and elicits collective brilliance from the team. This it can be seen the heart of the team functioning as a well oiled machine.</p>
<p>Letting go of the details can be a difficult thing for any person in a management position to do. It is all too easy to think that you are the only person that understands all of the details of the task at hand or perhaps it is the belief that no one else can do it as well as us. This, however, is the wrong approach. Asking assistance from others is not demonstrating a weakness, but instead it is a sign of confidence, strong management, and effective leadership. Yet many managers remember how effective they were at completing the task at hand and feel the need to jump right in, yet they should not – the task is one for their team to complete, not for themselves alone. In fact letting go of the details actually empowers the manager to take things to the next level; it is about leadership and gaining an understanding a bigger picture, which always empowers the manager.</p>
<p>As a manager it is important to establish a positive work environment where employees are not paralyzed by fear of failure, the effective manager must act a guide in moving projects forwards.</p>
<p>Further reading:</p>
<p>* <a href="http://bizcovering.com/management/leadership-and-the-fine-art-of-delegation/">Leadership and The Fine Art of Delegation</a><br />
* <a href="http://bizcovering.com/management/delegation-the-problem-solver-becoming-the-manager/">Delegation: The Problem Solver Becoming The Manager</a><br />
* <a href="http://bizcovering.com/management/the-effective-manager-empowering-your-staff-to-harness-their-strengths/">The Effective Manager: Empowering Your Staff to Harness Their Strengths</a><br />
* <a href="http://bizcovering.com/management/deligating-is-especially-difficult-when-things-go-wrong/">Delegating is Especially Difficult When Things Go Wrong</a><br />
* <a href="http://bizcovering.com/management/controlling-the-success-of-the-delegated-task/">Controlling The Success of The Delegated Task</a></p>
<div class="plus-one-wrap"><g:plusone count="false" href="http://cio-perspectives.com/2011/04/management-leadership-and-the-art-of-delegation/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://cio-perspectives.com/2011/04/management-leadership-and-the-art-of-delegation/feed/</wfw:commentRss>
		<slash:comments>78</slash:comments>
		</item>
		<item>
		<title>Virtual Teams, Project Slippage &amp; The &#8216;Fear Factor&#8217;</title>
		<link>http://cio-perspectives.com/2009/12/virtual-teams-project-slippage-the-fear-factor/</link>
		<comments>http://cio-perspectives.com/2009/12/virtual-teams-project-slippage-the-fear-factor/#comments</comments>
		<pubDate>Wed, 30 Dec 2009 17:19:56 +0000</pubDate>
		<dc:creator>Peter B. Giblett</dc:creator>
				<category><![CDATA[Agile Deployment]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Project Success]]></category>
		<category><![CDATA[Tele-working]]></category>
		<category><![CDATA[Time Management]]></category>
		<category><![CDATA[Collaboration]]></category>
		<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Successful Projects]]></category>
		<category><![CDATA[Telecommuting]]></category>

		<guid isPermaLink="false">http://cio-perspectives.com/?p=935</guid>
		<description><![CDATA[One of the biggest challenges in managing remote, or viurtual projects, has always been one of communication and collaboration. From the management perspective it is not possible to simply walk down the corridor and see the fear in people&#8217;s eyes: not fear of physical harm, but the fear that you are going to ask them [...]]]></description>
			<content:encoded><![CDATA[<p>One of the biggest challenges in managing remote, or viurtual projects, has always been one of communication and collaboration. From the management perspective it is not possible to simply walk down the corridor and see the fear in people&#8217;s eyes: not fear of physical harm, but the fear that you are going to ask them the dreaded question about their project task that is running behind schedule.</p>
<p>This short walk down the corridor often speaks volumes more than the weekly project meeting. To me this signals a time when a one-to-one meeting is required, in order to get to the bottom of the problem.</p>
<p>With remote team members this type of reaction seeking or non-verbal communication is not evident. It is possible to hear fear when a person speaks, yet in a teleconference it is possible to hide &#8211; simply by remaining silent. When you are in a teleconference with your remote team members do you ever ask for personal feedback from every person present? Trouble is that it is all too easy to forget the silent ones even in a face-to-face meeting.</p>
<p>Generally speaking in any meeting there are two reasons to be silent. Firstly <a href="http://www.experienceproject.com/question-answer/How-Does-Psychosocial-Theory-Help-As-A-Way-To-Combat-Shyness/670" target="_blank">shyness</a>, and secondly because that individual has something to hide.</p>
<p>Shyness is a symptom of <a href="http://ezinearticles.com/?Are-You-Shy?-How-To-Overcome-Shyness-At-Work&amp;id=116620" target="_blank">managing comfort zones</a>. We can all be shy when confronted with something new, and perhaps a little <a href="http://searchwarp.com/swa5667.htm" target="_blank">intimidated</a> particularly when we understand very little about it. It can normally be <a href="http://www.shakeyourshyness.com/Tips.HTM" target="_blank">managed</a> by coaxing that person out of their existing comfort zone and expanding that comfort zone to include the new working environment.</p>
<p>Having something to hide is a different matter. These team members are the onces who are most likely to bring bad results on a project, irrespective of the circumstances. <a href="http://cio-perspectives.com/2008/11/what-are-to-steps-to-managing-succesful-projects/" target="_blank">Projects</a> are always limited by time and resources, whenever there are problems it is always vital to share. Managing projects via Agile methods does allow problem areas to be ring-fenced and focused on more thoroughly at a later stage. I am always more concerned about those who hide away because they have a problem than I am the shy person.</p>
<p>Despite sayings like &#8220;<em>a problem shared is a problem halved</em>&#8221; having entered the main-flow of society, people tend to be concerned that when a problem is identified then it is their personal challenge to solve it. They hide the problem in the hope that no-one finds out about the problem. Sadly this is the point when it starts to have a negative impact on everything that you do. Project working is not generally the place for heroics. That person who focuses on the problem and tends to lose sight of their deliverables.  Here we are back at the team member who rushes back the other way when when they see you, their manager, in the corridor. Something is wrong here and needs to be solved.</p>
<p>BUT how do you do this when the person is working remotely? Many project managers believe that having remote workers is too risky. Yet it is the things we do not wish to do that we are often forced to do.  There is a certain amount that can be achieved by regular visits to remote sites, yet at all times you remain a stranger at that remote location &#8211; so there is a psychology to managing remote visits. <a href="http://blogs.techrepublic.com.com/itdojo/?p=124" target="_blank">Remote project workers</a> are a fact of life, as are constrained project budgets. The latter reduces out ability to complete regular remote-site visits, so it is essential to identify remoteness challenges of virtual teams in other ways.</p>
<p>It is vital all virtual team members are a part of developing and following the team plan &#8211; this must be lived and breathed. Knowing each remote worker is important &#8211; you probably need to spend a disproportionately high amount of time developing this relationship. You need to stay in touch, daily is best; set and follow an agenda for all meetings &#8211; ensure it is business focused. Leverage technology where appropriate &#8211; particularly collaboration tools.</p>
<div class="plus-one-wrap"><g:plusone count="false" href="http://cio-perspectives.com/2009/12/virtual-teams-project-slippage-the-fear-factor/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://cio-perspectives.com/2009/12/virtual-teams-project-slippage-the-fear-factor/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Good Decision Making</title>
		<link>http://cio-perspectives.com/2009/05/good-decision-making/</link>
		<comments>http://cio-perspectives.com/2009/05/good-decision-making/#comments</comments>
		<pubDate>Thu, 21 May 2009 23:28:01 +0000</pubDate>
		<dc:creator>Peter B. Giblett</dc:creator>
				<category><![CDATA[Business Intelligence]]></category>
		<category><![CDATA[Leadership & Business Effectiveness]]></category>
		<category><![CDATA[Time Management]]></category>
		<category><![CDATA[Decisions]]></category>
		<category><![CDATA[Leadership]]></category>

		<guid isPermaLink="false">http://cio-perspectives.com/?p=394</guid>
		<description><![CDATA[I think that I have good business instincts and given any situation I will make a good decision. Looking back on my career I am probably batting well above average, but is that good enough? In order to make a good decision it is important to have at hand all of the pertinent facts. In [...]]]></description>
			<content:encoded><![CDATA[<p>I think that I have good business instincts and given any situation I will make a good decision. Looking back on my career I am probably batting well above average, but is that good enough?</p>
<p>In order to make a good decision it is important to have at hand all of the pertinent facts. In a business environment that means having all the information, the statistics and personal knowledge necessary to make a decision. However we often have to make decision based on something less, the pressure of business need that snap decision. Apparently 80% of business leaders have to make major decisions without full information.</p>
<p>Having made a few of these types of decision myself over the years I know it is important to decide and move on. Today we have more information at our fingertips than we have ever had before. I can also attest even where decisions were made based on full Business Intelligence and forecasts mistakes can still be made, yet at the time a decision was necessary in order to move the situation forward. We are after all living in the here and now. Yesterday is over, and tomorrow never comes so we have to decide based on the best information available. Making better information available may be a part of the decision that we make. But still the decision must be made.</p>
<p>So we must take ownership of the decisions made and learn from them. Some may say that therefore we must also take the blame when things go wrong. As a part of learning (and these days most organisations seek to be learning organisations) we must learn when things go wrong and ensure that we do not make the same mistakes again. After all we based the decision on the best information that we had available to us at the time. But of course on the basis of living in the here and now we should also be prepared to re-look at old decisions and see if there are things to be learnt.</p>
<p>I have to think that nothing is permanent, we can always start over, make a new decision. But that is something people can be afraid to do &#8211; me included.</p>
<p>Here is where I hear some people scream &#8220;Oh No! &#8211; that Giblett fellow is going to cost us a fortune as we implement new systems in order to face new world challenges&#8221;. No that is not necessary. Just because we face change does not mean sweeping away our systems and replacing them with new. The change I am talking about here is ensuring that the business processes are capable of working successfully right here, right now. It is a business matter, not a systems one.</p>
<div class="plus-one-wrap"><g:plusone count="false" href="http://cio-perspectives.com/2009/05/good-decision-making/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://cio-perspectives.com/2009/05/good-decision-making/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Telecommuting: Essential Tools of the Trade</title>
		<link>http://cio-perspectives.com/2009/04/telecommuting-essential-tools-of-the-trade/</link>
		<comments>http://cio-perspectives.com/2009/04/telecommuting-essential-tools-of-the-trade/#comments</comments>
		<pubDate>Fri, 03 Apr 2009 14:17:38 +0000</pubDate>
		<dc:creator>Peter B. Giblett</dc:creator>
				<category><![CDATA[Tele-working]]></category>
		<category><![CDATA[Telecommuting]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://cio-perspectives.com/?p=241</guid>
		<description><![CDATA[In order to effectively tele-work the employee must have a good set of tools that will enhance their status in the eyes of their manager and their colleagues. In my earlier article I talked about the fact that Tele-workers face a consistent danger that &#8220;out of sight is out of mind&#8221; which may affect the [...]]]></description>
			<content:encoded><![CDATA[<p>In order to effectively tele-work the employee must have a good set of tools that will enhance their status in the eyes of their manager and their colleagues. In my <a title="Telecommuting, the best model for future working?" href="http://cio-perspectives.com/2008/12/is-telecommuting-the-best-model-for-future-business/" target="_blank">earlier article</a> I talked about the fact that Tele-workers face a consistent danger that &#8220;out of sight is out of mind&#8221; which may affect the manager and co-worker perceptions of the worker and their performance. In many respects the tele-worker has to be twice as visible as the office worker.</p>
<p><img class="alignleft size-full wp-image-242" title="mobile" src="/wp-content/uploads/2009/04/mobile.jpg" alt="mobile" width="115" height="195" />Essential tools include:</p>
<p>= A mobile/cellular phone. Which must be answerable at all times.</p>
<p>= Instant Messaging. This aids in visibility as on-line and available at all times.</p>
<p>= Remote Meeting Software, and a high quality phone so that you are involved in all meetings</p>
<p>= On-line training facility</p>
<p>= Status reports. They may not be needed for your job, but they assist visibility.</p>
<p>= A professional email signature and corporate email account if you are a contractor.</p>
<p>Phone availability is essential having the mobile with you at all times is essential, staff must be available during normal business hours. The tele-worker needs to be more visible than their office counterpart. Many office workers are expected to be available at all times these days, hence the popularity of the dreaded Blackberry.</p>
<p>Tele-workers should be given a corporate email account along with Instant Messaging capabilities. We want to ensure that they are a part of the corporate entity, and directories should include them.  They should accessing applications on the corporate network (through VPNs and firewalls). Depending on the role that they are required to perform granting access to corporate applications should be through virtual systems; what they have access to may need to be more limited than if they were doing the same job at the corporate office.</p>
<p>Instant messaging and remote meeting solutions are a part of the employee&#8217;s visibility in the role that they are performing. Many offices have found that use of IM within the office environment improves the flow of communications within the office in a non-destructive way. I have though seen it used to save one company money as one of the warehouse employees spotted an exceptionally large order for a customer &#8211; tried to call, engaged; turned to IM &#8211; success, there was a typo on the order which was corrected saving the company both money and reputation.</p>
<p>On-line training is very important in the new environment as the tele-worker can miss out on trainign about new procedures. Products like Camtasia are inexpensive and make the setup of an on-line training capability easy. Now the company is able to provide a suite of training materials for all of its employees.</p>
<p>In IT remote meeting software, like GoTo Meeting have been very widely used, they are rapidly becoming a must have tool in training.<span> </span>When two people can share a computer screen, the need ability to “show me” presents itself and knowledge and communication can flow freely. This can also facilitate conference calling even where no computerised element is required for the discussion.</p>
<p>Video conferencing software and webcams are certainly something to consider in making the tele-worker and effective part of the corporate entity.</p>
<p>When it come to providing status reports the majority of people groan then say &#8220;Must I?&#8221;. For the tele-worker, this is a key component of the work, their trumpet. A tele-worker must turn this into an art-form, but always be brief. The manager will always appreciate the 25 words that states concicely what has been acheived. and perhaps another 25 words about the challenges ahead. Where problems exist suggest solutions.</p>
<p>A challenging time ahead? I certainly think so.</p>
<p>I am grateful to <a href="http://it.toolbox.com/people/rpm13/">Ray Mannion</a> for his &#8220;<a href="http://raymannion.com/sap/must-have-tools-for-working-remotely/">Must Have Tools for Working Remotely</a>&#8221; in preparing this item.</p>
<div class="plus-one-wrap"><g:plusone count="false" href="http://cio-perspectives.com/2009/04/telecommuting-essential-tools-of-the-trade/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://cio-perspectives.com/2009/04/telecommuting-essential-tools-of-the-trade/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Handling Competing Priorities</title>
		<link>http://cio-perspectives.com/2009/01/handling-competing-priorities/</link>
		<comments>http://cio-perspectives.com/2009/01/handling-competing-priorities/#comments</comments>
		<pubDate>Fri, 16 Jan 2009 21:11:55 +0000</pubDate>
		<dc:creator>Peter B. Giblett</dc:creator>
				<category><![CDATA[Corporate Strategy]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Time Management]]></category>
		<category><![CDATA[Competing Priorities]]></category>

		<guid isPermaLink="false">http://cio-perspectives.com/?p=36</guid>
		<description><![CDATA[We would all like to say “Hold your horses we are only running 1 project this year” however this simply does not meet business reality. For the IT manager as soon as they have defined the annual list of priorities, there is pressure to add new projects, or to change the scope of existing authorised [...]]]></description>
			<content:encoded><![CDATA[<p><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves /> <w:TrackFormatting /> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF /> <w:LidThemeOther>EN-GB</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:SplitPgBreakAndParaMark /> <w:DontVertAlignCellWithSp /> <w:DontBreakConstrainedForcedTables /> <w:DontVertAlignInTxbx /> <w:Word11KerningPairs /> <w:CachedColBalance /> </w:Compatibility> <m:mathPr> <m:mathFont m:val="Cambria Math" /> <m:brkBin m:val="before" /> <m:brkBinSub m:val="&amp;amp;#45;-" /> <m:smallFrac m:val="off" /> <m:dispDef /> <m:lMargin m:val="0" /> <m:rMargin m:val="0" /> <m:defJc m:val="centerGroup" /> <m:wrapIndent m:val="1440" /> <m:intLim m:val="subSup" /> <m:naryLim m:val="undOvr" /> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267"> <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal" /> <w:LsdException Locked="false" Priority="9" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /> <w:LsdException Locked="false" Priority="39" Name="toc 1" /> <w:LsdException Locked="false" Priority="39" Name="toc 2" /> <w:LsdException Locked="false" Priority="39" Name="toc 3" /> <w:LsdException Locked="false" Priority="39" Name="toc 4" /> <w:LsdException Locked="false" Priority="39" Name="toc 5" /> <w:LsdException Locked="false" Priority="39" Name="toc 6" /> <w:LsdException Locked="false" Priority="39" Name="toc 7" /> <w:LsdException Locked="false" Priority="39" Name="toc 8" /> <w:LsdException Locked="false" Priority="39" Name="toc 9" /> <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /> <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title" /> <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /> <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /> <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong" /> <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /> <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /> <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /> <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /> <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote" /> <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /> <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /> <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /> <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /> <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /> <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title" /> <w:LsdException Locked="false" Priority="37" Name="Bibliography" /> <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /> </w:LatentStyles> </xml><![endif]--><br />
<!--   /* Font Definitions */  @font-face 	{font-family:Wingdings; 	panose-1:5 0 0 0 0 0 0 0 0 0; 	mso-font-charset:2; 	mso-generic-font-family:auto; 	mso-font-pitch:variable; 	mso-font-signature:0 268435456 0 0 -2147483648 0;} @font-face 	{font-family:"Cambria Math"; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:1; 	mso-generic-font-family:roman; 	mso-font-format:other; 	mso-font-pitch:variable; 	mso-font-signature:0 0 0 0 0 0;} @font-face 	{font-family:Calibri; 	panose-1:2 15 5 2 2 2 4 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:swiss; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1073750139 0 0 159 0;} @font-face 	{font-family:Tahoma; 	panose-1:2 11 6 4 3 5 4 4 2 4; 	mso-font-charset:0; 	mso-generic-font-family:swiss; 	mso-font-pitch:variable; 	mso-font-signature:1627400839 -2147483648 8 0 66047 0;} @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:swiss; 	mso-font-pitch:variable; 	mso-font-signature:536871559 0 0 0 415 0;}  /* Style Definitions */  p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-unhide:no; 	mso-style-qformat:yes; 	mso-style-parent:""; 	margin-top:6.0pt; 	margin-right:0cm; 	margin-bottom:0cm; 	margin-left:0cm; 	margin-bottom:.0001pt; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Tahoma","sans-serif"; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi; 	mso-fareast-language:EN-US;} p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph 	{mso-style-priority:34; 	mso-style-unhide:no; 	mso-style-qformat:yes; 	margin-top:6.0pt; 	margin-right:0cm; 	margin-bottom:0cm; 	margin-left:36.0pt; 	margin-bottom:.0001pt; 	mso-add-space:auto; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Tahoma","sans-serif"; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi; 	mso-fareast-language:EN-US;} p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst 	{mso-style-priority:34; 	mso-style-unhide:no; 	mso-style-qformat:yes; 	mso-style-type:export-only; 	margin-top:6.0pt; 	margin-right:0cm; 	margin-bottom:0cm; 	margin-left:36.0pt; 	margin-bottom:.0001pt; 	mso-add-space:auto; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Tahoma","sans-serif"; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi; 	mso-fareast-language:EN-US;} p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle 	{mso-style-priority:34; 	mso-style-unhide:no; 	mso-style-qformat:yes; 	mso-style-type:export-only; 	margin-top:0cm; 	margin-right:0cm; 	margin-bottom:0cm; 	margin-left:36.0pt; 	margin-bottom:.0001pt; 	mso-add-space:auto; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Tahoma","sans-serif"; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi; 	mso-fareast-language:EN-US;} p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast 	{mso-style-priority:34; 	mso-style-unhide:no; 	mso-style-qformat:yes; 	mso-style-type:export-only; 	margin-top:0cm; 	margin-right:0cm; 	margin-bottom:0cm; 	margin-left:36.0pt; 	margin-bottom:.0001pt; 	mso-add-space:auto; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Tahoma","sans-serif"; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi; 	mso-fareast-language:EN-US;} .MsoChpDefault 	{mso-style-type:export-only; 	mso-default-props:yes; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi; 	mso-fareast-language:EN-US;} .MsoPapDefault 	{mso-style-type:export-only; 	margin-bottom:10.0pt; 	line-height:115%;} @page Section1 	{size:612.0pt 792.0pt; 	margin:72.0pt 72.0pt 72.0pt 72.0pt; 	mso-header-margin:36.0pt; 	mso-footer-margin:36.0pt; 	mso-paper-source:0;} div.Section1 	{page:Section1;}  /* List Definitions */  @list l0 	{mso-list-id:695303410; 	mso-list-type:hybrid; 	mso-list-template-ids:1367742972 134807553 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;} @list l0:level1 	{mso-level-number-format:bullet; 	mso-level-text:; 	mso-level-tab-stop:none; 	mso-level-number-position:left; 	text-indent:-18.0pt; 	font-family:Symbol;} ol 	{margin-bottom:0cm;} ul 	{margin-bottom:0cm; --></p>
<p><span style="font-size: 10pt; line-height: 115%">We would all like to say “Hold your horses we are only running 1 project this year” however this simply does not meet business reality. For the IT manager as soon as they have defined the annual list of priorities, there is pressure to add new projects, or to change the scope of existing authorised projects.</span></p>
<p>It is simply not possible to say ‘NO’ to every request, eventhough this word is one of the most powerful within the IT Manager’s vocabulary. The pressures of these competing priorities can result in the splitting of attention, loss of focus, and inability to complete tasks and projects in a timely manner. In today’s business climate there is immense pressure for projects to succeed, yet we know that each additional request reduces the chances on-time delivery</p>
<p>We may moan that the business community has no concept of the impact of a change in scope. Yet in the time it takes to deliver the average project business needs have changed and IT cannot ignore the evolving needs. Organizations need to reliably deliver projects in shorter and shorter intervals, and some of the pressure include:</p>
<ul>
<li>Many projects and few clear priorities</li>
<li>Demands to multi-task</li>
<li>Procrastination,</li>
<li>Poor planning,</li>
<li>Personal disorganization</li>
</ul>
<p>Lack of clear priorities will cause inefficiencies in the day-to-day utilisation of project resources. If a Mary finishes a milestone ahead of schedule does the project manager or Mary know what they should be doing next?  As we have multiple projects Mary may think they can get a head-start on a new project, yet this may not be the wisest course of action at this time.</p>
<p>It is not a matter of whether or not to prioritise. It is largely a question of who is the most appropriate person to do a specific task and providing clear priorities within the context of the overall priority list. In the absence of priorities, team members will use their own prioritisation methods. First in first out (FIFO) is rarely the best form of prioritisation, yet it is the method that most people will fall back-on in the absence of any other method.</p>
<p>Multi-tasking (or overloading) is recognised as one of the biggest obstacles in a project for a team member, yet an IT manager is expected to do this with consummate ease. For the IT manager it is essential to gain control of their workday,  The key to doing this effectively is in ensuring that the “do it, delegate it, defer it, drop it” rule is effectively applies to every item in your inbox (and I don’t just mean the Outlook Inbox, I include the physical and mental inboxes as well) <a href="http://cio-perspectives.com/?p=31" target="_blank">click here</a> for an earlier article on this topic. Once you have control on your inbox, you can control the competing priorities. You therefore increase your personal productivity by gaining control of your workday.</p>
<p>By <a title="Peter's website" href="http://ontario-cio.com/" target="_blank">Peter B. Giblett </a></p>
<div class="plus-one-wrap"><g:plusone count="false" href="http://cio-perspectives.com/2009/01/handling-competing-priorities/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://cio-perspectives.com/2009/01/handling-competing-priorities/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
		<item>
		<title>IT Professional: Gaining Control of Your Work Day</title>
		<link>http://cio-perspectives.com/2008/12/getting-things-done-time-management-performing-effective-actions/</link>
		<comments>http://cio-perspectives.com/2008/12/getting-things-done-time-management-performing-effective-actions/#comments</comments>
		<pubDate>Tue, 16 Dec 2008 20:43:01 +0000</pubDate>
		<dc:creator>Peter B. Giblett</dc:creator>
				<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Time Management]]></category>
		<category><![CDATA[Gain Control]]></category>
		<category><![CDATA[Getting things done]]></category>

		<guid isPermaLink="false">http://cio-perspectives.com/?p=31</guid>
		<description><![CDATA[Every professional, irrespective of job title or industry faces a problem of too many deadlines and too many projects competing for our time. We have all seen it before, just when we have it all smoothly running, then  new crisis erupts. We constantly have to change our priorities and scramble to get control of our [...]]]></description>
			<content:encoded><![CDATA[<p>Every professional, irrespective of job title or industry faces a problem of too many deadlines and too many projects competing for our time. We have all seen it before, just when we have it all smoothly running, then  new crisis erupts. We constantly have to change our priorities and scramble to get control of our priorities once again &#8211; your daily regime must go on.</p>
<p>We can often look at others, who seem to have their stack of work perfectly arranged and appear unflustered whenever things go wrong. We can be the same, and this will help us deliver our projects on-time, irrespective of that last minute curve-ball thrown our way.</p>
<p>For anyone wishing to turn around how they organise themselves I heartily recommend you read <a title="A linke to David Allen's Book on Amazon.com" href="http://bit.ly/BQ0w" target="_blank">David Allen&#8217;s Getting Things Done</a>, it is a great book and the basis for much of this article. Before reading David&#8217;s book I had struggled to find my own philosophy for getting things done most of the other approaches or software I have seen don&#8217;t really work.</p>
<p>Some of the problems we face:</p>
<ul>
<li>New demands</li>
<li>Insufficient resources</li>
<li>The changing nature of our work</li>
<li>Too many deadlines</li>
</ul>
<p>If you can capture and complete all tasks that need to be done then you can certainly be a star within your organisation.</p>
<p>With all &#8216;stuff&#8217; that we must do irrespective of whether that is a complex task like writing a justification for a project, or the act of picking up out suit from the dry cleaners needs to get prioritised somewhere within our day. So to be successful in organising ourselves there is not really any separation between &#8216;things for work&#8217; and other tasks it is simply a matter of where we will do the activity.</p>
<p>Any &#8216;stuff&#8217; that is to be done is logically in our in-basket (even if we do not possess a physical basket).With every item we must know what it is and decide if it actionable. With every new idea you can make one of the following choices</p>
<ul>
<li>Do it,</li>
<li>Defer it,</li>
<li>Delegate it, or</li>
<li>Drop it.</li>
</ul>
<p><em><strong>Non-actionable items</strong></em> may be filed as reference material, or thrown away.</p>
<p><em><strong>Actionable items</strong></em> require some action to resolve them. An item can either be responded to immediately, put for future action, it can be delegated, or included as part of a project.</p>
<p>If we are going to respond immediately David Allen suggests it should take no longer than two minutes to complete these tasks &#8211; I will do it now it it takes less than 10 minutes. An invitation to attend a conference in 9 months time may be interesting but we do not need to take action on it today therefore we file it in a future action file. At some future date we can decide whether or not to attend. Likewise that nice-to-have requirement by the production manager. We can therefore file it for future review. A future action should either be either entered in the diary, or filed for future review.</p>
<p>We have to continue to review these items at the appropriate time, in a series of files that we look at daily. David Allen calls these a <em>tickler file</em>. We have day files 1 to 31 and monthly files January to December. We bring an item from where we filed it to the front by continuing to review our files and then performing the relevant action at the relevant time. That conference next September has an &#8216;early saver&#8217; deadline in July so we place it for future action next July. That requirement for the production manager is placed in the active file for 10th of next month (day file 10). As time goes on each file cycles to the back, ready for re-use.</p>
<p>If we decide to delegate it, then we are taking the decision to place an item on another person&#8217;s work queue. The person we may delegate will be the most appropriate person in the corporation. It may even be the President of the company. Within your own team it is important to understand the the team workloads. Remember you are adding to the team activity list by this action. When delegating a task to someone outside our team the appropriate level of diplomacy is required. This is especially true if you are adding to the already bulging actions for the CEO.</p>
<p>Within the IT team actionable items are essentially the lifeblood of the department and the IT leader needs to have their finger on the pulse.</p>
<p>It is not possible to do every task placed in front of us. At the end of the day you need to trust in your system and ensure it works for you. If lists fall behind reality then you will always be playing catch-up. When you trust your system you can feel fine about both the things you are going to do, as well as those you will not. Additionally within IT there should only be a limited number of ways that a team will pull activities off the work queue. Team members need to ensure that nothing gets in through back-door personal request.</p>
<p>By <a title="Peter B. Giblett's profile." href="http://ontario-cio.com/" target="_blank">Peter B. Giblett</a></p>
<div class="plus-one-wrap"><g:plusone count="false" href="http://cio-perspectives.com/2008/12/getting-things-done-time-management-performing-effective-actions/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://cio-perspectives.com/2008/12/getting-things-done-time-management-performing-effective-actions/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Is Telecommuting the best model for future business?</title>
		<link>http://cio-perspectives.com/2008/12/is-telecommuting-the-best-model-for-future-business/</link>
		<comments>http://cio-perspectives.com/2008/12/is-telecommuting-the-best-model-for-future-business/#comments</comments>
		<pubDate>Fri, 05 Dec 2008 02:13:09 +0000</pubDate>
		<dc:creator>Peter B. Giblett</dc:creator>
				<category><![CDATA[Corporate Strategy]]></category>
		<category><![CDATA[Tele-working]]></category>
		<category><![CDATA[Collaboration]]></category>
		<category><![CDATA[Cost Effectiveness]]></category>
		<category><![CDATA[Telecommuting]]></category>

		<guid isPermaLink="false">http://cio-perspectives.com/?p=27</guid>
		<description><![CDATA[By Peter B. Giblett In the Internet age a large number of the workforce responsible for data management can be remote workers. They do not need to travel to office buildings. It can be argued that the Web reverses many business processes: you do not go to work, work comes to you. Yet the average [...]]]></description>
			<content:encoded><![CDATA[<p>By <a title="Peter's profile" href="http://cio-perspectives.com//wp-admin/www.ontario-cio.com" target="_blank">Peter B. Giblett</a><br />
In the Internet age a large number of the workforce responsible for data management can be remote workers. They do not need to travel to office buildings. It can be argued that the Web reverses many business processes: you do not go to work, work comes to you. Yet the average corporation still requires attendance at the business premises.</p>
<div class="blogs_entrybody">The cost reductions associated with telecommuting can be attractive to corporations when facing a recession. The benefits of expanding access beyond the corporate office are compelling as:<br />
• Reduction in office space and operating expenses<br />
• Better work-life balance for employees<br />
• Increased employee productivity<br />
• Increased quality contact with customers<br />
• Contributes to &#8216;Green Computing&#8217;</p>
<p><span style="text-decoration: underline;">Cloud Computing Opportunity?</span></p>
<p>The introduction of &#8216;Cloud computing&#8217; creates the ability to access corporate services from outside of the enterprise which should aid the ability to telecommute. This technology is a long way from being considered mainstream. However the IT department must at this stage understand how this technology will change the corporation and plan for the future. In some sectors it is already seen as important &#8216;Cloud computing&#8217; e.g. for the sales-force.</p>
<p>Moves by larger software vendors into the cloud computing arena does add confidence in this application space, but this is still perhaps 3 (or more) years from maturing.</p>
<p><span style="text-decoration: underline;">The Human Dimension</span></p>
<p>There is the human dimension to consider here as well. Some people may do well telecommuting, but others may not have the personality or the discipline to be productive unless they are based in a traditional work setting. Telecommuters face a consistent danger that &#8220;out of sight is out of mind&#8221; which may affect the manager and co-worker perceptions of the worker and their performance. Will the tele-worker be first on the chopping block when redundancies are announced?</p>
<p>Tele-workers need to make a deliberate effort to demonstrate their work accomplishments, on-time delivery and productivity. Overall it is important to be responsive management demands.</p>
<p><span style="text-decoration: underline;">Video Conferencing</span></p>
<p>The introduction of video phones in the telecom market adds an interesting dimension to this discussion. Video has been tried in the UK mobile telecom market before. The concept is good in principle. I can see the use of it for business teleconferencing. Will it make video-conferencing as a part of telecommuting a normal way to carry out business? I doubt it.</p>
<p>I see video telecom currently as an experimental technology, bandwidth can be a big issue. If it is to break ground then it is in the area of home usage &#8211; we all want to see the grand-children without having to travel. The home market may in the long run move the business marketplace.</p>
<p>Video conferencing can also be managed effectively through the PC as there are many tools that will allow a person to become more visible.</p>
<p><span style="text-decoration: underline;">Projects Requiring Collaboration</span></p>
<p>Additionally telecommuting will complicate business processes. IT projects do require collaboration in order for successful delivery and personal contact is an important part of this process.</p>
<p>Working at home there are time when it is possible to get more done with fewer interruptions. The downside can be the lack of contact with colleagues.</p>
<p>I don&#8217;t think telecommuting is the best model for the future workplace, but I do believe it to be a viable model.</p></div>
<div class="plus-one-wrap"><g:plusone count="false" href="http://cio-perspectives.com/2008/12/is-telecommuting-the-best-model-for-future-business/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://cio-perspectives.com/2008/12/is-telecommuting-the-best-model-for-future-business/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

