<?xml version="1.0"?>
<?xml-stylesheet href="/transform" type="text/xsl"?>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:bibo="http://purl.org/ontology/bibo/" xmlns:bs="http://purl.org/ontology/bibo/status/" xmlns:ci="https://vocab.methodandstructure.com/content-inventory#" xmlns:dct="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:xhv="http://www.w3.org/1999/xhtml/vocab#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" lang="en" prefix="bibo: http://purl.org/ontology/bibo/ bs: http://purl.org/ontology/bibo/status/ ci: https://vocab.methodandstructure.com/content-inventory# dct: http://purl.org/dc/terms/ foaf: http://xmlns.com/foaf/0.1/ rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# xhv: http://www.w3.org/1999/xhtml/vocab# xsd: http://www.w3.org/2001/XMLSchema#" vocab="http://www.w3.org/1999/xhtml/vocab#" xml:lang="en">
  <head>
    <title property="dct:title">Considering the Spherical Cow</title>
    <base href="https://doriantaylor.com/considering-the-spherical-cow"/>
    <link href="document-stats#EZN41riL3fCo0XlzxOX22J" rev="ci:document"/>
    <link href="elsewhere" rel="alternate bookmark" title="Elsewhere"/>
    <link href="this-site" rel="alternate index" title="This Site"/>
    <link href="http://purl.org/ontology/bibo/status/published" rel="bibo:status"/>
    <link href="" rel="ci:canonical" title="Considering the Spherical Cow"/>
    <link href="lexicon/#E-ZY5i7K1cqzfT0p1L9ajJ" rel="dct:audience" title="Digital Media Practitioner"/>
    <link href="lexicon/#Er25AsP7lDnL8trRRAsODJ" rel="dct:audience" title="Digital Media Theorist"/>
    <link href="person/dorian-taylor#me" rel="dct:creator" title="Dorian Taylor"/>
    <link href="cost-value-perfection" rel="dct:hasPart"/>
    <link href="lexicon/#EbO7wOpvNV_oh7vlgWcszL" rel="dct:subject" title="Project Management"/>
    <link href="person/dorian-taylor" rel="meta" title="Who I Am"/>
    <link about="./" href="3f36c30c-6096-454a-8a22-c062100ae41f" rel="alternate" type="application/atom+xml"/>
    <link about="./" href="f07f5044-01bc-472d-9079-9b07771b731c" rel="alternate" type="application/atom+xml"/>
    <link about="./" href="this-site" rel="alternate"/>
    <link about="./" href="elsewhere" rel="alternate"/>
    <link about="./" href="e341ca62-0387-4cea-b69a-cdabc7656871" rel="alternate" type="application/atom+xml"/>
    <link about="verso/" href="3f36c30c-6096-454a-8a22-c062100ae41f" rel="alternate" type="application/atom+xml"/>
    <link about="verso/" href="this-site" rel="alternate"/>
    <link about="verso/" href="elsewhere" rel="alternate"/>
    <meta content="considering-the-spherical-cow" datatype="xsd:token" property="ci:canonical-slug"/>
    <meta content="I unabashedly believe perfectionism has a time and place, and in this article I attempt to reconcile it with reality." name="description" property="dct:abstract"/>
    <meta content="2009-09-26T06:14:03+00:00" datatype="xsd:dateTime" property="dct:created"/>
    <meta content="considering-the-spherical-cow" property="dct:identifier"/>
    <meta content="2009-09-27T01:34:57+00:00" datatype="xsd:dateTime" property="dct:issued"/>
    <meta content="2009-09-27T00:22:51+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2009-09-27T01:45:30+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2009-10-01T19:42:39+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2022-05-31T04:18:52+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2022-05-31T15:10:50+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta about="person/dorian-taylor#me" content="Dorian Taylor" name="author" property="foaf:name"/>
    <meta content="summary" name="twitter:card"/>
    <meta content="@doriantaylor" name="twitter:site"/>
    <meta content="Considering the Spherical Cow" name="twitter:title"/>
    <meta content="I unabashedly believe perfectionism has a time and place, and in this article I attempt to reconcile it with reality." name="twitter:description"/>
    <object>
      <nav>
        <ul>
          <li>
            <a href="document-stats#EZN41riL3fCo0XlzxOX22J" rev="ci:document" typeof="qb:Observation">
              <span>urn:uuid:64de35ae-22f7-47c2-9a34-5e5cf1397db6</span>
            </a>
          </li>
        </ul>
      </nav>
    </object>
  </head>
  <body about="" id="E4aOaczbYsPROMSOCeUmeJ" typeof="bibo:Article">
    <section id="EzqPQkMOeqdw_Ya2Fxo3FK">
      <p>I have been accused of perfectionism numerous times throughout my career. I also routinely find the matter to be the unfortunate subject of a number of extremely <span class="parenthesis" title="A significant number of these arguments have cost more than the effort the plaintiff was trying to save.">boring and costly arguments</span>. The truth is that I am doing something slightly different: I have found it monumentally advantageous in the early stages of my projects to <a href="http://en.wikipedia.org/wiki/Spherical_cow" title="Spherical cow &#x2014; Wikipedia" rel="dct:references">consider a spherical cow</a> and then incrementally converge this consideration with reality as I discover the nuances of my charge.</p>
      <p>We can say that in any design problem, there is an ensemble of a <a href="lexicon/context" title="Context" rel="dct:references">context</a> &#x2014; that which exists already and that we do not alter, and a <a href="lexicon/form" title="Form" rel="dct:references">form</a> &#x2014; that which we seek and work to acquire. We can say that the two <em>fit</em> one another and that the <a href="sketching-a-definition-of-design" title="Sketching a Definition of Design" rel="dct:references">purpose of design</a> is to produce this fit.</p>
      <p>It is entirely reasonable to suggest that there can exist <em>the idea</em> of a form that perfectly complements a given context, albeit with the following understanding:</p>
      <ol>
        <li>The context is dynamic, and therefore the form is a moving target.</li>
        <li>As is the case with dynamic systems, the effort required to approach a perfect fit <a href="http://en.wikipedia.org/wiki/Asymptote" title="Asymptote &#x2014; Wikipedia" rel="dct:references">increases exponentially</a> the closer I get to it.</li>
        <li>It is therefore not reasonable to expect to <em>produce</em> a perfect form, I can only <em>approach</em> it.</li>
        <li>Because I would need an infinite amount of information about the context to define a perfectly-fitting form.</li>
      </ol>
      <p>So why <em>consider</em> it if I can never completely <em>achieve</em> it?</p>
    </section>
    <section id="Ew4auH9a4qsqo8MiZxPr0L">
      <aside role="note" id="E5vkACIxp8K2u-6AAhXNdL">
        <section id="EaIIQq37Mpew-DiQiJj4aL"><img class="figure" style="width: 60ex; height: 50ex;" src="cost-value-perfection;scale=600,500" alt="Sketch of a graph depicting curves of design cost, value and proximity to &quot;perfection&quot;."/>
        <p>The <em>cost of design</em> grows as a function of the design team's effort over time, making it linear. The value of the designer's work to the client behaves like an S-curve, spending a period <em>below</em> the cost of design before converging and overtaking it, and eventually decaying into <a href="http://en.wikipedia.org/wiki/Diminishing_returns" title="Diminishing returns &#x2014; Wikipedia" rel="dct:references">diminishing returns</a>. As the design team works, it accrues more information about the context, bringing the form asymptotically closer to a <em>perfect fit</em>.</p>
        </section>
      </aside>
      <p>In my experience, it doesn't cost any more to <em>imagine</em> a perfect fit between form and context than it does to consider one that is <em>good enough</em>. In fact, I find it <em>harder</em> to aim for <em>good enough</em>, because I find myself spending extra effort figuring out what constitutes <em>merely satisfactory</em> performance instead of choosing what I am confident is best.</p>
      <p>And a funny thing happens on the way to production: <em>good enough</em> becomes the new <em>perfect</em> &#x2014; I can't <em>achieve</em> it, just <em>approach</em> it. Given that, if I aim for a perfect fit I ought to get <em>at least</em> good enough. If I aim for good enough, who knows what I'll get. Consider Michelangelo:</p>
      <blockquote style="font-weight: bolder" id="EqWp6nMaTEKCwDKdGcZQ4I">
        <p>The greater danger for most of us lies not in setting our aim too high and falling short; but in setting our aim too low, and achieving our mark.</p>
      </blockquote>
      <p>I think it is entirely safe to say that out there somewhere there is a perfect form for our context, and that we must learn about the context in order to synthesize a fitting form. It is extremely likely that the context will shift naturally, or our perspective will change with new information, and we will have to adjust our vision of the <em>perfectly-fitting form</em> accordingly. When we commit to production, our vision of an ideal form will enable us to stay open to future directions, instead of committing forever to suboptimal solutions.</p>
    </section>
    <aside role="note" id="ExKXxHddDshfB9d6IOx3eJ">
      <p>I anticipate at least three issues with this assertion. The first is undoubtedly a malaise among pragmatists and holders of pocketbooks of <em>carte blanche</em> spending of their precious resources. The others are around when to commit to production, and how to exercise the value of the designed form incrementally. I believe these subjects each deserve their own treatment, to be delivered in due time.</p>
    </aside>
  </body>
</html>
