<?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">The ROI of a Solved Problem</title>
    <base href="https://doriantaylor.com/the-roi-of-a-solved-problem"/>
    <link href="document-stats#EsPePYQ9zJicF1fMcg51qI" 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="The ROI of a Solved Problem"/>
    <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="//www.amazon.com/dp/0201626950" rel="dct:references"/>
    <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="the-roi-of-a-solved-problem" datatype="xsd:token" property="ci:canonical-slug"/>
    <meta content="Forecasting return on investment is the bane of all creative work. This is a model for showing first that it is overwhelmingly likely that a return will happen, and second that the return is so wild and speculative that forecasts are meaningless." name="description" property="dct:abstract"/>
    <meta content="2013-08-07T22:43:43+00:00" datatype="xsd:dateTime" property="dct:created"/>
    <meta content="the-roi-of-a-solved-problem" property="dct:identifier"/>
    <meta content="2013-08-07T22:40:33+00:00" datatype="xsd:dateTime" property="dct:issued"/>
    <meta content="2013-08-07T23:04:22+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2013-08-07T23:06:31+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2013-09-17T03:48:17+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="The ROI of a Solved Problem" name="twitter:title"/>
    <meta content="Forecasting return on investment is the bane of all creative work. This is a model for showing first that it is overwhelmingly likely that a return will happen, and second that the return is so wild and speculative that forecasts are meaningless." name="twitter:description"/>
    <meta content="https://doriantaylor.com/file/individual-values" name="twitter:image"/>
    <object>
      <nav>
        <ul>
          <li>
            <a href="demonstrate-this" rev="dct:references" typeof="bibo:Article">
              <span property="dct:title">Demonstrate This</span>
            </a>
          </li>
          <li>
            <a href="giant-conf-2014-dissolving-the-redesign" rev="dct:references" typeof="bibo:Article">
              <span property="dct:title">GIANT Conf 2014: Dissolving the Redesign</span>
            </a>
          </li>
          <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="lowering-the-risk-of-web-development" rev="dct:references" typeof="bibo:Article">
              <span property="dct:title">Lowering the Risk of Web Development</span>
            </a>
          </li>
          <li>
            <a href="skeleton-organs-circulation-sinew-skin" rev="dct:references" typeof="bibo:Article">
              <span property="dct:title">Skeleton, Organs, Circulation, Sinew, Skin</span>
            </a>
          </li>
          <li>
            <a href="the-hundred-year-infrastructure" rev="dct:references" typeof="bibo:Article">
              <span property="dct:title">The Hundred-Year Infrastructure</span>
            </a>
          </li>
          <li>
            <a href="the-value-of-tailored-information-infrastructure" rev="dct:references" typeof="bibo:Article">
              <span property="dct:title">The Value of Tailored Information Infrastructure</span>
            </a>
          </li>
          <li>
            <a href="toys" rev="dct:references" typeof="bibo:Article">
              <span property="dct:title">Toys</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#EsPePYQ9zJicF1fMcg51qI" rev="ci:document" typeof="qb:Observation">
              <span>urn:uuid:b0f78f61-0f73-4262-8705-d5f31c839d6a</span>
            </a>
          </li>
        </ul>
      </nav>
    </object>
  </head>
  <body about="" id="E9G0pjEdrXkyQnqt1o9U-J" typeof="bibo:Article">
    <p>So much value in the digital domain&#x2014;and creative work in general&#x2014;goes uncreated, because it's impossible to get a budget for it. <a href="on-the-building-of-software-and-websites" title="On the &#x201C;Building&#x201D; of Software and Websites" rel="dct:references">As I mentioned elsewhere</a>, not only is this value dirt cheap to acquire, <a href="http://www.ribbonfarm.com/2010/03/01/the-expedient-desirable-product/" title="Expedient Desirable Product" rel="dct:references">provided you know exactly what you need to do</a>&#x2014;and I hope you wouldn't be trying to convince somebody to pay you to do it if you didn't&#x2014;but it's virtually impossible to make any meaningful forecasts about the effort's <em>return</em>. The result is that the cost is often too <em>small</em> for a decision-maker to even spend any time considering, and even if it isn't, any <acronym title="Return on investment">ROI</acronym> projection is completely untrustworthy, making it hard to compare against other candidate investments.</p>
    <p>This article is a sketch of a mathematical model, a simulation for understanding the <em>shape</em> of the value generated by creative problem-solving of <em>any</em> kind, not just in technology. We care about creative problem-solving because it is the common core of all art, literature, design and innovation. The model's purpose is to show that the results of creative problem-solving are statistically <em>wild</em> in their value, and should be treated as <em>speculative</em>. It also hints at a strategy for making such speculation reliably profitable, by <em>changing the deal</em> to be about accumulating solved problems rather than <a href="money-for-opus-and-the-bits-for-free" title="Money-for-Opus (and the Bits for Free)" rel="dct:references">trading on specific deliverables</a>. This model is an integral part of my larger goal to arrange the business of creative work around the realities of its structure: you damage the process, <em>and</em> the results, by trying to force either the pace or the sequence, so <em>don't</em>. The proverbial goose will lay her golden eggs as long as you let her.</p>
    <aside role="note" id="EjJ60ljT7FxDQOyy5mu_yJ">
      <p>If I hadn't made it clear, this is a <em>simulation</em>. I have no idea how you would actually measure the value of most solved problems, and even if you could, I wager the cost of an empirical study would be astronomical. For starters, how can you separate the cost of acquiring the cognitive structure of the solved problem from the cost of rendering it into some kind of physical medium? <a href="http://en.wiktionary.org/wiki/utile#Noun" title="utile &#x2014; Wiktionary" rel="dct:references">What unit would you use?</a> How do you valuate the solution to a problem which itself is trivial, but is essential to solving some other, more conspicuously valuable problem? How do you monitor all the channels through which the information of a solution can flow?</p>
      <p>What you <em>can</em> say about information of any kind is that it filters through human civilization at the cumulative rate of one person convincing another person that it's worth their while to take up, until the number of people who care enough to convince another person is exhausted. Information can also be <em>private</em>, taking the form of what <a href="http://www.amazon.com/dp/0201626950?tag=doriantaylor-20">Don Norman calls</a> <em>cognitive artifacts</em>, which can be understood as intermediate representations that act as stepping stones toward the solution to a larger problem. As such, the model depicted here assumes that the lower dollar-value artifacts <em>could</em> be as simple as a Post-It note, that sparks an inspiration to create some kind of masterpiece.</p>
    </aside>
    <h2>The Model</h2>
    <p>The value created over time by any product you release out into the wild exhibits a similar shape: the <a href="http://en.wikipedia.org/wiki/Sigmoid_function" title="Sigmoid function &#x2014; Wikipedia" rel="dct:references">S-curve</a>. Growth starts out slow, then shoots up like a hockey stick, before finally flattening off at some arbitrary maximum which is <em>unknowable</em> in advance. Furthermore, the <em>speed</em> of the uptake is also unknowable, and like the work of so many artists and writers, the result could sit on a shelf for decades before it is rightfully appreciated&#x2014;but for the moment, we'll leave that problem to the marketing department.</p>
    <figure>
      <img class="figure" style="display: block; margin: auto; width: 400px; height: 300px;" src="file/gompertz-sample" alt="" rel="dct:hasPart"/>
      <figcaption>
        <p>Depicted here is a <a href="http://en.wikipedia.org/wiki/Gompertz_function" title="Gompertz function &#x2014; Wikipedia" rel="dct:references">Gompertz curve</a>, which is a simplified version of the <a href="http://en.wikipedia.org/wiki/Generalised_logistic_function" title="Generalised logistic function &#x2014; Wikipedia" rel="dct:references">generalized logistic function</a>. It is used to model things like the spread of diseases, and mobile phone usage uptake.</p>
      </figcaption>
    </figure>
    <p>Now, let's imagine our contrived, lone creator, showing up at work every day <a href="lofting-the-project-triangle" title="Lofting the Project Triangle" rel="dct:references">and producing <em>something</em></a>. In contrast to construction or manufacturing, the value of that <em>something</em> is non-uniform and completely unpredictable. It does, however, obey a rule. You've probably heard of it: the <a href="http://en.wikipedia.org/wiki/Pareto_principle" title="Pareto principle &#x2014; Wikipedia" rel="dct:references">80-20 rule</a>, <a href="http://en.wikipedia.org/wiki/Long_tail" title="Long tail &#x2014; Wikipedia" rel="dct:references">the long tail</a>, or <q><a href="http://en.wikipedia.org/wiki/Sturgeon%27s_Law" title="Sturgeon's Law &#x2014; Wikipedia" rel="dct:references">90% of everything is crap</a></q>. Its official name is the <a href="http://en.wikipedia.org/wiki/Pareto_distribution" title="Pareto distribution &#x2014; Wikipedia" rel="dct:references">Pareto distribution</a>, and you can find it just about <em>anywhere</em>.</p>
    <figure>
      <img class="figure" style="display: block; margin: auto; width: 500px; height: 300px;" src="file/random-pareto" alt="" title="Random Pareto samples, k=500, a=log4(5)" rel="dct:hasPart"/>
    </figure>
    <p>Most days, our friend creates something mundane, like some emails or a little experiment. But every week or two, she makes something conspicuously valuable, and <em>sometimes</em> she hits the jackpot.</p>
    <aside role="note" id="E430yTrx8cLhYViC2472YL">
      <p>A good contemporary example of this phenomenon, and from my neighbourhood, is <a href="http://www.flickr.com/" rel="dct:references">Flickr</a>, which was originally created as an accessory, for what was ultimately a failed project. Flickr is arguably a bigger success than the <a href="http://www.gnespy.com/museum/" title="GNE Museum" rel="dct:references">original game it was made for</a> would have been.</p>
    </aside>
    <p>We model this phenomenon by generating random values according to the Pareto rule, and feeding them into our curve function as the height and slope parameters, with the zero point for each curve corresponding to the completion of a new <em>something</em>.</p>
    <figure>
      <img class="figure" style="display: block; margin: auto; width: 500px; height: 300px;" src="file/individual-values" alt="" rel="dct:hasPart foaf:depiction"/>
      <figcaption>
        <p>Every day, our hypothetical actor solves one outstanding problem and commits it to some kind of artifact. In our simulated universe, the months (X axis) are 20 days long and there are no weekends or holidays. Our currency (Y axis) is whatever you want it to be: dollars, euros, simoleons, ducats, etc. The vertical red line indicates where our hypothetical creative professional's contract ends. The colours of the curves indicate where they start, starting with red and cycling through the colour wheel to violet, to give a sense of where they begin in the 100 days our hero is employed.</p>
      </figcaption>
    </figure>
    <p>Of course, the value of these <em>somethings</em> is cumulative, so we add them together:</p>
    <figure>
      <img class="figure" style="display: block; margin: auto; width: 500px; height: 300px;" src="file/cumulative-effect" alt="" rel="dct:hasPart"/>
    </figure>
    <p>You can already see that the range of outcomes is completely wild, so at this point we should understand that this kind of work is inherently speculative. Despite that, our hypothetical creator has to pay rent and put food on the table. The task, now, is to come up with a way to pay our hero fairly, and in such a way that will not cancel out the return.</p>
    <figure>
      <img class="figure" style="display: block; margin: auto; width: 500px; height: 300px;" src="file/cost-function" alt="" rel="dct:hasPart"/>
      <figcaption>
        <p>This is perhaps a good place to mention that when it comes to creative problem-solving, everything you ever learned about incentives is <em>backwards</em>. I will tackle this issue elsewhere, but for now, <a href="http://www.youtube.com/watch?v=rrkrvAUbU9Y" rel="dct:references">I'll leave you with Mr. Pink</a>.</p>
      </figcaption>
    </figure>
    <p>That's it: <samp>f(x) = -ax</samp>, quantized every 20 in-universe days to simulate real payments. Pay her a flat rate for a certain amount of committed days per month. Anywhere between five and twenty should suffice. As for <em>days</em> as the basic unit, <a href="introducing-the-cell" title="Introducing the Cell" rel="dct:references">I use a four-hour <em>cell</em>, myself</a>, because that's the smallest chunk of time in which I can reliably produce a meaningful result. If you subtract this function from the sum of the values of the artifacts, you get a sawtooth shape, like this:</p>
    <figure>
      <img class="figure" style="display: block; margin: auto; width: 500px; height: 300px;" src="file/net-return" alt="" rel="dct:hasPart"/>
      <figcaption>
        <p>I encourage you to <a href="file/gompertz-pareto.r" rel="dct:references">try the simulation yourself</a>, as I obviously chose favourable-looking results. Play with the inputs and see what kind of variations you come up with. You'll note that despite the values you enter, the results are all over the map.</p>
        <p>It goes without saying that this simulation is just a sketch&#x2014;a way of evoking the idea that deterministic forecasts of <acronym title="Return on investment">ROI</acronym> are unreliable when it comes to creative work. I hope that future revisions, and input from you, will converge around a more accurate depiction.</p>
      </figcaption>

    </figure>
    <p>I recognize that most real-life scenarios are going to be considerably more complex than this. For instance, I'm leaving out the arbitrary capital expenses that will emerge from time to time in order to get a particular job done&#x2014;but by then, one would expect that there was enough information about the return on that job to justify them. This model also fails to take into account the fact that more often than not, there is more than one person on the job, so the cost function will get more and less steep as people join the project, or complete their work. Finally, earlier results will inform later investments, and by extension, later results. In the end, the net return over time will, unsurprisingly to some, look something like this:</p>
    <figure>
      <img class="figure" style="display: block; margin: auto; width: 500px; height: 300px;" src="file/pareto-wiener-process" alt="" rel="dct:hasPart"/>
      <figcaption>
        <p>This is a <a href="http://en.wikipedia.org/wiki/Wiener_process" title="Wiener process &#x2014; Wikipedia" rel="dct:references">Wiener process</a> which varies by the Pareto rule. Total cop-out, to be sure, but it should be pretty close to what you would see if you jammed a bunch of random instances of those previous plots together and included capital expenses.</p>
      </figcaption>
    </figure>
    <p>If that looks to you like a stock chart, it's because it <a href="http://en.wikipedia.org/wiki/Black%E2%80%93Scholes" title="Black-Scholes &#x2014; Wikipedia" rel="dct:references">more or less is</a>, notwithstanding <span class="parenthesis" title="not that Black-Scholes had any.">having zero predictive value</span>. The point is that any endeavour to solve a problem is inherently speculative, but the costs are present no matter what. The trick is to arrange the process, and its financing, so that it is as likely as possible to yield net positive results concomitant to the investment at any given time. That is, if you pick a problem <a href="the-principle-of-one-degree" title="The Principle of One Degree" rel="dct:references">you can solve <em>today</em></a>, and close out the day with that problem <em>solved</em>, <a href="http://www.ribbonfarm.com/2010/03/01/the-expedient-desirable-product/" title="Expedient Desirable Product" rel="dct:references">you have an asset</a>. Even if it's only tangentially related to your business objectives. If, however, you try to conform to the milestones of a <a href="on-the-building-of-software-and-websites" title="On the &#x201C;Building&#x201D; of Software and Websites" rel="dct:references">conventional, prescriptive schedule</a>, the problems that you have to solve may present themselves in a sequence that leaves you empty-handed, some, maybe most days.</p>
    <p>If 90% of everything is crap, the obvious strategy should be to produce as much crap as you can afford, because the other 10% will be spectacular.</p>
  </body>
</html>
