<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Benjamin Grose on Medium]]></title>
        <description><![CDATA[Stories by Benjamin Grose on Medium]]></description>
        <link>https://medium.com/@bgrose25?source=rss-864ef1bd60ff------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*_LKrYNRyvlEx6MCt.jpg</url>
            <title>Stories by Benjamin Grose on Medium</title>
            <link>https://medium.com/@bgrose25?source=rss-864ef1bd60ff------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 16:33:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bgrose25/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to teach service design using wands, wizards, owls, and Hogwarts]]></title>
            <link>https://medium.com/@bgrose25/how-to-teach-service-design-using-wands-wizards-owls-and-hogwarts-a8043face626?source=rss-864ef1bd60ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8043face626</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[harry-potter]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-workshop]]></category>
            <dc:creator><![CDATA[Benjamin Grose]]></dc:creator>
            <pubDate>Thu, 04 Jul 2019 10:16:06 GMT</pubDate>
            <atom:updated>2019-07-04T10:35:07.702Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part 2: Future blueprinting 101</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Kp7TqRDyQt-BR9_jbenVg.png" /></figure><p>This is the second article in a two-part instalment all about teaching service design using Harry Potter.</p><p><a href="https://medium.com/@bgrose25/how-to-teach-service-design-using-wands-wizards-owls-and-hogwarts-660bb08f9da3">Read the first part.</a></p><h3>Where we left off</h3><p>At <a href="https://methods.co.uk/">Methods</a>, we run workshops on a Friday morning where one member of the team will run a practical session to teach the rest of us about a particular technique they’re using.</p><p>I ran a session recently about a service design technique called future blueprinting, which built upon the blueprinting session I ran last year.</p><p>This is what happened (and for those of you looking to run a future blueprinting workshop — this is how you could do it).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xU_4UpcgDlhmYY63" /></figure><h3>Preamble and set up</h3><p>Where there is a problem, people often itch and rush to get to a solution. I say: all in good time. You want to get there the right way, and with the right people in the room.</p><p>For those non-SD practitioners, ‘future blueprinting’ is a workshopping method that follows ‘as-is blueprinting’ as the second part of a two-part problem-solving show often used at the end of a Discovery or in early Alpha.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qhTQI40MddDjMG3-" /></figure><p>You should always start a workshop by setting expectations, so that’s exactly what I did.</p><p>You also want people’s brains, not their laptops. With ideation it’s very important that people are concentrating fully, and not distracted by emails etc etc, so gently set the ground rules.</p><p>As ever for a workshop, keep people fuelled. Buy decent snacks (not just chocolate) and remind them to eat them.</p><p>I’ve run a future blueprinting workshop using a few variations, but generally to solve a problem like the Hogwarts First Year Onboarding (i.e. an existing end-to-end service exists already but is in need of transformation) I’ve found that the following running order works well.</p><h3>The dark magic of ‘How might we’</h3><p>The real secret to this workshop is a simple technique invented by a very smart person and commandeered into many different workshop techniques over the years, including the likes of Google’s ‘Sprint’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*99BzjGIR7-YqhOsu" /></figure><p>How Might We is beautiful in its simplicity, and it’s at the heart of future blueprinting.</p><p>So my first job really was to introduce the technique to the room, with simple slides and a few examples.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kXtvisUYwT9guyQo" /></figure><h3>Recap</h3><p>Following the preamble and introduction to HMW, the first part of the workshop is all about providing a platform to start writing HMWs…Hopefully you already have at least one as-is blueprint, full of pain points, questions, and opportunities that you can use a vehicle for ideation.</p><p>Ours looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zAWFjMVpuA_xAvHg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6xLTAuebl15Hel5-" /></figure><p>You want to spend a bit of time here, and this can sometimes be hard as people often want to jump to the solutions. But playback the story. Dwell on key problem areas. Read aloud the journey in a narrative that can spark ideas and encourage people to write lots of HMWs. Because, as they teach you in service design school — an empty wall is not a good wall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*x6KYS7-dyk7WFt9-" /><figcaption><em>Charlotte playing back one of the blueprints</em></figcaption></figure><p>Depending on how long the interim is between blueprinting and future blueprinting, you might have also undertaken some additional research (possibly your UR honed in on some questions or gaps that came up in the blueprinting session that you’ve probed a little more in the meantime).</p><p>As it happened, I’d had ample time between the workshops to do some more ‘research’ — so I played this back too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*v8ybwSrZY4xJXm4R" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Vw40Y0kvwIBul18H" /></figure><h3>Inspire</h3><p>Depending on timings, and how many blueprints you have to recap (I’ve been in a session where we did eight to generate a huge wall of HMWs) you may want to break for lunch now. We only had two blueprints (and they were of the same end-to-end just created by two different teams) so we ploughed on into the next part: inspire!</p><p>Before you get to the stage where people have to start drawing stuff, it’s a good idea to just encourage them with a few examples of stuff that is working well out there in the world. Loosely linked to the problem you are trying to solve, aim for up to eight examples of stuff people are doing that they could learn from (and of course steal from).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1gYSB2R-4JIvyzV7" /></figure><p>For Hogwarts, I referenced the likes of Headspace, Replika, Revolut, as well as a few leftfield examples like…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FoMeLqZrdQyLMthZ" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uBkxapdQOm4CnDGO" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Czxp0aCUiuniqOX8" /></figure><h3>Pick n’ sketch</h3><p>Whether you ‘inspire’ before or after lunch, during lunch you’ll need to recruit a few Post-it fairies (or house elves) to help you as the facilitator to do a very important job…Grouping and theming the HMWs…</p><p>So this is what I did over lunch along with some kind house elves, whilst the rest of the team stuffed their faces with pizza…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oHItAj38iLXTgY_I" /><figcaption>Our HMW wall</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ue-3A9xN2dB87Azi" /><figcaption><em>Said face stuffing</em></figcaption></figure><p>Aim for either as many groups/themes as there are people (if a small group of up to 10) but if you have 10+ people then it’s a good idea to sort them into teams.</p><p>As this was Harry Potter, I of course came up with a fun way to group the teams that involved cutting out Hogwarts house emblems, screwing them up, and sticking them in a sorting hat for people to pick.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5HZcoUN_db9pY45T" /></figure><p>Either way, you need to make sure that someone at least is picking a HMW or two from each theme — so you can offer these on a first come first served basis (a “who wants this theme” round of hands up)…or just lay down the law and let people choose and hope they do as they are told. Fortunately, even the Slytherins did as they were bid. Each house picked around 10 HMWs across the dozen categories so there was enough consistency but also a bit of variation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jk6pmOPzxyQ2KLpJ" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2maaB7SA-f_d3QRU" /><figcaption>The teams picking their HMWs</figcaption></figure><h3>Crazy 8s</h3><p>Another piece of dark magic that someone clever came up with and everyone has since borrowed, is crazy 8s…an activity where it is key to encourage everyone to get creative.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mWcTgfuz_773K1CA" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*646Lzcj4z0oo9Pou" /><figcaption><em>Crazy 8s after about 4 minutes</em></figcaption></figure><p>Once everyone has panicked a bit and of course come up with some brilliant ideas (like Ryan’s final idea below which was also my personal favourite) get them to put aside these wonderful folded A4s for later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vSzoEaND86SywNnO" /><figcaption><em>Ryan showing off his crazy 8s</em></figcaption></figure><p>Next, it’s time for a bigger and more group-led activity.</p><p>After divergence, comes convergence, and this is where we mapped the future of Hogwarts First Year Onboarding experience.</p><h3>Map the future</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*R0RMrVrTh6LLrMo8" /></figure><p>To facilitate said future mapping I made simplified versions of the blueprint ‘blueprint’ and printed them out on A3. This activity is about bringing together what has been done so far and mapping it out ‘end-to-end’. Each team had essentially a minimum of 24 ideas that they were able to draw upon to map how they saw the future of Hogwarts, and how they could restore the school to its former glory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mAolNwQNiVi2adfz" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tLh0KipjV4rG5jAk" /><figcaption><em>Hufflepuff House whispering conspiratorially during Map the future</em></figcaption></figure><h3>Draw the things</h3><p>The final piece of the puzzle is to bring it all to life. Each house had their selected HMWs covering a range of themes from: mental health, travel, shopping, food, muggle-borns, and banking…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*D2Cr1ZuXM1Yi4JZc" /><figcaption><em>The teams picking their HMWs</em></figcaption></figure><p>They also had their crazy 8s. And they now had their maps. The only thing missing from what I call a ‘future blueprint’ pack were sketches of how the key parts of it could actually work. These are called ‘signature moments’, and the first part of Draw the things is to pick them.</p><p>At this point, before pen goes to paper, it’s a good idea to just clarify what sketching actually means…particularly for those who haven’t done it before…I find the following slides do a good job of relaxing the room and easing the rookies into sketching.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xtAuxbp7GyOlvbti" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YHiWhRSWvDAcfXoo" /></figure><p>Then show them that it’s perfectly ok to do any of the following….</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9bIP4xUzYw3X78Be" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*j1N0N4Ya4PDVMkrr" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DZaTB9q98f2LMZmN" /></figure><p>With the preamble over, you should now set a timer for around half an hour (longer if you have enough time), and walk the room through the ‘3 step sketch’ method as you go and the ‘things’ start to take form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ztEM0IfaG3inOD12" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2OX8WFKXJ5ZfEie9" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gCdy0EY1IzOaknnv" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*riSk9uMqI4hMJEJp" /><figcaption><em>Draw the things being drawn</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gMgnu2M3hIlN0ofj" /><figcaption><em>The Slytherins drawing on themselves</em></figcaption></figure><h3>Present and vote</h3><p>With the future blueprint pack complete, it’s time to get it all up on the wall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5zWB-r50rvQsdYvn" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a6ivZeH-t_YL2Obs" /><figcaption><em>Gryffindor House Captain presenting their ideas</em></figcaption></figure><p>There were some brilliant ideas, including Prep a Sort, Mag Up, The Jelcome Party, and the Snitch Mac 1 (the Draw the thing photos below explain these wonderful creations far better than I ever could…).</p><p>But the winners were of course Slytherin, who came up with HAWI — Hogwarts Automatic Wizard Identification…A skin based magic to solve all of your problems at Hogwarts…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lloZD8CdU8bGZiFh" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lNf7ysIdlxOUixl_" /><figcaption><em>Slytherin’s future blueprint pack</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*V76d-fRFlnv7uiIo" /><figcaption><em>Hufflepuff’s future blueprint pack</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*B4N87vhzM1Qr8BSE" /><figcaption><em>Gryffindor’s future blueprint pack</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZTO66Vk7BWFYEXFI" /><figcaption><em>Ravenclaw’s future blueprint pack (they lost their crazy 8s somewhere…)</em></figcaption></figure><h3>Wrap up</h3><p>In just 3 and a bit hours we had taken a system full of problems (albeit many of them made up by some of the more imaginative Potter heads in the room) taken it apart, interrogated it, and put it back together all over again. We had four solid routes for how the Hogwarts First Year Onboarding could work better, and hopefully solve the issues currently tainting the former greatest magic school in the world. Could ideas like Hawi, Mag Up, and The Full Broom Party restore Hogwarts to its former glory?</p><p>The only way to find out, of course, is to prototype these solutions and test them with real users in an Alpha, and hopefully — a Beta.</p><p>And unfortunately for Hagrid, it looks like his part in First Year Onboarding at Hogwarts School of Witchcraft and Wizardry, is over.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0grWLIYnhUQLmxAVIR36Uw.png" /><figcaption>Poor Hagrid</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8043face626" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to teach service design using wands, wizards, owls, and Hogwarts]]></title>
            <link>https://medium.com/@bgrose25/how-to-teach-service-design-using-wands-wizards-owls-and-hogwarts-660bb08f9da3?source=rss-864ef1bd60ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/660bb08f9da3</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[service-blueprint]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[harry-potter]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Benjamin Grose]]></dc:creator>
            <pubDate>Wed, 06 Dec 2017 12:17:56 GMT</pubDate>
            <atom:updated>2019-07-04T10:21:01.234Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gRyM92L0p_ZPZLbC4ST_TA.jpeg" /></figure><h4>Part 1: Blueprinting 101</h4><h4>What on earth does Harry Potter have to do with service design? Well, as it turns out, quite a lot…</h4><p>At <a href="https://methods.co.uk/">Methods</a>, we run monthly workshops on a Friday morning where one member of the team will run a practical session to teach the rest of us about a particular technique they’re using.</p><p>I ran a session recently about a service design technique called blueprinting.</p><p><em>(For those non SD practitioners, blueprinting is a workshopping method for mapping how a service works by breaking it down to its component parts.)</em></p><p>This is what happened.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*nv500JM_jecsDdQykqcAAw.jpeg" /></figure><p>Blueprinting isn’t the easiest technique to teach in practice. It relies on the people in the room having a considerable degree of knowledge about the chosen scenario and subject matter. We use it with public sector organisations to solve wicked problems by stripping them back to their core component parts. And outside of that organisation these problems aren’t always the most exciting, even if they are necessary to improve the lives of both citizens and civil servants. So coming up with a subject and a group of simulated scenarios to blueprint posed me a problem in itself. Do I use an example project, which no one in the room except me knows anything about? Do I make up a project? How do I make it both interesting and not the most boring 3.5 hours of people’s lives, and also ensure that we actually simulate a real blueprinting session as realistically as possible…</p><p>Having a strong theme is quite important to overall success. Especially if that theme suits those with an exuberant and active imagination.</p><p>Which led me to Harry Potter.</p><p>Which brings me to <strong>key point number 1:</strong></p><blockquote>Feel free to use this workshop template, but only if you have some real Potterheads in the room. I took a risk and fortunately it paid off…</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wyNy_dLLt0u7qMFR9X9vgw.jpeg" /><figcaption>…because Harry Potter himself turned up.</figcaption></figure><h3>Setting the scene</h3><p>It’s always best to start a workshop by setting both the scene and expectations.</p><p>You don’t want people to get the wrong idea about what a session like this is going to give them, so it’s a good idea to set the record straight from the off. Don’t promise the world. There’s a danger that some people could see workshops as a miracle cure, a ‘fix all’ technique that works because we will just throw some ‘design thinking’ at a problem and put some post-its on a wall, and doing that will solve the problem…etc etc etc.</p><p>It doesn’t quite work like that. So make sure you nip this expectation in the bud early.</p><p>Be honest. Be energetic. Be firm. Tell people to put their laptops away, then alleviate the silent but inevitable groans by drawing attention to the abundance of snacks on the table…</p><p>Which brings me to <strong>key point number 2:</strong></p><blockquote>Buy decent snacks.</blockquote><blockquote>I purchased a selection of Co-op bitesized snacks including caramel shortbreads and flapjacks, a box of matchmakers, and a multipack of drumstick squashies (which were a massive hit).</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*y8Rp7N7dKg1pfSEbw4AsZQ.jpeg" /><figcaption>A suitable disclaimer.</figcaption></figure><p>However, I qualified this disclaimer by saying that those who were here for magic were in the right place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Fpw-WkWlXrfyLOtnJrLFLg.jpeg" /><figcaption>Methods happened to have won some exciting new business that very morning.</figcaption></figure><p>With this in mind, it was time to find out whether I’d totally misjudged this lot and the workshop was doomed, or was going to be a roaring success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*pZjUGUKPtDkWDghLoQuxPw.jpeg" /><figcaption>The warm up activity.</figcaption></figure><p>Thankfully we had a good mix of Potter knowledge grades from 8.5s down to 0s, and once the experts were paired up with novices, we were ready to go.</p><p>First however, I did a bit of talking to kick things off properly.</p><h3>What is service design?</h3><p>At Methods we use a design thinking approach to service and product design. It’s not reinventing the wheel, more stripping the wheel back to its core components, and adding a third diamond to the double diamond because let’s face it, 3 is better 2. To avoid sounding like Gillette, I’ll qualify this a little more by saying that design is an ever-changing discipline. The emergence of areas such as service design and product design in the digital space have meant that the designer’s toolkit keeps getting bigger, as we tackle all sorts of problems across the industries. Therefore it’s only natural that the core process evolves too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*C1uaulpILH5Ba65xwQDtQA.jpeg" /><figcaption>The triple diamond approach.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Uy2KRr_YUISmj6r4kjfQrA.jpeg" /><figcaption>The ‘explaining a service to your nan’ slide.</figcaption></figure><p>There are lots of definitions out there for what service design is, some better than others, and I usually turn to an excellent definition coined by Erik and Megan at <a href="http://www.practicalservicedesign.com/">Practical Service Design</a>, especially if I want to sound intellectual.</p><blockquote>Service design is a human-centred design approach that places <strong>equal value</strong> on the <strong>customer experience and the business process</strong>, aiming to create quality customer <strong>experiences</strong>, and seamless service <strong>delivery</strong>.</blockquote><p>However if I am explaining this to my nan, as I usually do at Christmas every year, I go with something like the following.</p><blockquote>Service design is a process and methodology for finding out what the problems are (for an organisation) and deciding <strong>how best to solve them</strong>.</blockquote><p>The point of the context slides is to not only sell the idea that service design is necessary and important in our work, but to also cement the idea that the facilitator of this workshop knows what he’s doing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*s_NIw6kq6eM5of6LlHNMcA.jpeg" /><figcaption>Stage theory — illustration courtesy of Erik Flowers and Megan Miller at Practical Service Design.</figcaption></figure><p>Briefly cover important things like stage theory, the service design toolkit, the relationship between products and services, as well as what blueprinting is and where it fits in to an Agile project in the design process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*4Efp8dVibEL4tOkMg2co9g.jpeg" /><figcaption>Service designers are choreographers.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Naz3bUJSyPcirUkrx0-pdQ.jpeg" /><figcaption>Discovery and Alpha design tools.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*TiD1JjMG7bSLIKEPuDzMTg.jpeg" /><figcaption>When you blueprint.</figcaption></figure><h3>So what is blueprinting?</h3><p>A blueprint is a visualisation of how a service works across a particular scenario, broken down into its integral parts:</p><ul><li>Actions</li><li>Actors</li><li>Touchpoints</li><li>Systems and policies</li><li>Pain points, questions, and ideas</li></ul><p>It is a group workshopping method to solve a problem by getting upstream of it. It doesn’t work if you don’t have the right people.</p><p>When explaining the idea behind blueprinting I usually turn to a hero of mine — the advertising legend Dave Trott, who talks about solving problems by getting upstream of them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*pNr_U8PjLu1Q7qmMF7gNZg.jpeg" /><figcaption>Words from a legend.</figcaption></figure><p>Think of blueprinting as the <strong>embodiment of this approach to creative problem solving</strong>. It’s all about making sure you are solving the right problem.</p><p>It works well as a problem-solving technique because it:</p><ul><li>moves memory out of your head into the world, freeing up processing power</li><li>allows you to see connections and relationships you can’t easily visualise in your head</li><li>creates a shared understanding for teams. Now your team can be part of that distributed world you think with</li><li>facilitates knowledge transfer/learning — a great technique for anybody whose role touches service design/management</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CNTpkjVd_SUMkMg47g4XTQ.jpeg" /><figcaption>A blueprint in the wild.</figcaption></figure><p>But essentially, a blueprint is a narrative — it helps the team creating it see the bigger picture. And it’s also the glue that brings all the disciplines together: UX, research, business analysis, tech, policy…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*bGv-43D4S66aupsAjqX8dA.jpeg" /><figcaption>Fancy slide.</figcaption></figure><p>To create a blueprint, you need 3 things: experience maps, a scenario, and that scenario broken down into steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*vlmKfUXr_ZHWArMuH0R57Q.jpeg" /><figcaption>Blueprint ingredients (borrowed from Practical Service Design)</figcaption></figure><h3>Experience maps</h3><p>An experience map tells the end-to-end story of your service from a customer or actor’s <strong>point of view</strong>.</p><p>What they are doing, thinking, feeling, hearing, seeing…from before the start using your service, to when they stop using it. It’s a bit like a more actionable version of a persona.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N3AsEOnuok57e72mRMIxVQ.jpeg" /><figcaption>Experience map template.</figcaption></figure><p>It’s a visual representation rooted in empathy, and provides the experience skeleton for blueprinting. Like a persona, it’s usually not a depiction of an actual real-world, single customer’s (or service actor’s) experience. It’s an aggregate of experiences compiled from customer research and the knowledge of subject-matter experts in your organisation.</p><h3>Activity no.1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*CwD16T9HFGxY29VBOc3ljg.jpeg" /></figure><p>After explaining all of the above context in no longer than 15 minutes, it was time for the first activity. I split the groups into pairs (Potterheads with novices) gave them an experience map template, and (to give them a steer) put the following slide up and explained I had already conducted some user research that very morning…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*W5WeFQ1hUrOJKcVRNuxY9w.jpeg" /><figcaption>My user research.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0j522-YyKT5Ldbo4DCY0Ow.jpeg" /><figcaption>The team making their experience maps.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_jBM930PlyFupxHGeK73ww.jpeg" /><figcaption>The team’s experience maps.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YMZTGfNCY2kTtm2c0bYHig.jpeg" /><figcaption>Hermione Strangeville.</figcaption></figure><p>We ended up with a colourful array of first year students — from gender neutral Hillary, to Biscuit Drumstick Malfoy, to Hermione Strangeville — and some even drew their Hogwarts first year, using the range of blue, black, red and purple Sharpies I’d so thoughtfully provided.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UKMddu2M8kExR7X_pVVdrg.jpeg" /><figcaption>Biscuit Drumstick Malfoy.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8fyk8mMRdWCPN0gsfOh_aA.jpeg" /><figcaption>Hillary.</figcaption></figure><h3>So what do you blueprint?</h3><p>With one part of our ingredient list done (the who), it was onto the question of <strong>what </strong>we should actually blueprint…</p><p>The overarching theme of the blueprint should be a key scenario that takes place across customer experience and service delivery. An <strong>end-to-end view</strong> of an experience that spans some sort of <strong>start and finish.</strong></p><p>To find out what these are you usually have to do some digging around, conduct both user and stakeholder research, and then validate them beforehand with the Product Owner, and relevant SMEs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*khiQhq1lL1Bn5SnZ08H0Vg.jpeg" /><figcaption>Writing a scenario 101</figcaption></figure><p>But beware — a scenario is not a user journey. It’s a signature moment, often one of pain (which is why you’re blueprinting it — to alleviate the pain and make it all better for the customer(s) and the service actors).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*3r8BT4POageHBZqYdnhlkQ.jpeg" /><figcaption>An example Harry Potter-themed scenario.</figcaption></figure><p>The scenario should not cover the entirety of your experience map, only parts of them (and can cover more than one, it depends who is involved).</p><p>Use the ‘doing’ part of your experience maps to help create it — which is why it’s always useful to make these maps for both the customers and service actors involved, so that you have a full view of who is involved, when, and where.</p><h3>Activity no.2</h3><p>So we had our experience maps, we had our scenario, now we needed to break it down into steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*U8sl_M1MS0kNQWhGEcg6ZA.jpeg" /></figure><p>This is where I was relying on the Potterheads and their expert knowledge. I thought it was a good idea to brush up on my own already fairly substantial Potter knowledge, so I read <a href="http://harrypotter.wikia.com/">some webpages</a> on the tube that very morning. By the time I got to the office, I’d remembered/discovered that Muggle borns receive their letter by muggle post, the Sorting Hat gives a different song every year, and girls are allowed in the boy’s dormitories (but boys aren’t allowed in the girl’s dorms).</p><p>Whilst the pairs were presenting their experience maps back to one another I cunningly went around the room and put either a blue or yellow star on each, making sure that both teams had strong Potter knowledge representation. The team now split into those two groups and began building out their steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oSYZdU6h2SUxOcoi9FCriA.jpeg" /><figcaption>Digital Director Gordon being theatrical.</figcaption></figure><h4>A few quick tips about breaking scenarios into steps</h4><ul><li>Add the end goal first (in the case of this scenario is: student goes to sleep in the dorm)</li><li>Aim for less than 25 steps, otherwise you’ll be there all day and your arms will fall off</li><li>The scenario should not cover the entirety of your experience map, only parts of them (and can cover more than one, it depends who is involved)</li><li>Use the ‘doing’ part of your experience maps to help fill them out — which is why it’s always useful to do them for customers and service actors</li></ul><p>And finally the number one rule of breaking up a scenario, which also happens to be<strong> key point number 3:</strong></p><blockquote>You should know your scenario and steps, and have validated it with your Product Owner/SMEs, before the blueprinting session.</blockquote><h3>Blueprinting ‘jidoka’ style</h3><p>We use a ‘jidoka’ style method of blueprinting. This basically means asking ‘why’ a lot. It’s a technique I adapted from the resources developed by <a href="http://www.practicalservicedesign.com/mural-template/">Megan and Erik at Practical Service Design</a> (so big shout out to them), and one we’ve used with several public sector organisations such as the Education and Skills Funding Agency (ESFA), the Institute for Apprentices (IFA), and The Advisory, Conciliation and Arbitration Service (ACAS) to solve problems and come up with ideas.</p><p>The jidoka blueprinting technique is inspired by an old concept for handling and solving error that was coined by <a href="http://www.toyota-global.com/company/vision_philosophy/toyota_production_system/jidoka.html">Toyota Group assembly line</a>. It means: automation with a human touch.</p><p>If production line employees thought they saw an error, they pulled a cord (the andon) to stop the line.</p><p>Experts then converged upon the problem area to determine the cause, asking — “Why? Why did it happen? Why is that the reason? But why did that happen? Why was that the cause?”</p><blockquote><strong>The philosophy is to ask why as many times necessary to get to the root cause of the problem and then fix it so it never happens again .</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*KSGsyoh7vW65Xt8fnlQf2g.jpeg" /><figcaption>Ask why why why why why why why why why until you get to the root of the problem.</figcaption></figure><p>To begin with, you build out the blueprint of the scenario for both what’s happening frontstage, and backstage — the what(steps), the who(customer, service actors), the how (touchpoint, systems, rules) and then you ask why — <strong>a lot</strong>. The whole team writes pain points (drawn from your experience maps and the heads of your SMEs), questions they think they might need to go back out into the field and ask a user, as well as any other questions or ideas about how we could do things differently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*ht2TreufAMncnpDAMixAbQ.jpeg" /><figcaption>You can’t solve the right problem without insights.</figcaption></figure><h3>Third and final exercise</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*ywp7dUx0xlkn8PJSWrW4lA.jpeg" /></figure><p>So having explained all of this to the team, it was time to blueprint our scenarios…</p><p>I gave the teams some more ‘user research’ but generally let them and their imaginations do the rest.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*wqNgihBfJVwycvFSu2Hhlw.jpeg" /><figcaption>My research slide.</figcaption></figure><p>It took about an hour for each team to flesh out their blueprints and add as many jidokas as possible.</p><p>Which brings me to<strong> key point number 4:</strong></p><blockquote>Encourage everyone to add as many jidoka post-its as possible. Get people on their feet. Remove the tables and chairs if you need to. An empty blueprint is not a helpful blueprint, so you need as much on there as you can.</blockquote><p>As a final flourish, I gave each team a blue or yellow star (impulse buys at Ryman that morning even though I had no clear plan for them) and instructed the teams to place it on the blueprint to <strong>mark a key or vital area of pain.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8fkpXvUYrjXmaDaBPS2oOA.jpeg" /><figcaption>Blue star team’s blueprint.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eG5b9ITKuIs15kZRpC59-A.jpeg" /><figcaption>Yellow team discussing how one goes about setting up a wizard bank account.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ypq1E4I2knqFIRoa-WqHEA.jpeg" /><figcaption>Gavin from blue star team sneaking a look at yellow star team’s blueprint.</figcaption></figure><h3>Takeaways</h3><p>I finished up the session with a few top tips and takeaways, which I rattled through very quickly because it was lunch time and all the snacks had been eaten.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*yqabZ_RfBfQsijM5sdR3mA.jpeg" /><figcaption>How to take a blueprint down in a helpful way.</figcaption></figure><p>Some other top tips that I’ve learnt from doing this multiple times:</p><ul><li>Blueprinting is demanding on the facilitator. That’s why it’s best to have 2. (I once ran 3 separate sessions alone, covering 12 scenarios, and it almost killed me)</li><li>Ideally you have 2 facilitators and a Product Owner to help keep things on track</li><li>Do lots of work in advance. Work out the steps and put them up, as well as the Y axis labels</li><li>Then the first stage should be quickly running through the steps to validate them with the group, moving some around where you need to</li><li>Once you’ve documented it make sure you share it with the team (and beyond if you need to) so they can add anything that was missed, or has since come to them after the session. A blueprint is not a static identity, it should live and grow with the project</li></ul><h3>So — what’s next?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*i_dzY3jZA2IrvAe1wHQqOg.jpeg" /></figure><p>How do you take these problems, and get upstream of them to turn them into solutions? The hard part is done — after documenting and sharing it with the team and those stakeholders who couldn’t make the workshop (I usually do this using <a href="https://realtimeboard.com/">RealtimeBoard</a> or <a href="https://www.sketchapp.com/">Sketch</a>) — next comes the fun part where you start to sketch what the future could look like.</p><p>And in the world of Harry Potter, that future world is one of automated postal delivery systems, no more owls, some sort of wizard Amazon, and a more reliable replacement for the fat lady.</p><p><a href="https://medium.com/@bgrose25/how-to-teach-service-design-using-wands-wizards-owls-and-hogwarts-a8043face626">Read Part 2 — Future Blueprinting 101</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AsPHV2VsVoxz7cijz6xKqA.jpeg" /><figcaption>Blue Start Team’s Blueprint (Thanks Jack)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i_7ImoNHePU8y-llGWxQHQ.jpeg" /><figcaption>Yellow Start Team’s Blueprint (Thanks Charlotte)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*kvizjiSdXwBUWrIRdTVTlA.jpeg" /><figcaption>Big thank you slide.</figcaption></figure><p><a href="https://medium.com/@bgrose25">Ben Lyons-Grose</a> is a cat-enthusiast, a tea-advocate, and a novelist turned designer.</p><p>He is also Head of Service Design and UX at Methods, a digital agency that works with government to make public services better.</p><p>Get in touch at <a href="/service/mailto:ben.lyons-grose@methods.co.uk">ben.lyons-grose@methods.co.uk </a>if you want to find out more about Methods, service design, blueprinting, or Harry Potter.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=660bb08f9da3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to make good decisions.]]></title>
            <link>https://uxdesign.cc/how-to-make-good-decisions-e33bcf8511f6?source=rss-864ef1bd60ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/e33bcf8511f6</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[decision-making]]></category>
            <dc:creator><![CDATA[Benjamin Grose]]></dc:creator>
            <pubDate>Wed, 10 May 2017 17:31:10 GMT</pubDate>
            <atom:updated>2017-10-04T15:23:47.557Z</atom:updated>
            <content:encoded><![CDATA[<h4>What stripping a 150-year-old beam taught me about life, love, and product design.</h4><p>In the latest chapter of my adult life called ‘Home Renovation’, I had the pleasure of stripping the paint from a 150-year-old oak beam in my living room.</p><p>It was a long and cathartic learning experience that taught me some valuable lessons about decision making — a very elusive but important skill, particular across the disciplines I’ve found myself entangled in over the course of my career (UX, product strategy, football, novel writing, lunch, service design…).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9oVvlGO_6Ez676nJ2O2RHQ.jpeg" /><figcaption>Towards the end of the cathartic experience.</figcaption></figure><h4>So who the fuck decided to paint this lovely old beam?</h4><p>I started by applying a layer of <a href="https://www.google.co.uk/search?q=Nitromors&amp;oq=nit&amp;aqs=chrome.0.69i59j69i57j0l4.1747j0j1&amp;sourceid=chrome&amp;ie=UTF-8">Nitromors</a>. I wanted to buy <a href="https://www.google.co.uk/search?q=Nitromors&amp;oq=nit&amp;aqs=chrome.0.69i59j69i57j0l4.1747j0j1&amp;sourceid=chrome&amp;ie=UTF-8#q=Peelaway">Peelaway</a> as it had better reviews, but nobody stocked it. Nitromors is about £10 from B&amp;Q, the reviews say it’s a bit shit. It sort of was. I wouldn&#39;t buy bucket loads of it straight up. Buy a small batch and test it. There’s lesson one about good decisions: test the water if you can. Don’t buy the whole hog without tasting a bit of it and seeing if you like it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AKrAaw3CV_r_z_LA9NFHaw.jpeg" /><figcaption>This is what it looked like after the Nitromors had been to work and I’d give it a good scraping with a combination of two different scrapers and a chisel.</figcaption></figure><p>The Nitromors worked well for the first layer. It justified the investment, even if it didn’t live up to its promise on the tin. As in, it let me know that there was not only another layer under the first, but another layer on top of that one.</p><p>This was my revelation moment — hanging off a wobbly ladder in a Victorian house, my safety glasses fogged up and my throat dry.</p><p><strong>Someone had made the decision to paint this lovely old beam, not just once, but three times. Three times!</strong></p><h4>The fact of it is…</h4><p>It took about 50 hours for me to remove all the layers of paint from this old piece of wood.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AAZ-iL3Fzm9il3fxz6JOCg.jpeg" /><figcaption>A good 1o man hours in.</figcaption></figure><p>That’s a lot of hours for a man to reflect. I spent most of that time wondering about the story behind the madness of such a decision that was, many years later, causing me such grief in extended man hours. I also thought a lot about what this experience had taught me about decision making…</p><p>And the fact of it is: your decisions impact everyone (usually someone who you have never met, who could be living in another generation) so make sure they are the right ones. This applies to anything — love, football, lunch, product design, cats.</p><p>You don’t pay for your bad decisions. Other people do. It causes <strong>them</strong> pain, not you. In a case like my 150-year-old beam, the decision maker doesn’t care, they’ve sold the house and the consequences of their decision along with it. Another sucker 100 years later is the one who has to try and put right what they did wrong.</p><blockquote>So here’s the thing — approach something, anything, with this in mind — how is this decision going to affect someone else, and if it’s a bad one, how difficult will it be to put right?</blockquote><h4>About decision making.</h4><p>There’s a reason “I should have…” is common phrase. Hindsight is a bitch. So here’s the thing — approach something, anything, with this in mind — how is this decision going to affect someone else, and if it’s a bad one, how difficult will it be to put right?</p><p>There was a reason the best goalkeepers on the old Championship Manager PC game had 20/20 decision making. Oliver Kahn was unbeatable because of that stat alone. Decision making is an important life skill — integral across most (if not all) professions, and especially in the UX and product design industry. We design and build these experiences, but rarely are we the ones who have to use them. We move on to the next project, the next thing. It’s our users who have to deal with the consequences of our decisions. So we should be doing everything we can to make the right ones.</p><p>Saying that…</p><h4>It’s totally ok to make bad decisions.</h4><p>It’s alright to make bad decisions, as long as you learn from it. We’re human, after all. We don’t always make the right choices. But if we do make a wrong one, it’s not the end of the world. Live and learn and try again. It’s unlikely (unless you’re an idiot) that you’ll make the same bad decision twice.</p><h4>People will try and help you with decisions.</h4><p>You should always ask for help if you need it, but the real skill is knowing <strong>who to listen to </strong>and <strong>who not to listen to</strong>.</p><p>For example, many years ago I was working in two country pubs (say, The Crown and The Red Lion) part time to save money for a round the world trip. After a week, both offered me a full-time job. I chose the one that was closer to home, because I was too poor to own a car so I needed to cycle. Plus it was winter, so it was snowing a lot and the roads were perilous, especially at 1am after a pint or two of nourishing West Berkshire ale. But one of the locals at The Crown, the pub I’d decided to turn down, thought I had made the wrong decision.</p><p>“There comes a moment in your life when you look back at a decision and see it was the wrong one,” he said to me.</p><p>This <strong>wasn’t</strong> that time for me. Ignoring his opinion and deciding to go to The Red Lion was the right decision. He was biased. He didn’t like the other pub. And he didn’t really know me. I’d only served him beer for a week, after all. So, he didn’t have any context at all behind the factors that led to my decision.</p><p>So yes, we’re idiots not to ask for advice about decisions (just like we’re idiots not to test and validate our design decisions with actual users before rolling them out), but sometimes you have to know who to ask, and take what they think with a pinch of salt, especially if they don’t have all the context.</p><h4>What I’ve learnt about decisions, and how this applies to product and service design.</h4><p>To break it down then:</p><ul><li>You don’t pay for your bad decisions, your users do</li><li>Make decisions with data (if you can)</li><li>Make decisions with insights (always)</li><li>Teams produce better products than lone wolf designers</li><li>Teams <em>can</em> make decisions</li><li>Talk to people, and ask for help if you need to</li><li>Only listen to the right people</li><li>Test things with the right people, don’t just test for the sake of testing</li><li>Gut is important. If you are stuck, go with your gut. If you are wrong…well you’ll know next time</li></ul><p>But finally, and probably most importantly:</p><ul><li><strong>Problem solving</strong> and <strong>decision making</strong> are two integral and closely-bound areas of expertise that play out in tandem across the experience design process. If you want to be a good designer of anything you need to embrace and refine both these skills, which starts with learning as much about them as possible. A good place to start is with a some advice from two masters: Don Norman’s <a href="https://www.amazon.co.uk/Design-Everyday-Things-Donald-Norman/dp/0465050654"><em>The Design of Everyday Things</em></a><em>,</em> and Dave Trott’s <a href="https://www.amazon.co.uk/One-Plus-Equals-Three-Masterclass/dp/1447287037"><em>One Plus One Equals Three: A Masterclass in Creative Thinking.</em></a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*rGIOB3dSBlOeDSpmRa6zbQ.jpeg" /><figcaption>The experience design quadrant. How to make sure you are designing and building something people actually want.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*v5lbFDjVe5E9xPw0eAAzlQ.jpeg" /><figcaption>The experience design process (adapted from the Human Centred Design Process). How to practically approach and answer the questions in the quadrant above.</figcaption></figure><h4>And remember, we all have a choice.</h4><p>We all have a choice in anything. Making a decision (even if you make the wrong one) is better than not making a decision at all. Although, I do wish the guy who started the trend of painting my lovely old oak beam had thought twice before doing it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*apuiuwllvKCpoHBb0jy0SA.jpeg" /><figcaption>A mess, somewhere sort of close to the end.</figcaption></figure><h4>Quick word from a master.</h4><blockquote>“If you want to hire great people and have them stay working for you, you have to let them make a lot of decisions and you have to be run by ideas, not hierarchy. The best ideas have to win, otherwise good people don’t stay.”</blockquote><blockquote>Steve Jobs</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dqwU7YOIanMkMbVwFbHijg.jpeg" /><figcaption>Jobs was a pretty bold decision maker.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*aNPBhln7iDMY8qRcmoyCfA.jpeg" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e33bcf8511f6" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-make-good-decisions-e33bcf8511f6">How to make good decisions.</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ben’s rumble]]></title>
            <link>https://medium.com/strat-boiz/bens-rumble-b06c12fb323d?source=rss-864ef1bd60ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/b06c12fb323d</guid>
            <category><![CDATA[advice]]></category>
            <category><![CDATA[renovations]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[life]]></category>
            <dc:creator><![CDATA[Benjamin Grose]]></dc:creator>
            <pubDate>Fri, 28 Apr 2017 13:43:14 GMT</pubDate>
            <atom:updated>2017-04-28T13:43:14.651Z</atom:updated>
            <content:encoded><![CDATA[<h4>What renovating a Victorian house has taught me so far about how the world works</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eFHwM-y4HiD0SO3pcc-v1A@2x.jpeg" /></figure><ul><li>Whatever you have in mind for how much something is going to cost you in total, triple it. If you haven’t got enough money, make emergency arrangements for acquiring more money before you begin. Have a contingency. And triple that contingency</li><li>Whatever date you had in mind for completion of said task, triple it. The best things take time</li><li>Get your hands dirty. Don’t just pay someone else do everything for you. Taking part leads to a greater sense of ownership, and an understanding about how things work and how they are put together</li><li>Trust your wife/husband/partner. She/they know better than you</li><li>Stuff will go wrong. You will fail. And it doesn’t matter if you do. It’s how you deal with adversity that counts</li><li>Remember <em>why</em> you set about to do something. Stuff gets hard. Things happen. Goals change. People change. Don’t lose sight of the why. This is the most important thing. If you can’t remember why you are doing something, it’s not going to be any fun, or any good</li><li>Shop around for stuff. Don’t jump at the first offer for anything, just because it’s easy or convenient. We have this thing called the internet now. Use it</li><li>Talk to people who have done it already. There’s no shame in asking for advice on anything</li></ul><p><strong>Coming next week…</strong></p><p><strong>The editorial…</strong></p><h4>How to make better decisions: What stripping a 150 year old beam taught me about life, love, and product design.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b06c12fb323d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/strat-boiz/bens-rumble-b06c12fb323d">Ben’s rumble</a> was originally published in <a href="https://medium.com/strat-boiz">Strat Boiz</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Making of Mont Blanc Cardboard]]></title>
            <link>https://medium.com/@bgrose25/the-making-of-mont-blanc-cardboard-2c73d39c1eaa?source=rss-864ef1bd60ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c73d39c1eaa</guid>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[virtual-reality]]></category>
            <category><![CDATA[google-cardboard]]></category>
            <dc:creator><![CDATA[Benjamin Grose]]></dc:creator>
            <pubDate>Thu, 26 Jan 2017 12:44:34 GMT</pubDate>
            <atom:updated>2017-01-26T12:44:34.752Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wnY0sEVNV8rr0TWwPUf3FQ.jpeg" /><figcaption>Mont Blanc Cardboard poster image</figcaption></figure><h4>How we brought the ‘Monarch of the Mountains’ to your web browser</h4><p><a href="http://g.co/montblanccardboard">Mont Blanc Cardboard</a> is mobile VR experience built by Phantom and Google Brand Studio. It’s not an app, like most VR experiences for Google Cardboard. This works directly from your web browser. No download needed.</p><p>If you’re reading this on your mobile, I heavily recommend you <a href="http://g.co/montblanccardboard">tap this link</a> and climb the mountain. It even works without a Google Cardboard, but if you have one of those to hand, even better. You’ll get the full immersive experience.</p><p>This is the story of how we built it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LKdEIWlNaLwRdKIx36OphQ.png" /><figcaption>Mont Blanc Branded Cardboard</figcaption></figure><p>Apparently there are more pubs in York than there are days of the year. Not including bars, or even restaurants that sell alcohol. Just pubs alone. Good old-fashioned English ale houses.</p><p>It was in one of these pubs, that sometime in February, shortly after Mont Blanc Cardboard had launched, I was proudly showing anyone who was even vaguely interested — our Airbnb hosts who we’d met up with for a drink, my cousin, the bar staff, complete strangers — how you could climb to the summit of Mont Blanc using only your smartphone.</p><p>“It works in browser! You don’t even need to download an app! You don’t even need cardboard! Look!” And I panned the phone screen around so they can take in the view of the alps. “It’s using gyro!”</p><p>“So what did you actually do on this?” asked someone.</p><p>“Good question.”</p><p>I then had to try and explain what a strategist does. Which after a few beers is quite hard, so I just settled with — “I looked after the content. I wrote the script, told the story, and even went to Paris to meet Patrick Gabarrou.”</p><p>They all looked completely indifferent to the name. Apart from my wife, who had heard this twelve times already, and was giving me a look that said — <em>you’re embarrassing yourself, dear.</em></p><p>“He’s the French guy who guides you up the mountain. The narrator. I met him in Paris. I had to go over there to record the script…”</p><p>I’m interrupted by the last orders bell, and it was my round, so I had to put my phone away and stop the story there. For now.</p><h4>Before the climb</h4><p>What became Mont Blanc Cardboard actually started life as more of a Mont Blanc desktop trek that also had a Google Cardboard spin off. The idea in its first incarnation looked a little bit like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*BNan5aMe8WOCWvXT7_RCBA.jpeg" /><figcaption>An early concept for the Mont Blanc Trek, courtesy of Jamie Nicoll (Creative Director at Phantom)</figcaption></figure><p>Our original pitch was the next generation of the <a href="https://www.google.co.uk/maps/about/behind-the-scenes/streetview/treks/yosemite/">Yosemite Dawn Wall climb</a>, and it spanned desktop, mobile, and Google Cardboard. A few weeks later, the brief had developed to focus primarily on Google Cardboard, which was actually a very good thing. It meant we could concentrate all energy on making the Cardboard experience a truly groundbreaking experience. It allowed us, in Creative Director talk, to “shoot for the sky”.</p><p>The first tasks were far less glamorous.</p><p>This was our first time tackling VR specifically for Google Cardboard, so our development team invested in plenty of research and technical scoping ahead of build. But a bigger issue was that, due to timeframes (Mont Blanc needed to launch in November to coincide with a larger event in Paris to celebrate Mont Blanc as a cultural landmark) we didn’t actually have enough time to even build it as a Cardboard app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lamE9OyHb227D4bb284qzQ.jpeg" /><figcaption>Mobile cardboard view</figcaption></figure><p>Our solution was to propose something that hadn’t ever been done before, but our development team believed could actually be built quicker than an app and within the tight timeframe: build Mont Blanc <strong><em>in browser</em></strong>. No download needed. Calibrated across all latest devices. iOS and Android. This brought a whole host of challenges that the dev team had to overcome. To go into a bit more detail, we had to render each panoramic scene into a 3D sphere environment and split that into a stereoscopic view. We used some great webGL (three.js) technologies to help us achieve this. Then each of the hotspots and actions had to be <em>hand placed</em> in each 3D scene to make sure they were geographically accurate, and also looked right in a cardboard viewer. On top of this, we used the HTML layer of the browser to create a HUD that provides users with other key information, such as coordinates, altitude, temperature, and heartbeat. Having the HTML layer on top of the 3D scenes really helped build on the sense of depth that VR already creates. Visual elements aside, audio was a monstrous task — especially as Android and iOS devices behave very differently. Playing multiple layers of audio in each scene — including voice overs, atmospheric tracks, event-based sounds, with synced subtitles in both English and French, across all the latest devices and software— was a huge technical challenge for the team to overcome.</p><blockquote>The beauty of this project is that we were pretty much building the boat as we sailed it…</blockquote><h4>Content curation and UX</h4><p>The other key task was content.</p><p>I’m always of the opinion — having been stung too many times on projects where you’re waiting right up until the bittersweet end to receive content — that having too much content is way better than having too little. Even better if you already have that content from the start of a project, which was the case with this one. All the visual footage of Mont Blanc and the surrounding massif had already been captured before we came on board. US film production company, Sender Films, had captured close to 30 amazing panoramic scenes of athletes doing their thing on Mont Blanc, and the Google Street View team also had 360 degree footage of the entire route up the mountain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xtRlnjK8zQU461qQbNCl7g.jpeg" /><figcaption>Run with Killian pano</figcaption></figure><p>We decided pretty early on that it made sense to use the famous Goûter Route as the basis for the navigation, but the difficulty then was deciding which footage we should use to tell the story, how we could involve the best of the special athlete shots, whilst keeping the UX intuitive. Early proposals for the UX journey had 6 to 8 stages of the route to the summit, and 25 special panos. We ended up with 5 Goûter Route stages and 6 athlete panos, although the rest can be viewed on the <a href="https://www.google.co.uk/maps/about/behind-the-scenes/streetview/treks/mont-blanc/">Mont Blanc desktop site</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*4vJQOPuCIlDz1XcgRTOSCA.jpeg" /><figcaption>Early UX map featuring most of the content captured on the mountain and surrounding massif</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*ptzy6aLvEPJmELW4VXJdQA.jpeg" /><figcaption>A pano that didn’t make it into the experience.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*0ACIWo3itJef5zHY9EnusA.jpeg" /><figcaption>Another pano that didn’t make it into the experience.</figcaption></figure><p>In terms of the content detail, we took the same approach as we took to the footage — build up lots of content and then strip it back and refine it in the latter stages. We realised that on a cardboard experience, users simply aren’t going to stick around long enough to read lots and lots of text hotspots, no matter how interesting they are. With VR, the more there is to see, the less the audience remembers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MbXjWckOeZkKj__XLW44Lg.jpeg" /><figcaption>Sunset Jump pano with compass points plotted — key for design to dev asset handover</figcaption></figure><p>So 0n top of the visual footage that are the pieces of the experience, there are layers of different sound files (music, atmos, commentary, narration, custom SFX), text hotspots, image hotspots, and audio hotspots — across both French and English. In terms of sheer volume of content, it was a beast. How did we manage it? Through an epic content matrix that saved our lives many times over, especially when it came to the different sound files. Not only did this show the information architecture of the experience, including all the screens leading up to the first stage of the climb, but also detailed key HUD info in the HTML layer of the UI, such as coordinates, temperature, and heart rate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aItQLIhNS4Fgo6XMmhgPSg.png" /><figcaption>Our epic content matrix</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3mw3c6ewGpQsfk1u-5EcyA.png" /><figcaption>The layers of content in the experience were built out into each stage</figcaption></figure><blockquote>With VR, the more there is to see, the less the audience remembers.</blockquote><h4>UI design</h4><p>There was also a lot to think about when it came to designing the experience, especially with the UI. We wanted users to feel like they were climbing Mont Blanc wearing a set of smart ski goggles that feed you information as you climb. We also needed a way for users to navigate the experience without ever touching the screen, and we settled on a timed cross hair which you use to interact with icons(hotspots) in each scene. This brought with it a host of new challenges we had to overcome.</p><p>The key question we asked ourselves was: ‘<em>How do we make it clear to the user what they are supposed to do and how they go about doing it?’</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i4nfxXpOGlRcPsXsr2Q-Kg.jpeg" /><figcaption>Mont Blanc icon legend</figcaption></figure><p>There are 6 different types of icons in the experience (discounting the flag on the summit to finish the experience and see your mountain stats). Some, such as the information hotspot and the audio hotspot are recognisable icons, especially if users are already familiar with Google Treks. Others, such as the athlete icon which takes users off to the special panos, required a little more thought and a bit of user testing to get right.</p><p>We experimented with several different options for the icons that move you up and down the mountain, and take you back to the Goûter route from the athlete panos. Following user testing, we came up with the solution of making these icons a different colour so they stand out, and also animating the ‘up’ and ‘down’ arrows to attract the eye.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*3sAq3l5h8j1J_-xoGoPOoA.jpeg" /><figcaption>Final icon for ‘Going up’</figcaption></figure><p>We also experimented with the loading map which appears when a user jumps between scenes. From a UX perspective, we needed to make it clear that you were moving up and around the mountain, and also give you context about where you’re being taken to next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*xEt6_nQZSzu2JAZnok7ZpA.jpeg" /><figcaption>An alternative loading map with height scale</figcaption></figure><p>We tried several options, which included showing a height scale on one side, and a tooltip that fills from bottom to top to indicate loading, but we eventually decided to keep it simple. Highlight the route to the next scene to show the progression, and indicate with the same green colour the panos that users have already visited.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TpuQ2NfSrayJbbRUjxCIyw.gif" /><figcaption>Final Mont Blanc loading map</figcaption></figure><h4>To Paris</h4><p>For me, there are two things that make this experience stand out as something that I’m proud of — and that’s on top of the fact that we did things that haven’t been done before to deliver the best experience possible.</p><p>One is the detail and depth we went into with the sound design to bring each scene to life.</p><p>The other is the inclusion of Patrick Gabarrou, your high mountain guide and narrator on the journey up to the summit, who really helped bring another layer of authenticity to the experience. As scriptwriter, the duty fell to me to head to France to meet Patrick and run through the script before recording it in the YouTube space in the Paris Google office. So one cold morning in November, I found myself on the second earliest Eurostar to Paris — frantically still editing the script on the train over a croissant and strong cup of tea. Patrick was being flown in from Mont Blanc, fresh from his latest ascent to the summit. I spent the first hour going through the script with him, fact-checking various bits and pieces, and marking which sections I needed his help with — namely what you can see and feel when you get to the summit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*LKKQRfqkGNHkFRSc3McokA.jpeg" /><figcaption>Patrick familiarising himself with the script</figcaption></figure><p>I could speak no French (beyond asking the direction to the swimming pool), but fortunately, Patrick could speak pretty good English. So we managed, and I was able to give him enough direction for him to understand what it was we wanted. He was fantastic, improvising and generally improving the script by bringing his own ideas and personality to the whole thing — which is just what we hoped for.</p><p>Before I left, I asked him how many times he’d been up Mont Blanc, and his answer (around 5,000 times) completely blew my mind. But to him, it wasn’t anything special. It’s his day job. To risk death every day. To safely guide others up one of the most dangerous, accessible climbs in the world. “Benjamin,” he said before he left to go back to Chamonix, “just let me know when you are ready to make the climb for real, and I will take you up Mont Blanc.”</p><h4>In the sound studio</h4><p>The other part of the experience that I believe made a real difference was the care and attention that went into the sound design. We worked very closely with Across the Pond, and Jungle Studios to plan and capture this. Like our experience with Patrick, my brief that detailed the story of each scene and what we wanted to tell, only went so far.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*LZWlhSZimMoNv6cmJXm_ig.jpeg" /><figcaption>SFX brief detailing the different layers</figcaption></figure><p>Cullum, our talented sound engineer, brought his own ideas to the table which helped to push this experience as far as we could. It’s Cullum that you can hear in stage 2 of the Goûter Route, Arete Du Goûter, warning of the rockfall, and some members of the team also made it onto the experience with a little cameo appearance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*tcspoMlH5DVECjdbGr4mKw.jpeg" /><figcaption>Producer James in the studio practising his line “Give me some slack!”</figcaption></figure><p>In terms of the music, we settled on the opening piece pretty early on — the very otherworldy, almost space-like track that you hear at Tête Rousse, but it took a while to find a piece we liked for the summit.</p><p>When Phantom’s Creative Director (Jamie Nicoll) and I first heard the piece that we eventually settled on for the summit, we weren’t totally convinced by it, and earmarked two potential options, pending a decision. However, once we heard the music in situ, it just worked. I think I actually cried the first time I got to the summit, and the very Games-of-Thronesy music kicked in. We’d done so much to get there.</p><h4>Learnings and recognition</h4><p>We’ve been lucky enough to pick up two awards for the project so far — an <a href="https://thefwa.com/cases/mont-blanc-vr-experience">FWA Mobile</a>, and Best Interactive Design at the <a href="https://www.designweek.co.uk/issues/13-19-june-2016/design-week-awards-2016-winners-full/">Design Week awards</a> — but it’s not about the winning. Yes it’s nice to pick up recognition for your work, but I think the best thing to happen since the project launched was actually a meeting we had as a team about 5 months after the project wrapped up.</p><p>We all sat down in the studio with some sticky notes, pens, and a blank wall and discussed what had gone well, what hadn’t gone so well, and also a list of actions items. Ultimately, we came out of the meeting with an invaluable list of learnings to take forward into the next project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/1*YGZX7MvO9vo3vHgQZgvlHQ.png" /><figcaption>Design Week Awards</figcaption></figure><h4>The new medium</h4><p>Back to the pub in York (by the way, if you’ve never been to York I suggest you go, it’s a beautiful city).</p><p>There was a reason I wanted to show it to everyone in the pub (and have shown it to everyone in more than just that pub in York since it launched). Simply — I’m proud of it, it’s probably the best thing I’ve ever done, and I’m proud of the whole amazing team at Phantom and Brand Studio that built it.</p><p>VR is such a new medium, and it’s an exciting one. There are no rules yet, and it’s down to us — the creators of experiences for this medium — to learn them and lay them down as we go. I was in LA several years ago and I was walking through Hollywood when I heard a really drunk (or just crazy) guy say as he looked up at the moon — “We’re not in a film, We’re not in a book. We’re not in a joke.” I wrote it down and later used it in a novel, but I was reminded of this guy and his words very recently when I was at the Cannes Lions Festival.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Es6cWNjYFZwpq3iZ3OqmZA.jpeg" /><figcaption>Cannes</figcaption></figure><p>We entered Mont Blanc into the Digital Craft category, and although we didn’t win a Lion, it was amazing to just see our work alongside the best of the industry in such an iconic festival. Talks from Google, Samsung, The Mill, MediaMonks, they all focused on VR and how it will transform our lives — whether through story, art, memory, distraction therapy, psychology…VR is a new medium, totally unlike any other. Books, films, jokes, plays — these mediums are very separate: from real life, and from the people who use it. They are just vessels, instruments that house a narrative. With VR, that’s not true anymore. With VR, the medium and real life, the medium and us (as creators and consumers) are closer than ever before. The link between us and the medium has become far more congruous.</p><p>We can now exist <em>inside</em> our medium. As participants in the story.</p><p>And that’s exciting.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FTG8SpS5U-xc%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DTG8SpS5U-xc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FTG8SpS5U-xc%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/821dd62f294f370bd6d4bfa484b2c9fc/href">https://medium.com/media/821dd62f294f370bd6d4bfa484b2c9fc/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c73d39c1eaa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Digital and literature]]></title>
            <link>https://medium.com/phntmldn/digital-and-literature-it-s-more-than-just-publishing-an-ebook-100b2faaa235?source=rss-864ef1bd60ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/100b2faaa235</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[literature]]></category>
            <category><![CDATA[books]]></category>
            <dc:creator><![CDATA[Benjamin Grose]]></dc:creator>
            <pubDate>Thu, 28 May 2015 14:04:17 GMT</pubDate>
            <atom:updated>2016-03-17T18:01:14.048Z</atom:updated>
            <content:encoded><![CDATA[<h3>It’s more than just publishing an eBook</h3><h3><strong>Great and terrible things can happen when we merge art and technology</strong></h3><p><strong>It’s an interesting time</strong> in publishing. We seem to have almost got past<strong> </strong>this<strong> </strong>‘uncertain’ period in the business, this ‘turmoil’ when digital finally entered the publishing industry and everyone started to panic. In the last few years we’ve heard all sorts of apocalyptic predictions, but the fact is nobody really knows what is going to happen. We’re in the middle of a revolution, and who knows when that’s going to come to an end. But we can speculate, of course.</p><p>The current state of things are — eBooks are now a staple part of any publishing house, everybody seems to have a Kindle (or at least a device which can turn into a Kindle), and the market share figures of eBook sales are slowly growing. In 2015 the ebook market <a href="http://www.theguardian.com/books/2015/feb/01/the-ebook-is-dead-long-live-print-digital-sales">is predicted to be worth £350m</a>.</p><p>But the book is still going strong. Yes, more fiction has moved to digital, and physical books sales in general have declined <a href="http://www.theguardian.com/books/2015/jan/13/sales-printed-books-fell-150m--five-years">by £150m in five years</a>, but there have been a number of resurgences — the sale of trade paperbacks increased in the first half of 2013, even if the hardback was down. Bookshops perhaps aren’t the bustling, vibrant places they once were — but they are still here.</p><p>So we are still buying books. Not everybody has a Kindle, yet. Publishing is not dying, it is simply undergoing a metamorphosis of the like it hasn’t seen for a long time. And that brings me to another issue…</p><h3>Is this good news or bad news for writers?</h3><p>Long gone are the days of the booming 80s, when the Big Six of the publishing world threw huge sums of money at the likes of Martin Amis, Ian McEwan and Julian Barnes, and across the water, writers such as Bret Easton Ellis, Jay McInerney and Tama Janowitz paraded around New York as the ‘literary Brat Pack’ because they’d written cool books of the zeitgeist. These days a writer is lucky to receive an advance that even tip-toes into five figures, let alone the mythical six and seven figure deals of the past. There are exceptions to this rule, of course. There is no less writing talent around than before, but it is an increasingly rare thing when talent combines with a lot of luck to land a writer a big pay day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*O2smSRjUkZD1H7oneD_tjQ.jpeg" /><figcaption>Jay McInerney, Tama Janowitz and Bret Easton Ellis in New York in the 1980s.</figcaption></figure><p>The number of writers who make a living from purely writing novels is pitifully small (something like 2%) and there have been many <a href="http://www.theguardian.com/books/2014/jul/08/authors-incomes-collapse-alcs-survey">articles full of doom and gloom published about this recently</a>. It’s getting increasingly more difficult to get into that bracket, even though there are now more opportunities and platforms to sell your book beyond the traditional high street retailers. Amazon has transformed the publishing landscape, everybody has decided to start writing a book, and the market has hence become saturated with all sorts of questionable literature. Some of it is very good, of course. Some of it is also very bad. And then there’s a lot of stuff in the middle. Lots and lots of stuff. Millions of eBooks are available on Amazon alone. We’ve moved from a business dominated by a few conglomerates and their gatekeepers (literary agents), to smaller houses looking to inject a bit of the esoteric and overlooked into the marketplace, to the start of ‘Everyone Wants to be a Writer Syndrome’ and the self (or vanity) publishing era that followed it. And now — we have the eReader, the eBook and platforms such as Amazon’s Kindle Direct Publishing.</p><p>There are many benefits of publishing digitally with Amazon. The royalty rates a writer receives if they publish a novel with Amazon are more than a traditional publisher will offer you. Amazon give you a maximum of 70% on sales and a minimum of 35%, whereas the best you are likely to receive from a publishing house is 15% on hardback books, and 8% on paperbacks.</p><blockquote>“Please, no matter how we advance technologically, please don’t abandon the book. There is nothing in our material world more beautiful than the book.”</blockquote><blockquote><em>Patti Smith</em></blockquote><h3>What next?</h3><p>This is the bit where digital comes in. And this is where we writers should all start getting excited again. Because the good old days of huge advances, ‘rock star’ lifestyles, legendary book tours, and that romanticised dream of getting on the tube and seeing everyone reading your book, are all but gone. With technology, we are actually reading more than ever, even if what we’re reading isn’t as highbrow as it used be. And with eReaders, the act of reading has become more clandestine. We can download and read whatever we want, whether that by <em>Mein Kampf</em> (which has been rocketing up the UK eBook charts recently) or <em>Fifty Shades of Grey</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*wptq3wfCAeLb9KaTy7HPug.jpeg" /><figcaption>Readers on the tube</figcaption></figure><p>This was one of the big trends in recent years — we saw an increase in the sale of erotica to the point where everyone decided they had a hot and kinky tale of whips and chains in their locker waiting to come out. Another trend was eShorts, or Kindle Singles, which Amazon describe as ‘Compelling Ideas Expressed at their Natural Length’ — a piece of writing typically between 5,000 and 30,000 words in length. Kindle Singles is a marvellously simple and brilliant idea. Why? Because they’re not simply eBooks. <a href="http://www.theguardian.com/books/booksblog/2013/sep/05/amazon-kindle-singles-short">They’re pieces of writing that are often unpublishable in any other format, and they fill what was formerly quite a sizable hole in publishing </a>— consisting of forgotten, useless novellas, short memoirs, and short stories that are commonly too expensive for a traditional publishing house to print. There’s no special technology involved here. That’s the beauty of it. It just makes sense.</p><h3>Great and terrible things can happen when we merge art and technology</h3><p>Technology has changed the way publishers are marketing their products and it has changed the way that we consume products, but what about the product itself? Why aren’t we talking more about that? It’s much more exciting. This could be the year when we truly start to realise <a href="http://www.theguardian.com/culture-professionals-network/culture-professionals-blog/2014/mar/14/survival-uk-arts-culture-digital">the great things we can do with art and technology</a>. Because digital is more than just publishing an eBook or sending a few tweets. We could use digital to improve or enhance the reading experience, forging ahead into tantalising and unexplored territory to create something that has longevity and innovation. That is more than just a gimmick.</p><p>But this is very tough, and something that<a href="http://www.theguardian.com/profile/jennifer-rankin"> Jennifer Rankin</a> discussed back in 2013 in <a href="http://www.theguardian.com/books/2013/oct/14/books-immersive-stories-app-the-craftsman">her article about how publishers and authors are trying to break through in the world of digital and literature</a>. So it is starting to happen. The industry is slowly, slowly adapting to the new world. We have such enterprises as Amazon’s Kindle Single, unique publishing platforms such Medium, (which is remarkable in how it has bridged the divide between publishing, reading, and technology), and even publishers determined to bring something new to the market, such as <a href="https://thepigeonhole.com/">The Pigeonhole</a>, which is just as much of a community as a publisher — offering serialised online books and printing physical editions based on popularity. Another recent venture is <a href="https://beta.macguffin.io/">MacGuffin</a> — launched by Comma Press, it allows authors to self-publish short pieces of writing, both as text and audio file, and provides detailed analytics to show where readers stopped reading. It’s also worth mentioning the likes of <a href="http://www.aitkenalexander.co.uk/">Aitken Alexander’s new website</a> which breaks the mould of what a literary agency’s site has been and is expected to be (namely where potential authors go to get agents’ contact details and submission preferences) and looks at what it could be — a content hub, filled with more than just news of book deals, but fresh, interesting and relevant content from the publishing world, often curated from elsewhere on the web. From the revolutionary and forward-thinking, to the controversial — such as <a href="http://www.theguardian.com/technology/2009/jun/24/twitter-literature-twitterature">Penguin’s hotly debated and highly controversial venture Twitterature</a>, which involves squashing classics into twenty tweets or less, or Clean Read, the app which<a href="http://www.theguardian.com/books/booksblog/2015/mar/16/ebooks-app-clean-reader-replace-swearwords"> replaces ‘unclean’ words with more palatable alternatives</a> (which the writer in me thinks is utterly diabolical, but the digital strategist in me admires for their nerve, determination and creativity). From the mad and radical to the very basic. Building microsites or apps can be very effective, going beyond just a marketing tool and way of shipping more copies, and actually supporting or even expanding on a novel by offering extra chapters or outtakes, which are great for building an audience and tying readers over until the next novel. All of these things are great, but I think they are just the beginning — the small pitter-patter of stones before an avalanche. So much is possible with digital and literature, and as much as I think this is a good thing — as a bibliophile and book collector myself and one who doesn’t own an eReader — I hope that the paperback will survive too. Beautiful physical editions of novels will always find homes when there are people around who still appreciate them. They will look after themselves, like they always have, and hopefully bookshops will also have the staying power and ingenuity to survive the recent purge. The key is going to be how the old world exists alongside the new world, and for me that is where the potential and the excitement is.</p><p>So hopefully in the next few years we’ll be reading more articles about some amazing ventures, ideas, and inventions in the world of literature and publishing — as opposed to just the same old news stories about the death of the novel, the death of the eBook, or the death of the writer himself as machine written literature tops the bestseller chart for the first time, and the year after goes on to claim the Booker Prize.</p><h3><a href="http://www.bbc.com/culture/story/20150122-could-a-robot-write-a-novel">C<strong>ould a robot really write a nov</strong>el?</a></h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=100b2faaa235" width="1" height="1" alt=""><hr><p><a href="https://medium.com/phntmldn/digital-and-literature-it-s-more-than-just-publishing-an-ebook-100b2faaa235">Digital and literature</a> was originally published in <a href="https://medium.com/phntmldn">Phantom</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kindle Singles]]></title>
            <link>https://medium.com/@bgrose25/kindle-singles-7581d28ac025?source=rss-864ef1bd60ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/7581d28ac025</guid>
            <dc:creator><![CDATA[Benjamin Grose]]></dc:creator>
            <pubDate>Thu, 31 Oct 2013 22:54:34 GMT</pubDate>
            <atom:updated>2013-10-31T22:54:34.637Z</atom:updated>
            <content:encoded><![CDATA[<h4>High Time to Get into Bed with the Enemy</h4><p>It’s the latest venture by super company Amazon: Kindle Singles — typically between 5,000 and 30,000 words and described as ‘Compelling Ideas Expressed at their Natural Length’ — it may just be the best thing to happen in publishing for a long time. There was a time when writers/agents/publishers considered online conglomerates such as Amazon to be the arch enemy of publishing, as they were effectively killing bookshops. Traditions were being broken down, and sites like Amazon were able to offer an unlimited range of books at far cheaper prices. In effect, Amazon was testing the long standing contract between publishers and booksellers, and destroying some of the grandeur, the romanticism of being an author — going into a nice, buzzing bookshop and seeing your novel on the shelf. Then Amazon upped the stakes even more by introducing eReaders. Before long, the larger bookshops realised that if they were to survive, they had to join forces with this super power, and overnight they were stocking the whole range of Amazon Kindles.</p><p>Kindle Singles are the future. Why? Because they’re not simply eBooks. They are pieces of writing that are often unpublishable in any other format; they are filling what was formerly quite a sizable hole in publishing, consisting of the forgotten, useless novellas, short memoirs, narratives and short stories. Furthermore, Amazon are even offering much better royalty rates than you would ever see from a traditional publisher — usually an author would see around 15% on hardbacks, and barely 8% on paperbacks. Kindle Single’s authors receive 70%. So it’s not surprising that everyone is getting involved. Stephen King is one of the latest benefactors. He wrote an 8,000 word piece of non-fiction called <em>Guns </em>that was too long for a traditional article, and would eventually have seen the light of day in a number of year’s time in a collection of essays — had it not been for Kindle Singles. He submitted it on a Friday, Amazon read it over the weekend, then published it the next week. But it’s not only established writers who can benefit. Amazon look for new voices too, and any writer can approach them directly. So, if you’ve got a 20,000 word novella kicking around on your laptop that you wrote when you were an undergrad that you thought was good but everyone told you was, in terms of getting it published, a dead end — get into bed with the enemy. Send it to Amazon. It might just be the beginning of a long and happy affair.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7581d28ac025" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>