<?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">An Early Iteration on Iteration</title>
    <base href="https://doriantaylor.com/an-early-iteration-on-iteration"/>
    <link href="document-stats#ENawzl20eNXcqGCV8pFUcJ" 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="An Early Iteration on Iteration"/>
    <link href="lexicon/#EzqXIsriaILFcWjXdS7FbI" rel="dct:audience" title="Software Developer"/>
    <link href="person/dorian-taylor#me" rel="dct:creator" title="Dorian Taylor"/>
    <link href="//www.amazon.com/dp/0123740371" rel="dct:references"/>
    <link href="//www.amazon.com/dp/0789305259" rel="dct:references"/>
    <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="an-early-iteration-on-iteration" datatype="xsd:token" property="ci:canonical-slug"/>
    <meta content="With the advent of Agile process models and the increasing influence of user experience design, iterative development promises value early on &#x2014; but does it deliver?" name="description" property="dct:abstract"/>
    <meta content="2009-12-14T03:36:25+00:00" datatype="xsd:dateTime" property="dct:created"/>
    <meta content="an-early-iteration-on-iteration" property="dct:identifier"/>
    <meta content="2009-12-14T03:37:01+00:00" datatype="xsd:dateTime" property="dct:issued"/>
    <meta content="2009-12-14T03:39:00+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2009-12-14T03:41:41+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2009-12-14T06:07:40+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2022-05-31T04:18:52+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="An Early Iteration on Iteration" name="twitter:title"/>
    <meta content="With the advent of Agile process models and the increasing influence of user experience design, iterative development promises value early on &#x2014; but does it deliver?" name="twitter:description"/>
    <object>
      <nav>
        <ul>
          <li>
            <a href="document-stats#ENawzl20eNXcqGCV8pFUcJ" rev="ci:document" typeof="qb:Observation">
              <span>urn:uuid:35ac3397-6d1e-4357-972a-18257ca4551c</span>
            </a>
          </li>
        </ul>
      </nav>
    </object>
  </head>
  <body about="" id="ER0I8PPVAt1pycsa_OrAyK" typeof="bibo:Article">
    <p>Iteration is an essential approach to the development of any technique, not just software. It's just that <em>code</em>, no matter how <a href="http://en.wikipedia.org/wiki/High-level_programming_language" title="High-level programming language &#x2014; Wikipedia" rel="dct:references">high-level the language</a> or <a href="http://en.wikipedia.org/wiki/Code_refactoring" title="Code refactoring &#x2014; Wikipedia" rel="dct:references">kitted-out the infrastructure</a>, is about the <em>slowest</em> medium to iterate with. This isn't to say that it is never appropriate to iterate code, just that we can get a lot of mileage out of instruments <a href="http://www.amazon.com/gp/product/0123740371?ie=UTF8&amp;tag=doriantaylor-20&amp;linkCode=as2&amp;camp=1789&amp;creative=9325&amp;creativeASIN=0123740371" title="Amazon.com: Sketching User Experiences: Getting the Design Right and the Right Design (Interactive Technologies) (9780123740373): Bill Buxton: Books">as simple as a pencil and paper</a>, or a whiteboard and some frank discussion.</p>
    <p>A good indicator of whether or not to use a computer to iterate &#x2014; or if so, in what capacity &#x2014; is the <em>volume</em> of information relative to the rigidity of its <em>shape</em>. Computers perform well over large sets of relatively homogenous data, but the performance gains break down when we need to <a href="stop-guessing-and-get-the-data" title="Stop Guessing and Get the Data" rel="dct:references">get heterogeneous data all the same shape</a>, or worse, we don't know what shape they should become. Low-cost, low-tech methods enable us to experiment profligately with different shapes, but break down when we add volume. Computers are also useful when we already have many pieces of information and need to experiment moving them around relative to one another. That said, it is a mistake to underestimate the utility of a photocopier, some scissors and some tape.</p>
    <p>It's worth noting that this relationship <a href="http://en.wikipedia.org/wiki/Periodicity" title="Periodicity &#x2014; Wikipedia" rel="dct:references">can be periodic</a> too. We can take interim results from a computer into a low-tech world just as easily as we can use them to crisply refine the chaos of yesteryear's communication techniques. For example, most of us can type much faster than we can write by hand, and the results tend to look better. It may make sense, for instance, to assemble <a href="http://en.wikipedia.org/wiki/Microcontent" title="Microcontent &#x2014; Wikipedia" rel="dct:references">microcopy</a> established in a previous sketching iteration into a document, print it out and glue it to further sketches. Potentially more effective would be to simply number the text in the document and put those numbers next to some horizontal squiggles in the sketches.</p>
    <p>Conversely, there is little wisdom in designing for aggregated content such as a control surface for a corporate database, or even presentation graphics, without in the <em>very least</em> some kind of feel for the shape of the data. Many an ostensibly good design has been botched when <a href="http://en.wikipedia.org/wiki/Lorem_ipsum" title="Lorem ipsum &#x2014; Wikipedia" rel="dct:references">lorem ipsum</a> was supplanted for real content.</p>
    <p>As the <a href="http://www.maedastudio.com/index.php" title="MAEDASTUDIO" rel="dct:references">preeminent digital artist</a> <a href="http://www.amazon.com/gp/product/0789305259?ie=UTF8&amp;tag=doriantaylor-20&amp;linkCode=as2&amp;camp=1789&amp;creative=9325&amp;creativeASIN=0789305259" title="Amazon.com: Maeda @ Media (9780789305251): John Maeda: Books">Dr. John Maeda wrote</a>, <q>[t]ap the power of the design machine. Its metamechanical hands do not tire.</q> Just ask yourself first if untiring metamechanical hands are really what you need at your current stage of development.</p>
  </body>
</html>
