<?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">Where is the User in this Picture?</title>
    <base href="https://doriantaylor.com/where-is-the-user-in-this-picture"/>
    <link href="document-stats#EjCyEzkAYw9AIiKmiECZJI" 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="Where is the User in this Picture?"/>
    <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="designer-role" rel="dct:hasPart"/>
    <link href="ecosystem-of-software-production" 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="where-is-the-user-in-this-picture" datatype="xsd:token" property="ci:canonical-slug"/>
    <meta content="Interaction designers, information architects and other user experience professionals may wonder why I omitted the user from this doodle." name="description" property="dct:abstract"/>
    <meta content="2009-03-20T18:36:37+00:00" datatype="xsd:dateTime" property="dct:created"/>
    <meta content="where-is-the-user-in-this-picture" property="dct:identifier"/>
    <meta content="2009-03-20T19:03:18+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2009-03-22T07:45:50+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="Where is the User in this Picture?" name="twitter:title"/>
    <meta content="Interaction designers, information architects and other user experience professionals may wonder why I omitted the user from this doodle." name="twitter:description"/>
    <object>
      <nav>
        <ul>
          <li>
            <a href="document-stats#EjCyEzkAYw9AIiKmiECZJI" rev="ci:document" typeof="qb:Observation">
              <span>urn:uuid:8c2c84ce-4018-4c3d-8008-88a9a2102649</span>
            </a>
          </li>
        </ul>
      </nav>
    </object>
  </head>
  <body about="" id="EaK7zSsobSQCe8N0xytyOL" typeof="bibo:Article">
    <p>Some user experience professionals have asked me in the past why there is no <em>user</em> in this diagram:</p>
    <img class="figure" style="width: 60ex; height: 40ex;" src="designer-role;desaturate;scale=600,400" alt="Sketch depicting the role of a designer as an intermediary between business and technical interests." title="The technical guy's shirt is an homage to a nerd I saw on a street with a t-shirt that just read &quot;teh&quot;."/>
    <p>The short answer is <strong>just because</strong>. It was a doodle that I thought was cute, so I scanned it and put it on my front page, <a href="this-whole-site-is-a-sketch" title="This Whole Site is a Sketch" rel="dct:references">in keeping with a theme</a>.</p>
    <p>The longer answer is that I wanted to focus on the designer as the <em>mediator</em> between business and technical interests, which I recognize as just one of many roles. I wanted to depict the designer as someone who reinforces confidence and <a rel="dct:references xhv:glossary" href="lexicon/conceptual-integrity" title="Conceptual Integrity">conceptual integrity</a> by demonstrating <em>value</em> to businesspeople and justifying their <em>investment</em>. Equally, to technologists, designers must demonstrate their <em>competence</em> and justify the <em>conclusions</em> they reach in the <a href="why-build-software-when-you-can-define-it" title="Why Build Software When You Can Define It?" rel="dct:references">definition of an outcome</a>.</p>
    <p>Besides, when you look at software production as a system and a process, there really is a little <em>user</em> in everyone.</p>
    <img class="figure" style="width: 60ex; height: 30ex;" src="ecosystem-of-software-production;scale=600,300" alt="Sketch depicting the ecosystem of the production of software and other knowledge products." title="Ecosystem of software production"/>
    <aside role="note" id="Es6bkoytAzM4Li5vzOVa5J">I should probably elaborate on the constituents of this diagram. First, the diagram at the very top is meant to depict the <strong>producer</strong> who solves a problem for a <strong>client</strong>. The client may in turn resell some artifact generated by the solution to a <strong>customer</strong> who may or may not be the same entity as a <strong>user</strong>. There also exist third-party <strong>vendors</strong> in this system who supply some piece of the solution, either directly to clients or through producers.</aside>
  </body>
</html>
