<?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">Dissolving the Redesign</title>
    <base href="https://doriantaylor.com/dissolving-the-redesign"/>
    <link href="document-stats#Ek7bUakcwtda-SGR5xDfoI" 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="Dissolving the Redesign"/>
    <link href="lexicon/#E-ZY5i7K1cqzfT0p1L9ajJ" rel="dct:audience" title="Digital Media Practitioner"/>
    <link href="person/dorian-taylor#me" rel="dct:creator" title="Dorian Taylor"/>
    <link href="file/reverse-proxy" rel="dct:hasPart"/>
    <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="dissolving-the-redesign" datatype="xsd:token" property="ci:canonical-slug"/>
    <meta content="The redesign, as a concept, is neither necessary nor desirable when applied to working with the Web. I would also like to make it the technically, organizationally and financially inferior decision." name="description" property="dct:abstract"/>
    <meta content="2012-08-01T16:22:51+00:00" datatype="xsd:dateTime" property="dct:created"/>
    <meta content="dissolving-the-redesign" property="dct:identifier"/>
    <meta content="2012-08-01T16:23:46+00:00" datatype="xsd:dateTime" property="dct:issued"/>
    <meta content="2012-08-06T03:39:41+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2019-03-11T08:14:10+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_large_image" name="twitter:card"/>
    <meta content="@doriantaylor" name="twitter:site"/>
    <meta content="Dissolving the Redesign" name="twitter:title"/>
    <meta content="The redesign, as a concept, is neither necessary nor desirable when applied to working with the Web. I would also like to make it the technically, organizationally and financially inferior decision." name="twitter:description"/>
    <meta content="https://doriantaylor.com/file/reverse-proxy;scale=500,300" name="twitter:image"/>
    <object>
      <nav>
        <ul>
          <li>
            <a href="interview-with-lara-fedoroff-for-ux-radio" rev="dct:references" typeof="bibo:Article">
              <span property="dct:title">Interview With Lara Fedoroff for UX Radio</span>
            </a>
          </li>
          <li>
            <a href="the-redesign-dissolved" rev="dct:references" typeof="bibo:Article">
              <span property="dct:title">The Redesign, Dissolved</span>
            </a>
          </li>
          <li>
            <a href="website-change-diary" rev="dct:references" typeof="bibo:Article">
              <span property="dct:title">Website Change Diary</span>
            </a>
          </li>
          <li>
            <a href="document-stats#Ek7bUakcwtda-SGR5xDfoI" rev="ci:document" typeof="qb:Observation">
              <span>urn:uuid:93b6d46a-4730-4b5d-86be-486479c437e8</span>
            </a>
          </li>
        </ul>
      </nav>
    </object>
  </head>
  <body about="" id="EorQ1S5LIio7Y0rleQW9dK" typeof="bibo:Article">
    <p>I have this conjecture that the easier it is to dress a new medium up like the media that came before it, the longer it stays that way. The <abbr title="World-Wide Web">Web</abbr> has been around for two decades now, so judging by <a href="http://en.wikipedia.org/wiki/History_of_the_automobile#Veteran_era" title="History of the automobile (Veteran era) &#x2014; Wikipedia" rel="dct:references">important innovations</a> <a href="http://en.wikipedia.org/wiki/History_of_film#The_silent_era" title="History of film (The silent era) &#x2014; Wikipedia" rel="dct:references">in the past</a>, the <abbr title="World-Wide Web">Web</abbr> is due to come into its own. I believe we should help it along.</p>
    <p>I'm <em>not</em> talking about responsive design (which, by the way, while being all the rage these days, <a href="http://tools.ietf.org/html/rfc2295" rel="dct:references">was conceived in the 90s</a>). The idea I wish to challenge is that of the <em>redesign</em>.</p>
    <p>To <em>re</em>-anything is to throw something out and start again, which for the <abbr title="World-Wide Web">Web</abbr> is as easy as nuking your <a href="http://httpd.apache.org/docs/current/mod/core.html#documentroot" title="core - Apache HTTP Server (DocumentRoot Directive)" rel="dct:references">document root</a> and copying something into its place. But whenever we do that, it's like a big up-yours to every user and every site in the neighbourhood, because we upset the positions of things and sever connections which are valuable to both them <em>and</em> us.</p>
    <p>But network diplomacy aside, the idea of the <em>redesign</em> has implications for both fulfillment <em>and</em> financial risk, which all major <abbr title="World-Wide Web">Web</abbr> properties mitigate by chopping their products up into increments <em>which they can deploy and get feedback on immediately</em>. My question is: <em>why do people work any other way</em>?</p>
    <figure>
     <img style="display: block; margin: auto" src="file/reverse-proxy;scale=500,300" alt="" rel="foaf:depiction"/>
    </figure>
    <p>So I'm inventing a process, which is <a href="http://contentsmagazine.com/articles/no-longer-no-sense-of-an-ending/" title="No Longer No Sense of an Ending | Contents Magazine" rel="dct:references">part of a larger process</a> for managing the lifecycle of <abbr title="World-Wide Web">Web</abbr> resources. I'm redesigning the redesign, to not have to <em>be</em> a redesign. And I'm touching on the organizational and financial aspects as well.</p>
    <aside role="note" id="EPXHqHNa8C3ebuodXEFsuL">
      <p>I've been notified that mister Rosenfeld <a href="http://louisrosenfeld.com/home/bloug_archive/2008/04/the_redesign_must_die_talk.html" title="" rel="dct:references">has already considered</a> this topic <a href="http://www.louisrosenfeld.com/home/bloug_archive/2011/04/the_new_redesign_must_die_talk.html" title="" rel="dct:references">more than once</a>. Great minds think alike! And what I'm interested in doing is assembling a toolkit to make the process the easiest and most obvious thing to do.</p>
    </aside>
    <p>This is a learning process, which I am piloting with the <a href="http://iainstitute.org/" title="The Information Architecture Institute" rel="dct:references"><acronym title="Information architecture">IA</acronym> Institute</a> and some choice clients. I would also eventually like to partner with some web shops to refine it. My goal is to codify this process so we can all start working this way.</p>
    <p>All the pieces have been lying around since the beginning, I suppose it just takes somebody to put them together.</p>
  </body>
</html>
