<?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 Mint Digital on Medium]]></title>
        <description><![CDATA[Stories by Mint Digital on Medium]]></description>
        <link>https://medium.com/@mintdigital?source=rss-a7de1c130adc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6tS_tagrx8ymZisjaZ0SSg.png</url>
            <title>Stories by Mint Digital on Medium</title>
            <link>https://medium.com/@mintdigital?source=rss-a7de1c130adc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:14:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mintdigital/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[SMEs: Take this opportunity to help improve UK business banking]]></title>
            <link>https://medium.com/@mintdigital/smes-take-this-opportunity-to-help-improve-uk-business-banking-e3a0d0d15a07?source=rss-a7de1c130adc------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3a0d0d15a07</guid>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[open-banking]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[sme]]></category>
            <dc:creator><![CDATA[Mint Digital]]></dc:creator>
            <pubDate>Thu, 29 Jun 2017 12:59:11 GMT</pubDate>
            <atom:updated>2017-06-29T14:25:42.471Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*kI_8W6oql_xWuCVY.jpg" /><figcaption>SMEs - register your interest here: <a href="https://goo.gl/kxEBZt">https://goo.gl/kxEBZt</a></figcaption></figure><p>Recently we announced that we’ve been appointed <a href="https://mintdigital.com/blog/nesta-open-up-challenge-open-banking">user experience partners for the Open Up Challenge</a>.</p><p>The Challenge is one part of a bigger shift toward ‘open banking’. Regulatory requirements mean that up to now the digital innovation that permeates our lives has been difficult to achieve in banking. That changes with this initiative: new open banking APIs will enable fintech and other startups to transform how small businesses manage their finances.</p><p>Twenty Challenge participants will be able to win up to <a href="http://openup.challenges.org/prize/">£1m of equity-free funding</a> and access an unprecedented data sandbox of real, anonymised customer banking data. It’s a rare opportunity for UK tech talent to be at the very forefront of innovation in arguably the UK’s leading industry.</p><p>The regulatory changes that have led to the Open Up Challenge, and the potential benefits for customers and particpants, mean that this is a landmark moment in British industry. We are one of the first countries to take this large a step towards a future of open banking, and the improved consumer choice it could offer. We can expect other countries to follow suit, with <a href="https://www.out-law.com/en/articles/2017/april/independent-body-must-lead-on-open-banking-reforms-in-australia-says-report/">Australia already taking steps in a similar direction</a>.</p><p>For these reasons, Mint is really excited to be playing a part in an initiative that uses the UK’s talent in tech to enhance its already world-leading offering in financial services.</p><blockquote><a href="https://docs.google.com/forms/d/e/1FAIpQLSfXlhfptaLqNaYIrciOsRjD2kg89gYt6srgHhdakTi4qhLTFg/viewform?usp=sf_link"><strong>SMEs: Register your interest in Open Up Challenge user-testing here</strong></a></blockquote><p>We’ll be offering participants a mix of one-to-one and group support, <a href="http://www.growthbusiness.co.uk/open-banking-fintech-firms-need-know-2551033/">with the aim of ensuring user-centred design principles</a> are factored into their product roadmaps. With UX required to sit alongside robust security protocols, we’ll use our knowledge and experience of product development to help the 20 deliver products that are both innovative and pleasing to use.</p><p>Then, during the judging phase in December 2017, we’ll be <strong>testing participants’ products with real small businesses</strong>. This will be an integral part of the Open Up Challenge’s judging process, and we’re encouraging SMEs to <a href="https://docs.google.com/forms/d/e/1FAIpQLSfXlhfptaLqNaYIrciOsRjD2kg89gYt6srgHhdakTi4qhLTFg/viewform?usp=sf_link">register their interest now</a>.</p><h4><strong>If your company is interested in testing cutting edge business banking apps and services, please </strong><a href="https://docs.google.com/forms/d/e/1FAIpQLSfXlhfptaLqNaYIrciOsRjD2kg89gYt6srgHhdakTi4qhLTFg/viewform?usp=sf_link"><strong>complete this short form to register your interest</strong></a><strong> and we’ll be in touch.</strong></h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F29a464%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F29a464%2F&amp;image=https%3A%2F%2Fe.enpose.co%2F%3Fkey%3DdRXnS9Gplk%26w%3D700%26h%3D425%26url%3Dhttps%253A%252F%252Fupscri.be%252F29a464%252F%253Fenpose&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/e3ed68bd40d0bdc96e031cbad511a4ff/href">https://medium.com/media/e3ed68bd40d0bdc96e031cbad511a4ff/href</a></iframe><p><em>Originally published at </em><a href="https://mintdigital.com/blog/open-up-challenge-user-testing"><em>mintdigital.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3a0d0d15a07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My advice on becoming a better coder — by Shoshi Roberts]]></title>
            <link>https://medium.com/mint-digital/my-advice-on-becoming-a-better-coder-by-shoshi-roberts-9629a496bf43?source=rss-a7de1c130adc------2</link>
            <guid isPermaLink="false">https://medium.com/p/9629a496bf43</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[practice]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Mint Digital]]></dc:creator>
            <pubDate>Tue, 06 Jun 2017 10:12:39 GMT</pubDate>
            <atom:updated>2017-06-13T16:19:54.961Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*JF86iGCWpk5jDT9SI7Pv5g.jpeg" /><figcaption>© Shoshi, please do not reuse without the author’s permission.</figcaption></figure><h4>The best way to become a good coder? Always be working at becoming a better coder, says Mint developer Shoshi.</h4><p><em>[Writer’s note: I made a comment at a meetup about the ‘right way’ to learn to code, and a colleague emailed me afterwards to ask what I meant. While it sounds initially dogmatic, in the end it’s very practical. This post is my effort to deconstruct what those loaded words translate to in reality.]</em></p><p>Ideally, everyone learns from a mentor or teacher who’s an excellent developer, reads things on the internet that align with best practices, and grows to form their own efficient way of coding. This is of course usually not the case.</p><p>Describing what makes a good coder is similar to describing what makes a good writer. There’s no precise formula, but there are some general rules that allow everybody to build artfully from the same foundation. People will develop different styles and preferences, which is great. No one way is right, but some ways are messier, less efficient, easier to break, or slower for the computer.</p><p>When you’re starting out, it’s difficult to determine if you’re learning from sources that are ‘good’ or ‘bad’, so you just try your best. Price here is not a measure of quality, sometimes it’s the exact opposite. When in doubt, a language or framework’s own tutorials are a good place to start.</p><p>Everybody is bound to run across a Stack Overflow page that suggests a hacky way of doing something. You’ll hopefully come to discover later that some of the things you learned are hacks and there are ‘better’ ways to do things. ‘Better’ here means more efficient, readable, performant, reusable, modular, and not exploiting any bug of the system.</p><p>I say ‘hopefully’ because noticing where there’s room for improvement in your code is the first step to being a better coder. If you stop once you’ve achieved a desired result, your learning will eventually hit a wall. Especially when technology inevitably moves on to new languages and approaches.</p><p>Over time, if you’ve developed good habits, you’ll be able to identify “bad” code by how it’s architected. In good code you’ll generally see: — less steps — readable logic — minimal looping or nested conditionals — a contextually appropriate amount of reusability</p><p>If you see the same code repeated over and over, run away. <a href="https://blog.codinghorror.com/code-smells/">Here are some other things to look out for</a>. Even if you’ve learned everything ‘wrong’ from the start, don’t panic. It’s certainly not a career killer. Unlearning ‘bad’ habits and relearning good ones can help you become a better coder in the end by giving you a greater foundational knowledge of why to make one choice over another.</p><p>While brevity is not always better, good coders may find over time that they prefer deleting code to adding code. This is often a sign that you’re able to problem solve in a more modular and reusable way.</p><p>The best way to be a good coder is to always be working at becoming a better coder. You know best where you haven’t quite hit the sweet spot in your code. Refactor the bits that give you trouble, or the ones you hate editing for fear of breaking something. Look to the parts that you might describe as ‘fragile’ and see if they can be made stronger. Dig deeper into the methods you don’t fully understand.</p><p>There are exceptions and reasons why code might have to be a certain way, but they could also be opportunities for refactoring. The same goes for code that seems too long or complex, or any code that you come back to months later and think, “wtf is going on here?”</p><p>As long as you’re continually learning and striving to write cleaner, more efficient code, that makes you a good coder.</p><p><em>Originally published at </em><a href="https://mintdigital.com/blog/becoming-better-coder"><em>mintdigital.com</em></a><em>.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F29a464%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F29a464%2F&amp;image=https%3A%2F%2Fe.enpose.co%2F%3Fkey%3DdRXnS9Gplk%26w%3D700%26h%3D425%26url%3Dhttps%253A%252F%252Fupscri.be%252F29a464%252F%253Fenpose&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/e3ed68bd40d0bdc96e031cbad511a4ff/href">https://medium.com/media/e3ed68bd40d0bdc96e031cbad511a4ff/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9629a496bf43" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mint-digital/my-advice-on-becoming-a-better-coder-by-shoshi-roberts-9629a496bf43">My advice on becoming a better coder — by Shoshi Roberts</a> was originally published in <a href="https://medium.com/mint-digital">Mint Digital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We created a Snapchat custom geofilter tool. Unfortunately, so did Snapchat]]></title>
            <link>https://medium.com/mint-digital/we-created-a-snapchat-custom-geofilter-tool-unfortunately-so-did-snapchat-2f6ef5b0513?source=rss-a7de1c130adc------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f6ef5b0513</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[snapchat]]></category>
            <category><![CDATA[geofilters]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Mint Digital]]></dc:creator>
            <pubDate>Fri, 21 Oct 2016 10:39:27 GMT</pubDate>
            <atom:updated>2017-07-21T12:53:07.426Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*MgsLguwlt2N_qqX8T8UZ7g.png" /></figure><h4>An insight into the development of YelloGeo — the Mint product that never was</h4><h4>What follows is a true story.</h4><p>It’s a fast-moving tale of opportunism, entrepreneurialism, innovation and, ultimately, broken dreams set in the cut n’ thrust world of digital product development. Hold onto your Moleskines.</p><p><strong><em>TL;DR</em></strong>: <em>We made a Snapchat geofilter creation tool, but then Snapchat released their own just as we were about to ship. You can </em><a href="https://www.dropbox.com/sh/idmy90gbv454h5r/AACul21nqpyj6oxvwRxtNDCCa?dl=0"><em>download the geofilter template files</em></a><em> we were due to launch with, if you like (they’re free).</em></p><h4>The idea</h4><p>One of Mint’s esteemed front-end developers, <a href="https://twitter.com/bradleyfew">Brad Few</a>, is a big fan of Snapchat. Indeed his Twitter bio boldly states: “I’m better at Snapchat than you.” Brad’s obsession led him to spy an opportunity when, in February 2016, <a href="https://www.youtube.com/watch?v=E_ZjEeEez_0">Snapchat announced that users could create and upload their own geofilters</a> for use on the service. Having previously created a tool to <a href="http://scbutton.com/">allow people to embed their Snapchat name</a> on websites, he had become very familiar with the platform and its audience.</p><p>Brad immediately clocked that most Snapchat users would have neither the artistic skill nor the patience to create and submit custom geofilters that would do special events justice. Generally speaking you don’t want a shoddy-looking geofilter for a friend’s wedding or birthday party — you want something that looks classy, that people will want to actually use.</p><p>Brad surmised that there was therefore a potential market of people who would be willing to pay for a tool that would help them create their own geofilters.</p><h4>Validation</h4><p>With a storied history of <a href="https://mintdigital.com/work/ventures/">developing our own products</a>, Mint has the skill and experience to pursue our own ventures — indeed we’re proud to say it’s one of the things that differentiates us. So when Brad pitched the idea to the Mint directors, they were able to see the potential and set about ‘ringfencing resource’ (i.e. they worked out who could work on the product and how much time they could spend on it).</p><p>Meanwhile, lots of people started offering what, at first glance, could have looked like competing products. <a href="https://www.geofilters.co/">Geofilters.co</a>, <a href="http://www.geofilter.studio/">geofilter.studio</a>, <a href="https://eventfilters.com/">eventfilters.com</a>… virtually every conceivable possible use of the word ‘filter’ was in use as a service name and URL.</p><p>However, we felt that people using the majority of these services would be taking something of a stab in the dark, as the relationship followed a client/agency model — only, without any physical meetings to build trust. Over email you’d tell them what event you needed a geofilter for, and they would go away and design it, leaving you to trust that:</p><p>a) the geofilter would be delivered in good time<br>b) the quality would be worth paying for<br>c) they’d be willing to make tweaks if you weren’t satisfied</p><p>…. and so on. In short: they relied on customers trusting strangers about whom they knew very little.</p><p>What nobody appeared to be offering was a foolproof tool that used nicely-designed templates and an onscreen interface that allowed people to essentially <strong>build their own geofilters</strong>. So that’s what we set out to build.</p><h4>Work begins</h4><p>Wireframes were drawn up, illustrating that contrary to the risk of emailing a stranger, this tool — which had acquired the working name of Snapetto — would use a simple, quick and easy interface to take you from zero to geofilter hero in as little as a minute or two. We also decided that rather than building a native app, we’d save time by starting out with a web app that could be used in a browser.</p><p>Brad and designer <a href="https://twitter.com/tomjrt">Tom</a> were given two days to pull together a functioning prototype that would validate the assumption that we would be able to create geofilter assets programmatically. Wireframes were created to outline how the user would move through the app. This was then applied to the functioning prototype, which used <a href="http://phantomjs.org/">PhantomJS</a> to create screenshots as transparent .png files. These files would be saved and used as the geofilters.</p><p><a href="https://filter-fun.herokuapp.com/">You can see the prototype here</a>. We tested it on Snapchat on a night out for <a href="https://twitter.com/simonfl3tcher">Simon</a>’s birthday, capturing red hot ping pong action in the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RaJ3PuguyD4h0iavZagsNA.png" /><figcaption>Wireframes</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-9njmMp9HJRWkWNn7QxX7g.png" /><figcaption>Working prototype</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/1*3euvOVM3V2aITIoIvnWteQ.jpeg" /><figcaption>Prototype ping-pong test</figcaption></figure><p>The next day we checked Snapchat’s analytics, which were pretty promising in terms of what we could expect once the product was out there and being used.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iAVLcKFNBae1hV3BKzZ0vA.png" /><figcaption>Prototype test analytics</figcaption></figure><p>Once we were satisfied that we were on the right track when it came to functionality, we started work on a fun and colourful design that would appeal to Snapchat’s userbase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/971/1*rRC3foF_bthL0uA_pO3DBQ.png" /><figcaption>User interface design</figcaption></figure><p>While we got stuck into the challenges of building out the product, we witnessed noted Snapchat fan Gary Vaynerchuck — a leading early adopter in the tech world — touting the creation of geofilters as <a href="https://www.garyvaynerchuk.com/how-to-create-and-use-snapchats-new-custom-geofilters/">a great business opportunity</a>. All the signs were pointing to the fact that we had spotted a market and were moving swiftly to capitalise on it; indeed the scenario reminded us of the creation of <a href="https://mintdigital.com/blog/stickygram">Stickygram</a>, when we were the first people to use Instagram’s then-new API to create a tool that enabled people to put photos on fridge magnets (<a href="http://www.cityam.com/article/printing-site-photobox-snaps-london-based-instagram-firm">Stickygram was later acquired by Photobox</a>). However, we also remained conscious that given the pronouncements of the likes of Vaynerchuck, others would be trying to do something similar.</p><p>Also in the back of our minds was the knowledge that Snapchat themselves could choose to enter the arena at any point, and that if they did it would likely mean the end of our product. However, at this point there was no sign of them doing that, and we convinced ourselves that given Snapchat’s overall growth they had enough bigger fish to focus on.</p><h4>Roadblocks</h4><p>As a company that builds companies while also <a href="https://mintdigital.com/work/digital-transformation/">maintaining more traditional client/agency relationships</a>, Mint is continuously working to balance the demands that come with each model. Snapetto’s development faced competition for resource from a number of other projects, some of which were up there with the most consuming engagements we’ve worked on in the company’s 10+ years.</p><p>The result was that the availability of the required resource that we could devote to the app’s development was rarely continuous. A couple of days’ progress would be hampered by a week during which we couldn’t get a whole lot done. It’s not a new challenge, but nevertheless it is one for which there is no solution other than unlimited resources — something very few companies enjoy.</p><p>The fact that we used this project to practice using <a href="http://elixir-lang.org/">Elixir</a> introduced challenges as well. Back-end developers at Mint have been excited by Elixir for a while, training themselves up and attending conferences to become more familiar with it. Snapetto’s timing represented a chance to put some of what had been learned into practice, and Mint’s leadership were happy to approve the opportunity.</p><p>This decision will pay off in the long term, and indeed while working on other products recently we’ve benefited from the internal knowledge gained during this time. However, using Elixir unavoidably slowed progress somewhat, if only because of the disparity between the knowledge of back and front-end developers. If a back-ender was called away to work on something else, a front-ender wasn’t able to jump in and aid Snapetto’s progress.</p><h4>A threat emerges</h4><p>With Snapchat geofilters now a recognised business opportunity, it was only a matter of time before someone else attempted the same thing as us. Enter <a href="https://pepperfilters.com/">PepperFilters</a>, which gained some good traction <a href="https://www.producthunt.com/tech/pepper-filters">from the Product Hunt effect</a> after a nifty stunt involving chasing <a href="https://www.crunchbase.com/person/justin-kan#/entity">noted entrepreneur Justin Kan</a> through an airport.</p><p>There was no doubt PepperFilters was hitting many of the same marks as our tool. You could pick templates from a list, for a number of event types, and then edit the text that would appear in the final filter. You then paid to download your filter.</p><p>Did PepperFilters invalidate our idea? We needed to figure out whether, while it was effectively doing the same thing, our product could do it better. This resulted in lots of back-and-forth within the team. It’s not easy to be objective about something you’ve spent time on, and you can become distracted by ‘sunk costs’.</p><p>However, we felt there were a few of reasons that we should press on:</p><p><strong>1.</strong> <strong>Speed of user experience</strong>. We felt that PepperFilters was attempting to do a bit too much. There were dozens of filter templates on offer, which on the one hand is good for the user; but on the other hand if you want to choose and create your geofilter quickly, paralysis of choice can set in and the process slows.</p><p><strong>2. Ease of use</strong>. We were confident we could provide a nicer user interface when it came to creating a geofilter. With moveable text boxes and dozens of font boxes, again we felt Pepperfilters’ approach was a bit overcomplicated. By keeping the UI quick, simple and elegant we would provide a more pleasant experience.</p><p><strong>3. Snapchat submission.</strong> Very few services offered to take care of submitting created geofilters to Snapchat for approval. This was understandable: it’s logistically tricky and opens up a whole lot of overhead when it comes to customer service. But we felt we could handle it, and saving customers even more time and effort would be a compelling feature of the product.</p><p>With these perceived advantages on our side, we continued development. There was certainly a recognition that we had missed ‘first mover advantage’, but with Snapchat’s huge userbase we felt there was still enough pie for multiple players.</p><h4>Preparing to ship</h4><p>Snapchat geofilters were now being <a href="https://theringer.com/geofilters-are-the-newest-snapchat-megatrend-38cc2035cfef#.5awsxk4nt">referred to as a megatrend</a>, which while encouraging was also concerning: the number of players was likely to continue to grow, while we were missing the boat for press coverage that comes with a new tool. Accordingly we started working on a marketing plan that centred instead around direct influencer outreach.</p><p>Meanwhile we needed to finalise the name of the product. Using <a href="http://www.upvoter.co/">Upvoter</a> (another Mint product; give it a try if you need to make group decisions!), the wider Mint team used their votes to <a href="http://www.upvoter.co/tallies/wf9zqtwa">pick the best name</a>. Then Brad went and chose the one he wanted anyway, thereby proving that democracy is a vicious lie. <strong>YelloGeo</strong> it was.</p><p>With the name decided it was time to refine the design, add copy to the website, take some product shots, get the T&amp;Cs sorted, and get the thing out the door.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*MgsLguwlt2N_qqX8T8UZ7g.png" /><figcaption>Homepage design</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*2X_Dkf3Ou9fgRcqIuLXiKg.png" /><figcaption>Homepage design</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/1*4bvS1yUi-cBFnHXr3hhQtA.jpeg" /><figcaption>A shot of YelloGeo in use</figcaption></figure><h4>The nail in the coffin</h4><p><strong>And then Snapchat went and did it themselves anyway, as they had every right to do.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*yVEbbpdG3-dqmG9bkR56Nw.png" /><figcaption>Snapchat’s geofilter creation tool</figcaption></figure><p>While it wasn’t widely publicised at the time, Brad quickly spotted Snapchat’s tool that allowed people to create their own geofilters. It did pretty much the same things YelloGeo did (it even chose the same three categories of birthdays, weddings and ‘general’ congratulations) and was pretty close to the Pepperfilters approach.</p><p>Snapchat also had the advantage of not needing to estimate an average cost for creating a geofence around locations (which is how we were approaching this feature). Whatever mysterious witchcraft they used to calculate geofence costs, obviously they had free and full access to that.</p><p><strong>But the real kicker was that Snapchat’s tool was free to use</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uGsg80Sr47pMK6OUu9HrJQ.png" /><figcaption>Snapchat’s geofilter creation tool</figcaption></figure><p>At any point in YelloGeo’s life, this development would have made our product pretty much redundant — assuming you know it exists, why would you pay to use a third party tool when the native one is free?</p><p>With a heavy heart the team members agreed that there wasn’t much point shipping YelloGeo, even though we were mere days away from being able to do so.</p><p>In a way it was just as well this happened before we shipped and invested more resource in refining YelloGeo, and then a bunch more resource (and possibly money) to promote it.</p><p>It’s just a shame that the ultimate validation of our idea was the same thing that killed it off.</p><p>However, we’ll take what we learned and move onto the next venture emboldened by the fact that, but for Snapchat’s move, we would have been in a great position to capitalise on a huge market.</p><p><strong>The End (of YelloGeo)</strong></p><p><strong>If you like the look of the geofilter templates we created, you can </strong><a href="https://www.dropbox.com/sh/leloznqaad9ilsn/AAAON8jqbv8qG2_vue72k9Q3a?dl=0"><strong>download them for free at this Dropbox link</strong></a><strong>.</strong></p><blockquote>- Each image is available as both an .svg file and a .png file. They’re transparent, so once customised they can be submitted to Snapchat.<br>- To open and edit the .svg files you’ll need to use software like Adobe Illustrator or similar.<br>- To open and edit the .png files you can use most image editing software.<br>- There’s also a layered .psd file if you want to adapt the designs in Photoshop.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F29a464%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F29a464%2F&amp;image=https%3A%2F%2Fe.enpose.co%2F%3Fkey%3DdRXnS9Gplk%26w%3D700%26h%3D425%26url%3Dhttps%253A%252F%252Fupscri.be%252F29a464%252F%253Fenpose&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/e3ed68bd40d0bdc96e031cbad511a4ff/href">https://medium.com/media/e3ed68bd40d0bdc96e031cbad511a4ff/href</a></iframe><h4>Need help building a digital product or transforming your organisation’s digital presence? <a href="https://calendly.com/mintdigital">Book a chat with Mint here</a>.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f6ef5b0513" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mint-digital/we-created-a-snapchat-custom-geofilter-tool-unfortunately-so-did-snapchat-2f6ef5b0513">We created a Snapchat custom geofilter tool. Unfortunately, so did Snapchat</a> was originally published in <a href="https://medium.com/mint-digital">Mint Digital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WhiteAlbum: An obituary]]></title>
            <link>https://medium.com/mint-digital/whitealbum-an-obituary-8ac4e224d861?source=rss-a7de1c130adc------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ac4e224d861</guid>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Mint Digital]]></dc:creator>
            <pubDate>Thu, 15 Oct 2015 12:38:13 GMT</pubDate>
            <atom:updated>2015-10-15T12:38:13.684Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*_rh_kWkSEhCCE8WEhl2Utg.png" /></figure><h4>What we learned when a product didn’t work out.</h4><p><em>By </em><a href="https://medium.com/u/306c86171ce4"><em>Tim Morgan</em></a><em>, </em><a href="http://mintdigital.com/"><em>Mint Digital</em></a><em>’s CEO</em></p><p>Since <a href="http://blog.whitealbumapp.com/post/124927023533/farewell-fellow-shooters">WhiteAlbum was shuttered</a> a few people have asked me about the decision, and what led to it. There’s no denying the product had what looked like a very successful launch, <a href="http://www.wired.com/2015/01/app-turns-iphone-crappy-disposable-camera-thats-good-thing/">with lots of publicity</a> and some glowing reviews. I can appreciate that, viewed from outside the Mint bubble, there might appear to be a disconnect between that launch and the product’s subsequent closure mere months down the line.</p><p>I talked to the founders about the notion of publishing a ‘post-mortem’ of sorts, which is something we tend not to do very much — not because we don’t want to, but if we pondered over every product we shut down (of which there have been over fifty) we’d never get any work done. However, I thought the case of <a href="http://whitealbumapp.com/">WhiteAlbum</a> provided an interesting opportunity to share the thinking behind closing down a product, and the kinds of things we try to learn in the aftermath.</p><p>When start-ups shut down, any post-mortems are usually intended as a point of learning reference to others about ‘what went wrong’, or why something failed. The trouble I have with these is that in my experience nobody <em>really</em> knows why something failed. They might have an opinion, but they don’t <em>know</em> .</p><p>Of course, the same is true of success. Most successful entrepreneurs, in my opinion, don’t really know <em>why</em> they succeeded — but they sure like to think they do, and it’s generally because they themselves are awesome.</p><p>I prefer to see success and failure as more ethereal than that. They are undoubtedly reliant to some extent on your actions, but there is no precise correlation. The factors that determine your success or failure are as much out of your control as they are within.</p><p>And that is a realisation that is both comforting and terrifying.</p><p>For this reason, if I was forced to assign a death-related term to this kind of debrief, I’d be more inclined to plump for ‘obituary’. That’s because this is my point of view of what happened at WhiteAlbum. It’s not necessarily the opinion of the founders, Greg and Will, and it’s certainly not as scientifically, demonstrably proven as a post-mortem.</p><p>Before I get to my thoughts around what worked and what didn’t with WhiteAlbum, I’ll start by taking you through its inception.</p><h3>The birth of WhiteAlbum</h3><p>The first I heard of WhiteAlbum was in a hotel in Dorset during <a href="http://mintdigital.com/blog/what-we-made-at-4D2L">Mint’s annual company wide retreat to the country</a>. Greg mentioned towards the end of the week that he’d had this idea for reproducing disposable photography, but in digital form. He wanted to recapture the delayed gratification of taking photos and then not knowing what they looked like until you got them developed.</p><p>My initial reaction was: “This’ll never work.” I believe that technology changes life permanently and for the better, and to me this idea sounded like a step backwards. However, having spent some time with Greg he convinced me that it was worth testing the appetite of the consumer to see whether this was something people want or not. We thought that without too much investment we could get an alpha version of the app into people’s hands and see how they responded to it.</p><h3>The product development phase</h3><p>The trouble with products that combine the digital and the physical is that you can’t really test them without making them. The test is as much whether people like the finished physical product as it is whether they like the concept, and product development (physical product development, that is) is neither cheap nor easy.</p><p>So next we spent time prototyping the physical product (boxes, print finishes) and tried to find a reliable supplier/printer of these services. Meantime we put a holding page up to gather an early group of user testers who could try the product for free.</p><h3>The launch of WhiteAlbum</h3><p>On New Year’s Day 2015 we launched WhiteAlbum. By this point I had been user-testing the product, and I loved it. The more time I spent with Greg the more I liked the brand and the lifestyle element of it, and when my first set of prints arrived I was really pleased and excited.</p><p>A few weeks later we officially launched <a href="http://www.producthunt.com/tech/whitealbum-2">via Product Hunt</a> and gathered quite a lot of press. We had thousands of users immediately and I wrote a blog post <a href="http://mintdigital.com/blog/Disposable-camera-app-for-your-phone">about how WhiteAlbum had passed the first test of “definitely being a something”</a>.</p><h3>We need to raise money</h3><p>After the success of the launch we took the decision to to raise a round of seed finance for WhiteAlbum. This was partly carrot and partly stick. The founders felt that they would have a better chance of fulfilling the potential of WhiteAlbum if they had their own funding, bank account and P&amp;L responsibility.</p><p>Meanwhile Mint felt that, like <a href="https://www.deskbeers.com/">DeskBeers</a> and <a href="https://boomf.com/">Boomf</a> before it, we couldn’t afford to fund the growth of WhiteAlbum and concurred that external funding would give the product the best chance of fulfilling its potential.</p><h3>Things start to wobble</h3><p>We started planning to raise money (gathering data, putting together a deck and drawing up a list of potential investors) in around March 2015. It was roughly the same time that <a href="http://www.bbc.co.uk/news/business-32072330">trading took a turn south</a>. Suddenly the growth and popularity of WhiteAlbum seemed short-lived, and we were unable to sustain the early momentum.</p><h3>A pivot</h3><p>Whilst planning the fundraising deck and contemplating the trading of WhiteAlbum, we felt that a disposable camera app — although a cool idea — was not the billion-dollar opportunity we all thought it might be. But we did identify an alternative that might represent just that. We updated our investor materials accordingly.</p><h3>Starting again</h3><p>The problem with this approach was that it actually cast us back in time. The thing we had data for related to an app that we were admitting in our deck was not the <strong>real</strong> opportunity. The thing we were seeking funding for didn’t actually exist at all. Savvy investors would say, “Come back to me in six months’ time when you’ve built out the new product” (which we named WhiteAlbum+).</p><h3>The vicious circle</h3><p>Except we didn’t <strong>have</strong> six months to build out the product. We had run out of the funding that we were prepared to invest in WhiteAlbum and we couldn’t afford to invest the amount it would have taken to get the necessary traction for WhiteAlbum+.</p><p>On reflection we can probably condense this story down to some moments where things went wrong. This is my list:</p><ol><li><strong>Product/market fit.</strong> Maybe I was right with my gut instinct. Perhaps we should never have contemplated a disposable camera app. We once considered a music app that forced you to listen to entire albums, and I remember thinking “cool” and then “but no”. Perhaps the market for retro/limited apps (where the limit here is the inability to pick and choose your photos before you print) is one of novelty only, rather than the longer-lasting returning-customer type of market that’s required to raise money against.</li><li><strong>Physical product development. </strong>I wonder whether we could have come to the conclusion about demand and the disposable camera opportunity earlier. The main reason we didn’t was a tremendous amount of time invested in the physical product and the supply chain related to it. Had we been able to condense this period we might have been able to launch earlier, get through the cycle earlier and have enough left in the tank to build WhiteAlbum+.</li><li><strong>Marketing expertise.</strong> It’s very common when a start-up fails for the reason to be “well, marketing”. Indeed I recently read something that suggested 95% of startups fail because of marketing (or lack thereof). I can’t believe that’s true. If you read “marketing” in this instance to mean “insufficient numbers of people buying the product”, then yes, I’m sure that 95% stat is true. If you read it to mean “this product would have succeeded had it had more marketing expertise/competence”, I will eat my marketing books if that 95% stat is true. I think lack of consumer demand is not the same as lack of marketing expertise.</li></ol><p>However, I do concede that in the case of WhiteAlbum we did not spend money on marketing experts or any paid customer acquisition methods, and that that might well have been the reason why the numbers went south after launch.</p><h3>Lessons learnt</h3><p>So, all that being said — what can <a href="http://mintdigital.com/">Mint</a> as a company (and Greg and Will as the founders) take away from this?</p><ol><li>If this was a failure of product/market fit (and if I had to choose I would say it was) then perhaps that’s a danger inherent in today’s ‘early adopter’ markets. I’ve often wondered how many people back something on Kickstarter, say, because it looks cool rather than there being a compelling product/market fit. Do lean methodologies of testing appetite ahead of launch lend themselves to fake results manifested by lots of press and attention in the early stage — but little longevity beyond that? I don’t have a definitive answer to this, but that’s the thinking I’m leaning towards at the moment.</li><li>Perhaps physical products start better with a third-party manufacturing relationship already established. Starting from scratch is time-consuming and risky, since you’re investing in something before being able to ascertain demand.</li><li><a href="http://mintdigital.com/blog/internal-ventures-employee-engagement-questions">I’ve spoken recently</a> about how we don’t always necessarily know to what extent we’re willing to financially back a product. In the case of WhiteAlbum, perhaps we shouldn’t have taken on such a project without a bigger initial budget with which to see it through. I’m loathe to say this, since it can kind of be applied to any business: “We failed because we didn’t have enough money!” However, sometimes it’s true. I’ve observed many times in the early stages of start-ups that lack of capital can be decisive in terms of either kicking on or not (although it’s rare for founders to reflect on this as a key reason for success!). Lack of funding curtailed our investment in marketing, and also our ability to ‘go again’ with WhiteAlbum+.</li><li>Still on funding: the amount we were looking to raise ($500K) potentially put us in a funny spot with prospective investors in terms of ease of putting us in a ‘stage bracket’. This was probably amplified by the pivot mid-stage. Perhaps we should have tried to raise a lower amount and started from scratch with WhiteAlbum+.</li></ol><p>I’ve written recently about the risks inherent in pursuing what we refer to as ‘internal ventures’. I suppose WhiteAlbum is an example of a venture that didn’t work out, and that’s a shame for both us as product developers and those users who really liked said product. But as with everything we work on at Mint, the team — which worked harmoniously throughout — learned a lot and I’m proud of what we achieved during what was a fun ride. I think the experience will continue to be beneficial to everyone who was involved.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ac4e224d861" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mint-digital/whitealbum-an-obituary-8ac4e224d861">WhiteAlbum: An obituary</a> was originally published in <a href="https://medium.com/mint-digital">Mint Digital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Internal ventures work for us. Would they work for you?]]></title>
            <link>https://medium.com/@mintdigital/internal-ventures-work-for-us-would-they-work-for-you-9f27b518f008?source=rss-a7de1c130adc------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f27b518f008</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[employee-engagement]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Mint Digital]]></dc:creator>
            <pubDate>Thu, 08 Oct 2015 13:05:34 GMT</pubDate>
            <atom:updated>2015-10-08T13:05:34.581Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*oY4B01sNtxTVIWaj1CsnUA.jpeg" /></figure><h4>Does empowering staff via internal product ventures lead to a happier workforce — or is it more nuanced than that?</h4><p><em>By </em><a href="https://medium.com/u/306c86171ce4"><em>Tim Morgan</em></a><em>, Mint Digital’s CEO.</em></p><p>I’ve been fortunate to have been invited to speak a bit about employee engagement recently, particularly in relation to the way we’ve enabled employees to pursue ventures at <a href="http://mintdigital.com/">Mint Digital.</a></p><p>(For those who don’t know, Mint is a digital agency — but we’ve produced several successful products of our own outside of our client services business, many of which have crossed the digital/physical divide. We’re behind <a href="https://www.deskbeers.com/">Deskbeers</a>, <a href="http://techcrunch.com/2010/03/24/real-time-social-sports-gaming-startup-picklive-closes-seed-funding/">Picklive</a> and <a href="http://tubesocks.co/">Tubesocks</a> to name but a few.)</p><p>In April I presented at the <a href="http://engageemployee.com/summits/2016-employee-engagement-summit/">Employee Engagement Summit</a>, which was an event aimed at HR professionals. My presentation was called ‘Why we deliberately plan to lose some of our best people’ (you have to give your presentations provocative titles, or nobody shows up).</p><p>I also took part in a breakfast panel on employee engagement with <a href="http://www.purplecubed.com/">Purple Cubed</a> in September, and was recently interviewed by the Institute of Leadership &amp; Management <a href="https://www.i-l-m.com/Insight/Inspire/2015/September/Happy-and-engaged-staff">on the topic of keeping small teams happy</a>.</p><p>Throughout these conversations, there was a genuine curiosity about whether enabling internal ventures could be used as a way to empower people at other, typically larger, companies. Does Mint’s small size lend itself more to this approach? Could firms in other spheres use a similar method? Do internal ventures by definition make staff happy, or is it more nuanced than that?</p><p>I’ve had plenty of opportunities to think about what we’ve done at Mint, and why the way we’ve empowered staff via product ventures may/may not be a fit for other companies. By which I mean I’ve pondered and cogitated and come up with exactly zero solid conclusions.</p><p>Nevertheless, I’ve been persuaded that my thoughts around some of the questions I’ve been asked might be useful to some people, so here are five things you may want to consider if you’re thinking of enabling your workforce to pursue ventures aside from your core business.</p><h3>1. Who owns what?</h3><p>Venturing from within a parent company tends to necessitate a different risk and return profile than ‘normal’ entrepreneurship. If you’re enabling staff to <a href="http://mintdigital.com/helping-startups#deskbeers">create products on your dime</a>, you need to think about what you (as an employer) and they (as an employee) are each entitled to. It’s in everyone’s interest to try and get this nailed down pretty early on during the process.</p><p>Operationally, at Mint we’ve kept ventures under the Mint umbrella until the point at which it makes more sense to spin them out as a separate entity — if indeed they ever reach this stage (and many don’t — spinning something out naturally depends on a number of considerations, such as a particular venture’s rate of growth, etc). Before that point, however, we’ve saved a lot of hassle by keeping them in-house. You don’t want to go setting up a whole new company if you don’t have to.</p><h3>2. Are you willing to risk workplace harmony?</h3><p>To put it in its starkest terms: if Mint says no to an employee’s idea, or <a href="http://mintdigital.com/blog/Foldable-me">closes one down</a>, all the parties affected by that decision have to come into the office the next morning and crack on with the normal working day. That can be tough. If a venture capitalist turns you down, you don’t typically have to exchange small talk next to the coffee machine the next day.</p><p>In reality, over the last couple of years we didn’t actually say no very much when it came to getting ventures started. But we did need to take pragmatic decisions about closing them down when that’s what made sense, regardless of how we might have felt about the individuals involved.</p><p>I’d also say that to be successful in our ventures, we’ve always needed to prioritise our broader team’s ability to execute an idea, whatever that idea may be. To rely on the talents of specific individuals over the team would be to put too many eggs in too few baskets. To use a football analogy, you could end up in the kind of situation Tottenham Hotspur found themselves in after Gareth Bale upped sticks to Real Madrid.</p><p>This team approach is somewhat different from how VCs might look at an aspiring entrepreneur. Sometimes a product idea may not be fully-formed, but an investor will have faith in the individual behind it and invest accordingly. We don’t have that luxury.</p><p>In short, <a href="http://techcrunch.com/2010/03/24/real-time-social-sports-gaming-startup-picklive-closes-seed-funding/">enabling your staff to pursue</a> ventures the way Mint has is not necessarily the best route to workplace harmony, and probably wouldn’t be for everyone.</p><h3>3. Are you ready to step outside your comfort zone?</h3><p>Restricting the scope of the ventures you’re willing to back is somewhat antithetical to the notion of modern product development. If what you’re trying to do is define a problem and propose a solution to that problem, applying restrictions is likely to affect the quality of the outcome of a venture.</p><p>For example, while Mint Digital has historically been identified as a digital product company, the fact that we refused to be held to that description enabled us to branch out into physical product development. If we’d been unable to stray from the digital realm, we most likely wouldn’t have created <a href="http://tubesocks.co/">socks the colour of the tube</a>, or <a href="https://www.getprojecteo.com/">a mini Instagram projector</a>, or <a href="https://thebathory.com/">personalised bath salts</a>. And such a world doesn’t bear thinking about.</p><h3>4. Do you need tight financial controls?</h3><p>Venture capital typically comes in defined rounds, and while you’re spending one round you’re usually thinking about how you’re going to raise the next. This can have all sorts of impacts on your strategy and thinking around a product, and that’s something you have to be willing to deal with if you go down that route.</p><p>That may sound obvious, but I’m mentioning it because — believe it or not — at Mint we’ve never really defined the amount we’re willing to invest in a venture. The proof tends to be in the pudding.</p><p>For us, investing in a venture has always been more of an incremental thing. We’ll see a product get to a certain point, and then invest a bit more as required, and continue (or not) in that vein. There are two particular consequences to this approach I’d like to mention.</p><p>On the one hand, it’s highly enabling, and allows us to act in what is probably an unusually nimble fashion. On the other hand, since we don’t know the extent to which we’re willing to back something, we also haven’t always known the best time to stop.</p><p>How you — or more likely your finance department — feel about this point may give an indication as to whether encouraging the Mint ventures model is a viable step for your organisation.</p><h3>5. Can you fit venturing in amongst other priorities?</h3><p>The most common questions I get tend to be variations of: “Does pursuing ventures threaten your priorities as an agency?”</p><p>To address this I’ll start by saying I’m confident there’s never been a time when Mint has let a client down as a result of our ventures. However, while I understand why this question comes up so often, I’d also challenge its implied assumption that people and organisations are unable to juggle priorities and do them justice.</p><p>For example, my priority right now might be client X — but my priority for the year could be to develop product Y towards launch. As long as we can arrange our resources to service both of these requirements adequately, there doesn’t need to be an inherent conflict between the two.</p><p>I’m not saying this is necessarily easy, but I do believe that for Mint these things enjoy a symbiotic relationship: doing one makes us better at doing the other. Developing products gives us a better understanding of the challenges our clients face, and collaborating with our clients inspires our own product development.</p><p>At this point I’d love to be able to tell you (or sell you) our secret formula for combining client services and ventures. But, without wishing to sound disingenuous, I’m afraid there isn’t one. Things are a lot more nuanced than that. All I can say is that for Mint our approach and decision-making have been based more on principles than processes. The result is that while we may not always get it right, we’ve remained agile enough to be able to successfully capitalise on the times we do.</p><p>So there we go. As I promised, I haven’t given you any answers — but hopefully I’ve given you an insight into our approach and some points to think about. And if not, at least now you know where you can <a href="http://tubesocks.co/">buy some new socks</a>.</p><p><a href="http://mintdigital.com/blog/internal-ventures-employee-engagement-questions"><strong><em>This post first appeared on the Mint Digital blog.</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f27b518f008" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Product Development Detective]]></title>
            <link>https://medium.com/@mintdigital/the-product-development-detective-b9cabb43c797?source=rss-a7de1c130adc------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9cabb43c797</guid>
            <dc:creator><![CDATA[Mint Digital]]></dc:creator>
            <pubDate>Tue, 27 Jan 2015 12:22:44 GMT</pubDate>
            <atom:updated>2015-05-21T13:28:46.779Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j8yLe4g6zxNfrOOREQvf3g.jpeg" /></figure><p>It begins with a knock at the door.</p><p>Or perhaps a telephone call, a letter, even a newspaper headline. There may be a body. There will certainly be something hidden and unexplained. A mystery, a secret, a problem to be solved.</p><p>There follows a process of observation and investigation — clues, facts, witnesses. Hypotheses will be proposed and interrogated, answers will prove false. Eventually — preferably in a dazzling dénouement — the facts will reveal an explanation that satisfies, a solution to the problem.</p><p>If, like me, you are a fan of detective stories, this structure will be familiar. But twist it just a little — we <em>rarely </em>have to deal with bodies — and I think it looks rather like the way we make products at <a href="http://mintdigital.com/">Mint</a>. The cycle of <strong>observe &gt; test &gt; analyse</strong> is at the heart of our approach to product development and is, in essence, detective work.</p><p>Of course, this approach is firmly rooted in the principles of Agile development: fast, iterative, user-focused. But the detective story parallel throws up some interesting corollaries when you consider the work of the Agile <em>agency.</em></p><p>We’re waiting for that knock on the door; a client with a problem, a question. That problem will throw us into an unfamiliar world. There will be interviews and evidence to be collected. We’ll probably come up with a few red herrings before arriving, eventually, at what we believe is the ‘right’ product, the right solution for that problem. All for twenty five dollars a day plus expenses. Or thereabouts.</p><p><strong>So, how we can apply the art of detection to the mean streets of product development?</strong></p><p>It’s a wonderfully mercurial genre, but perhaps it’s the endlessly reinvented Sherlock Holmes, the “consulting detective”, who casts the longest shadow…</p><h4><strong>1. Start by defining a question or problem</strong></h4><p>Whodunnit? Detective stories are driven by A Big Question. Usually it’s the classic “whodunnit?”; sometimes it’s more like “whydunnit?” or “howdunnit?” But the question is every-present, and the desire for a solution is what propels the narrative forwards.</p><p>Sherlock Holmes’ advice is to focus on the “elementary”. The essentials. What is the big problem you are really trying to solve? Write it down, put a question mark at the end. Is it the <em>right </em>question? Revisit and refine.</p><h4><strong>2. Data, data, data</strong></h4><blockquote>“Data! Data! Data!” he cried impatiently. “I can’t make bricks without clay.”</blockquote><p>Holmes is obsessed with data. His method is the acute “observation of trifles” and rapid assessment of that data. (For a crash course in this, I recommend Maria Konnikova’s <a href="http://www.amazon.co.uk/Mastermind-Think-Like-Sherlock-Holmes/dp/0857867245"><em>Mastermind: How to Think Like Sherlock Holmes</em></a><em>.)</em></p><p>Holmes recommends approaching a problem with “an absolutely blank mind”, resisting the urge to form theories:</p><blockquote>“It is a capital mistake to theorise before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts.”</blockquote><p>In product development, we need to ground our ideas in hard facts. Evidence. This means beginning from a place of deliberate open-mindedness and conducting meaningful research: data analysis, market research, interviews, competitor analysis. We also need to learn how to filter this data — separate the real clues from the red herrings.</p><h4><strong>3. The suspects</strong></h4><p>A product of his time — the late-Victorian period of scientific inquiry and psychological analysis — Holmes’ empirical approach to detection applies the principles of the “scientific method” to <em>people.</em></p><p>As much as possible, we need to test things (concepts, paper prototypes, clickable prototypes) at every stage on real people. There’s an art to scripting user interviews, but we also need to learn when to simply listen and when to question the validity of feedback. “You see,” Holmes tells Watson, “but you do not observe.”</p><h4><strong>4. Deduction</strong></h4><p>The plot thickens… The process of hypothesis or concept generation is a mixture of weighing evidence and bringing in our own insights — the weight of our experience. Spotting commonalities between crimes is key to the detective. As Holmes says:</p><blockquote>“There is a strong family resemblance about misdeeds, and if you have all the details of a thousand at your finger ends, it is odd if you can’t unravel the thousand and first.”</blockquote><p>Have you solved a similar problem before? Has anyone on your team? Think laterally — has the problem been tackled in a different context?<br>This is the time for brainstorms and post its. Verbalising helps, says Holmes.</p><blockquote>“Nothing clears up a case so much as stating it to another person.”</blockquote><p>But you should also make time for solo reflection, Holmes would disappear in a cloud of smoke over “a three pipe problem”, Poirot was all about exercising his “little grey cells”.</p><h4><strong>5. The solution</strong></h4><p>Aha! The big finish. This is the scene where you gather everyone together to announce the solution, preferably in a display of wholly unexpected intellectual theatrics. The butler did it. Case closed.</p><p>And this, I think, is where the product development detective, and the crime-solving one part ways. The traditional crime novel is all about exposing truth and isolating guilt, pulling back the curtain to reveal “whodunnit”. There is <strong>one </strong>true solution. One exit from the labyrinth. “There was the case,” says Dr. Watson in ‘The Man with the Twisted Lip’, “and of course there was but one way out of it.”</p><p>But the product development labyrinth is trickier. We may find any number of solutions to our problem. Finding the ‘right’ product is always going to be an iterative process, ‘solutions’ evolve and pivot.</p><p>And we don’t walk off into the mist in the final act. Or at least we shouldn’t. At <a href="http://mintdigital.com/">Mint</a>, we’re increasingly seeing that our work doesn’t end with product launch. Growing products into real businesses, adapting to changing needs, understanding emerging behaviours — that’s often the real challenge.</p><p>Now, Watson, is that a knock at the door? The game’s afoot. Let’s solve some problems today.</p><p>*</p><p><em>by </em><a href="http://mintdigital.com/laura"><em>Laura Grace</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9cabb43c797" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mint Digital is 10]]></title>
            <link>https://medium.com/@mintdigital/mint-digital-is-10-6c65e56c347d?source=rss-a7de1c130adc------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c65e56c347d</guid>
            <dc:creator><![CDATA[Mint Digital]]></dc:creator>
            <pubDate>Mon, 24 Nov 2014 14:37:48 GMT</pubDate>
            <atom:updated>2014-11-24T14:37:48.198Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*M8JgJCD3d-ihelRu6GAkzw.gif" /></figure><p>It’s our 10th birthday!</p><p>We’ve put together some of our proudest moments and favourite memories to share with everyone we’ve met along the way.</p><p><a href="http://weare10.mintdigital.com/">Take a look</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c65e56c347d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Mint approach to: Discovering users’ needs]]></title>
            <link>https://medium.com/@mintdigital/the-mint-approach-to-discovering-users-needs-a718e9fe9826?source=rss-a7de1c130adc------2</link>
            <guid isPermaLink="false">https://medium.com/p/a718e9fe9826</guid>
            <dc:creator><![CDATA[Mint Digital]]></dc:creator>
            <pubDate>Wed, 22 Oct 2014 15:19:29 GMT</pubDate>
            <atom:updated>2014-10-22T15:20:14.060Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PvZBGHLXJ1wHZ3Hkeb3auA.jpeg" /></figure><p>You can’t create a great product or take it to market without paying close attention to your users’ needs. That’s why we build user research into every project at Mint, whether we’re working for a client or creating and marketing a product of our own.</p><p>There are countless ways to learn about audiences and their behaviours and needs. We’ve conducted user research in all kinds of ways at Mint: <a href="http://mintdigital.com/blog/gp-patient-survey">sometimes a discovery phase lasts weeks</a>, other times budgets and deadlines are tighter and we need to get creative to find out what we need to know quickly.</p><p>Here are some of the things we’ve learned.</p><h4>You don’t need a big budget or a lot of time to do discovery.</h4><p>Lots of discovery is always helpful. But some discovery is better than none at all, and you can find out a surprising amount in a short timeframe just from people around you. Interview people around your office who fit the target market. Send a questionnaire to friends and family. <a href="http://vimeo.com/102911252">Set up a free coffee stand and survey 76 people in an hour</a>.</p><h4>Start with questions</h4><p>Before you even start thinking about how to conduct your research, you need to think about what it is you need to find out and why. A good set of research questions will help you focus and use your time more efficiently—you can think about the best way to make sure each question gets answered. Frame the problem you’re trying to solve clearly in order to keep your research questions pointed.</p><h4>Choose your methods wisely</h4><p>Qualitative research is particularly important early on when creating a brand new product. Observation and open-ended interviews with users are good techniques for learning about an audience’s existing behaviours, to ensure you create something that fits in with their lives. Questionnaires are good for building on and validating early research. If you’re looking to improve an existing product, you’ll likely want to start with analytics or lab-based usability testing.</p><h4>Put things in front of users</h4><p>Sometimes the problem you’re trying to solve is really open, or involves new user behaviours. You might want to help users express needs they don’t even know they have.</p><p>Workshops can be the best way to learn in these instances. Putting stimuli like paper wireframes in front of users as a starting point to see how they’ll react can teach you all sorts of things that you can’t get at through observation or interviews alone. <a href="http://mintdigital.com/blog/gp-patient-survey">During one recent project</a>, we learned that the audience, GP practice managers, were interested in having the information on our wireframes displayed as posters on their practice noticeboards. We never would have discovered this need if we hadn’t showed the practice managers our wireframes and explored what they wanted to do with them.</p><p>Sometimes a workshop isn’t enough, however—you may want to test how people react to your concept in real life, as opposed what they say they’d do in a workshop. If that’s the case, then <a href="http://blogs.hbr.org/2014/03/the-future-of-prototyping-is-now-live/">live prototyping</a>is the way to go. Mint did this during our discovery phase for<a href="https://sticky9.com/">StickyGram</a>: creating a landing page for the still-yet-to-be-built product, sending it around to influencers, and asking people to leave their email address if they were interested. In the end, our landing page had 14,000 signups—more than enough proof that StickyGram was a sound proposition worth prototyping and building.</p><h4>Summarise everything as you go</h4><p>Be sure to clearly sum up your learnings from each phase of research—not only does this help keep you focussed, it makes it easier for others who haven’t been along for the whole process to digest your findings, helping the team to be more efficient.</p><p>Cross check your findings with your research questions as you go along to ensure they’re being answered, and add any new research questions to your list. Keep this up and you’ll be able to build up a clear list of requirements for a product that meets your audience’s needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a718e9fe9826" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Applying for Design Roles]]></title>
            <link>https://medium.com/@mintdigital/applying-for-design-roles-d03dad292b40?source=rss-a7de1c130adc------2</link>
            <guid isPermaLink="false">https://medium.com/p/d03dad292b40</guid>
            <dc:creator><![CDATA[Mint Digital]]></dc:creator>
            <pubDate>Tue, 21 Oct 2014 10:44:17 GMT</pubDate>
            <atom:updated>2014-10-21T11:31:53.435Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6YJ26eMAr_W8hVti8vDhaw.png" /></figure><p>When we have a designer position available at Mint, we tend to get a lot of applications; most very good, some that need improvement. It’s quite a task going through all of them to find the right candidate. It’s also hard for young designers to know how to stand out, or what studios are looking for.</p><p>So, we’ve put together some basic tips for young designers. We hope you find them helpful.</p><h4>Read the job description carefully</h4><p>Make sure you read the job description thoroughly. Do your skills and experience match what’s required? Does the person they’re looking for sound like you? If you decide to apply, explain how and why you match this criteria.</p><h4>Find the right balance of projects</h4><p>Try and show a balance of work and different skills, but be decisive: pick projects you feel are your strongest or ones you most enjoyed working on. You don’t want someone to have to wade through a sea of projects to find your strongest work.</p><h4>Personal work and professional work</h4><p>If you work on personal design projects outside of your day-to-day work, show these too. It’s always relevant and shows you’re enthusiastic about what you do.</p><h4>Show your process</h4><p>Sketches, testing, wireframing and iterating are all part of the design process. It’s great to see your process — it gives us more of an insight into how you work (definitely more so than a Dribbble-esque image of designs stacked up at an angle).</p><h4>Stand out</h4><p>Standing out doesn’t mean adding skill bars to your CV that shows you’re a 9/10 star Photoshop ninja. It doesn’t mean making your homepage a full-width photo of yourself alongside a caption that says: “Making everything pixel perfect”.</p><p>Try not to be influenced by popular trends, and don’t present yourself as someone you’re not, let your work speak for itself.</p><h4>Cover letter</h4><p>If a job advert asks for a cover letter, take the time to write one and tailor it to the position. Let them know why you think you’re the best person for the job. Tip: the following does not constitute a cover letter:</p><p>“Hello, Please find attached my CV. Thanks”</p><h4>Design your CV</h4><p>You’re a designer, and if there’s one thing you should be able to sell, it’s yourself. It may sound obvious, but the amount of CV’s I see that have very little care or effort put into them is quite worrying. It’s a piece of communication design, so show off your layout skills and present your experience clearly, no one will have the time to try and decipher it.</p><h4>Refine, reread and refine</h4><p>Try and keep your CV short and sharp with only relevant content. Explain briefly what you’ve been doing in previous positions but don’t be too vague (you can probably leave a previous part-time job at Morrisons out though).</p><h4>No egos please</h4><p>There seems to be a trend amongst a lot of recent graduates who, I can only guess, must have been told to be bold and brash to stand out. But there’s a fine line between being confident and coming across as arrogant, writing “See you at the interview stages”, or “We all know that you want to hire me”, unsurprisingly has the opposite effect.</p><h4>Room for improvement</h4><p>This is more of an etiquette for studios, but if you’ve taken the time to apply for a job, it’s only fair that they make the effort to respond, even if it’s a straight-out rejection. If you’ve attended an interview then you should certainly be getting more than a “Sorry you’ve been unsuccessful” email. If they haven’t given you specific feedback, follow up with the people who interviewed you — it’s the only way you’ll know how to improve next time.</p><p>These are just some basic tips and I hope they might come in useful. Like people, all studios are different and have different cultures, so make sure you read up about the company before applying.</p><p>Looking for inspiration? Another designer at Mint, Kim, has even made a useful resource, <a href="http://niceportfol.io/">http://niceportfol.io/</a>, that aims to showcase some of the best design portfolios on the web.</p><p>Good luck.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d03dad292b40" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Importance of Life Time Value]]></title>
            <link>https://medium.com/@mintdigital/the-importance-of-life-time-value-cc3638427c7?source=rss-a7de1c130adc------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc3638427c7</guid>
            <dc:creator><![CDATA[Mint Digital]]></dc:creator>
            <pubDate>Tue, 14 Oct 2014 11:48:00 GMT</pubDate>
            <atom:updated>2014-10-14T14:48:11.345Z</atom:updated>
            <content:encoded><![CDATA[<h3>The importance of lifetime value</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*jVRJ06dgi7PGoyURT23DPA.jpeg" /></figure><p>For most startups, the first step is to find a core group of users who love the product. This is the group of early adopters; the customers who help you develop the product, the ones you talk to frequently and the ones who will evangelise the product (if you do a good job!). With DeskBeers we were lucky in that we found this early adopter group quickly: turns out that there’s a big appetite in London for amazing beers delivered to your office at the end of the week (who knew?).</p><p>After cultivating this group of early adopters, the next step is to scale. For a while this involved cold emails and cold calls, letting companies around London know that DeskBeers existed and they could buy some beers from us, if they fancied it. This worked well but with a small team, it’s ultimately very time consuming and expensive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/455/1*iEcHcDqv5t_8f6N2GZz4NQ.png" /></figure><p>Over the past 6 months we’ve trialled different forms of paid advertising, online and offline. Before we embarked on this, we needed to determine how much we could sustainably spend and how to interpret results. We allocated trial budgets to various advertising platforms and doubled down on the platforms that showed us the results that we wanted; a profitable referral of new customers. This is how we did it:</p><p><strong>Method</strong>:</p><ol><li>Collect data required to calculate lifetime value (LTV); retention rate, customer lifespan etc. Take a look at this <a href="https://blog.kissmetrics.com/how-to-calculate-lifetime-value/">Kissmetrics infographic</a> for more information.</li><li>Use LTV to inform marketing spend. For DeskBeers, let’s say LTV at the time was around £100*, meaning that to break even on paid acquisition we could spend up to £100 per acquired customer.</li><li>We initially started running adverts on Twitter, Facebook and LinkedIn. Facebook showed the best early results so we doubled down on our Facebook ads.</li></ol><p>As a result, we saw an increase of unique views on our site, and more importantly an increase in subscriptions. The resulting CPA (cost per acquisition) via Facebook of, say, £75* was comfortably within our ceiling amount of £100 per new customer (the LTV).</p><p>This is good news and is a conclusion of sorts, however, the analytics fun is only just beginning. First, we will be keeping an eye on our figures, ensuring LTV remains above CPA. We do this by re-running the calculations as we gather more data. We’re building up a picture of our customers referred by Facebook, asking questions like “do they order more or less beer than the average DeskBeers customer?”; “do they order more frequently?”. Over time, this will give us a solid idea of the LTV specific to this group. As long as we can ensure that lifetime value remains greater than cost per acquisition then we will continue to run these adverts.</p><p>As far as online advertising is concerned, we’ve tested our messaging, imagery and the target audience. Most online advertising platforms determine how much you pay for an engagement (click, like, retweet etc.) by how relevant your ads are to users and we’ve driven down this cost of engagement over time to further reduce our CPA.</p><p>Looking further ahead, we want to trial offline and outdoor advertising for DeskBeers in a similarly quantitative fashion. This requires a bigger budget to trial and its results are harder to measure. However, focusing on selected areas and isolating our advertising efforts, we expect to have a good idea of what works and what doesn’t when it comes to selling subscription craft beer.</p><p><em>*these figures are just for reference, and aren’t actual figures</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc3638427c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>