<?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; 30 Days</title>
	<atom:link href="http://archetyped.com/tag/30-days/feed/" rel="self" type="application/rss+xml" />
	<link>http://archetyped.com</link>
	<description>Explore, Experiment, Inspire</description>
	<lastBuildDate>Thu, 10 May 2012 19:19:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Blog &#8250; Schedule Changes</title>
		<link>http://archetyped.com/blog/schedule-changes/</link>
		<comments>http://archetyped.com/blog/schedule-changes/#comments</comments>
		<pubDate>Fri, 06 Apr 2012 00:26:31 +0000</pubDate>
		<dc:creator>Sol</dc:creator>
				<category><![CDATA[Feature]]></category>
		<category><![CDATA[30 Days]]></category>
		<category><![CDATA[Experiment]]></category>
		<category><![CDATA[Productivity]]></category>
		<category><![CDATA[Results]]></category>
		<category><![CDATA[Schedule]]></category>
		<category><![CDATA[Time]]></category>
		<category><![CDATA[Workflow]]></category>

		<guid isPermaLink="false">http://archetyped.com/auto-draft/</guid>
		<description><![CDATA[During my previous , one of the questions that arose was how larger projects would fit into a workflow that allowed only one day per week to work on any given project.  Despite the many benefits of such a constant variation of work (increased motivation to make progress, a fresh start every day, etc.), the ...]]></description>
			<content:encoded><![CDATA[<p>During my previous <a href="http://archetyped.com/blog/30-days-of-schedules-in-review/" title="30 Days of Schedules: In Review">experiment with schedules</a>, one of the questions that arose was how larger projects would fit into a workflow that allowed only one day per week to work on any given project.  Despite the many benefits of such a constant variation of work (increased motivation to make progress, a fresh start every day, etc.), the reality is that a project that would take 2 weeks of work would end up taking <strong>2.5 months</strong> to complete, which is obviously not ideal.</p>
<h2>A new experiment: 2 for 1</h2>
<p>This week, I have begun experimenting with a schedule that allots <em>two</em> days per week to a project instead of just one.</p>
<p>I will still be grouping multiple projects together on the same days as I have found that it helps to keep my eyes from glazing over as can happen when working on one thing for too long.  The projects are grouped together strategically (related workflows, thought processes, etc.) to maintain as much momentum as possible throughout the day.  I have also injected a day (Wednesday) where I do something <strong>completely different</strong> to optimize the transition between the first half of the week and the second half.</p>
<h3>The Schedule</h3>
<ul>
<li><strong>Monday-Tuesday</strong></li>
<ul>
<li><a href="http://archetyped.com/tools/simple-lightbox/" title="Simple Lightbox">Simple Lightbox</a></li>
<li><a href="http://archetyped.com/tools/cornerstone/" title="Cornerstone">Cornerstone</a></li>
</ul>
<li><strong>Wednesday</strong></li>
<ul>
<li>Photography</li>
<li>Video</li>
</ul>
<li><strong>Thursday-Friday</strong></li>
<ul>
<li><em>Top-Secret Project</em></li>
<li>Site Maintenance</li>
</ul>
</ul>
<h2>Benefits</h2>
<p>Some of the main benefits one may expect from such a schedule are:</p>
<ul>
<li><strong>Better use of momentum</strong> &#8212; Momentum is a powerful tool, and by allocating two consecutive days per week to a project, I will be able to harness the momentum from the first day to make even more progress the next day.<br />
<strong></strong></li>
<li><strong>Increased focus</strong> &#8212; With fewer projects to juggle, I can focus more attention on specific projects.<br />
<strong></strong></li>
<li><strong>Faster project completion</strong> &#8212; With more time to work on a given project, I will be able to complete the projects faster</li>
<li><strong>Increased availability for new projects</strong> &#8212; There are <em>always</em> projects on the backburner.  By completing current projects faster, I will be able to start working on the awaiting projects sooner.</li>
</ul>
<h2>Pitfalls</h2>
<p>Though one additional day may seem trivial, such a change to the schedule is not without its pitfalls:</p>
<ul>
<li><strong>Less variation</strong> &#8212; Variation was one of the best things about working on a different project every day.  The daily change was refreshing and kept boredom at bay.  By focusing on fewer projects during the week, I may become bored with the repetition.</li>
<li><strong>No progress on other projects</strong>  &#8212; In order to spend more time on certain projects, work will need to be stopped on other projects.  It pains me to put a halt on some projects, even though it provides more time to another project.</li>
<li><strong>Less pressure</strong> &#8212; This is a big one.  By allocating more time to a project during the week, I am essentially <strong>extending the deadline</strong> for the tasks I have scheduled.  I will need to remain vigilant to avoid the <a href="http://en.wikipedia.org/wiki/J._Wellington_Wimpy">Wimpy-esque</a> thought that I can &#8220;take care of it tomorrow.&#8221;</li>
</ul>
<h2>The middle road</h2>
<p>I admit that one of the primary motivations for changing my weekly schedule is a <strong>lack of patience</strong>&#8211; I want to finish certain projects, and I don&#8217;t want to wait.  However, by taking the middle road and allocating only one additional day to each project, I&#8217;m hoping that I will benefit both from the <strong>variation</strong> of a daily schedule and the <strong>increased time</strong> of a more selective schedule.</p>
<p><a href="http://archetyped.com/blog/schedule-changes/"> Schedule Changes</a> was originally published on <a href="http://archetyped.com">Archetyped</a> on April 5, 2012 02:26pm</p>]]></content:encoded>
			<wfw:commentRss>http://archetyped.com/blog/schedule-changes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Blog &#8250; 30 Days of Schedules: In Review</title>
		<link>http://archetyped.com/blog/30-days-of-schedules-in-review/</link>
		<comments>http://archetyped.com/blog/30-days-of-schedules-in-review/#comments</comments>
		<pubDate>Wed, 23 Nov 2011 03:24:00 +0000</pubDate>
		<dc:creator>Sol</dc:creator>
				<category><![CDATA[Feature]]></category>
		<category><![CDATA[30 Days]]></category>
		<category><![CDATA[Experiment]]></category>
		<category><![CDATA[Post-mortem]]></category>
		<category><![CDATA[Productivity]]></category>
		<category><![CDATA[Results]]></category>
		<category><![CDATA[Schedule]]></category>
		<category><![CDATA[Time]]></category>

		<guid isPermaLink="false">http://archetyped.com/auto-draft/</guid>
		<description><![CDATA[It's been a little over a month since I started experimenting with schedules and the results are the most unexpected and impactful of any of my experiments to date.]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s been a little over a month since I <a href="http://archetyped.com/blog/30-days-of-schedules/" title="30 Days of Schedules">started experimenting with schedules</a> and the results are the most unexpected <em>and</em> impactful of any of my experiments to date.</p>
<h2>Limits for Liberation</h2>
<p>I had been thinking about the power of limits for a while before starting this experiment.  Limits&#8211; as opposed to an overabundance of choice&#8211; can <strong>improve focus</strong> and allow us to be more creative with our resources.  If you only have one tool for the job, you get started and make it work.  If you have an entire <em>shed</em> of tools, you can spend all day trying to decide on the <strong>best tool</strong> for the job.</p>
<p>For this experiment, limits were primarily being placed on the my <strong>flexibility</strong> (what I could work on) as well as on my <strong>availability</strong> (the amount of time I could spend on a project).</p>
<h3>Flexibility</h3>
<p>Each day of the week was mapped out in advance.  I would be served up with different projects to work on each day.  I could not deviate from the schedule.</p>
<p>Those 3 statements strike fear down to my very core.</p>
<p>There&#8217;s nothing fun about predictability, but by removing the <em>&#8220;what am I doing today?&#8221;</em> decision off from the top of the stack, I was able to focus on the <strong>real work</strong>, which is <strong>very fun</strong> indeed.  The increase in the amount of focus was also unexpected in that distractions were not an issue at all.</p>
<p>Another result of limiting my options was an <strong>increase in satisfaction</strong> with what I was doing on a given day.  There are so many things that I want to do that I often struggled with a guilty feeling that, <em>&#8220;I should be working on [other project]&#8220;</em>, instead of what I was actually working on.  By dividing my week amongst my high-priority projects, I could rest easy in the knowledge that I have time allotted for each project.  This allowed me to fully embrace what I was scheduled to work on for a given day, whether it be business development (Monday) or more creative endeavors (Thursday).</p>
<h3>Availability</h3>
<p>As you might imagine, having only one day per week to work on a project was a very real limit.  This was probably one of the toughest aspects of the entire experiment for one simple reason&#8211; momentum.</p>
<p>When I first started this experiment, I was worried about the wasted momentum from not being able to continue working on a project the following day.  Getting into the &#8220;zone&#8221; while working on a project is rarely immediate, so once you do get in the zone and things are moving along smoothly, it&#8217;s quite difficult to stop cold and work on something new the next day.</p>
<p><!-- tweet id : 126192349025021952 --><br />
<style type='text/css'>#bbpBox_126192349025021952 a { text-decoration:none; color:#0b5259; }#bbpBox_126192349025021952 a:hover { text-decoration:underline; }</style>
<div id='bbpBox_126192349025021952' class='bbpBox' style='padding:20px; margin:5px 0; background-color:#282828; background-image:url(http://a1.twimg.com/profile_background_images/68764889/screenshot.png); background-repeat:no-repeat'>
<div style='background:#fff; padding:10px; margin:0; min-height:48px; color:#333333; -moz-border-radius:5px; -webkit-border-radius:5px;'><span style='width:100%; font-size:18px; line-height:22px;'>This is why I was hesitant to schedule just 1 day for a particular proj.I&#8217;ve got momentum and would love another day to finish current tasks</span>
<div class='bbp-actions' style='font-size:12px; width:100%; padding:5px 0; margin:0 0 10px 0; border-bottom:1px solid #e6e6e6;'><img align='middle' src='http://archetyped.com/wp-content/plugins/twitter-blackbird-pie//images/bird.png' /><a title='tweeted on October 17, 2011 9:06 pm' href='http://twitter.com/#!/archetyped/status/126192349025021952' target='_blank'>October 17, 2011 9:06 pm</a> via <a href="http://seesmic.com/" rel="nofollow" target="blank">Seesmic</a><a href='https://twitter.com/intent/tweet?in_reply_to=126192349025021952&#038;related=archetyped' class='bbp-action bbp-reply-action' title='Reply'><span><em style='margin-left: 1em;'></em><strong>Reply</strong></span></a><a href='https://twitter.com/intent/retweet?tweet_id=126192349025021952&#038;related=archetyped' class='bbp-action bbp-retweet-action' title='Retweet'><span><em style='margin-left: 1em;'></em><strong>Retweet</strong></span></a><a href='https://twitter.com/intent/favorite?tweet_id=126192349025021952&#038;related=archetyped' class='bbp-action bbp-favorite-action' title='Favorite'><span><em style='margin-left: 1em;'></em><strong>Favorite</strong></span></a></div>
<div style='float:left; padding:0; margin:0'><a href='http://twitter.com/intent/user?screen_name=archetyped'><img style='width:48px; height:48px; padding-right:7px; border:none; background:none; margin:0' src='http://a2.twimg.com/profile_images/647251084/avatar_default_normal.jpg' /></a></div>
<div style='float:left; padding:0; margin:0'><a style='font-weight:bold' href='http://twitter.com/intent/user?screen_name=archetyped'>@archetyped</a>
<div style='margin:0; padding-top:2px'>Archetyped</div>
</div>
<div style='clear:both'></div>
</div>
</div>
<p><!-- end of tweet --></p>
<p><!-- tweet id : 127086832579133440 --><br />
<style type='text/css'>#bbpBox_127086832579133440 a { text-decoration:none; color:#0b5259; }#bbpBox_127086832579133440 a:hover { text-decoration:underline; }</style>
<div id='bbpBox_127086832579133440' class='bbpBox' style='padding:20px; margin:5px 0; background-color:#282828; background-image:url(http://a1.twimg.com/profile_background_images/68764889/screenshot.png); background-repeat:no-repeat'>
<div style='background:#fff; padding:10px; margin:0; min-height:48px; color:#333333; -moz-border-radius:5px; -webkit-border-radius:5px;'><span style='width:100%; font-size:18px; line-height:22px;'>Strong desire to continue work on my projects from yesterday before starting on my scheduled projects today.</span>
<div class='bbp-actions' style='font-size:12px; width:100%; padding:5px 0; margin:0 0 10px 0; border-bottom:1px solid #e6e6e6;'><img align='middle' src='http://archetyped.com/wp-content/plugins/twitter-blackbird-pie//images/bird.png' /><a title='tweeted on October 20, 2011 8:20 am' href='http://twitter.com/#!/archetyped/status/127086832579133440' target='_blank'>October 20, 2011 8:20 am</a> via <a href="http://seesmic.com/" rel="nofollow" target="blank">Seesmic</a><a href='https://twitter.com/intent/tweet?in_reply_to=127086832579133440&#038;related=archetyped' class='bbp-action bbp-reply-action' title='Reply'><span><em style='margin-left: 1em;'></em><strong>Reply</strong></span></a><a href='https://twitter.com/intent/retweet?tweet_id=127086832579133440&#038;related=archetyped' class='bbp-action bbp-retweet-action' title='Retweet'><span><em style='margin-left: 1em;'></em><strong>Retweet</strong></span></a><a href='https://twitter.com/intent/favorite?tweet_id=127086832579133440&#038;related=archetyped' class='bbp-action bbp-favorite-action' title='Favorite'><span><em style='margin-left: 1em;'></em><strong>Favorite</strong></span></a></div>
<div style='float:left; padding:0; margin:0'><a href='http://twitter.com/intent/user?screen_name=archetyped'><img style='width:48px; height:48px; padding-right:7px; border:none; background:none; margin:0' src='http://a2.twimg.com/profile_images/647251084/avatar_default_normal.jpg' /></a></div>
<div style='float:left; padding:0; margin:0'><a style='font-weight:bold' href='http://twitter.com/intent/user?screen_name=archetyped'>@archetyped</a>
<div style='margin:0; padding-top:2px'>Archetyped</div>
</div>
<div style='clear:both'></div>
</div>
</div>
<p><!-- end of tweet --></p>
<p>However, something unexpected occurred:</p>
<p><!-- tweet id : 126192584040255489 --><br />
<style type='text/css'>#bbpBox_126192584040255489 a { text-decoration:none; color:#0b5259; }#bbpBox_126192584040255489 a:hover { text-decoration:underline; }</style>
<div id='bbpBox_126192584040255489' class='bbpBox' style='padding:20px; margin:5px 0; background-color:#282828; background-image:url(http://a1.twimg.com/profile_background_images/68764889/screenshot.png); background-repeat:no-repeat'>
<div style='background:#fff; padding:10px; margin:0; min-height:48px; color:#333333; -moz-border-radius:5px; -webkit-border-radius:5px;'><span style='width:100%; font-size:18px; line-height:22px;'>At the same time, I know I pushed hard to get a lot done today because I would be focusing on another project tomorrow</span>
<div class='bbp-actions' style='font-size:12px; width:100%; padding:5px 0; margin:0 0 10px 0; border-bottom:1px solid #e6e6e6;'><img align='middle' src='http://archetyped.com/wp-content/plugins/twitter-blackbird-pie//images/bird.png' /><a title='tweeted on October 17, 2011 9:07 pm' href='http://twitter.com/#!/archetyped/status/126192584040255489' target='_blank'>October 17, 2011 9:07 pm</a> via <a href="http://seesmic.com/" rel="nofollow" target="blank">Seesmic</a><a href='https://twitter.com/intent/tweet?in_reply_to=126192584040255489&#038;related=archetyped' class='bbp-action bbp-reply-action' title='Reply'><span><em style='margin-left: 1em;'></em><strong>Reply</strong></span></a><a href='https://twitter.com/intent/retweet?tweet_id=126192584040255489&#038;related=archetyped' class='bbp-action bbp-retweet-action' title='Retweet'><span><em style='margin-left: 1em;'></em><strong>Retweet</strong></span></a><a href='https://twitter.com/intent/favorite?tweet_id=126192584040255489&#038;related=archetyped' class='bbp-action bbp-favorite-action' title='Favorite'><span><em style='margin-left: 1em;'></em><strong>Favorite</strong></span></a></div>
<div style='float:left; padding:0; margin:0'><a href='http://twitter.com/intent/user?screen_name=archetyped'><img style='width:48px; height:48px; padding-right:7px; border:none; background:none; margin:0' src='http://a2.twimg.com/profile_images/647251084/avatar_default_normal.jpg' /></a></div>
<div style='float:left; padding:0; margin:0'><a style='font-weight:bold' href='http://twitter.com/intent/user?screen_name=archetyped'>@archetyped</a>
<div style='margin:0; padding-top:2px'>Archetyped</div>
</div>
<div style='clear:both'></div>
</div>
</div>
<p><!-- end of tweet --></p>
<p>Knowing that I was limited to one day to accomplish something on a project was a great motivator to remain focused on <strong>real results</strong>.  As a result, the past 30 days yielded some of my best work to date.</p>
<p>While momentum is definitely important for continued progress, it is not the only factor.  Placing a limit time (i.e. a deadline) applies a healthy pressure that helps us to prioritize and focus more effectively.  This allows us to use any momentum we&#8217;ve built up to its fullest throughout the day, thus mitigating its loss at the end of the day.</p>
<h4>Two more bonuses from having a daily deadline:</h4>
<ol>
<li><strong>Momentum is less important</strong> &#8212; As I became used to the lack of momentum from starting work on a different project each day, I depended on it less and less.  Momentum is still a valuable tool, but now I have more tools to work with.</li>
<li><strong>Easier to get started</strong> &#8212; Perhaps it&#8217;s simply because I only have a day to get real results on a project, but I found myself diving into my projects much faster at the start of the day.  I spent far less time on email, news, etc. as I was itching to get going each day.</li>
</ol>
<h2>A Fresh Start</h2>
<p>A key factor that offset many of the downsides of having a fixed schedule was that each day of the week would bring something different from the last.  It didn&#8217;t matter if I had worked myself to the bone on yesterday&#8217;s projects, because today offered something completely new.  I was pleasantly surprised to find that I was actually <strong>looking forward to my work</strong> instead of thinking about how I could put it off.</p>
<h2>Accomplishment</h2>
<p>Each day I had two options:</p>
<ol>
<li>Finish something (reach a milestone, release a new version of software, publish an article, etc.)</li>
<li>Leave work unfinished until the next week.</li>
</ol>
<p>The threat of having to wait for an entire week to finish a project was a strong motivator.  Though not always possible, reaching a milestone each day was always the goal and led to some real results:</p>
<ul>
<li>7 major updates of <a href="http://archetyped.com/tools/simple-lightbox/" title="Simple Lightbox">Simple Lightbox</a></li>
<li>Major progress on <a href="http://archetyped.com/tools/cornerstone/" title="Cornerstone">Cornerstone</a></li>
<li>15 new articles published on this site</li>
<li>4 Video projects shot</li>
<li>3 <a title="Videos" href="http://vimeo.com/archetyped/" target="_blank">Video projects published</a> with a 4th 75% completed (Update: completed!)</li>
<li>40+ <a href="http://www.flickr.com/photos/mrorange/" target="_blank">photos published</a></li>
<li>Started work on several new projects</li>
</ul>
<p>However, perhaps more important than the actual accomplishments was the increased<strong><em> sense</em> of accomplishment</strong>.  It is incredibly satisfying to finish something and move on to the next project each day.</p>
<h2>The Downside</h2>
<p>As expected, there were some downsides to having a fixed schedule:</p>
<ul>
<li><strong>No room for &#8220;life&#8221; to happen</strong> &#8212; If something unexpected comes up, a fixed schedule is harder to work around and the day may be lost.  This <em>almost</em> happened, but I was able to shuffle my daily schedule around to accommodate things such as an unexpected trip to the vet.</li>
<li><strong>Less time to decompress</strong> &#8212; To be honest, I didn&#8217;t plan for relaxing (I never do), but the reality is that we<strong> need</strong> to decompress or we risk burning out somewhere down the road.  On the other hand, the real reason I had less time to relax at the end of each day was because I was having too much fun working on my projects.  A bad thing?  Maybe just a little.</li>
<li><strong>No room for &#8220;dead days&#8221;</strong> &#8212; We&#8217;ve all experienced this type of day.  Despite your best intentions, you just never really spring into action.  According to my notes, this occurred <strong>once</strong> during the 30 day experiment.  As a result, the tasks scheduled for that day took an extra week to be completed.</li>
<li><strong>No wiggle room</strong> &#8212; The biggest downside of them all.  No continuing a project the following day.  Work could sit incomplete for an entire week, mocking you.  Then again, if I want to make progress on any of my other projects, this is a necessary evil.</li>
<li><strong>No room for other projects</strong> &#8212; My days are filled.  How will I fit in another project?  I think the answer has to do with <strong>finishing</strong> one of the projects currently in rotation&#8230;</li>
</ul>
<p>Honestly, those are all the downsides that I can think off.  To be frank, none of them significantly detracted from the benefits I experienced during this experiment (see above).</p>
<h2>To Be Continued?</h2>
<p>Yes, definitely; a schedule is here to stay.  A strong <strong>sense of purpose and fulfillment</strong> are the key reasons that I will continue keeping a schedule.</p>
<h2>Tweaks</h2>
<p>I kept the same schedule throughout the entire 30 day experiment, even though I initially planned to tweak things after the first 2 weeks.  I ultimately decided that it was best to let things run their course for the entire 30 days to better evaluate the costs of such a schedule.  Here are some tweaks that I am considering:</p>
<ul>
<li><strong>Implement a biweekly rotation</strong> &#8212; 2 consecutive days per project may allow more to get done.  One potential downside is that by increasing the deadline, I decrease the pressure that helps to improve focus and prioritization.  I&#8217;ll also have to let a project hang in limbo for <strong>two weeks</strong> instead of just one.</li>
<li><strong>Reevaluate project grouping</strong> &#8212; It turns out that the original daily pairings of projects worked out really well and there was very little friction to speak of.  At the same time, I did find that work on some projects claimed the entire day, leaving no time to work on the other project scheduled on the same day.  It is possible that a different distribution of projects throughout the week will ameliorate this.</li>
</ul>
<p>Ultimately, I think I will continue with the original schedule, tweaking it as needed, and evaluating the results.</p>
<h2>Conclusions</h2>
<p>This experiment has made it clear that there are 2 very important factors for experiencing fulfillment and satisfaction in life:</p>
<ol>
<li><strong>Purpose</strong> &#8212; knowing your role and why you&#8217;re doing it is vital to being satisfied.</li>
<li><strong>Results</strong> &#8212; experiencing the fruits of our labor keeps us motivated to keep on trucking.</li>
</ol>
<p><a href="http://archetyped.com/blog/30-days-of-schedules-in-review/"> 30 Days of Schedules: In Review</a> was originally published on <a href="http://archetyped.com">Archetyped</a> on November 22, 2011 05:24pm</p>]]></content:encoded>
			<wfw:commentRss>http://archetyped.com/blog/30-days-of-schedules-in-review/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<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>
		<item>
		<title>Blog &#8250; 30 Days of Decision: In Review</title>
		<link>http://archetyped.com/blog/30-days-of-decision-in-review/</link>
		<comments>http://archetyped.com/blog/30-days-of-decision-in-review/#comments</comments>
		<pubDate>Fri, 30 Sep 2011 20:29:27 +0000</pubDate>
		<dc:creator>Sol</dc:creator>
				<category><![CDATA[Feature]]></category>
		<category><![CDATA[30 Days]]></category>
		<category><![CDATA[Decision]]></category>
		<category><![CDATA[Experiment]]></category>
		<category><![CDATA[Post-mortem]]></category>
		<category><![CDATA[Results]]></category>

		<guid isPermaLink="false">http://archetyped.com/auto-draft/</guid>
		<description><![CDATA[I recently spent 30 days sticking to my decisions.  The results of this experiment were quite interesting, sometimes unexpected, and other times enlightening.]]></description>
			<content:encoded><![CDATA[<p>I recently spent 30 days <a href="http://archetyped.com/blog/30-days-of-decision/" title="30 Days of Decision">sticking to my decisions</a>.  The results of this experiment were quite interesting, sometimes unexpected, and other times enlightening.</p>
<h3>How it began</h3>
<p>For some time, I had been thinking about how <strong>hard</strong> it can be live with a decision in particular because it is so <em>easy</em> to renege on the decisions that we make.  This is especially true in the world of shopping, where stores like Costco with their nearly limitless return policies allow us to shop sans stress thanks to the knowledge that we can always return it if it doesn&#8217;t work/we don&#8217;t like it/find something better/smells funny months&#8211; or even <em>years&#8211;</em> later.</p>
<p>The problem is that this freedom creates a <strong>mindset</strong> that creeps into other areas of our lives.</p>
<p>I didn&#8217;t like the idea that I might be making decisions with the &#8220;assurance&#8221; that I could always go back on them later if the outcome didn&#8217;t strike my fancy.  With that in mind, I thought it might be interesting to see how things would be different if I simply did not have the option to <em>undo</em> a decision.</p>
<p>In other words, I wanted to know what is the worst that could happen?</p>
<h3>Assumptions</h3>
<p>Here were my assumptions regarding living with the decisions that we make:</p>
<ul>
<li>I may spend more money, but it probably won&#8217;t be as bad as I imagine</li>
<li>Things may not go as planned, but that will likely not lead to ruin</li>
<li>Decisions would be <strong>easier</strong> to make since I would have to live with <em>any</em> decision I ultimately made anyway</li>
</ul>
<p>In a strange twist of irony though, I never quite reached the point of <em>deciding</em> to undertake this experiment.</p>
<h3>At the Bike Shop</h3>
<p>Things changed when I was looking for some parts at a bike shop one afternoon.  I was contemplating buying a $9 part that I was <em>pretty sure</em> would fit my needs, but I wasn&#8217;t sure if there would be something better or cheaper somewhere else (likely online).  This was not an expensive purchase, but making the decision to buy the part was proving to be difficult.  It was when I considered asking about the shop&#8217;s return policy that I made my first and best decision of this experiment.  I was so disenchanted by my mindset of buying something only if I could return it, that I decided that I would start the experiment immediately.</p>
<p>I would buy this $9 part <strong>without the ability to return it</strong>.</p>
<p>The feeling of liberation was abrupt and quite uplifting.  No longer having the option to go back on a decision <strong>freed</strong> me from having to think about contingencies should a decision not go as planned.  Now, when I make a decision, I live with the consequences, ever moving forward and adjusting as necessary.</p>
<p>This was going to be awesome.</p>
<p>And that first day was indeed awesome.</p>
<h3>Indecision</h3>
<p>By the second day of this experiment, I realized how much of a problem not being able to return something I purchased could be, especially since I was right in the middle of buying some business equipment.  If a piece of equipment did not work out and I could not return it, then I would have even less funds to get something else.  The result was that I spent a couple late nights pouring over my research so that I would select the right items the first time.  Still, pulling the trigger and actually buying the items was proving to be difficult.</p>
<p>Indecision had arrived.  I was definitely not expecting this.</p>
<p>Interestingly, I found that I was actually more stressed out by this indecision than I was trying to keep track of return policies, etc. prior to this experiment.</p>
<h3>Busting Indecision</h3>
<p>After a couple days of sparring with indecision, I was relieved to have a <em>&#8220;this is stupid&#8221;</em> moment and simply got out of the ring.</p>
<p>I could not simply hold off from making &#8220;big&#8221; decisions for the next 30 days, so my only other option was to start making decisions and living with them.  This was the whole point of the experiment&#8211; to find out how things would be if I made a decision and lived with the consequences.</p>
<p>Issues with indecision were mostly left behind at this point, though some big decisions did take longer than desired to make.</p>
<h3>Productivity</h3>
<p>Deciding what to spend money on wasn&#8217;t the only aspect of daily life that was affected by this experiment.  In fact, one of the most positive results of this experiment was <strong>increased productivity</strong>.</p>
<p>When I <em>decided</em> that I was going to finish a task on a given day, then I would work on that task until I finished it.  Just as I was liberated from thinking about return policies when buying something, I was liberated from the excuses for procrastination when I decided I was going to do something.</p>
<p>Getting stuff done was never so easy.</p>
<h3>Feeding Time</h3>
<p>In my <a href="http://archetyped.com/blog/30-days-of-decision/" title="30 Days of Decision">original post</a> on this 30 day experiment, I noted that one of the challenges would be deciding where to eat.  This may not sound like a big deal for some, but I don&#8217;t eat out often, so when I drop cash for someone else to cook for me, <strong>it better be good</strong>.</p>
<p>Choosing where to eat was thankfully simplified during this experiment.  I stopped thinking, &#8220;what if it&#8217;s not good?&#8221; and just chose a restaurant for a new experience.  Not all experiences are equal, but <em>all</em> new experiences add to the refinement of my tastes.</p>
<p>Food was not always awesome, but I don&#8217;t regret going to any of the restaurants I chose because it helped me to gain a better understanding of what I like and what I don&#8217;t like.  This confirmed my assumption that the world would not end if I made a decision that turned out to be less than ideal.</p>
<h3>Buyer&#8217;s Remorse</h3>
<p>I also expected that I would spend more money without the ability to undo a decision, since I was possible that would spend money on the <strong>wrong</strong> thing before ultimately buying the <strong>right</strong> thing.  During this experiment, this did happen couple times, with interesting results.</p>
<p>The first time, I actually bought the <strong>wrong model</strong> of a piece of equipment I needed.  After the initial shock of my mistake subsided, I found that I didn&#8217;t really feel all that bad about it.  It was my fault and I couldn&#8217;t return it to get the right model, so I would just have to make due with the model I bought.  The difference in models came down to accessories included with each model, which I determined would cost me an additional $50 if I wanted to purchase the accessories included with the other model.  It would have been nice to have those additional accessories, but in the end, I decided to work with what I already had, which has yet to present any major issues.</p>
<p><strong>Cost of learning to proofreading things before ordering:</strong> $50</p>
<p>A good lesson learned at a fair price.</p>
<p>The second time, I bought something that I was completely sold on.  I scoured reviews and gathered as much information as I could to make sure this was &#8220;the one,&#8221; so I was fairly confident that I was making a good decision.</p>
<p>Obviously, I this is the perfect setup for a letdown.</p>
<p>And let down I was.  The variance between what I had hoped for and what I received was incredible.  I was disillusioned to say the least.  Worse yet, I was only days away from completing this experiment and had I waited, I could have returned the item without any delay.</p>
<p>However, I chose to buy this item <em>during</em> my experiment for two reasons:</p>
<ol>
<li>I had no major disasters as of yet during this experiment and this was a decision fraught with unknowns</li>
<li>I wanted the item and did not want to wait</li>
</ol>
<p>Buying this item provided me with a good learning experience and helped to answer the question, &#8220;what&#8217;s the worst that could happen?&#8221;  In this case, the worst consequence was that I was very dissatisfied with my purchase and would have loved to return it and get my money back.</p>
<p>The most significant lesson though had to do with <strong>patience</strong>.  I could have waited until after the experiment was over but didn&#8217;t want to because I <em>knew</em> the item would be awesome.  It wasn&#8217;t awesome, and this decision was a good reminder of how sometimes taking a breather to get a clearer perspective on things <em>before</em> making a decision can be a good thing.</p>
<p><strong>The cost of this item?</strong> $60.</p>
<p>It&#8217;s not a huge amount, but the cognitive dissonance (aka <em>buyer&#8217;s remorse</em>) from this purchase was immense.  I didn&#8217;t really have a problem with <em>how</em> much I spent, but rather on <em>what</em> the money spent on&#8211; a bad decision.</p>
<p>I still would love to return this item, but I am keeping it mostly because it keeps the lessons learned at the forefront of my mind.</p>
<h3>Closing Thoughts</h3>
<p>All in all, this experiment was a great experience.</p>
<p>I gained a more balanced perspective on the importance of the decisions that I make (they usually are neither life threatening nor inconsequential).</p>
<p>Perhaps the greatest result of this experiment is that the <strong>mindset</strong> of making a decision with an &#8220;escape plan&#8221; has been greatly diminished.  It is very important to experience the <strong>consequences of a decision</strong> (whether positive or negative), as they teach invaluable lessons that will help you make better decisions in the future.</p>
<p><a href="http://archetyped.com/blog/30-days-of-decision-in-review/"> 30 Days of Decision: In Review</a> was originally published on <a href="http://archetyped.com">Archetyped</a> on September 30, 2011 10:29am</p>]]></content:encoded>
			<wfw:commentRss>http://archetyped.com/blog/30-days-of-decision-in-review/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Blog &#8250; 30 Days of Decision</title>
		<link>http://archetyped.com/blog/30-days-of-decision/</link>
		<comments>http://archetyped.com/blog/30-days-of-decision/#comments</comments>
		<pubDate>Sun, 07 Aug 2011 09:00:25 +0000</pubDate>
		<dc:creator>Sol</dc:creator>
				<category><![CDATA[Feature]]></category>
		<category><![CDATA[30 Days]]></category>
		<category><![CDATA[Decision]]></category>
		<category><![CDATA[Experiment]]></category>

		<guid isPermaLink="false">http://archetyped.com/auto-draft/</guid>
		<description><![CDATA[We live in a world with an abundance of choice.  However, as the options available to us increase, so does the complexity in making a decision.]]></description>
			<content:encoded><![CDATA[<p>We live in a world with an abundance of choice.  However, as the options available to us increase, so does the complexity in making a decision.</p>
<p>The worst byproduct of such freedom to choose is the freedom to <strong>backtrack on a decision</strong>.</p>
<p>Don&#8217;t like something you bought?  Not to worry, there&#8217;s a 30 day return policy.</p>
<p>Unsure whether you&#8217;re getting the best option for your needs?  Turn around and take your pick from 5 other options.</p>
<p>Bleu Cheese or Thousand Island with your salad?  Bleu Cheese&#8230;no Thousand Island&#8230;no&#8230;.can you come back to me?</p>
<p>Hemming and hawing over the myriad of choices can easily lead to indecision.  That is why <strong>I&#8217;ve decided to spend the next 30 days sticking to every decision I make</strong>.</p>
<h2>The Rules</h2>
<p>As usual, I like to keep things simple, so there is really just one rule&#8211; <strong>if I decide something, I have to live with it</strong>.</p>
<p>If I buy something I don&#8217;t like, I won&#8217;t return it.</p>
<p>If I decide to do something, I must do it.</p>
<h2>Why?</h2>
<p>Primarily, I&#8217;m interested in the ramifications of having to live with the trivial decisions that we make every day even if we don&#8217;t make the &#8220;right&#8221; one.  It&#8217;s generally so easy to change our mind when we realize moments after making a decision (i.e. which DVD to rent) that we may not even notice when we backtrack on our initial decisions.  I&#8217;m curious what sort of effects making the wrong decision, but making the best of it, will have.  I like the idea that every little decision is like a fork in the road that will take us down one path or another.  By resolving to stick to my original decision despite my misgivings, I will be taking the a completely different set of forks in the road.</p>
<h2>30 Days</h2>
<p>Just to be clear, the idea is not to hold off on switching up my decisions for just 30 days.  Any decision I make during this experiment cannot be overturned, even after the 30 days has elapsed.  The 30 day time frame is meant to provide enough of a sample to evaluate the effectiveness (or lack thereof) of this experiment.  If it proves to be fruitful, I will more than likely continue the practice.  If not, I&#8217;ll have only spent 30 days on it.</p>
<h2>Challenges</h2>
<p>Here are some challenges I know I&#8217;m in for:</p>
<ul>
<li><strong>Choosing where to eat</strong>.  We don&#8217;t eat out very often and I want the experience to be worth my time and money.</li>
<li><strong>Deciding to buy something</strong>.  I don&#8217;t like spending money, so when I do, I like to make sure I&#8217;m getting the best bang for my buck.</li>
<li><strong>Deciding <em>which</em> thing to buy</strong>.  Similar to the previous one, but now that I&#8217;ve decided to spend money, I want to make sure I&#8217;m spending it on the right option.</li>
</ul>
<div class="highlight">
<p><strong>Update:</strong> Read <a href="http://archetyped.com/blog/30-days-of-decision-in-review/" title="30 Days of Decision: In Review">my evaluation of this experiment</a>.</p>
</div>
<p><a href="http://archetyped.com/blog/30-days-of-decision/"> 30 Days of Decision</a> was originally published on <a href="http://archetyped.com">Archetyped</a> on August 6, 2011 11:00pm</p>]]></content:encoded>
			<wfw:commentRss>http://archetyped.com/blog/30-days-of-decision/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

