<?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>TomDoepker.com &#187; Self-management</title>
	<atom:link href="http://tomdoepker.com/category/self-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://tomdoepker.com</link>
	<description>The web development portfolio of Tom Doepker, web site designer, developer and team lead</description>
	<lastBuildDate>Thu, 26 Jan 2012 15:31:45 +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>A Great Web Site is Never Done</title>
		<link>http://tomdoepker.com/2008/06/12/a-great-web-site-is-never-done/</link>
		<comments>http://tomdoepker.com/2008/06/12/a-great-web-site-is-never-done/#comments</comments>
		<pubDate>Thu, 12 Jun 2008 16:08:40 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Self-management]]></category>

		<guid isPermaLink="false">http://tomdoepker.com/2008/06/12/a-great-web-site-is-never-done/</guid>
		<description><![CDATA[As the leader of an in-house team, I find myself repeatedly facing the painter’s dilemma of: “When do I stop painting? When is the painting done?” Because of their nature, no Web site is ever really done. Projects are finished, milestones and agreed-upon deliverables met, but there’s always something else that could be done. Of [...]]]></description>
			<content:encoded><![CDATA[<p>As the leader of an in-house team, I find myself repeatedly facing the painter’s dilemma of: “When do I stop painting? When is the painting <em>done</em>?” Because of their nature, no Web site is ever really done. Projects are finished, milestones and agreed-upon deliverables met, but there’s always something else that could be done. Of course, there are always plenty of other people waiting to begin work on their projects – not to mention your own list of pet projects – so what do you do?</p>
<p><strong>Set priorities.</strong> Ask yourself, “What can I or my team realistically do that will have the greatest impact?” Whether on a specific project or the organization as a whole, look for a way to focus on your strengths. Too often, defining priorities is done through a process of “negative empiricism” in which everyone comes out a little demoralized thinking about how great it would have been to do something that would have been unrealistic anyway.</p>
<p>Focusing on what you know that you and your team can accomplish if you aim high creates an unblinking view of what you should be doing. In my current role, the main priority is: “To give Clermont County a voice to the world”. This has repeatedly helped us to make decisions on tough issues.</p>
<p><strong>Limit Priorities.</strong> Don’t juggle too much. Do this by delegating everything you can and giving your limited time to the one or two (maybe even three) things that will have the greatest impact.</p>
<p><strong>YOUR priorities are not necessarily THEIR priorities.</strong> Involve your superiors, your peers and your direct reports in setting priorities. A little consensus-building goes a long way.</p>
<p>The most important thing I have found here is that humility is terribly important. Sure, you’ll have opinions, but make sure to listen to what others have to say on the matter. You can’t be afraid of being wrong here because – hopefully – you have surrounded yourself with smart people. Take advantage of them. Seek out opinions that differ from your own and see if your thoughts can stand up to theirs.</p>
<h2>What Does a Good Priority Look Like?</h2>
<ul>
<li>It meets your boss’ goals. Don’t bother otherwise.</li>
<li>Your team feels like they own them. What’s more likely to get you a better result: forcing them to do it your “right way”, or conceding a bit and letting them do it “their way”?</li>
<li>It inspires you and feels like the right thing to do for the future of the organization.</li>
<li>It’s not going to be easy. Nothing good ever is. Look to grow.</li>
<li>It is a basic guideline that allows plenty of room for adaptation.</li>
</ul>
<p><strong><br />
Stick to your priorities.</strong> I’ve learned the hard way that this is the tough part. Regularly review your priorities. Are you committing enough of your time to them? Are the projects you and your team are working on now the best use of time for those priorities? Is this priority still legitimate?</p>
<p>By consistently reminding yourself of where your focus should be, keeping it there is that much easier.</p>
]]></content:encoded>
			<wfw:commentRss>http://tomdoepker.com/2008/06/12/a-great-web-site-is-never-done/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic page generated in 0.758 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2012-02-06 02:34:43 -->

