<?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 Mitchell Petrie on Medium]]></title>
        <description><![CDATA[Stories by Mitchell Petrie on Medium]]></description>
        <link>https://medium.com/@_mitchellpetrie?source=rss-e76cd25f669e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*skvTCh-RYp_hxmF-4TDIvQ.jpeg</url>
            <title>Stories by Mitchell Petrie on Medium</title>
            <link>https://medium.com/@_mitchellpetrie?source=rss-e76cd25f669e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:43:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@_mitchellpetrie/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[Approaching complexity]]></title>
            <link>https://uxdesign.cc/approaching-complexity-8f16c85dbde8?source=rss-e76cd25f669e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f16c85dbde8</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Mitchell Petrie]]></dc:creator>
            <pubDate>Fri, 11 Sep 2020 11:01:56 GMT</pubDate>
            <atom:updated>2020-09-15T11:18:14.693Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y8pVDpHYFGChZzInWTkn2A.png" /></figure><p>Often in product and design, we see complex and simple as opposite ends of a spectrum. We strive to create simple products and view complexity as the enemy of good design. But the reality is that it’s not that simple.</p><p>For every task, there is a necessary amount of complexity. For example, to slice a potato you need a potato and a knife. Then you push the knife through the potato. You can’t reduce this further without altering the outcome.</p><p>Whereas, simplicity is an intangible feeling. Your perception of ease based on that interaction. Was the knife sharp enough? Did you hold the knife correctly? Did you have a flat surface to reduce the risk of injuring yourself? Simplicity doesn’t come from removing necessary complexity but from complexity more usable.</p><p>In pursuit of value we’ll almost always create complexity in our products. This could be threads in a chat, recurring purchases for common items or adding optional attendees to an invite. Complexity is very often the manifestation of value and that’s fine.</p><p>But, when complexity isn’t considered or we don’t understand the system it exists within that can create complications. This is what we want to avoid.</p><h3>How can we prevent complications?</h3><p>Understanding a person’s mindset and how the systems behind the scenes work make this easier. Once we have that then we can apply some of these approaches.</p><h4>Reframe the complexity</h4><p>A system needing information in a particular way shouldn’t mean we’re constrained to that. We should reframe those requirements in a way that aligns with how peoples process that information.</p><h4>Use common language</h4><p>Every company has its own “insider” terminology but, speaking the user’s language goes a long way. It helps to minimise confusion and gives them the confidence to move forward.</p><p>As an example: When sending money to a savings account, internally we call this a “Deposit”. However, speaking with customers showed that they refer to this as “Topping up”. So that’s the terminology we should use when we talking to customers about deposits.</p><h4>Expose complexity in favour of clarity</h4><p>Sometimes hiding complexity can lead to confusion. If a person is unsure why we’re asking something they’ll be reluctant to answer. For example, when opening an ISA (Tax-efficient account) you’re asked to provide your national insurance number. This is a personal number that many people do not feel comfortable giving out. Yet, companies do need this for tax reporting purposes.</p><p>By explaining to people how we use their information we reduce that reluctance.</p><h4>or shift it below the surface.</h4><p>Once you understand the system behind the interaction you can look to shift the complexity off of the user and onto your product. An example of this is postcode lookup. Instead of typing their whole address we can ask for only the postcode and return a list of addresses to choose from. Reducing the amount of work a person has to do</p><h3>Putting these into practice</h3><p>Let’s look at running a person’s details through an identity check. As part of this, we need to provide a 3rd party with a person’s address and how long they’ve lived there for.</p><p>The 3rd party system expects to receive a duration formatted as years and months, for example, Years: 1 &amp; Months: 3. We could ask our customers to fill this in for us. But, after speaking with people that’s not how they think. They aren’t machines counting the time they’ve spent living somewhere. Instead, they have memorable dates like the day they moved in or the day they brought home their puppy.</p><p>If asked to tell us how long they had lived at their address they’d first need to work it out. Taking the date they moved in and counting the time between then and today. For someone who moved in on the 22nd November 2017 their thought process would likely look something like this:</p><p>From 22nd November 2017 to the 22nd November 2019 is <strong>2 years</strong> and then…</p><p>from 22nd November 2019 to the 8th September 2020 is <strong>9 months</strong> (+ some remainder of days)</p><p>For most people this isn’t difficult but, does complicate things. Adding the need for time-consuming, error-prone mental arithmetic.</p><p>Instead, we can reframe the question to match the user’s way of thinking and ask them “When did you move in?” This removes a lot of the work a person would need to do and reduces the chance of an error from an incorrect answer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u_5OJbfu_nK6s5kEbus-2A.png" /></figure><p>We can then shift that complexity below the surface onto our systems. Which will work out the difference between the date provided and right now. Along with converting it to the correct format and passing it on to the 3rd party.</p><p>Complexity in our products is — for the most part — inevitable. It reflects the richness and nuance of the experiences we’re creating. Rather than trying to avoid complexity, we should be making conscious decisions about how we surface it.</p><p>If you liked this I’d highly recommend buying a copy of <a href="https://www.amazon.co.uk/Living-Complexity-Press-Donald-Norman/dp/0262528940">Living with Complexity by Donald Norman</a>. I read it a few years ago and it’s stuck with me ever since, inspiring this article. You can find me on Twitter as <a href="https://www.twitter.com/Petr_ie">@Petr_ie</a></p><p>And finally, a huge thanks to <a href="https://twitter.com/charliepearcexo?s=21">Charlie Pearce</a> for the illustration and Alex, Zulfi and Ana for their comments and feedback! 🎉</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*1ByHXslPhfmoZlaN" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f16c85dbde8" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/approaching-complexity-8f16c85dbde8">Approaching complexity</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[Creating colour systems]]></title>
            <link>https://medium.com/@_mitchellpetrie/creating-colour-systems-b4a7ab5dc2ee?source=rss-e76cd25f669e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4a7ab5dc2ee</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[colors]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Mitchell Petrie]]></dc:creator>
            <pubDate>Fri, 20 Sep 2019 07:50:08 GMT</pubDate>
            <atom:updated>2019-09-20T07:50:08.306Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Screenshots of where the Freetrade app started." src="https://cdn-images-1.medium.com/max/1024/1*qwA7PTDt7RknYDVmb8bFWw.png" /></figure><h4>and shipping dark mode 👀 🌘</h4><p>As we scaled our team at Freetrade, we began having conversations around when it was right to use certain styles, colours and patterns and although we had a decent component library, this only existed in our design tooling. As a result, much of the rules and re-usability was being lost in translation from design to code.</p><p>This was then compounded by having no clear palette in our codebase which would often lead to the creation of new colours to fit each project:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c9c7e89782c285e4edb8251fb8ae6059/href">https://medium.com/media/c9c7e89782c285e4edb8251fb8ae6059/href</a></iframe><p>Because of this, I decided to codify the rules we’d kept in our heads and create a single source of truth™ for both design and engineering. But, before solving for this I first — as with all things — needed to identify the cause of the challenges:</p><ol><li><strong>Our colour palette was unclear<br></strong>From the list above, any idea which of those is the correct one to use for grey text? No, me neither. And, yet, on each project, the teams were required to pick from that list and hope for the best.</li><li><strong>Our rules weren’t understood<br></strong>Rules are only rules if they can be understood and enforced and so if the team don’t fully understand the “rules” we have, or we don’t have the tooling to enforce them, then they don’t exist.</li></ol><h3>Fixing our palette with design tokens 🎨</h3><p>A design token is a named entity that stores a piece of visual design information such as colour, spacing, border-style or type size. As an example, take this text:</p><figure><img alt="Left: Text link shown using color: #F7618B. Right: Text link shown using color: freedom pink. With the same results." src="https://cdn-images-1.medium.com/max/1024/1*l8TNLZburHBhKbTpcTYnQg.png" /></figure><p>It’s comprised of many tokens but, let’s focus on colour. So, Instead of using color: #F7618B you would have color: freedomPink. Whilst visually this produces the same result, with the tokenised value you know what you’re going to get.</p><h4>Getting started</h4><p>I began by creating tokens for all of our palette then, using <a href="https://github.com/salesforce-ux/theo">Theo</a> (<em>a tool from the team at Salesforce</em>) we would transform their values to the formats we use on iOS and Android. Once transformed our tokens would then be run through a custom format that we had created to spit out two files, colors.swift for iOS and colors.xml for Android.</p><h4>Now, here’s where things get fancy 🎩</h4><p>These files would then be included in the app so that they can be referenced when building UI. What makes this approach exciting (<em>at least for me</em>) is a couple of things:</p><ol><li><strong>It makes it easier to use the colour specified in the designs<br></strong>Since now all colours are pre-defined and named in human-readable ways we don’t need to pull out the colour picker or create something new. This minimises mistakes made when using colours.</li><li><strong>Colours are centralised, making changes easier<br></strong>Colours are stored in their own file. When we come to tweaking or changing one that change will be applied to every instance in which it was referenced.</li><li><strong>It removes a barrier for non-technical members of the team<br></strong>With the colour values now separated from the functional code of the core product, things get a whole-lot-less intimidating. People can now update and add colours without fear of breaking anything.</li></ol><h3>Creating rules 👮‍♀️</h3><p>As I was working on this Apple announced system-wide support for dark mode. This would add complexity to our colour palette and additional logic to factor in.</p><p>So, to understand how this would affect us we first tried to just invert everything to see how that felt and for the most part it was pretty good but some of the main things that didn’t work were:</p><p><strong>Shadows and dimmers no-longer provided visual separation<br></strong>We frequently use shadows or dimmer layers to separate an element from its background. However, shadows just make black a little more… black.</p><figure><img alt="Left: Card in light-mode differentiated from the background. Right: Card in dark-mode without differentiation." src="https://cdn-images-1.medium.com/max/1024/1*A9J7r2F8TmaketH-6pe66A.png" /></figure><p><strong>Our brand palette had been created for a light product<br></strong>When we put our light brand colours on a dark background they felt out of place and didn’t evoke the same feeling as in a light theme.</p><figure><img alt="Example of existing brand colours not looking correct in dark mode." src="https://cdn-images-1.medium.com/max/1024/1*UkZYCKQWHaG4Pv1sQ_GGaA.png" /></figure><h4>So, how do we fix these? 🔨</h4><p>Given the initial challenges we had with the team’s uncertainty around when to use certain colours or patterns, combined with the needs introduced by the addition of dark mode, we decided to combine both colour and use case into what we would call a declarative token.</p><p>This meant we could smartly invert our interface, for example: having tokens for both <strong>screen background</strong> and <strong>card background</strong>.</p><p><strong>The side effect of this change?<br></strong>This introduces many, <em>many</em> more colour tokens than before. So, to ensure we don’t begin to recreate the issues that brought about this project we would still maintain our palette as aliases i.e. Freedom Pink, Indigo, Green, etc.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/79f18638e353aa995bb5a68d922fe5a0/href">https://medium.com/media/79f18638e353aa995bb5a68d922fe5a0/href</a></iframe><p>And, they would be pulled into our declarative colour tokens.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3b4e75266e0e5e68bbfb14d8ca723796/href">https://medium.com/media/3b4e75266e0e5e68bbfb14d8ca723796/href</a></iframe><p>This is looking pretty good, but it’s not yet in the correct format. What iOS requires is a single colour string for an element. To get to this we adapted our existing custom format to combine the light and dark variants of tokens into a single string that looks like this.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/616e5f548259fee2ed896635e030b72f/href">https://medium.com/media/616e5f548259fee2ed896635e030b72f/href</a></iframe><p>So that now, when we apply card_default in our iOS app, we’ll get a result that’s applied differently in both light and dark mode.</p><figure><img alt="Left: Card on white. Right: Adjusted card on black." src="https://cdn-images-1.medium.com/max/1024/1*kCvWhBrScYwJSffxdXJySw.png" /></figure><p>Next, we needed to get the colours looking right. In most cases where we’d had issues, we found there wasn’t a single colour that would give us a colour contrast rating and visual look and feel we wanted in both light and dark mode. So, to make this work we needed to be able to provide both light and dark variants of our colours.</p><p>To do this we take a palette token, for example, apricot20 - our lightest shade of yellowish-orange - create a second version and append _light and _dark respectively.</p><figure><img alt="Left: Brand colours on white. Right: Adjusted brand colours on dark." src="https://cdn-images-1.medium.com/max/1024/1*OB7eXWNpe86ZHeZ9zalckw.png" /></figure><p>When a dark mode variant isn’t provided it will fall back to just using a single colour for both light and dark values.</p><p>Whilst this solution doesn’t provide the cleanest code it is very explicit and doesn’t leave much room for misinterpretation which is exactly what we want to avoid.</p><h3>So, where are we now?</h3><p>Our colours and rules are now coupled in code and when it comes to styling an element e.g. a card, instead of specifying the exact colour we just have color: card_default which makes it easy to know which style to use reducing the likelihood that we’d make a mistake and saving everyone a bit of time.</p><p>This also makes it simple for the design team to go in, tweak a colour token and have that change apply throughout our apps, across multiple platforms without needing to take up engineering time.</p><p>On top of all that, we have a lovely new dark mode to demo all this work.</p><figure><img alt="Gif: Transitioning between light and dark mode." src="https://cdn-images-1.medium.com/max/1024/1*31TGu_qMe4P3zzES4olOuA.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4a7ab5dc2ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving Freetrade into Figma]]></title>
            <link>https://blog.prototypr.io/moving-freetrade-into-figma-798fe289398d?source=rss-e76cd25f669e------2</link>
            <guid isPermaLink="false">https://medium.com/p/798fe289398d</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[figma]]></category>
            <dc:creator><![CDATA[Mitchell Petrie]]></dc:creator>
            <pubDate>Thu, 07 Mar 2019 17:36:43 GMT</pubDate>
            <atom:updated>2019-03-10T19:27:57.973Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dOM-MLQEIlw0wCuOIK_xtg.jpeg" /></figure><h4>Our process and what we learned</h4><p><em>I’ve had a few people ask me to share the slides from my talk at Figma London. On their own, they don’t really tell our story so I’ve put this together for those who couldn’t be there.</em></p><h4>What is Free…trade?</h4><p>So for those of you who aren’t familiar with Freetrade, we’re a challenger stockbroker. Our mission is opening the world of investing to everyone. We do this by cutting out the fees, rethinking the tech and, most importantly, using super-simple, intuitive design for our products.</p><h4>A little background</h4><p>Going back just a few months we only had one designer. However, come November last year we quickly grew the team from 1 to 3 with a 4th hire coming not long after.</p><p>We knew that having a master file with no version control wasn’t going to work for us so we wanted to explore how we evolve our process.</p><h4>What mattered to us?</h4><p>Now, there’s nothing design teams love more than to try a load of shiny new tools but really, it came down to what mattered most to us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vlQZSDfwvzNT_I42a_Xonw.jpeg" /></figure><p><strong>Open &amp; Transparent<br></strong>At Freetrade we have a super transparent culture. We share work early and often both internally and externally with our community. We have weekly design critiques, where anyone from the team can join and give feedback. We even <a href="https://www.notion.so/freetrade/6f1f87c6027642639ab342e7c161f8b8">opened up our roadmap</a> for you all to see. So we wanted our new process to reflect that transparency and enable us to share more seamlessly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IQVwdMLCiJSaRULXjOkhow.jpeg" /></figure><p><strong>Remote collaboration<br></strong>We have a partially distributed team — meaning there are often times where we’ll want to collaborate but aren’t able to sit beside one another.</p><p>Previously, collaborating like this means entering the hell that is sharing your screen and trying to guide others around, pointing frantically only to realise they can’t see anything you’re doing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TIsZ17UvaObdvh8JGgHK0A.jpeg" /></figure><p><strong>Future proof<br></strong>Because we’re a small team migrating everyone was relatively simple. But, we would be growing the team quickly and would prefer not to need to do this again anytime soon. So we wanted to make sure that the approach we took would grow with us.</p><p><strong>Our choice?</strong></p><p>Figma. Whilst we believed this would be best for our team there were some things we’d be sad to see go.</p><ul><li>Pulling live data into our designs.</li><li>Various auto-layout plugins i.e. Anima.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YTUHS9a99aclCbKDy7d-DQ.jpeg" /></figure><h3>What do we need to do?</h3><p>Now that we knew where we wanted to get too, what did we need to do to get there?</p><p><strong>Component Library<br></strong>With such a new team we knew that moving to Figma without bringing our component library with us would create a lot of inconsistency. So we decided this would be the first thing we wanted to have.</p><p><strong>Core Flows<br></strong>To make things easier for everyone we also wanted to have our core screens and flows in Figma so that people could reuse them rather than have to start from scratch each time.</p><p>This also gave us a good opportunity to iron out any issues with our component library</p><p><strong>Bring in the rest of the team!<br></strong>With both our component library and most core flows in Figma we could begin to bring in the rest of the team.</p><p>Instead of just bring everyone in all at once we asked that people just use Figma for any new projects so as not to disrupt any on-going work.</p><h4>Timelines</h4><p>I’d love to say we did some fancy cost/benefit analysis. A Gantt chart or two and spreadsheets as far as the eye could see but in reality, it looked a little more like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Xrv16SLVcthn_5lSAbnRw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3UUz_qChttMtau1c1MnQlA.jpeg" /></figure><h3>Switching Day</h3><p>So, we switched - from this point on Figma would be the tool we used for all new projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1XRyaAXAx-bRxfDhRg0quA.jpeg" /></figure><p><strong>Working together<br></strong>From day one being able to collaborate in the same file was great. We could jump on a call, and both work side by side, leaving comments or iterations of our own.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K4E_ja-ILlzJne5PeG6fsA.jpeg" /></figure><p><strong>Components<br></strong>Because of the way that overrides work in Figma we were able to go from 11 variations of a row down to just 5. And, it was a similar story for the rest of our component library. This made it easier to maintain and faster to find and use our components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a3DoSFPbw26MZ_wuChK2gA.jpeg" /></figure><p><strong>Cost savings<br></strong>Here’s your chance to make friends with your finance team.</p><p>For us, switching to using just Figma instead of Sketch, Wake &amp; Zeplin was ~65% cheaper. About £279/person each year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_LlfA0eN3JBxaGDZJVrTZg.jpeg" /></figure><h3>A not-so-obvious problem</h3><p>But, not everything went smoothly. People were familiar with our existing process and because there was no official way of marking something as the leading idea it became hard for people to focus their feedback or even know if work was ready to be built.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OeYOgGk6ANXDuA_Z8ZeqAQ.jpeg" /></figure><h4>Problem solved… right?</h4><p>I decided to start adding watermelons to designs that were my current favourite. Now, obviously, this was <em>genius</em>.</p><p>However, it didn’t catch on…</p><h4>Another approach</h4><p>After we put in more than 30 seconds of thought into this problem we decided to create a document template for our projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bsrNbB0okyMqAUEI4teAPg.jpeg" /><figcaption>This would also appear in the project browser.</figcaption></figure><p>First, we created a page for a project thumbnail this essentially maps to the epic in Jira and makes it easy for someone to go and learn more about the context of a project</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IfemqxQglg-Fq26rAQ5LbQ.jpeg" /></figure><p><strong>Page per user story<br></strong>We then created pages for each user story</p><p>We did this to make it easy to understand specific flows, keep feedback focussed to the problem we’re solving and make it easier to hand over chunks of work to developers rather than crushing them by dropping the whole project on them at once.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F322012318%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F322012318&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F764855176_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1554" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/ff15a3d2e5d75f1b218f44b4bb5c12d0/href">https://medium.com/media/ff15a3d2e5d75f1b218f44b4bb5c12d0/href</a></iframe><p><strong>Status block<br></strong>We’ve also created a component that makes it easy to set the status of a piece of work. Currently, the states we have are:</p><ul><li>Work in progress</li><li>Open for feedback</li><li>Ready for development</li></ul><p>However, iteration is a naturally messy and somewhat unstructured process so we wanted to have a place where we could explore quickly, make a mess and find the best solution.</p><p>For that, we added a drafts page:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qe-uIgp_oOhKEgMe5hxEoQ.jpeg" /></figure><p><strong>Drafts<br></strong>Here, we have every single iteration we go through as we work on a project. It’s messy but having it in its own page allows us to explore freely without clogging up more polished flows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hgEGjI6h2aFI5D-Dg9g7cw.jpeg" /><figcaption>Obligatory <a href="https://twitter.com/Petr_ie">follow me on Twitter</a> etc</figcaption></figure><h3>We’re hiring</h3><p>If you’re interested in helping to bring accessible investing to everyone come <a href="https://freetrade.io/careers/">join us!</a> We’re looking to bring in an additional two lovely people to join our design team along with a ton of other roles across the rest of the team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=798fe289398d" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/moving-freetrade-into-figma-798fe289398d">Moving Freetrade into Figma</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing for US stocks]]></title>
            <link>https://medium.com/@_mitchellpetrie/designing-for-us-stocks-f57a18011512?source=rss-e76cd25f669e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f57a18011512</guid>
            <category><![CDATA[investment]]></category>
            <category><![CDATA[investing]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[building]]></category>
            <dc:creator><![CDATA[Mitchell Petrie]]></dc:creator>
            <pubDate>Wed, 23 Jan 2019 10:10:55 GMT</pubDate>
            <atom:updated>2019-12-12T11:34:14.819Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VcaeHIojqzZWqkImY1ulfQ.png" /></figure><p>You might have noticed that yesterday we launched US stocks on the Freetrade app.</p><p>They’re already available for a few lucky people and we’ll be bringing them to everyone in the next week. Who wouldn’t want to purchase a few of those oh so shiny, no-emission Tesla shares? 🚗⚡️</p><p>As for the design work, you might think “It’s not that hard, right? Just switch the £’s → $’s.”</p><p>Sort of, but not quite!</p><p>The introduction of a foreign market brings a ton of complexities to address so let’s walk through the few that have the most impact on the design of Freetrade.</p><h4>“Just switch the £’s → $’s”</h4><p>Right now the app is only available in the UK. So it’s fair to assume that most of the people using Freetrade are familiar with investing in £’s. With the addition of US stocks, we needed to work out how to show the stock values in a way that you could relate to your whole portfolio.</p><p>So when you navigate to a stock, you’ll see the current share price in dollars. However, the current value of <strong>your investment </strong>is shown in £’s for simplicity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H5Wb-l_bbJJjidBG4LkENA.png" /></figure><p>While we believe this is the best choice for us right now, we can also see arguments for handling this differently, especially as we add additional features so <a href="https://community.freetrade.io/">we’d love to hear your thoughts too.</a></p><h4>GMT, BST, UTC, IDK…</h4><p>With US stocks comes the exciting addition of new stock exchanges: in this case the New York Stock Exchange and NASDAQ. Their opening hours are obviously based on the time in the US, so in UK time, they’re different from the open hours for the London Stock Exchange and UK stocks. Turns out Americans like daylight just as much as us!</p><p>Now I’m sure there’s some of you among us, who<em> “just know”</em> that when it’s 2pm here in the UK it’s 9am in New York. I, however, am not one of those people.</p><p>At first, we explored showing the timezone in addition to the time to make it easier to look it up and do the maths for yourselves. But we thought we could do better.</p><p>So when we speak about the opening hours of foreign markets we’ll try to make things easy by converting times to the equivalent time in your local timezone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O-ShM9E8Y3rXdbSyXda8qg.gif" /><figcaption>✨ 🧙‍♂️</figcaption></figure><p>The first example of this — as shown above — is in our handy Market hours information drawer. But you’ll also see this popping up in other areas of the app where relevant.</p><h4>Currency conversion</h4><p>The cash in your account is held in GBP so when you’re purchasing US shares there’s a little maths to be done to work out exactly how much you’re putting into a stock. Rather than put that work on you, we’ve added the live conversion value underneath the amount you enter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gF0QWmBBPmeLpauK09YUuA.png" /></figure><p>While we were designing for currency conversion, we were also working on another tweak. We know some people face issues with Basic orders failing due to price fluctuations between the time they queue the order and the time it goes through.</p><p>This would be particularly relevant for US stocks since they tend to have a higher price per single share which can lead to larger fluctuations.</p><p>So, as a simple solution, we added some code that tracks the daily price variance of a stock and some contextual text to help you know if you’ve reserved enough cash to avoid the price moving outside your range.</p><p>You can read more about this part of the project<a href="https://community.freetrade.io/t/reducing-the-number-of-failed-orders/3114"> here on our community forum.</a></p><p>We know how much everyone’s been waiting for US stocks and it’s been great working on a feature that means so much to everyone.</p><p>Working on this has also created a model for how we build the app for all sorts of overseas stocks and exchanges. We’re sure there’ll be plenty of individual nuance for each market, but it’s great to have got our first set in place.</p><p>We can’t wait to activate US investing for everyone on the app next week. Stay tuned!</p><p>👩‍💻<em> </em><a href="https://freetrade.io/careers/"><em>Help us bring free investing to the UK and beyond, check out our open roles.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f57a18011512" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Guide To Working With British Designers]]></title>
            <link>https://medium.com/@_mitchellpetrie/a-guide-to-working-with-british-designers-115faae6bc1f?source=rss-e76cd25f669e------2</link>
            <guid isPermaLink="false">https://medium.com/p/115faae6bc1f</guid>
            <category><![CDATA[britain]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[humor]]></category>
            <category><![CDATA[uk]]></category>
            <dc:creator><![CDATA[Mitchell Petrie]]></dc:creator>
            <pubDate>Thu, 14 Jun 2018 08:36:05 GMT</pubDate>
            <atom:updated>2019-08-16T10:05:13.275Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uvvbjUhpftp75nQ84xvzgw.png" /></figure><p>So perhaps, sometimes we aren’t as direct as we could be. So rather than having to change ourselves, here’s a handy guide to help you understand what we <em>really</em> mean.</p><p>What’s said: <strong>“Good”</strong><br>What we mean: <strong>“Good”</strong></p><p><em>Simple, right?</em></p><p>What’s said <strong>“Pretty good”<br></strong>What’s meant: <strong>“Really not good at all.”</strong></p><p><em>Oh.</em></p><p>What’s said: <strong>“Quite good”<br></strong>What’s meant: <strong>“Overall, pretty disappointing.”</strong></p><p>Yeah, and it’s not a whole lot clearer with the negatives either.</p><p>What’s said:<strong> “Not bad”<br></strong>What’s meant:<strong> “Great”</strong></p><h3>On an ongoing project:</h3><p>What’s said: <strong>“It’s going ok”<br></strong>What’s meant: <strong>“It’s all a mess and I haven’t slept for days”</strong></p><p>What’s said: <strong>“It’s a bit unclear”<br></strong>What’s meant: <strong>“I have no idea what we’re trying to achieve here”</strong></p><h3>On giving/receiving feedback:</h3><p>What’s said: <strong>“We should spend some more time on…”<br></strong>What’s meant: <strong>“That is the worst thing I have seen today.”</strong></p><p>What’s said: <strong>“Yeah, could do.”<br></strong>What’s meant: <strong>“No we absolutely won’t.”</strong></p><p>What’s said: <strong>“Let’s pair on this.”</strong><br>What’s meant: <strong>“I’m taking over.”</strong></p><p>What’s said: <strong>“That’s interesting.”</strong><br>What’s meant: <strong>“That’s terrible.”</strong></p><p>What’s said: <strong>“That’s out of scope”</strong><br>What’s meant: <strong>“I really would prefer that we didn’t release that ever.”</strong></p><p>What’s said: <strong>“OK thanks I’ll think about it some more”<br></strong>What’s meant: <strong>“You have been no help at all, rather you’ve wasted my time, so thanks…”</strong></p><p>What’s said: <strong>“Not entirely happy.”<br></strong>What’s meant: <strong>“Really, couldn’t be less happy.”</strong></p><p>What’s said: <strong>“Lets A-B test this.”<br></strong>What’s meant: <strong>“We’ll never revisit this.”</strong></p><p>What’s said: <strong>“I’ll keep that in mind”</strong><br>What’s meant: <strong>“Don’t expect to see any changes there”</strong></p><p>What’s said: <strong>“That’s an idea.”<br></strong>What’s meant: <strong>“That is in the most literal sense, an ‘idea’. Now, let’s never speak of it again.”</strong></p><p>Finally, sorry to <a href="https://medium.com/u/897ef2a3efa3">Alex Manthei</a>, <a href="https://medium.com/u/eea3738ca108">Anna Zawilska</a> (who have called me out the most on this) and anyone else who has the misfortune of working with me in both the past and the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=115faae6bc1f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Where’s my order?]]></title>
            <link>https://medium.com/designing-lyst/researching-without-a-researcher-2742a670fa56?source=rss-e76cd25f669e------2</link>
            <guid isPermaLink="false">https://medium.com/p/2742a670fa56</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Mitchell Petrie]]></dc:creator>
            <pubDate>Fri, 17 Nov 2017 17:15:13 GMT</pubDate>
            <atom:updated>2019-01-22T16:43:52.550Z</atom:updated>
            <content:encoded><![CDATA[<p>Lyst has one of the largest selections of fashion in the world. We have achieved this scale by holding no stock. When people buy on Lyst, they are really buying from one of thousands of fashion stores.</p><p>This has its benefits, but it comes with problems too. The most common question our customer care team receives is, “Where’s my order?” These customers were struggling to understand what was happening after they made a purchase through Lyst.</p><p>This case study is about how we tried to address this issue, showing some of the process that went into it and how we approached research without a researcher.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eeyySxI4pgzWFNQFCoRsnA.png" /></figure><p>For a while, people had been contacting Lyst to ask what was happening with their order. It wasn’t until the opening of 2017, when we sat down to talk with our customer care team, that we realised this was now creating thousands of enquiries highlighting that there was a larger problem to explore.</p><p>Reading into the customer support enquiries a few themes began to emerge. To explore these themes and get to the root of the problem we looked deeper into the kind of experience people were really having post purchase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wyrLCnJ3nOMBseDE_ynR8g.png" /></figure><h3>So, the problems</h3><p>After reviewing the existing experience, the emails we’d received and the reviews of the experience we had a good idea of what the problems were.</p><ul><li>There is no holistic overview of what’s happening with an order, leaving customers guessing.</li><li>Customers don’t know who is responsible for fulfilling what.</li><li>The existing ‘solutions’ we had in place just weren’t good enough for customers and they end up having to contact customer care.</li></ul><p><em>Or in the words of a customer…</em></p><blockquote><strong>“I want to know what’s happening with my order but I don’t know where to look to find out.”</strong></blockquote><h4>Where do we go from here?</h4><p>Having assessed the problems it was clear to us that we should be focussing on providing a single point of reference for their order, providing clarity around the process and instilling trust in the customer.</p><p>Given a lack of time we decided to move forward and design an order history. This is a common pattern amongst almost all of our partners so we felt confident moving forward with this rather than needlessly reinventing the wheel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*65Ph5APVeplk_-tGTl7DAg.png" /><figcaption>Some examples from competitors.</figcaption></figure><h3>What makes a good order history?</h3><p>With it decided that we wanted to keep things simple and leverage an existing pattern we then needed to find out <em>what makes a good order history. </em>To do this we used a mix of methods; competitor analysis, talking to friends &amp; family &amp; our knowledge of how people use Lyst.</p><p>First, keeping with spirit of not reinventing the wheel we knew we could learn a lot about what people have become accustomed to from looking at our competitors. In particular, we were interested in the kinds of information they included in their order history.</p><p>With this we then asked friends and family to sort the different types of information from the most to least important. We ran this with friends and family as a proxy for real research participants.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fn3wD5I59jw8anMmqJqkYw.png" /><figcaption>For this we used the ranking scale from Formula 1 since its heavily weighted towards to the top positions. This worked well for us as people would often find it hard to decide what was more or less important with the bottom few things but had a very clear idea of what was the most important.</figcaption></figure><p>Ideally, we’d have done actual user testing with real scenarios trialling various hierarchies of information rather than just asking people. However, we had neither the time nor resources to go beyond this during this project.</p><p>The most useful thing we did was look into all the possible pain points in the current experience and think through the potential emotional consequences for the customer. Whilst this isn’t the same as speaking to real people, it did allow us to focus on what the role of an order history could be in these circumstances.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kEwwhjbHakcbrkpfJjzgDA.png" /></figure><h4>Why was this the most useful?</h4><p>We could have looked at the usage data on our existing solution. This would show us that most people want to view delivery timings. This is obviously still important to us but it’s not those customers that are struggling with their order, nor needing to contact customer care.</p><p>With an idea of what’s important in resolving people’s problems, we were ready to move forward and start creating something real.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E9ETsZzrDMfYa6dgFza1bg.png" /><figcaption>Early sketches → Wireframes → What we shipped → A Future Version</figcaption></figure><h3>Turning what we learned into something tangible</h3><p>We started with a series of sketches, refining them through continuous iteration with the team before turning them into wireframes. Here we could begin to work on the intricacies of the messaging and interactions.</p><p>Given our original problems stemmed from a lack of clarity it was really important to us that we had one clear message coming through to customers for each of the potential scenarios.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Ntn-tEB2zO_CthGqC-Oxw.png" /></figure><p>Even without a researcher it’s still possible to test. We iterated through tons of different messaging whilst testing with friends and family to make sure that we managed to communicate exactly what we needed to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3yM1q_etbx7zM5SCow4D9Q.gif" /></figure><h3>Learning from the launch</h3><p>We launched this alongside an overhaul of our help centre. The combined impact of these projects resulted in a significant drop in order related issues being received by our customer care team. 🎉</p><p>However, from this we learned how we would have been better to launch each of these separately. It would have allowed us to measure each projects impact independently meaning we could better understand how helpful it really was to our customers.</p><h3>What else did we learn?</h3><ul><li><strong>Being coherent is key. </strong>One of the biggest downfalls of our old solution was that customers were continuously passed from one company to another, none of which acknowledged the roles of the others.</li><li><strong>Emotions matter. </strong>In a world of <em>‘data driven’</em> projects, it can be easy to forget how people are feeling when they interact with your designs.<br>For this project, the customers emotions gave us a completely different perspective to what our data would have told us.</li><li><strong>It’s the little things.</strong> We as designers spend so much time working on projects that’ll really <em>‘push the needle’ </em>that it can become difficult to make a case for projects like this.<br>But, fixing these things <strong>does</strong> matter. It may not be the most visited part of the app, nor the most exciting but to those who need it, it becomes super important.</li></ul><p>As with all projects this is a culmination of the whole team’s work so a huge thanks to Emma, <a href="https://twitter.com/xoalexo">Alex</a>, <a href="https://twitter.com/marcoshdezcif">Marcos</a>, <a href="https://twitter.com/carlostify">Carlos</a>, <a href="https://twitter.com/mikeaquilina4">Mike</a> &amp; Madhuri. 🙌</p><p><em>If you want to work on projects like this we’re </em><a href="https://www.lyst.com/careers/"><em>hiring at Lyst</em></a><em>.</em></p><p><em>I sometimes write very short things on </em><a href="https://twitter.com/_MitchellPetrie"><em>Twitter</em></a><em>. </em>🤷‍</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2742a670fa56" width="1" height="1" alt=""><hr><p><a href="https://medium.com/designing-lyst/researching-without-a-researcher-2742a670fa56">Where’s my order?</a> was originally published in <a href="https://medium.com/designing-lyst">Designing Lyst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>