<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: 1: Accountability</title>
	<atom:link href="http://www.ldscio.org/2008/07/14/1-accountability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ldscio.org/2008/07/14/1-accountability/</link>
	<description>Chief Information Officer for The Church of Jesus Christ of Latter-day Saints</description>
	<lastBuildDate>Sun, 21 Mar 2010 05:35:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ralph</title>
		<link>http://www.ldscio.org/2008/07/14/1-accountability/comment-page-1/#comment-2157</link>
		<dc:creator>Ralph</dc:creator>
		<pubDate>Sat, 13 Sep 2008 03:32:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/?p=126#comment-2157</guid>
		<description>The concept of micromanaging is such an intriguing one.  It bugs me that so many good people, when they get into management turn to micromanaging styles.  Micromanaging makes people feel insignificant, except the manager who then feels over significant.  

I think it intriguing, the leadership of the LDS church concept.  The leaders, yes they lead when they need to.  But they have such love for the peope, they would rather give service to those who need it, rather than play the boss and kick back and do nothing but order and watch.  To be of service to those undeneith you flies in the face of typical world management styles, yet it appears to build more people&#039;s character than micromanaging does.  

The true mark of good management tactics are good communications, return and report expectations, help when you can, even in small things.  Don&#039;t play games with people.  And last of all (there are others, but we will stop here), treat all your employees with great respect.

I like the sign in a business that says &quot;Treat your employees like you would like them to treat your customers&quot;.  I think that somewhat summerizes it.</description>
		<content:encoded><![CDATA[<p>The concept of micromanaging is such an intriguing one.  It bugs me that so many good people, when they get into management turn to micromanaging styles.  Micromanaging makes people feel insignificant, except the manager who then feels over significant.  </p>
<p>I think it intriguing, the leadership of the LDS church concept.  The leaders, yes they lead when they need to.  But they have such love for the peope, they would rather give service to those who need it, rather than play the boss and kick back and do nothing but order and watch.  To be of service to those undeneith you flies in the face of typical world management styles, yet it appears to build more people&#8217;s character than micromanaging does.  </p>
<p>The true mark of good management tactics are good communications, return and report expectations, help when you can, even in small things.  Don&#8217;t play games with people.  And last of all (there are others, but we will stop here), treat all your employees with great respect.</p>
<p>I like the sign in a business that says &#8220;Treat your employees like you would like them to treat your customers&#8221;.  I think that somewhat summerizes it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J. Edgardo Pina</title>
		<link>http://www.ldscio.org/2008/07/14/1-accountability/comment-page-1/#comment-2117</link>
		<dc:creator>J. Edgardo Pina</dc:creator>
		<pubDate>Sat, 16 Aug 2008 00:05:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/?p=126#comment-2117</guid>
		<description>I have learned that to be able to provide effective accountability-based leadership, many times I should assist first (and some times force) my managers (yes, managers) to understand what they want, how much effort (and money!) it requires, their willingness to compromise in some areas and to identify those areas where they wont compromise, and many times to re-asses the priority of the assignment regarding the cost/benefit that will be achieved after the mission is successfully accomplished. IT projects are not static, so we need to identify those core accountability-benchmarks that we need to focus on first. I know by personal experience that this principle of accountability is critical for the success of all organizations. I have successfully applied these principles in multi-country IT and cross-organizational environments and I would feel blessed of having the opportunity to do the same within ICS. Thanks for your thoughts.</description>
		<content:encoded><![CDATA[<p>I have learned that to be able to provide effective accountability-based leadership, many times I should assist first (and some times force) my managers (yes, managers) to understand what they want, how much effort (and money!) it requires, their willingness to compromise in some areas and to identify those areas where they wont compromise, and many times to re-asses the priority of the assignment regarding the cost/benefit that will be achieved after the mission is successfully accomplished. IT projects are not static, so we need to identify those core accountability-benchmarks that we need to focus on first. I know by personal experience that this principle of accountability is critical for the success of all organizations. I have successfully applied these principles in multi-country IT and cross-organizational environments and I would feel blessed of having the opportunity to do the same within ICS. Thanks for your thoughts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heidi Mason</title>
		<link>http://www.ldscio.org/2008/07/14/1-accountability/comment-page-1/#comment-2111</link>
		<dc:creator>Heidi Mason</dc:creator>
		<pubDate>Wed, 13 Aug 2008 03:29:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/?p=126#comment-2111</guid>
		<description>It&#039;s great to see how much accountability you take on for ICS. When I started working in ICS, I was impressed with how much trust seemed to be floating around. It made a little more sense when I was introduced to the cultural beliefs, and now it makes even more sense now that I&#039;ve been reading &quot;Journey to the Emerald City.&quot; I am personally very impressed with how accountable you hold yourself, and in turn how accountable it makes each of us employees. (Would that I could remain with ICS, but alas, I&#039;m a temporary! Tomorrow I interview with the company that published &quot;The Oz Principle&quot; and &quot;Journey to the Emerald City&quot; as a staff writer. I feel prepared for their culture based on the one I&#039;ve experienced in ICS, so thank you!)</description>
		<content:encoded><![CDATA[<p>It&#8217;s great to see how much accountability you take on for ICS. When I started working in ICS, I was impressed with how much trust seemed to be floating around. It made a little more sense when I was introduced to the cultural beliefs, and now it makes even more sense now that I&#8217;ve been reading &#8220;Journey to the Emerald City.&#8221; I am personally very impressed with how accountable you hold yourself, and in turn how accountable it makes each of us employees. (Would that I could remain with ICS, but alas, I&#8217;m a temporary! Tomorrow I interview with the company that published &#8220;The Oz Principle&#8221; and &#8220;Journey to the Emerald City&#8221; as a staff writer. I feel prepared for their culture based on the one I&#8217;ve experienced in ICS, so thank you!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cousin Kirsten</title>
		<link>http://www.ldscio.org/2008/07/14/1-accountability/comment-page-1/#comment-2107</link>
		<dc:creator>Cousin Kirsten</dc:creator>
		<pubDate>Thu, 07 Aug 2008 22:30:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/?p=126#comment-2107</guid>
		<description>I agree so much.  Those things really apply to parenting as well.  Sometimes I micromanage my kids, and they end up ornery and impossible to deal with.  This was a great reminder to set them free within proper boundaries.</description>
		<content:encoded><![CDATA[<p>I agree so much.  Those things really apply to parenting as well.  Sometimes I micromanage my kids, and they end up ornery and impossible to deal with.  This was a great reminder to set them free within proper boundaries.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Lockard</title>
		<link>http://www.ldscio.org/2008/07/14/1-accountability/comment-page-1/#comment-2104</link>
		<dc:creator>Nathan Lockard</dc:creator>
		<pubDate>Sat, 02 Aug 2008 03:51:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/?p=126#comment-2104</guid>
		<description>What a great post!  At my first job I was blessed with the opportunity to work for your village chieftain.  I say I was blessed because I got to learn very early in my career the management principle that you’ve outlined here.

I was an intern on the Nintendo Power magazine staff and my primary responsibility was to take screenshots of that month&#039;s featured video games.  On one project I was given the added responsibility of making callouts for the location of items on every map in a 120+ page guide book.  Because the game was still under development these item locations tended to move around from week to week.  I had no documentation and was forced to play thru the game and recheck all of these callouts each time I got a new drop of code, which took time.  Before the project started, my manager had given me a vague, loose description of what she needed me to do.  She told me that it was my job to make sure that the maps were correct.  It wasn&#039;t until we were doing the final check of the proofs on the day before we went to print that she asked me if I had made sure that the locations of some ultra-rare items were correct.  She was extremely anxious because as she put it, the game wasn&#039;t very complicated, but that those items were difficult to find, so revealing how to find them was one of the most important value propositions of the guide.  Luckily I had figured that out on my own and had checked those items on the final build and sure enough, they had moved.

Long story short, from that experience I learned that as a manager I need to define what success looks like and that on the flipside, I need to ask my manager to do the same.</description>
		<content:encoded><![CDATA[<p>What a great post!  At my first job I was blessed with the opportunity to work for your village chieftain.  I say I was blessed because I got to learn very early in my career the management principle that you’ve outlined here.</p>
<p>I was an intern on the Nintendo Power magazine staff and my primary responsibility was to take screenshots of that month&#8217;s featured video games.  On one project I was given the added responsibility of making callouts for the location of items on every map in a 120+ page guide book.  Because the game was still under development these item locations tended to move around from week to week.  I had no documentation and was forced to play thru the game and recheck all of these callouts each time I got a new drop of code, which took time.  Before the project started, my manager had given me a vague, loose description of what she needed me to do.  She told me that it was my job to make sure that the maps were correct.  It wasn&#8217;t until we were doing the final check of the proofs on the day before we went to print that she asked me if I had made sure that the locations of some ultra-rare items were correct.  She was extremely anxious because as she put it, the game wasn&#8217;t very complicated, but that those items were difficult to find, so revealing how to find them was one of the most important value propositions of the guide.  Luckily I had figured that out on my own and had checked those items on the final build and sure enough, they had moved.</p>
<p>Long story short, from that experience I learned that as a manager I need to define what success looks like and that on the flipside, I need to ask my manager to do the same.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Peay</title>
		<link>http://www.ldscio.org/2008/07/14/1-accountability/comment-page-1/#comment-2103</link>
		<dc:creator>Dan Peay</dc:creator>
		<pubDate>Thu, 31 Jul 2008 17:17:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/?p=126#comment-2103</guid>
		<description>Very insighful! An excellent and practicle application of agency within the Lord’s boundries or within covenant.</description>
		<content:encoded><![CDATA[<p>Very insighful! An excellent and practicle application of agency within the Lord’s boundries or within covenant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony Tietjen</title>
		<link>http://www.ldscio.org/2008/07/14/1-accountability/comment-page-1/#comment-2092</link>
		<dc:creator>Anthony Tietjen</dc:creator>
		<pubDate>Sat, 19 Jul 2008 20:32:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/?p=126#comment-2092</guid>
		<description>Thanks for the article. One thing I would suggest is taking precautionary measures (if needed) before assigning things out. For example, if you are going to assign someone to modify your organization&#039;s website, it would be a good idea to make a backup of the files in case an accident does occur. (Such as the files get deleted.)

Yes, people need to be responsible for their actions, but you can try to make it so that an accident doesn&#039;t cause a detriment.</description>
		<content:encoded><![CDATA[<p>Thanks for the article. One thing I would suggest is taking precautionary measures (if needed) before assigning things out. For example, if you are going to assign someone to modify your organization&#8217;s website, it would be a good idea to make a backup of the files in case an accident does occur. (Such as the files get deleted.)</p>
<p>Yes, people need to be responsible for their actions, but you can try to make it so that an accident doesn&#8217;t cause a detriment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mario Hipol</title>
		<link>http://www.ldscio.org/2008/07/14/1-accountability/comment-page-1/#comment-2076</link>
		<dc:creator>Mario Hipol</dc:creator>
		<pubDate>Wed, 16 Jul 2008 20:14:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/?p=126#comment-2076</guid>
		<description>I think that sometimes we also have to be careful how much we press for information too.  I have worked with people in the past that have been asked to &quot;get a rock,&quot; and in turn asked their chief to provide them with a sample of the rock they were to go get. 

There is a fine line between being a useful part of a project team and hindering your teams progress.

&lt;em&gt;[Joel: It&#039;s a great point. Thank you, Mario. Sometimes people invite management to get involved by asking questions in the wrong way or asking the wrong questions altogether. Employees should gauge the propensity of the boss to micromanage or to want things done a certain way and throttle questions accordingly. Managers should encourage people to ask questions, but try to be perscriptive only when it really matters.]&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>I think that sometimes we also have to be careful how much we press for information too.  I have worked with people in the past that have been asked to &#8220;get a rock,&#8221; and in turn asked their chief to provide them with a sample of the rock they were to go get. </p>
<p>There is a fine line between being a useful part of a project team and hindering your teams progress.</p>
<p><em>[Joel: It's a great point. Thank you, Mario. Sometimes people invite management to get involved by asking questions in the wrong way or asking the wrong questions altogether. Employees should gauge the propensity of the boss to micromanage or to want things done a certain way and throttle questions accordingly. Managers should encourage people to ask questions, but try to be perscriptive only when it really matters.]</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon&#8217;s Geek Stuff &#8230; &#38; Stuff &#187; Accountability</title>
		<link>http://www.ldscio.org/2008/07/14/1-accountability/comment-page-1/#comment-2075</link>
		<dc:creator>Jon&#8217;s Geek Stuff &#8230; &#38; Stuff &#187; Accountability</dc:creator>
		<pubDate>Wed, 16 Jul 2008 20:05:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/?p=126#comment-2075</guid>
		<description>[...] Accountability [...]</description>
		<content:encoded><![CDATA[<p>[...] Accountability [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Syphax</title>
		<link>http://www.ldscio.org/2008/07/14/1-accountability/comment-page-1/#comment-2074</link>
		<dc:creator>Syphax</dc:creator>
		<pubDate>Wed, 16 Jul 2008 03:23:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/?p=126#comment-2074</guid>
		<description>(I was going to say throw the rock at him, but that&#039;s why I don&#039;t manage this blog)

&lt;em&gt;[Joel: You&#039;re hired!]&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>(I was going to say throw the rock at him, but that&#8217;s why I don&#8217;t manage this blog)</p>
<p><em>[Joel: You're hired!]</em></p>
]]></content:encoded>
	</item>
</channel>
</rss>
