<?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>Archetyped &#8250; Management</title>
	<atom:link href="http://archetyped.com/tag/management/feed/" rel="self" type="application/rss+xml" />
	<link>http://archetyped.com</link>
	<description>Explore, Experiment, Inspire</description>
	<lastBuildDate>Tue, 21 Feb 2012 23:49:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Blog &#8250; 30 Days of Schedules</title>
		<link>http://archetyped.com/blog/30-days-of-schedules/</link>
		<comments>http://archetyped.com/blog/30-days-of-schedules/#comments</comments>
		<pubDate>Mon, 17 Oct 2011 06:00:17 +0000</pubDate>
		<dc:creator>Sol</dc:creator>
				<category><![CDATA[Feature]]></category>
		<category><![CDATA[30 Days]]></category>
		<category><![CDATA[Experiment]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Productivity]]></category>
		<category><![CDATA[Schedule]]></category>
		<category><![CDATA[Time]]></category>

		<guid isPermaLink="false">http://archetyped.com/auto-draft/</guid>
		<description><![CDATA[There is a great sense of freedom that accompanies being self-employed.  However, with that freedom comes great responsibility.  I put my assumptions to the test to see if having a fixed schedule will help me accomplish more in the same amount of time.]]></description>
			<content:encoded><![CDATA[<p>There is a great sense of freedom that accompanies being self-employed.  However, to paraphrase a well known wall-crawler, <strong>with great freedom comes great responsibility</strong>.</p>
<p>When there&#8217;s no one else breathing down your neck to get stuff done, <strong>you</strong> have to be even more attentive to how effective you are with your time.</p>
<p>I work on projects that I am passionate about and have a deep interest in.  Nonetheless, <strong>momentum is incredibly important</strong> as <a href="http://archetyped.com/blog/mountain-climbing/" title="Mountain Climbing">any project worth doing will have it&#8217;s share of hard work</a>.  Therefore, when I am working on a project and making good progress, I will generally continue to work on that project until I reach a milestone of some sort.  Stopping short of that feels like a waste of all of the momentum I&#8217;ve built up when the end could be just around the corner.</p>
<h2>The Problem</h2>
<p>It may be obvious what kind of problem this way of working may present&#8211; by focusing all of my attention on a <em>single</em> project, <strong>all other projects fall by the wayside</strong>.  If I was only interested and passionate about one thing at a time, this would not be a problem, but alas, I am usually working on several projects concurrently.</p>
<p>This leads to the dreaded <strong>&#8220;should be&#8217;s&#8221;</strong>, where I think about how I <em>should be</em> working on one project while I am working on another.  The longer that I don&#8217;t get back to working on a project, the stronger the feeling that I should be working on it gets.</p>
<p>The end result is a feeling of dissatisfaction with what I&#8217;ve accomplished and a sense that there&#8217;s always more to be done.</p>
<h2>A Solution?</h2>
<p>Though I plan out what I will be working on next, I have always been of the belief that there wasn&#8217;t much point in creating a rigid schedule because I wanted the <strong>freedom</strong> to continue working on a project into the next day (or week), should the current task require it.  Creating a fixed schedule would either stop all momentum cold, or cause me to feel guilty because I wasn&#8217;t sticking to it.</p>
<p>But was it true?</p>
<p>I decided to put my assumptions to the test, and so for the next 30 days, I will be working on a fixed schedule where my projects change on a daily basis.</p>
<h2>The Details</h2>
<ul>
<li>I will be working on 1-2 projects (maximum) per day.</li>
<li>I will work on <strong>different</strong> projects each day of the week.</li>
<li>The schedule repeats on a weekly basis.</li>
</ul>
<p>Here is my weekly schedule for the next 30 days:</p>
<h3>Monday</h3>
<ol>
<li><a href="http://archetyped.com/tools/simple-lightbox/" title="Simple Lightbox">Simple Lightbox</a></li>
<li>Business development</li>
</ol>
<h3>Tuesday</h3>
<ol>
<li><a href="http://archetyped.com/tools/cornerstone/" title="Cornerstone">Cornerstone</a></li>
<li>Site maintenance</li>
</ol>
<h3>Wednesday</h3>
<ol>
<li>Art (design, photography, etc.)</li>
<li><a href="http://archetyped.com/lab/wordpress-in-the-classroom-brainstorming/" title="WordPress in the Classroom: Brainstorming">Wordpress in the Classroom</a></li>
</ol>
<h3>Thursday</h3>
<ol>
<li>Video (Shoot)</li>
</ol>
<h3>Friday</h3>
<ol>
<li>Video (Edit)</li>
</ol>
<p>I&#8217;ve grouped projects together that are either related somehow (e.g. <a href="http://archetyped.com/tools/cornerstone/" title="Cornerstone">Cornerstone</a> is used heavily on this site, so it will play a role in the site&#8217;s maintenance), or where one project will present a refreshing change from the other (so that I don&#8217;t get burnt out during the day).</p>
<h2>The Rules</h2>
<p>As always, I like to keep things simple, so the rules are deliberately brief:</p>
<ul>
<li><strong>I can only work on the projects scheduled for the current day</strong>.  If I finish the tasks I scheduled for the current day&#8217;s projects, I can work on other tasks for those projects, but it would probably be better if I called it a day.</li>
<ul>
<li><strong>Exception:</strong> User support for my <a href="http://archetyped.com/tools/" title="Tools">software/plugins</a> is exempt from this as waiting a week for an answer to a question or bug report is unreasonable.</li>
</ul>
<li><strong>No adjustments</strong>. At least for the initial 30 days. I want to see this schedule through to the end to see how bad (or good) things get if I rigidly hold myself to the original schedule.</li>
</ul>
<h2>Closing Thoughts</h2>
<p>I don&#8217;t begrudge structure, in fact I love it.  I&#8217;ve just never felt that a rigid and predefined schedule lends itself to creativity.  However, one of the questions I&#8217;d like explore over the next 30 days is if <strong>adding more structure to my schedule will free me to be more creative in other areas</strong> (e.g. in my projects).</p>
<div class="highlight"><strong>Update:</strong> A <a href="http://archetyped.com/blog/30-days-of-schedules-in-review/" title="30 Days of Schedules: In Review">review of the results of this experiment</a> has been posted.</div>
<p><a href="http://archetyped.com/blog/30-days-of-schedules/"> 30 Days of Schedules</a> was originally published on <a href="http://archetyped.com">Archetyped</a> on October 16, 2011 08:00pm</p>]]></content:encoded>
			<wfw:commentRss>http://archetyped.com/blog/30-days-of-schedules/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

