{"id":2545,"date":"2013-07-09T12:35:08","date_gmt":"2013-07-09T11:35:08","guid":{"rendered":"http:\/\/t-machine.org\/?p=2545"},"modified":"2013-07-09T12:36:20","modified_gmt":"2013-07-09T11:36:20","slug":"kickstarter-projects-visualized-2013","status":"publish","type":"post","link":"http:\/\/new.t-machine.org\/index.php\/2013\/07\/09\/kickstarter-projects-visualized-2013\/","title":{"rendered":"Kickstarter projects – visualized (2013)"},"content":{"rendered":"

In the past, I’ve found Thomas’s Kickstarter analysis for game-projects very useful<\/a>. Today I found something that complements them: an excellent visualization of Kickstarter projects<\/a>.<\/p>\n

It takes a little thought to understand how to use it, so here’s some ultra-quick example analysis…
\n<\/p>\n

WTF is this thing?<\/h2>\n

First, download the ZIP for Windows<\/a> or Mac<\/a>, and run the app inside it.<\/p>\n

You get an odd scatter graph, with a precise readout attached to your mouse position (gives you the exact X and Y co-ords of your position):<\/p>\n

\"Screen<\/p>\n

Usage notes:<\/p>\n

    \n
  1. You can only see a tiny fraction of the graph by default, you have to click the “zoom” word in bottom left, and click the – minus button repeatedly\n
  2. Most of the axes data is missing, to make it “look cooler”, perhaps (hmm). Instead you need to move your mouse around the screen to see what you’re looking at\n<\/ol>\n

    Some interesting things you can find quickly<\/h2>\n

    Lines drifting up the screen<\/h3>\n

    These:<\/p>\n

    \"Screen<\/p>\n

    …represent “most people do Kickstarters at round-number target amounts (x-value is the same), but the actual amount raised varies widely (y-value has many different values)”<\/p>\n

    Bright lights along the y=x (Gradient:1) slope<\/h3>\n

    At all scales, you see a cluster of lights in a diagonal line going up and to the right:<\/p>\n

    \"Screen<\/p>\n

    The line represents “project raised EXACTLY its target amount”.<\/p>\n

    Immediately we can see something interesting: apart from “tiny” projects ($3,000 or less), the vertical upwards streaks are considerably brighter than the y=x diagonal line. In fact, most of the y=x line is missing – we see instead an implicit line, made up of the bottom edges of bright streaks.<\/p>\n

    If we didn’t already know better (from watching Kickstarter), we’d expect the y=x line to be a cluster that blobbed-out both above and below the strict y=x line. Instead … it’s a hard-edge below, and blurred upwards above.<\/p>\n

    i.e: Projects over $3k generally succeed wildly – with lots of variation in the “overshoot” – or fail by a wide margin (blackness beneath the y=x line)<\/p>\n

    How fractal is it?<\/h3>\n

    We’d expect this graph to be fractal and self-similar: as you zoom out, it should look almost the same as when you’re zoomed in.<\/p>\n

    Let’s compare the graph at 0-$500:<\/p>\n

    \"Screen<\/p>\n

    $0 – $2500:<\/p>\n

    \"Screen<\/p>\n

    $0 – $10k:<\/p>\n

    \"Screen<\/p>\n

    $0 – $50k:<\/p>\n

    \"Screen<\/p>\n

    and finally: $0 – $200k:<\/p>\n

    \"Screen<\/p>\n

    Some quick broad-strokes observations (NB: these are not statistically accurate – I’m simply pointing out the ultra-fast, at-a-glance analysis you can do here. If you’re following Kickstarter a lot, and don’t have time to keep re-analysing in detail, this gives you a fast view):<\/p>\n

      \n
    1. this part is easier to see for yourself by actively zooming the app in\/out, so you can see the animated change in self-similarity.\n
    2. Most of the range is self-similar.\n
    3. Below $300-$500, it’s very different – the normal trends of KS don’t apply\n
    4. Projects over $30,000 funding target do badly on KS: much higher rate of failure\n
    5. Projects $1k-$8k tend to do well: much higher rate of success\n<\/ol>\n

      If you need less than $30k, it doesn’t matter how much you ask for<\/h3>\n

      Look at the left-hand edge of the $200,000 graph again:<\/p>\n

      <\/p>\n

      Looking “above” the x=y line, we see that the density of dots is almost constant left-to-right. If that’s accurate, it means that the final amount raised is largely independent of the amount they originally asked for<\/strong>.<\/p>\n

      That’s interesting for projects that intend to set their funding bar lower than possible, in order to raise the chances of getting “some funding” as opposed to “nothing”.<\/p>\n

      This analysis sucks<\/h2>\n

      Why, yes! – yes it does. If you want accurate analysis, it’s not enough to take quick guesses (as above). You absolutely need to look at calculated<\/strong> co-dependence\/independence, rather than guessing (because those figures are almost impossible to do correctly in your head – you want a spreadsheet or computer to calc them for you).<\/p>\n

      But these days it’s so easy to collect metrics that we often find ourselves overwhelmed by numbers. Many of us fall back to glancing at the raw numbers and guessing trends from them – which is the very worst option of all (humans are terrible at accurately doing stats-analysis by gut feel).<\/p>\n

      In those situations, where we’re too lazy \/ overwhelmed to look at the correct figures, visualizations like this can help a lot.<\/p>\n

      Also … although I’ve looked at many spreadsheets and presentations on KS stats, I’d never internalized quite how much people stick to the “round numbers” of funding targets. This visualization made that a lot more obvious to me. Similarly with the variance on “actual amount received, when successful” – I knew it usually overshot by a large amount, but I had the impression (from Kickstarter.com’s own press releases and conversations) that the overshoot was clustered … and yet clearly it’s not.<\/p>\n","protected":false},"excerpt":{"rendered":"

      In the past, I’ve found Thomas’s Kickstarter analysis for game-projects very useful. Today I found something that complements them: an excellent visualization of Kickstarter projects. It takes a little thought to understand how to use it, so here’s some ultra-quick example analysis…<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[50,59,62,46],"tags":[],"_links":{"self":[{"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/posts\/2545"}],"collection":[{"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/comments?post=2545"}],"version-history":[{"count":7,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/posts\/2545\/revisions"}],"predecessor-version":[{"id":2561,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/posts\/2545\/revisions\/2561"}],"wp:attachment":[{"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/media?parent=2545"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/categories?post=2545"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/tags?post=2545"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}