<?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">Open for Business</title>
    <base href="https://doriantaylor.com/open-for-business"/>
    <link href="document-stats#EdRAwqSZ-DWw0rne_Kg65K" 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="Open for Business"/>
    <link href="lexicon/#EcIIUNUVDvNNAs5I-A7arJ" rel="dct:audience" title="Everybody"/>
    <link href="person/dorian-taylor#me" rel="dct:creator" title="Dorian Taylor"/>
    <link href="lexicon/#E4loioIj0q52nszE712G5J" rel="dct:subject" title="Marketing"/>
    <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="open-for-business" datatype="xsd:token" property="ci:canonical-slug"/>
    <meta content="Here's the plan: I assemble a group of awesome subscribers and regularly send them a curated stream of novel, semi-custom software, IA and UX technique." name="description" property="dct:abstract"/>
    <meta content="2010-10-14T21:19:24+00:00" datatype="xsd:dateTime" property="dct:created"/>
    <meta content="open-for-business" property="dct:identifier"/>
    <meta content="2010-10-14T21:17:22+00:00" datatype="xsd:dateTime" property="dct:issued"/>
    <meta content="2010-10-14T21:19:41+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2010-10-28T22:48:59+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2010-10-28T22:55:15+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2010-10-29T00:08:47+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2010-10-29T01:16:10+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2010-10-29T01:16:34+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2010-10-29T01:23:47+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2010-11-15T23:00:51+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="Open for Business" name="twitter:title"/>
    <meta content="Here's the plan: I assemble a group of awesome subscribers and regularly send them a curated stream of novel, semi-custom software, IA and UX technique." name="twitter:description"/>
    <object>
      <nav>
        <ul>
          <li>
            <a href="document-stats#EdRAwqSZ-DWw0rne_Kg65K" rev="ci:document" typeof="qb:Observation">
              <span>urn:uuid:751030a9-267e-40d6-ac34-ae77bf2a0eb9</span>
            </a>
          </li>
        </ul>
      </nav>
    </object>
  </head>
  <body about="" id="Ew_Bt3r1NCZcIGu5TwQl2L" typeof="bibo:Article">
    <p>Every organization I've worked with has had a contingent of unsolved problems related to software and information systems, be it in their products or their infrastructure. While these problems would be valuable to solve, there is almost always something more pressing for staff to do, and the problem usually has to be fairly significant before one even entertains hiring a consultant.</p>
    <p>There exists also an inherent uncertainty to problem-solving. As a professional problem-solver I can say that to date I have yet to observe (and not for a lack of searching) an effective means of estimating the cost of solving a <em>specific</em> problem, since doing so is effectively attempting to predict when I will gain an understanding of what the problem is or find somebody else who does (which would entail understanding enough to constrain who to look for and explain it to them). I can, however, state the following observations:</p>
    <ul>
      <li>Many disparate organizations have similar problems related to software and information systems;</li>
      <li>Access to solutions to these problems is valuable despite their level of business-criticality;</li>
      <li>Many of these problems fall well within the capacity of a single competent individual to solve quickly and efficiently once he or she gains comprehension;</li>
      <li>Over time, as this individual learns more about the idiosyncrasies of a given organization, he or she can proactively address problems for which solutions are conveniently available;</li>
      <li>These problems are easily pooled and amortized across a cohort of subscribers;</li>
      <li>If the pool is large enough it is overwhelmingly likely that there will always be a valuable problem which is convenient to solve right now;</li>
      <li>The economics of software and information systems afford results on a frequent (e.g. sub-monthly) basis;</li>
      <li>Likewise, the cost of this process to the individual subscriber can be brought far below that of a dedicated employee or consultant.</li>
    </ul>
    <p>What I'm offering can effectively be understood as <em>serendipitous</em> software/<acronym title="Information Technology">IT</acronym> <acronym title="Research and Development">R&amp;D</acronym>. For a flat subscription fee (to be determined), I maintain a dossier (i.e. an extranet) where I accrue what I learn about your organization (the fee also covers communication). To this dossier I attach the findings I deem relevant (relevant ones are curated, though you have access to all of them). Findings, in this case, refer to artifacts such as bookmarks, notes, reports, data visualizations, tutorials and software prototypes. What I work on is determined partly by demand from the subscriber base, partly by whatever problem is handy to solve at the time.</p>
    <p>What I'm aiming for with this configuration is a means of providing affordable access to useful strategies and tactics to organizations who have to deal with information systems&#x2014;that is to say, every organization in some capacity. I am currently in the preliminary stages of gauging interest; I will be answering questions and arriving at a price for this service in the coming weeks.</p>
    <p><a href="javascript:sendMail('gmail.com',%20'dorian.taylor',%20'Dorian,%20tell%20me%20more%20about%20your%20zany%20scheme!');" rel="dct:references">Please send me an email</a> if you would like more information. Thank you for your attention.</p>
  </body>
</html>
