<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Aaron Gerdes: Tag process</title>
    <link>http://www.aarongerdes.com/articles/tag/process</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Strategy, design, and technology to stand out and win business.</description>
    <item>
      <title>Uncomfortable creative process: Should we hide behind formality?</title>
      <description>&lt;p&gt;Prolific designer Michael Bierut blogs honestly &lt;a href="http://www.designobserver.com/archives/017485.html"&gt;about a common unease among designers&lt;/a&gt;:&lt;/p&gt;


	&lt;blockquote&gt;
		&lt;p&gt;The iterative process, the role of improvisation, the adjustments that are made in response to audience feedback, all of these elements are a part of any design process. And, in a way, they&amp;#8217;ve always been the ones that have vaguely unnerving to me.&lt;/p&gt;
	&lt;/blockquote&gt;


	&lt;p&gt;I&amp;#8217;ve mentioned some fear wrapped up in my own process in an &lt;a href="http://www.aarongerdes.com/articles/2006/04/25/create-more-results-from-less-energy-fine-tuning-your-ratio-of-process-to-results"&gt;earlier post&lt;/a&gt;.&lt;/p&gt;


	&lt;p&gt;Firms tend to market processes as a proof that we&amp;#8217;ll be able to replicate past victories &amp;#8212; to show prospects our success hasn&amp;#8217;t only been through luck. Yet sometimes we break process. I&amp;#8217;ve done it over constraints, at the client&amp;#8217;s request, and because sometimes the first concept out of the gate is the right one (and all the stakeholders agree). If you&amp;#8217;re too rigid in those situations, you interfere with natural momentum.&lt;/p&gt;


	&lt;p&gt;This is why I&amp;#8217;m an advocate of less formality and less bulk in a process.&lt;/p&gt;</description>
      <pubDate>Sun, 10 Sep 2006 20:12:00 -0700</pubDate>
      <guid isPermaLink="false">urn:uuid:f9a123d3-ae6e-4dd0-8d80-c2d419bcf2c6</guid>
      <author>aarongerdes@gmail.com (Aaron Gerdes)</author>
      <link>http://www.aarongerdes.com/articles/2006/09/10/uncomfortable-creative-process-should-we-hide-behind-formality</link>
      <category>design</category>
      <category>process</category>
      <category>simplicity</category>
      <trackback:ping>http://www.aarongerdes.com/articles/trackback/87</trackback:ping>
    </item>
    <item>
      <title>Design Process, Reality Check</title>
      <description>&lt;p&gt;Brian Sooy &lt;a href="http://bscodesignmatters.blogspot.com/2006/05/skeet-shooting-in-dark.html"&gt;has a great quote&lt;/a&gt;, via &lt;a href="http://blog.guykawasaki.com/2006/05/another_font_st.html"&gt;Guy Kawasaki&lt;/a&gt;:&lt;/p&gt;


	&lt;blockquote&gt;
		&lt;p&gt;Design consists of creating things for clients who may not know what they want, until they see what you&amp;#8217;ve done, then they know exactly what they want, but it&amp;#8217;s not what you did.&lt;/p&gt;
	&lt;/blockquote&gt;


	&lt;p&gt;The quote made me laugh, most designers have issued this complaint at one point. I&amp;#8217;ll supplement this with my own statement about good design:&lt;/p&gt;


	&lt;blockquote&gt;
		&lt;p&gt;A good designer is one who accepts and integrates this reality into their process to produce a better result with less friction.&lt;/p&gt;
	&lt;/blockquote&gt;


	&lt;p&gt;A designer can be many of things. I don&amp;#8217;t claim to have a monopoly on what it is. The above isn&amp;#8217;t an exhaustive definition, but the good ones definitely have this in common.&lt;/p&gt;</description>
      <pubDate>Mon, 05 Jun 2006 11:02:00 -0700</pubDate>
      <guid isPermaLink="false">urn:uuid:958ac886-7ce8-4545-b15a-b3ae11e4b5eb</guid>
      <author>aarongerdes@gmail.com (Aaron Gerdes)</author>
      <link>http://www.aarongerdes.com/articles/2006/06/05/design-process-reality-check</link>
      <category>design</category>
      <category>process</category>
      <trackback:ping>http://www.aarongerdes.com/articles/trackback/55</trackback:ping>
    </item>
    <item>
      <title>Create more results from less energy: fine tuning your ratio of process to results.</title>
      <description>&lt;p&gt;When you hone a knife, you&amp;#8217;re sharpening it by inflicting friction on the dull edges.&lt;/p&gt;


	&lt;p&gt;I&amp;#8217;ve been honing my process for delivering branding and marketing work for almost ten years. It&amp;#8217;s never been as complex as the first day I used it. The process has been honed into a smarter, simpler tool.&lt;/p&gt;


	&lt;p&gt;When we&amp;#8217;re operating from a fearful mindset, we often judge something&amp;#8217;s effectiveness by its &amp;#8220;weight&amp;#8221;. While in this mindset, effectiveness is confused with our ability to safely hide behind it.&lt;/p&gt;


	&lt;p&gt;I realize now that when I struck out to develop my own business, the process was something I wanted to hide behind. In &lt;a href="http://www.amazon.com/E-Myth-Businesses-Work-What-About/dp/0887300405/sr=8-5/qid=1160784260/ref=pd_bbs_5/002-6936559-6840009?ie=UTF8"&gt;Michael Gerber&amp;#8217;s excellent book The E-Myth&lt;/a&gt;, Gerber urges entrepreneurs to create processes. I warped that concept to develop of my process into something formal enough to offset the risk of working with a new company. In reality, I was placing formalities in between myself and the successful track record I wanted to establish.&lt;/p&gt;


	&lt;p&gt;Writers understand this. If you can&amp;#8217;t write a good book, you can at least write a long one. But they have editors. Unfortunately, many of our business processes will forever be a first draft: too many words, a lack of focus, and after some time even the authors have difficulty understanding the meaning.&lt;/p&gt;


	&lt;p&gt;Massive functional specs fall prey to change and misunderstandings. I&amp;#8217;ve found since I began my business that my process has evolved from trying to understand &lt;em&gt;everything&lt;/em&gt; before beginning work to having a general idea and iterating solutions. This delivers better results because:&lt;/p&gt;


	&lt;ol&gt;
	&lt;li&gt;It&amp;#8217;s more collaborative.&lt;/li&gt;
		&lt;li&gt;It forces you to overcome a fear of criticism.&lt;/li&gt;
		&lt;li&gt;People are better at defining things by what they&amp;#8217;re not than by answering questions about what they are.&lt;/li&gt;
	&lt;/ol&gt;


	&lt;p&gt;There are two added benefits. The first is flexibility. Instead of trying to impose my systematic theory of design on a 2 week project, I can keep sane and work within parameters. The second is happiness. I&amp;#8217;m assuming you&amp;#8217;re happier being authentic. As you cut away formality, you find what falls on the floor doesn&amp;#8217;t justify the time is sucks from doing what you&amp;#8217;re good at.&lt;/p&gt;</description>
      <pubDate>Tue, 25 Apr 2006 22:23:00 -0700</pubDate>
      <guid isPermaLink="false">urn:uuid:7dd1a055-5101-4115-86b8-ce45b13f300f</guid>
      <author>aarongerdes@gmail.com (Aaron Gerdes)</author>
      <link>http://www.aarongerdes.com/articles/2006/04/25/create-more-results-from-less-energy-fine-tuning-your-ratio-of-process-to-results</link>
      <category>simplicity</category>
      <category>process</category>
      <category>planning</category>
      <category>fear</category>
      <trackback:ping>http://www.aarongerdes.com/articles/trackback/82</trackback:ping>
    </item>
  </channel>
</rss>
