 




<?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>Oh I See! Getting CIOs to view their jobs from a different angle &#187; Follow up</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/Oh-I-See/tag/follow-up/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/Oh-I-See</link>
	<description></description>
	<lastBuildDate>Sun, 12 May 2013 23:15:58 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>I hate you for this</title>
		<link>http://itknowledgeexchange.techtarget.com/Oh-I-See/i-hate-you-for-this/</link>
		<comments>http://itknowledgeexchange.techtarget.com/Oh-I-See/i-hate-you-for-this/#comments</comments>
		<pubDate>Tue, 23 Aug 2011 14:14:27 +0000</pubDate>
		<dc:creator>Arun Gupta</dc:creator>
				<category><![CDATA[BITA]]></category>
		<category><![CDATA[Follow up]]></category>
		<category><![CDATA[project management]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/Oh-I-See/?p=382</guid>
		<description><![CDATA[Irregularity in project status updates from the team can be irksome for a CIO. Shoppers Stop’s Arun Gupta probes why follow ups are so time consuming.]]></description>
				<content:encoded><![CDATA[<p class="MsoNormal"><span lang="EN-GB">The meeting finished with agreement on clear responsibilities, time lines and the next scheduled meeting date four weeks away. The minutes circulated to the team the next day captured this very well. Like all projects, this one was thus far on track though the next three months were critical. The requirement gathering had gone well and the first cut was delivered on time. Everyone seemed geared to take on the challenge and another <a href="http://searchcio.techtarget.in/tip/Project-review-tips-for-effective-project-management" target="_blank">successful project delivered</a>.</span></p>
<p class="MsoNormal"><span lang="EN-GB">Over the next few weeks, some updates were received on the portal, a couple of emails and then none. I began to wonder, getting anxious, if everything was okay with the project. So a reminder was sent to the group asking for updates; received one response, silence from others. With just one week remaining for the next meeting, and progress report depicting inconsistent updates, acidity levels started rising on the real progress.</span></p>
<p class="MsoNormal"><span lang="EN-GB">So I started calling folks and walking across to their workstations to figure out what gives? Some titbits:</span></p>
<p class="MsoNormal"><em><span lang="EN-GB">“Yes, I have completed the tasks, but was too busy to provide an update.”</span></em></p>
<p class="MsoNormal"><em><span lang="EN-GB">“You should have the status by the end of the day.”</span></em></p>
<p class="MsoNormal"><em><span lang="EN-GB">“Why are you getting on my back? By the time we get to the meeting, we will be on track.”</span></em></p>
<p class="MsoNormal"><em><span lang="EN-GB">“Sorry, something urgent came up, so I am a bit behind schedule.”</span></em></p>
<p class="MsoNormal"><span lang="EN-GB">All this made me wonder, here we are in the midst of an important project that has Board visibility, will provide a significant benefit, everyone vied to be on <a href="http://searchcio.techtarget.in/news/1513343/Management-of-IT-projects-Mantras-for-success" target="_blank">the project due to the positive impact</a>; but they do not find time to provide an update! What causes such </span><span>behavior</span><span lang="EN-GB">? Why do some people find it difficult to provide open and clear communication on agreed milestones or request for information? Why is follow up necessary?</span></p>
<p class="MsoNormal"><span lang="EN-GB">With multiple priorities and fires that need to be doused, short-term dementia is pervasive. Rarely the lack of response is out of disrespect, disregard, or plain indifference. <a href="http://searchcio.techtarget.in/news/1515503/IT-project-management-basics-Get-the-individual-components-right" target="_blank">Follow-up is essential</a> to bring the issue at hand to attention, to reinforce the signal of ownership and shared responsibility. It also helps to bring back focus to what matters.</span></p>
<p class="MsoNormal"><span lang="EN-GB">Having said this, there could be instances of no response where connect is not adequately strong or in some cases due to missing shared accountability. Another factor that contributes to silence is the fear of conflict. This occurs when the issue and people are inseparable. Culturally, many are unable to provide bad news and thus prefer not to respond. In all these cases, the leader has to intervene and create the way forward.</span></p>
<p class="MsoNormal"><span lang="EN-GB">IT organizations suffer the most when following up with diverse groups—internal and external. When working on cross-functional projects or while solving problems that require different technologies to work together, it is important for IT leaders to inculcate missionary discipline within the team to ensure that the initiatives in which IT participates, there is clear communication to all stakeholders.</span></p>
<p class="MsoNormal"><span lang="EN-GB">Someone summed it up well “If I did not have to follow-up, I would save half my day”.</span></p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/Oh-I-See/i-hate-you-for-this/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
