<?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[Life at Farewill - Medium]]></title>
        <description><![CDATA[Stories from and about the team at Farewill - Medium]]></description>
        <link>https://medium.com/farewill?source=rss----e1959b290f5e---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Life at Farewill - Medium</title>
            <link>https://medium.com/farewill?source=rss----e1959b290f5e---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 11:44:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/farewill" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Onboarding — not even ‘remotely’ problematic]]></title>
            <link>https://medium.com/farewill/onboarding-not-even-remotely-problematic-edcb110130b6?source=rss----e1959b290f5e---4</link>
            <guid isPermaLink="false">https://medium.com/p/edcb110130b6</guid>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[benefits-of-remote-work]]></category>
            <category><![CDATA[remote-onboarding]]></category>
            <dc:creator><![CDATA[Liz Pope]]></dc:creator>
            <pubDate>Tue, 08 Jun 2021 12:59:32 GMT</pubDate>
            <atom:updated>2021-06-08T12:59:32.584Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Onboarding — not even ‘remotely’ problematic</strong></h3><p>I’ve recently joined Farewill, and though (like most people) I’ve been working remotely for the past 12+ months, the idea of onboarding remotely was still slightly daunting. Starting at a new company is all about interacting with others and usually involves a lot of leaning across the desk to ask your new colleagues questions. In the past year I’ve got used to not having colleagues “across the desk” and have instead jumped into slack, but that has been with people I already knew, not those I’m building new relationships with. So I’ve been pleasantly surprised at how much I’ve enjoyed onboarding remotely. I’ve not just thought it’s “ok”, but there are actually things which I think I would have missed if I’d gone into the office! They include the following….</p><h3><strong>Everyone is wearing digital name badges</strong></h3><p>It’s difficult to learn everyone’s names when you are being given a lot of new information and meeting new people all the time. So it’s not unusual to have those awkward moments of “is that Billie or Millie?” and spend the meeting trying awkwardly to not use their name yet still be polite! Remote onboarding solves this, as names are clearly visible so it’s just a quick hover over a profile picture or video box to give the reminder you need and save the awkwardness!</p><h3><strong>You can wear comfy slippers!</strong></h3><p>Ok, so this isn’t just about slippers and jogging bottoms but more about the fear of what to wear. Picking an outfit for your first day at a new job is daunting and time consuming. If I’d been going into the office then I probably would have spent half of the Sunday trying on everything I own, becoming increasingly worried and frustrated only to declare “I have nothing to wear!”. I’m not saying I didn’t give my first day’s outfit any thought or that I didn’t put on slightly more makeup than usual for working from home, but there’s certainly less stress when you’re only going to be seen from the waist up and not in high definition!</p><h3><strong>There’s no commute worry</strong></h3><p>We all want to be on time (ideally a little early) for our first day, and not to be hot and bothered or panicky from getting lost because you got off at the wrong bus stop or missed the office entrance. Well, there is no fear of that when your first day is from home — I’d struggle to get lost in the couple of metres between my bedroom and the spare room where my desk is!</p><p>It also meant I got a decent night’s sleep, as I wasn’t worried about missing my alarm and then missing the train etc… Farewill does a 10 am start in your first week, so I took the opportunity to go to the gym or walk the dogs each morning, which cleared my head and gave me a nice vitamin D boost. It’s something I’m trying to build a habit of, it will mean I’ll have to get up earlier (as the 10 am starts don’t last forever, though flexible working hours give me plenty of options) but I’ve found it so beneficial.</p><h3><strong>Privacy if you need it</strong></h3><p>Although building relationships and spending time with people is important in a new job, having some privacy is also important if you want to get away from things a little. I’m definitely not suggesting that if you’re struggling you should put a brave face on and pretend you are fine — but more that if you do have just a small moment of panic or feel slightly overwhelmed that you can appreciate the privacy that being at home affords you. I’ve certainly found home comforts (being able to go and cuddle my dogs for instance!) a real perk if I need 10 minutes to clear my head. I can do so without prying eyes or anyone getting concerned about me like they might if I were in the office and had a slightly confused look on my face.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Okdt7pu_FxZLZZdqbMXVyg.jpeg" /></figure><p>These are just a few things I’ve enjoyed about onboarding remotely. I’m sure there have been others — the remote social events and budget for lunch at the fortnightly Passion Talks spring to mind, but they are more Farewill specific!</p><h3><strong>Remote onboarding post-pandemic</strong></h3><p>We all know by now that remote working is very effective, and the plans that most businesses are aiming for post-pandemic is ‘hybrid’ working, where people are given the choice as to how much time they spend in the office. But a trap I think some companies might fall into is that when someone is onboarding they will be asked to be in the office more, and might not get remote privileges until later.</p><p>I’d always thought (pre-pandemic) that those who were joining as remote workers should spend the first fortnight fully in the office, as that was the best way for them to onboard. Back then that might well have been the correct decision, but given how remote working has matured and how much more inclusive it now is, I advise against that insistence and encourage that the hybrid (or fully remote) working options should be given to all employees, in onboarding or not.</p><p>You might be thinking, but surely it makes more sense on day 1 to go into the office to get your laptop? But why? We’ve been shipping laptops for the last year, what’s to stop us from keeping doing so. Or at least offering people the option. “Would you rather do day 1 in the office or at home where you can wear your slippers?”……I know which I would choose!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edcb110130b6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farewill/onboarding-not-even-remotely-problematic-edcb110130b6">Onboarding — not even ‘remotely’ problematic</a> was originally published in <a href="https://medium.com/farewill">Life at Farewill</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet the Farewill design team: part two]]></title>
            <link>https://medium.com/farewill/meet-the-farewill-design-team-part-two-4ab99d757ac8?source=rss----e1959b290f5e---4</link>
            <guid isPermaLink="false">https://medium.com/p/4ab99d757ac8</guid>
            <category><![CDATA[product-designer]]></category>
            <category><![CDATA[design-teams]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Lucija Penko]]></dc:creator>
            <pubDate>Fri, 09 Apr 2021 09:16:34 GMT</pubDate>
            <atom:updated>2021-04-09T09:16:34.221Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A blog series about what it means to be a designer at Farewill, and what problems we’re solving at the moment.</em></p><p>Death is hard. So many people do not talk about what happens once they’re gone, or find it difficult to manage the long, complex admin after a loved one dies. At Farewill we’re on a mission to change the way the world deals with death. It’s a challenging problem space but it can be incredibly rewarding.</p><p>We try to break the taboo by getting people talking more about death, how they want to be remembered and make it easier for them to plan ahead. One of our latest projects involved exploring how urns can reflect who we really are <a href="https://farewill.com/urns">in collaboration with ceramic artist John Booth</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KWEN4D3ZBIgCWP5czIYe7g.png" /><figcaption>Snapshot of the John Booth collaboration page</figcaption></figure><h3><strong>We’re a bunch of product and marketing designers, user researchers and writers</strong></h3><p>This is part two in the blog series where we showcase our design teammates and shine a light on the challenges we’re solving at the moment. <a href="https://medium.com/farewill/meet-the-farewill-design-team-part-one-8a3ff97673e6">A few weeks ago we told you a bit about how we work and you met Han, Louis and Victor</a>. This time round we’re introducing our user researcher Clare and product designers Lucija and Tom.</p><p><em>Want to join us? </em><a href="https://farewill.com/careers"><em>We’re looking for senior product designers and user researchers</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*peiZnqjOMo-guG9ErpmuTQ.png" /><figcaption>Clare Ridd</figcaption></figure><h3><strong>Clare Ridd</strong></h3><p><em>Lead user researcher<br>Social: </em><a href="https://www.linkedin.com/in/clare-ridd-74356a84/?originalSubdomain=uk"><em>LinkedIn</em></a><em>, </em><a href="https://twitter.com/clareridd?lang=en"><em>Twitter</em></a></p><p><strong>How did you become a user researcher?<br></strong>I started out doing research working on government digital transformation. It was the early days of government digital and we were just starting to work on signing transactional services, so a really exciting time to be doing the work. I had never heard of user research before and was working in a strategy role. But I had a really great manager who arranged for me to go and meet with the user researcher. I was hooked from day 1: the work spoke to my interest in people, in design and in technology.</p><p><strong>What do you like about working at Farewill?</strong><br>Understanding how people think about planning for, and dealing with death is fascinating. The more people we talk to the more we learn about how people’s personal beliefs, culture and background influence their choices. Being part of creating products that can meet as many people’s needs as possible while catering for this individuality is a hugely exciting challenge.</p><p><strong>What motivates and inspires you?</strong><br>Talking to people about really difficult topics and when they’ve often had been through a really difficult experience such as bereavement is not only a privilege but it also challenges me to be a better researcher. I couldn’t do any one that without being part of a fantastically talented and supportive team. It’s incredibly motivating to work with people who are curious about people’s experiences and so are invested in doing research and acting on the outcome.</p><p><strong>What challenge are you working on right now?</strong><br>Right now I’m working on expanding what we offer as part of our funeral services. I’m working in a multi-disciplinary team alongside a designer, writer, product manager and engineers to work out what the next thing we can offer people is — and then launch it!<br>I also get to work on other projects that aren’t part of my main team — things like understanding why people start but don’t finish their wills, and how we can build personas that allow us to understand the full depth and complexity of people’s experiences and use this to build better products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kLZdaZkmmDoQY0x5SBC3Qg.png" /><figcaption>Clare running a remote user testing session</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*LIZ0_1Bop1N7_ziws9RVew.jpeg" /><figcaption>Lucija Penko</figcaption></figure><h3>Lucija Penko</h3><p><em>Product designer<br>Social: </em><a href="https://www.linkedin.com/in/lucija-penko-34105577/"><em>LinkedIn</em></a></p><p><strong>How did you become a product designer?</strong><br>I wanted to make things, innovate and dedicate my energy on projects with a positive social impact. That’s why I chose to study architecture, to build things and plan cities. I worked for a few years as an architect before deciding to make a change and pursue a new career as a product designer. Long story short, here I am.</p><p><strong>What do you like about working at Farewill?</strong><br>The culture — I’m surrounded by the smartest, the most driven and the kindest bunch of people I’ve ever worked with. It’s an environment full of inspiring challenges and opportunities to learn. The mission — I think it’s a rare opportunity and a privilege to work on trying to answer important questions around dealing with death. It affects us all at some point in our lives and there’s so much opportunity to improve.</p><p><strong>What motivates and inspires you?</strong><br>I live for feedback. Any kind, good and bad. It’s an invaluable way of seeing my work ‘in the wild’, understanding how I can make it better and it also gives the first hand insight into the impact my efforts have. I also really love discussing big concepts and crazy ideas that make me question reality. I’m currently obsessed with the concept of time as a dimension, how it affects our perception of things and how it all links back to design stuff.</p><p><strong>What challenge are you working on right now?</strong><br>Since joining I’ve worked on a range of projects, from customer facing challenges, to improving our internal tools to help our operations team better focus on customer needs. But at the moment my main focus is centered around helping build Farewill’s design system. It’s a deep dive into the intricacies of what a great product looks like and also an amazing opportunity to focus on accessibility and uncovering ways we can make our products work better for everyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*95YL0Hb9QU9gQ0oslvRiAA.png" /><figcaption>Buttons components and a snapshot of a page in the design system</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*YjuzeiWD34G_pAK4XTqbkQ.png" /><figcaption>Tom Hiskey</figcaption></figure><h3>Tom Hiskey</h3><p><em>Lead product designer<br>Social: </em><a href="https://twitter.com/tomhiskey?lang=en"><em>Twitter</em></a></p><p><strong>How did you become a product designer?</strong><br>In a very roundabout way, starting 11 years ago while running a small and unsuccessful startup. Long story.</p><p><strong>What do you like about working at Farewill?</strong><br>The mix of kindness and learning. We’ve done a lot to normalise conversations about mental health and wellbeing (we even have a free service with external counsellors, which I’ve used). We’re kind and we support each other. But we also love to learn. The design crit is a good example of that — a safe space where we help each other solve problems and improve as designers.</p><p><strong>What motivates and inspires you?</strong><br>To pick one thing — hearing from customers and their incredibly rich, personal experiences. It can be touching and emotional, and it brings home why we’re here.</p><p><strong>What challenge are you working on right now?</strong><br>I’ve been working with Clare on personas. They boil down around 2 years of user research into 5 stories. Personas get a bad rap at times, and we wanted ours to be genuinely relevant and useful — to help us make better product decisions and empathise with our customers. It’s been an incredibly thorough and rewarding process, and at times it’s been emotional reading about people’s experiences of death. We’re going to make our personas public and blog about how we made them — coming soon!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0wPu7C-9roZCr-ORI8mx4Q.png" /><figcaption>Snapshot of a persona</figcaption></figure><p>Enjoyed reading this? If you haven’t already, have a look at <a href="https://medium.com/farewill/meet-the-farewill-design-team-part-one-8a3ff97673e6">part one</a> of the series and stay tuned for more intros from the team in the next few weeks.</p><p><em>Want to join us? We’re looking for </em><a href="https://farewill.com/careers"><em>senior product designers and user researchers</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ab99d757ac8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farewill/meet-the-farewill-design-team-part-two-4ab99d757ac8">Meet the Farewill design team: part two</a> was originally published in <a href="https://medium.com/farewill">Life at Farewill</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet the Farewill design team: part one]]></title>
            <link>https://medium.com/farewill/meet-the-farewill-design-team-part-one-8a3ff97673e6?source=rss----e1959b290f5e---4</link>
            <guid isPermaLink="false">https://medium.com/p/8a3ff97673e6</guid>
            <category><![CDATA[product-designer]]></category>
            <category><![CDATA[design-teams]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Lucija Penko]]></dc:creator>
            <pubDate>Fri, 26 Mar 2021 16:13:25 GMT</pubDate>
            <atom:updated>2021-03-26T16:13:25.563Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A blog series about what it means to be a designer at Farewill, and what problems we’re solving at the moment.</em></p><p>Whether you’ve lost someone you love or are facing up to your own mortality, it’s a stressful process. The big, gloomy industry behind it doesn’t help. That’s why so many people die without talking about what happens once they’re gone, and others get lost in the complex, expensive admin after somebody dies.</p><p>We created <a href="https://farewill.com/">Farewill</a> with a clear mission in mind: to change the way the world deals with death. By putting ourselves in our customers’ shoes and always prioritising their needs, we want to make it easier to plan ahead, deal with death, and get people breaking the taboo.</p><p>That leaves us with a challenging, but rewarding, problem space. How we design solutions to these problems is at the heart of how Farewill functions.</p><h3>We’re a bunch of product and marketing designers, user researchers and writers</h3><p>We’re structured as a guild, which means we’re each part of a different cross-functional product team, alongside people like product managers, engineers and data analysts.</p><p>But we love spending time together as a design team too. We get together in <a href="https://medium.com/farewill/design-crits-how-we-make-better-products-by-sharing-openly-6d03d35bf32">weekly design crits</a>, fortnightly show and tells, and the odd social (we got creative on Zoom…). We think it’s super important that everyone in the company feels like they’re part of the design process, which means we keep our rituals open to anyone who wants to contribute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*paYj7Ww3XVifAz7tEgKW_Q.jpeg" /><figcaption>Zoom room shenanigans</figcaption></figure><p>This weekly series will shine a light on who we are and what working at Farewill means to us. Up first, you’ll meet Han, Louis and Victor.</p><p><em>Want to join us? We’re looking for </em><a href="https://farewill.com/careers"><em>senior product designers and user researchers</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*MOzSaOfVygvczuj9p9vGfw.jpeg" /><figcaption>Han Li</figcaption></figure><h3><strong>Han Li</strong></h3><p><em>Product designer</em><strong><em><br></em></strong><em>Social: </em><a href="http://www.linkedin.com/in/hanli-designer"><em>LinkedIn</em></a></p><p><strong>How did you become a product designer?</strong><br>Growing up I enjoyed making art, particularly using mediums such as printmaking and painting. I ended up going to an art school where they also offered graphic design. I spent a few years working in Museums, not as a designer at first, but a generalist embedded in digital teams. I got to learn about user experience design and digital product development.</p><p><strong>What do you like about working at Farewill?</strong><br>To see people celebrating each other’s achievements, giving each other a hand and all working towards helping people deal with death. We regularly hear about the impact of our work in our weekly company meeting, where we highlight a customer story of the week.</p><p><strong>What motivates and inspires you?</strong><br>Everyday I get to work with fun, inspiring and talented colleagues. We make time to get to know each other through coffee chats and team socials, and we regularly share work in progress in our design crits.<br>I love taking the time to listen to podcasts whilst doing everyday things, like running or cooking. It sparks new ideas and is a fun way to learn.</p><p><strong>What challenge are you working on right now?</strong><br>When someone dies, it’s an emotional and difficult period for their family and loved ones. There’s also a lot to sort out — from planning the funeral to the more administrative work of contacting organisations and closing down accounts.<br>We want to design our services so they help customers to focus on the stuff that matters, instead of doing the admin work such as contacting banks or completing forms. The first step is to help people understand what they need to do, and then help them find the right service for their needs. That could be taking everything off their hands, or a more cost-effective service where we just help with the legal forms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sODpOrflk8-IGxMfSXcAlg.png" /><figcaption>Design explorations in Figma</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*Y9wagoCNKOdzSknxlLoqpQ.png" /><figcaption>Louis Buck</figcaption></figure><h3>Louis Buck</h3><p><em>Lead marketing designer</em><strong><em><br></em></strong><em>Social: </em><a href="https://www.linkedin.com/in/louis-buck-55883174/"><em>LinkedIn</em></a><em>, </em><a href="http://www.instagram.com/louis_louis"><em>Instagram</em></a></p><p><strong>How did you become a designer?</strong><br>As a teenager, I never saw it as something I could be when I grew up. Even though I was constantly drawing skateboarding and band logos, and coding my Myspace to be super cool (cough). Then at university I was designing everything for club nights I used to run, whilst studying for a business degree. My first job was actually in IT — and when the need for a website came along, I volunteered and had a bit of an epiphany. I started to find reward in designing solutions to problems.</p><p><strong>What do you like about working at Farewill?</strong><br>I’ve always enjoyed learning how to change people’s perceptions through design. I like working somewhere that’s trying to change the norm for the better. I never want to stop learning about design. I’m constantly soaking up new wisdom and ideas, working with people with lots of different skill sets.</p><p><strong>What motivates and inspires you?</strong><br>A chance to be creative and try new things. Other designers inspire me the most.</p><p><strong>What challenge are you working on right now?</strong><br>I’ve been working on how we can bring empathy and warmth when delivering ashes to our customers. Finding a way we could — as a company — reduce that anxiety (even just a little bit) has been hugely challenging, inspiring and rewarding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ktC6IML5gHNQPZ9roczDrw.jpeg" /><figcaption>A snippet of the ashes scattering guide</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*ZTzFvU1lYakFiy3IXqg7mg.png" /><figcaption>Victor Hwang</figcaption></figure><h3>Victor Hwang</h3><p><em>Lead product designer</em><strong><em><br></em></strong><em>Social: </em><a href="https://www.linkedin.com/in/vfhwang"><em>Linkedin</em></a><em>, </em><a href="https://twitter.com/_victorhwang"><em>Twitter</em></a></p><p><strong>How did you become a product designer?</strong><br>I spent far too long in Photoshop as a child, making <a href="https://twitter.com/ultrabrilliant/status/956471141530513408">forum signatures</a> and <a href="https://www.google.com/search?q=neopets+guild+layouts&amp;tbm=isch">neopets guild layouts</a>. After school I studied graphic design and then ended up on a UX grad scheme at the BBC.</p><p><strong>What do you like about working at Farewill?</strong><br>There’s lots to like! I think most of all it’s the opportunity to tackle a really tough, human problem with a bunch of incredibly talented and motivated people. I also like that we value different strengths across the design team. We’ve done lots of pairing, even through lockdown.</p><p><strong>What motivates and inspires you?<br></strong>I find Gunpei Yokoi’s philosophy of ‘<a href="https://en.wikipedia.org/wiki/Gunpei_Yokoi#:~:text=%22Withered%20technology%22%20in%20this%20context,fun%20gameplay%20are%20more%20important.">Lateral Thinking with Withered Technology</a>’ incredibly inspirational. And I like looking at buildings. Recently I’ve been enjoying <a href="https://www.thingsyoucanbuy.co.uk/">Stefi Orazi’s perambulations</a>.</p><p><strong>What challenge are you working on right now?<br></strong>We’re in discovery at the moment, trying to figure out how we could make organising a funeral a better experience. Most people are doing it for the first time, and there’s obviously lots of other things to deal with at the same time when someone dies. We’re testing loads of different service models, looking at how we can create a human connection at every stage of the process. It’s a really exciting challenge!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bTHRJgTrk-X0x5LMPgzVjA.png" /><figcaption>Early prototype of an online funeral planning service</figcaption></figure><p>Like what you just read? Stay tuned for more intros from the team next week.</p><p><em>Want to join us? We’re looking for </em><a href="https://farewill.com/careers"><em>senior product designers and user researchers</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a3ff97673e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farewill/meet-the-farewill-design-team-part-one-8a3ff97673e6">Meet the Farewill design team: part one</a> was originally published in <a href="https://medium.com/farewill">Life at Farewill</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Internal tools — things we’ve learned from building software just for us]]></title>
            <link>https://medium.com/farewill/internal-tools-things-weve-learned-from-building-software-just-for-us-b05a9b9dc315?source=rss----e1959b290f5e---4</link>
            <guid isPermaLink="false">https://medium.com/p/b05a9b9dc315</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[internal-tools]]></category>
            <dc:creator><![CDATA[Tom Hiskey]]></dc:creator>
            <pubDate>Mon, 05 Oct 2020 16:02:04 GMT</pubDate>
            <atom:updated>2020-10-05T16:50:13.916Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Internal tools — things we’ve learned from building software just for us</strong></h3><p>As Farewill grows, so does the importance of our internal tooling — the software unseen by customers that helps power our services. We build much of it ourselves, and we take a great deal of care over it.</p><h3>Why do we build internal tooling?</h3><p>Our decision to build our operational software was very carefully considered and well researched. It’s now a key part of our product strategy. Why and how we took that view deserves its own blog post! One way to sum it up is that it gives us a level of control over both the experience of our operational teams, and by extension our customers, that we felt we couldn’t achieve by buying off-the-shelf.</p><p>Here are a few things we’ve learned, and the impact it has on life at Farewill.</p><h3>1 . Treat internal users like customers</h3><p>We design Backstage (the name we give to the tools we build) with the same care as we would any part of our customer-facing product.</p><p>That means adhering to our usual high standards of content design, usability and clarity. For example:</p><ul><li>The words we use in our internal tools are consistent with our customer-facing products (e.g. ‘the person who died’ rather than ‘the deceased’)</li><li>We write plainly, but also appropriately for the context (for the parts of the system used solely by legal specialists, it’s ok to use some jargon)</li><li>We use the same components as our customer-facing products (typography, buttons, errors, labels etc)</li></ul><p>Our aim is to give new starters a shallow learning curve, and everyone a delightfully fast and accurate experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/918/1*jziCUzQWkgphwEqDCqiVCw.png" /><figcaption>We approach internal tooling with the same sensibilities as our customer-facing products</figcaption></figure><h3>2. N<strong>urture short feedback loops</strong></h3><p>A short feedback loop means learning and improving things quickly. That’s one of the joys of building Backstage.</p><p>Our users are no more than a desk or two away — or in these more complicated times, a Zoom call. Like a driving test, we know almost instantly if we’ve ‘passed’ or ‘failed’ and what to improve on next time.</p><p>These loops don’t happen without effort, so we nurture them:</p><ul><li>Users are involved in projects from the start — almost all our probate operations and legal team participated in a recent kick-off, for example</li><li>We run projects openly— written and verbal project updates, one-to-one chats, observation sessions, open design processes, etc</li><li>In probate, a member of our operations team has a specific part of her role dedicated to joining up with the product team — she helps give feedback and produce training materials, among other things</li><li>Similarly, our lead probate solicitor is part of our product team and joins us for rituals and feedback sessions</li><li>Thankfully our users are incredibly engaged with the process and generous with their time and thoughts — we couldn’t do it without them!</li></ul><p>These feedback loops are not only beneficial for product outcomes, but also for the wider Farewill team. The Ops team tells us it’s fun to be involved in the product side of a startup, and they’re grateful when their feedback leads directly to outcomes which make their jobs easier.</p><p>As our cremation ops team member Catrin said after a recent project:</p><blockquote>We can now add three or four new customers in the time it took to add a single customer, the form generation saves hours every day!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yfy2akHlmA5MTuR2CFJGag.png" /><figcaption>Needs gathered from users in a workshop for internal tooling</figcaption></figure><h3>3. Relish the <strong>wonderfully thorny design challenge</strong></h3><p>As designers at Farewill we tackle a variety of juicy problems, from conversion rates on a sign-up form to helping customers customise a funeral. I love the challenges that come with internal tooling, including:</p><ul><li>Domain knowledge —getting deeply embedded in a subject (in our case, the legal and operational side of death)</li><li>Operational knowledge — getting to know how the company works and adapting when processes change</li><li>Service design — helping identify, unpick and improve the way the different elements of our services join up</li><li>Usability — making complex tasks quick to complete, even for new starters</li></ul><p>Not only is it a fun and challenging area to be involved in, it’s deeply rewarding to be simplifying things for our teammates and indirectly improving customer experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*ZrjuxEVcCI-DQGPT2CgqUw.png" /><figcaption>An excerpt from a service blueprint</figcaption></figure><h3>4. <strong>Understand the ‘why’</strong></h3><p>There’s an adage in product design that ‘users don’t know what they want’.</p><p>I prefer to say that we don’t expect users to be product designers. It’s not their job to think about consistency, usability, scalability or feasibility. So we try not to take all ideas at face value — we dig beneath the ‘what’ and get stuck in to the ‘why’.</p><p>That’s particularly true of internal tools. They can be addressing hugely complex processes, and our users are often subject matter experts. They may have years of ideas and expectations from previous jobs.</p><p>But we don’t want simply to replicate what’s come before.</p><p>So as a product team we try to get to the nub of the problems and work up from there. We do that in a bunch of ways such as observing users, asking a lot of ‘why’ questions, and using wireframes to test and iterate on ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m_gYOdU6jRilxUQ0Xcc9Lg.jpeg" /><figcaption>A remote user test with early stage Backstage ‘wireframes’ (un-styled outlines)</figcaption></figure><h4>An example</h4><p>Our probate team had different ways to mark a case as needing attention — placing a card in a certain column, using labels, leaving comments and tagging teammates. We didn’t want to blindly replicate this behaviour in our own tools, so we tried to understand the problems that the team needed solving.</p><p>We ended up achieving the same outcome in a simpler way, with a ‘Priority case’ toggle and more powerful filters to hone in on difficult cases.</p><p>After all the care and effort, it’s wonderful to get feedback like this from an ops team member:</p><blockquote>What you’ve done is amazing. The burden has been lifted!</blockquote><h3>A few failures</h3><p>If it sounds like we’ve got this nailed, we haven’t. Alongside many successes, we’ve launched features that have flopped. For a feature about logging particular complexities with a case, we rushed into it because we thought we knew the answers, but we hadn’t made the most of those wonderfully short feedback loops I mentioned earlier. It turned out we’d got it wrong. We’re still learning!</p><h3><strong>Final thoughts</strong></h3><ul><li>We regularly bring in-progress designs for Backstage to <a href="https://medium.com/farewill/design-crits-how-we-make-better-products-by-sharing-openly-6d03d35bf32">our design crit</a></li><li>We need to get better at making Backstage more accessible — for example, I worry that we’d struggle to accommodate visually impaired team members</li><li>Our internal team all use large screens, so we don’t need to design Backstage to be responsive (thank goodness — that’s a daunting prospect!)</li><li>Measuring the success of projects for internal tools can be difficult, but it’s doable — something for another blog post</li></ul><h3><strong>Join the team!</strong></h3><p>Keep a look out for product jobs at Farewill and help us build our internal tools. Or become a sales, ops or legal team member and enjoy using them! Current openings are on <a href="https://farewill.com/careers">our careers page</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b05a9b9dc315" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farewill/internal-tools-things-weve-learned-from-building-software-just-for-us-b05a9b9dc315">Internal tools — things we’ve learned from building software just for us</a> was originally published in <a href="https://medium.com/farewill">Life at Farewill</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design crits — how we make better products by sharing openly]]></title>
            <link>https://medium.com/farewill/design-crits-how-we-make-better-products-by-sharing-openly-6d03d35bf32?source=rss----e1959b290f5e---4</link>
            <guid isPermaLink="false">https://medium.com/p/6d03d35bf32</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[design-critique]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[crit]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Tom Hiskey]]></dc:creator>
            <pubDate>Wed, 11 Mar 2020 11:05:41 GMT</pubDate>
            <atom:updated>2020-05-11T17:12:36.951Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Design crits — how we make better products by sharing openly</strong></h3><p>Design crits at Farewill are a fun, humbling and high impact part of our design process.</p><h3>What is a crit?</h3><p>A crit (short for critique) is a get-together of designers and others to share and comment on work-in-progress designs.</p><p>Farewill’s design crit takes place every Tuesday at 3pm. The format is fairly simple:</p><ul><li>On a Tuesday morning, anyone hoping to share something posts a brief description on our #design Slack channel. We use this to set our agenda.</li><li>At the crit, the presenter gives some context — for example, about research, data, needs and whether the design is 30%, 60% or 90% done</li><li>They say what sort of feedback they’re looking for — e.g. anything at all, or honing in on a specific feature</li><li>They present the designs, then there’s a group discussion</li><li>The presenter takes notes</li></ul><p>Our crits are open to anyone. The Design Guild always attends and we’re almost always the ones sharing the designs. Other regular visitors are <a href="https://medium.com/@tambuildsthings">Tam</a> and <a href="https://twitter.com/jmaskell">James</a>, our product managers, and <a href="https://twitter.com/dg_farewill?lang=en">Dan</a>, our CEO, plus developers like <a href="https://twitter.com/charlotte_dann?lang=en">Charlotte</a>.</p><figure><img alt="Louis, Victor, me, Clare and Ethan (L — R): the Farewill Design Guild" src="https://cdn-images-1.medium.com/max/1024/1*UvwzdHbL1vgqDRVoxuWGJg.jpeg" /><figcaption>Louis, Victor, me, Clare and Ethan (L-R): the Farewill Design Guild, at a design crit. Tam is out of shot.</figcaption></figure><p>It took us a few months to get comfortable with the crit format as a team. Now, we often have external guests. We recently welcomed visitors from Lloyds Bank, a product manager keen to see how we do things, and students considering a career in user research.</p><h3>Our crit rules</h3><p>To help our crits run smoothly we have 4 main rules. We stole them from Sarah Richards’ wonderful book, <a href="https://contentdesign.london/book/">Content Design</a>. They are:</p><ol><li>be respectful: everyone did the best job possible with the knowledge they had at the time</li><li>only discuss the design / content, not the person who created it</li><li>only give constructive criticism: ‘that’s crap’ is unhelpful and unacceptable</li><li>no one has to defend a decision</li></ol><p>We want everyone to be clear and direct, but to be nice. That’s an important part of the normalisation process: people will be less likely to share work in a crit if they don’t consider it a safe space.</p><h3>An example</h3><p>I recently brought some rough sketches for an internal tool I was working on for our probate team. They were 30% done, at most. In the spirit of vulnerability and sharing early, I used the crit to get feedback on some questionable ideas…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DnPsisGTgGICIG8GHB7Ikw.gif" /><figcaption>A rough sketch I brought to our design crit</figcaption></figure><p>Feedback included:</p><ul><li>The way users need to mark sections as complete is confusing</li><li>The dark, floating list of things to do is confusing too, and why is it at the bottom of the screen?</li><li>Because it’s at the bottom, it could be a long way from the section header, which could make things unclear or less usable</li><li>The ‘blob’ illustration is just ‘juice’ — a needless addition that could be off-putting for users</li></ul><p>The feedback helped to nudge the designs forward, which meant when we tested them with users we weren’t doing so with half-baked ideas.</p><p>Thanks in part to the crit, the section above ended up looking more like this…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F-PzAfhYNXY6L50IMvngag.gif" /><figcaption>A later sketch which evolved from crit feedback, research and testing</figcaption></figure><h3><strong>Making the most of a crit</strong></h3><p>I get the most out of a design crit when I share work at an early stage. Designs that are 30% can have a number of glaring problems. That’s ok! It’s good to root them out quickly — the crit is a great forum for doing that.</p><p>But it does mean being vulnerable and humble, and focusing on outcomes over ego. It’s important that sharing scrappy work is normalised, so everyone feels comfortable airing their dirty laundry. Crits are bad when they become an ego-stroking ‘show and tell’.</p><p>Giving a bit of context can be very helpful, but teammates will rarely know as much about the problem as the presenter. That’s ok — it’s fine to keep things subjective. The presenter can assess and cherry pick feedback depending on how it fits with evidence from users.</p><p>Much of my work has nudged forward or significantly improved by sharing early and openly at the crit. By sharing designs with my amazingly talented colleagues, I’ve learned a lot.</p><h3>Part of a wider process</h3><p>Our design crit is one part of a wider product design process. We start by identifying user needs and problems from user research (owned by our researcher <a href="https://twitter.com/clareridd?lang=en">Clare</a>) and data. We articulate business requirements and work with stakeholders, PMs and developers from start to finish. We run a very open, collaborative process. We test our designs with users. We iterate. We measure.</p><p>The crit is no replacement or shortcut for any of this. But as part of a healthy, balanced design diet, it can be super useful.</p><blockquote>As part of a healthy, balanced design diet, a crit can be super useful</blockquote><h3>Join the team!</h3><p>Our crits are a fun, safe space which have helped me improve as a designer. If you’re a product designer, marketing designer, content designer or user researcher, keep a look out for creative jobs at Farewill — <a href="https://farewill.com/careers">https://farewill.com/careers</a>. We’d love you to join our team, and our next crit!</p><p>If you’d like to read more about crits, check out:</p><ul><li><a href="https://medium.com/swlh/using-the-30-60-90-framework-for-design-critique-960b68026b6f">Using the 30–60–90 Framework for Design Critique</a></li><li><a href="http://contentdesign.london/wp-content/uploads/2017/09/sarah-richards.content-design.poster.3.pdf">Sarah Richards’ crit rules poster</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d03d35bf32" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farewill/design-crits-how-we-make-better-products-by-sharing-openly-6d03d35bf32">Design crits — how we make better products by sharing openly</a> was originally published in <a href="https://medium.com/farewill">Life at Farewill</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to talk to your customers by this time next week]]></title>
            <link>https://medium.com/farewill/how-to-talk-to-your-customers-by-this-time-next-week-bf0fa182d7a2?source=rss----e1959b290f5e---4</link>
            <guid isPermaLink="false">https://medium.com/p/bf0fa182d7a2</guid>
            <category><![CDATA[customer-interview]]></category>
            <category><![CDATA[product-discovery]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[research-methods]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Tam Finlay]]></dc:creator>
            <pubDate>Mon, 19 Aug 2019 12:03:50 GMT</pubDate>
            <atom:updated>2019-08-19T12:03:53.042Z</atom:updated>
            <content:encoded><![CDATA[<p>It is easy to fall into the paradox pit of knowing you should be talking to your customers but just never quite getting around to doing it.</p><p>Most Product teams know that customer research is enormously valuable <em>but also</em> don’t do it because of the feeling that it is complicated and difficult and needs to be done ‘properly’.</p><p>Well, I hereby give you permission to talk to your customers. And, this post will detail how the <a href="http://farewill.com/">Farewill</a> team recently got from zero to customer insights within a week. Let’s do it!</p><figure><img alt="Step-by-step process" src="https://cdn-images-1.medium.com/max/1024/1*BPzKoHmIhL8yQqWOOJUJ7A.png" /><figcaption>Seven days to customer insights</figcaption></figure><h4><strong>Overview:</strong></h4><p><strong>Day 1</strong> — Who do you want to speak to and why?<br><strong>Day 2</strong> — Write a script and recruit participants<br><strong>Day 3 / 4 </strong>— Booking in participants<br><strong>Day 5 / 6 </strong>— Talk to customers!<br><strong>Day 7 </strong>— Analysis and review</p><p>Let’s breakdown what that looks like in practice:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ZdUsR9u4gpRRLmfSygzTg.png" /></figure><h3><strong>Day 1 — Who do you want to speak to and why?</strong></h3><p>To have insightful conversations with your customers it is important to be clear on the problem areas you want to hear more about. Discussing this with your team and agreeing from the start means you can write better questions, listen with the same goals in mind, and dig into the answers most useful to your problem.</p><p>Recently we wanted to hear about how and when our customers decided on who they included in their will, the ways they’d want to share things between those people, and therefore what improvements could make the biggest difference to our current journey.</p><p>We started a document to collect together the team’s questions. These don’t have to be framed as research questions at this point, that comes later, for now you can just have a rough brain dump of the thoughts and questions you’ve got as a team.</p><p>An example is Chris, <a href="https://medium.com/farewill/what-sealed-the-deal-for-me-was-an-engineering-team-thats-66-female-q-a-with-ethel-ng-from-2330b62ac5eb">a developer on the team</a>, wrote “I’d like to know if people pause to check something and do more research (e,g googling something or checking our help centre or talking to someone they know) since this could indicate information we should have in the page.”</p><p>Once you’ve drafted together the sorts of questions you want to ask you can then figure out which group of your customers you want to speak to. We had questions around the choices people were making both before and after signing up so we decided to talk to people who had registered with us in the last couple of weeks, given us permission to contact them, and had got at least halfway through writing their will. This way the information we were interested in would hopefully still be fresh in their minds.</p><p>With your questions doc and participant group sorted, on to day 2!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QEKvof4GFO2_DBaHn_jgAw.png" /></figure><h3><strong>Day 2 — Write a script and recruit participants</strong></h3><p>With fresh eyes you can now review your questions doc and re-write this into a call script. There will likely be themes that you can pull out from your question doc to write broad and open questions for your script. During the interviews you can dig into the details to try to answer specifics, but you’ll learn more by starting with open questions. The best method we’ve found is to ask open questions, listen intently, and dig into the details with specifics. A nice trick is to add hints to your script to remind you what to listen out for and dig into specific areas.</p><p>It is quite difficult to write good, open questions and remain genuinely open to the discussion going in a completely different direction. But in my experience any time you invest in listening to your customers’ stories is time very well spent. You’ll get much bigger insights from listening to the thoughts and motivations of your customer, rather than asking for positive feedback on your existing ideas.</p><p>I like to turn the script into a spreadsheet with a row for each participant and each question in a column. This makes filling in the script easier when you’re on the call, and also feels easier to read when you’re doing analysis later.</p><figure><img alt="Example script spreadsheet" src="https://cdn-images-1.medium.com/max/1024/1*zqVoojOelK4-8KeIcTaE2A.png" /><figcaption>Example script spreadsheet</figcaption></figure><p>Once you’re happy with your script you can turn your focus to recruiting your participants. This is where you get to flex your email copywriting muscles. The biggest challenge here is to write a short, snappy email with as few unanswered questions as possible.</p><p>Your email should make it really easy for people to understand:<br>- Why you’re interested in talking to them,<br>- When they’ll need to be available,<br>- How long they’ll need to be available,<br>- What is in it for them,<br>- How to sign up to a call.</p><p>Depending on your business and audience you might want to finesse that list, but that’s what works for Farewill currently. The exact content of the email will change based on what and who you want to talk to, as well as your brand and company tone of voice.</p><figure><img alt="Example participant recruitment email" src="https://cdn-images-1.medium.com/max/616/1*ZwgNdFV3F9cq6TJnYH1JEQ.png" /><figcaption>Example participant recruitment email</figcaption></figure><p>To allow people to schedule calls with us we use a free tool called <a href="https://calendly.com/">Calendly</a>. This makes the process really easy compared to bouncing back-and-forth with several people all at the same time.</p><p>We also use an email tool called <a href="https://mailchimp.com/">Mailchimp</a> where we can see send, open, and click rates for our emails. This means we can make some informed guesses on how future emails might perform too. Looking at past email performance means you can do some maths to figure out how many people to send your new email to.</p><p>We usually see 8–10% of people who open our participant email then click to book in a call. So if we want to talk to 10–15 people we know we need about 180 people to open the email. We can use Mailchimp to segment out enough people, making sure they meet our participant criteria from day 1.</p><p>The first time I did this I gave participants the choice of up to a 2 week window to book in a time for a call. However, I’ve found the longer the period is, the more likely people are to drop out, forget, or just lose interest. It’ll also take you longer to be able to summarise and action what you’ve found by virtue of taking 2 weeks to do the calls. For our most recent research calls we gave people just a 2 day window to pick from and we still got plenty of participants signing up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q7TIQhhrDLuHPOHPR2_rgA.png" /></figure><h3><strong>Day 3 and 4 — Booking in participants</strong></h3><p>Sending out the participant email is when things start getting exciting. Most of the sign ups will come in the first few hours but definitely give people a couple of days to get around to it. We usually see about half our participants book in over the following couple of days. If you’re using something like calendly then this is the easiest bit. You just have to keep an eye on your calendar to discuss with your team who’ll be taking each call.</p><p>I really recommend having a mix of people run the calls. We make a shared list where everyone in the team can assign themselves to calls that are convenient for them. I’ll then assign myself to the ones remaining. This gives everyone the opportunity to talk directly to customers and it means one person isn’t jumping from call to call to call, which can be exhausting. It also makes the analysis part more fun because everyone can contribute to share the stories they heard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y3tUVYEIo5SoViKwEI4dJQ.png" /></figure><h3><strong>Day 5 and 6 — Talk to customers!</strong></h3><p>Starting day 5 you’ll hopefully have 10–15 calls booked in over the next couple of days. We use a tool called <a href="https://aircall.io/">Aircall</a> to make the calls. One really useful feature here is Aircall automatically records the calls for you. Having recordings makes it easier to clarify any points that don’t come through in the notes. Also, any team members new to phone research can listen to previous calls to hear how these conversations tend to flow.</p><h3><strong>Some techniques for talking and listening</strong></h3><h4>Warm up questions</h4><p>As with any conversation, the start can be a bit awkward. It can help the participant feel at ease by explaining clearly what the plan is and that no answers are right or wrong. A new tweak we recently added was saying “If there’s any questions you don’t want to answer, just say so and we can skip them”. We’ve very rarely had people ask to skip a question but saying this up front can put people’s mind at rest a little more.</p><h4>Shine the spotlight</h4><p>Once you’ve explained the call you can start shining a light on the participant. The more the participant talks, the more you can listen and the more you can learn. Imagine a spotlight between you and the person you’re talking to. Whoever is talking has the spotlight on them. Your goal is to shine the light on them and their story as much as possible.</p><h4>Positive verbal nudges</h4><p>For lots of participants, talking to a researcher on the phone can be a bit daunting. Without the visual clues of things like eye contact, nodding, and smiles, it is hard for the participant to know if what they’re saying is useful. And everyone naturally likes to feel like what they&#39;re contributing is interesting.</p><p>Some verbal shorthand you can use to encourage your participants is some positive “Uh huh”s, “Hmm”s, “Okay”s and “Yep”s. These are often enough to let your participant know you’ve understood and you are interested in them continuing their story.</p><p>One mistake I made early on when learning this was overusing Okays. One participant said to me “You say okay a lot!”. Remember you want to sound interested and encouraging, not robotic.</p><h4>Parroting</h4><p>Participant: “I was watching TV and your advert came on.”<br>Researcher: “Okay, so you were watching TV and our advert came on.”</p><p>Parroting is a clever technique to dig into the detail of what someone has said. You simply repeat back what you just heard. It might look weird written down, but this happens in natural conversation all the time. It is a communication shortcut we all naturally learn that means “I am interested in hearing more of that story, please continue”.</p><h4>Can you tell me more about that?</h4><p>A slightly more direct way to ask someone to continue their story is by asking “Can you tell me more about that?” This works really well if you pair it up with a short summary of what you’ve heard so far. For example, “So you were watching TV and you saw our advert and it stood out to you. Can you tell me more about that?” This is a great way to signal that you’re interested in hearing more and participants often have more to share.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c0xC7ZvPtCPztKNs5v0yYg.png" /></figure><h3><strong>Day 7 — Analysis and review</strong></h3><p>Congrats! You’ve spoken to your customers and heard directly from them! Yessss!</p><p>Now it’s time to switch brain tracks into synthesis and analysis mode. Having the recordings and script notes is really essential for this. Without notes and recordings to go back to you can end up trying to piece together findings from your memory, which will lead you to making poorer decisions on much vaguer evidence.</p><p>At Farewill we are still iterating on the best ways to do this analysis stage but generally we’ll re-read the notes from every call with a view to absorbing everything together. This way you can start to pull out themes, patterns, and quotes to then get to clear findings.</p><p>We do this by summarising the answers from <strong>each person individually</strong> to get a short profile of them and their context. We then review all the answers to <strong>each</strong> <strong>question individually</strong> to get a sense of the patterns or groups of thought for each one.</p><p>While doing this analysis we’re looking to answer things like — Are the same kind of answers repeated across the group or sub-groups? Did people get confused about the same or similar points? Is there a common thought pattern or decision happening at key points in the journey?</p><p>We then combine these findings together along with quotes and quantitative data to create a slide deck of key findings and patterns from the research. We use this deck in the team as an artifact to refer back to as we work, and also to share and present around the rest of the business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/877/1*Y8OL2Fj1xJ3zZgFZi2aPTg.png" /><figcaption>Example slide from findings deck</figcaption></figure><h3><strong>Our results</strong></h3><p>Our recent research calls took us 5 working days from start to finish, with a weekend in the middle to give participants time to book in. Our team was 3 people — 1 Product Manager, 1 Designer and 1 Developer — and our spend was £200 on participant rewards.</p><p>We sent 257 recruitment emails. 180 people opened the email. 16 people clicked the link to set up a call. 12 people booked in. We spoke to 10 customers.</p><p>We’ve already been using the findings and insights from the calls to inform the product work our team is tackling. This research, along with other discovery work, helped us hone in on 3 key problems to solve as well as giving us further clarity on the language to use throughout the customer journey.</p><p>Additionally, by presenting the findings, quotes, and stories to the entire business the whole team has a much more vivid understanding of who we’re building for, and a real human understanding of the impact of our work across every team.</p><blockquote><strong>PS</strong> Let us know in the comments if you try these techniques out for yourself.</blockquote><blockquote>If you want to come and practice together, <a href="https://farewill.com/careers">we’re hiring</a>!</blockquote><h4><strong>Further reading</strong></h4><p>Rocket surgery made easy by Steve Krug<br><a href="https://www.amazon.co.uk/Rocket-Surgery-Made-Easy-Yourself/dp/0321657292">https://www.amazon.co.uk/Rocket-Surgery-Made-Easy-Yourself/dp/0321657292</a></p><p>Why You Are Asking the Wrong Customer Interview Questions by Teresa Torres<br><a href="https://www.producttalk.org/2016/03/customer-interview-questions/">https://www.producttalk.org/2016/03/customer-interview-questions/</a></p><p>Listening deeply by Indi Young<br><a href="https://medium.com/inclusive-software/listening-deeply-fe55ac43bd32">https://medium.com/inclusive-software/listening-deeply-fe55ac43bd32</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf0fa182d7a2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farewill/how-to-talk-to-your-customers-by-this-time-next-week-bf0fa182d7a2">How to talk to your customers by this time next week</a> was originally published in <a href="https://medium.com/farewill">Life at Farewill</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“What sealed the deal for me was…an engineering team that’s 66% female” — Q&A with Ethel Ng from…]]></title>
            <link>https://medium.com/farewill/what-sealed-the-deal-for-me-was-an-engineering-team-thats-66-female-q-a-with-ethel-ng-from-2330b62ac5eb?source=rss----e1959b290f5e---4</link>
            <guid isPermaLink="false">https://medium.com/p/2330b62ac5eb</guid>
            <category><![CDATA[legaltech]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[full-stack]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Tom Rogers]]></dc:creator>
            <pubDate>Tue, 13 Aug 2019 14:58:10 GMT</pubDate>
            <atom:updated>2019-08-13T16:06:42.597Z</atom:updated>
            <content:encoded><![CDATA[<h3>“What sealed the deal for me was…an engineering team that’s 60% female” — Q&amp;A with Ethel Ng from Farewill</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3dtvt2BqGkfG_KfZyUexhg.jpeg" /><figcaption>Farewill Engineering team July 2019 (Ethel sat bottom left)</figcaption></figure><p><strong>Hello Ethel, please introduce yourself!</strong></p><p>Hello! I’m a full stack developer at <a href="https://farewill.com/">Farewill</a>. I’ve just joined in the beginning of July and work as part of the wills experience team.</p><p><strong>How did you get into software development? And what have you worked on in the past?</strong></p><p>I definitely didn’t grow up planning to be a developer — despite being around computers and the “digitally savvy” one from a young age I was totally unaware it was an option open to me. At university I studied Psychology, but after graduating I found out about a bootcamp (<a href="https://makers.tech/">Makers</a>) and signed up as I thought it would give me a better shot at a career I was interested in. The course gave me enough real-world skills to get my first job at ustwo after 12 weeks.</p><p>It’s only after joining the industry that I’ve realised there’s a huge amount of developers from “non-traditional” backgrounds out here.</p><p>From my agency experience I’ve worked on a whole range of projects from in-flight travel, supermarket back offices, e-commerce, healthcare.</p><p><strong>What does that mean day-to-day?</strong></p><p>There’s a lot that goes on behind the scenes of the website! As a developer I could be working on anything from prototyping new features, improving our compliance with payment regulation, or building internal tools for our customer operations teams. Being a full stack developer means that I’m involved at all levels from the shiny interface that someone sees to the backend systems that generate the wills or communicate with third-party services.</p><p>At Farewill we work in small cross-functional teams, and developers are fairly included in product decisions. We’re able to question things and suggest ideas for how to improve the product or the way we work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I4ZPpZItgp021bXNna6KOA.png" /><figcaption>Ethel and Chris pairing (both Engineers on the Wills Experience product team)</figcaption></figure><p><strong>What attracted you to Farewill and why did you decide to join?</strong></p><p>I’d been working at an agency for a good amount of time and gotten really good at starting things up from scratch, so my main motivation for my next role was finding a place where I could build up long-term ownership of a product. I wanted to work at a startup that had shipped a product with a live customer base, but one that was early-stage enough that I could still have an impact.</p><p>Out of the companies I looked at, I really liked Farewill’s proposition — there’s definitely something fun about telling people you work in the death industry! Jokes aside it’s about making a difference in a field that’s been pretty untouched by technology, and doing it in a way that’s human and respectful. In recent years I’ve started being more critical of the role that technology plays in society, and I wanted to be part of a company that uses tech to equalise access rather than catering to privileged groups.</p><p>What sealed the deal for me was the diversity of <a href="https://farewill.com/about">the team</a>. I’m lucky enough that this hasn’t been an issue for me in my career so far, but I know I can’t do my best work in an environment where I don’t feel included. An engineering team that’s 60% female is unheard of.</p><p><strong>What makes this company different from others you’ve worked for?</strong></p><p>It’s early days but there are some differences to agency life that I appreciate. Aside from having OKRs per quarter there is a longer-term vision which makes it clear what we’re striving towards. Technical decisions have to be more considered as ultimately we’re the ones who will maintain them. Bugs also come with a greater personal frustration knowing that they’re affecting customers out in the wild.</p><p><strong>What would you tell someone thinking of applying to a role at Farewill?</strong></p><p>We’re still a small team and there’s lots of room for you to find your niche, so I’d recommend it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2330b62ac5eb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farewill/what-sealed-the-deal-for-me-was-an-engineering-team-thats-66-female-q-a-with-ethel-ng-from-2330b62ac5eb">“What sealed the deal for me was…an engineering team that’s 66% female” — Q&amp;A with Ethel Ng from…</a> was originally published in <a href="https://medium.com/farewill">Life at Farewill</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wills for couples — a look at how design works at Farewill]]></title>
            <link>https://medium.com/farewill/wills-for-couples-a-look-at-how-design-works-at-farewill-f800d377d503?source=rss----e1959b290f5e---4</link>
            <guid isPermaLink="false">https://medium.com/p/f800d377d503</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Victor Hwang]]></dc:creator>
            <pubDate>Fri, 17 May 2019 09:44:34 GMT</pubDate>
            <atom:updated>2019-05-17T11:28:36.903Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Wills for couples — a look at how design works at Farewill</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gl4sdlVX6FTr_gz0" /></figure><p>At Farewill all our will specialists (the people helping customers get their will sorted) are in-house — making it easy to listen in on the kinds of problems people are experiencing with our product.</p><p>In my first few days, one phone call stood out — someone had filled every part of their will, meant only for them, with both their and their partners details. This meant they’d have to go back and rewrite almost the whole thing.</p><p>We dug further into customer questions, analysed the data and spoke to users, and realised that this was a symptom of a broader problem with couples wills. So we decided as a team it was time to improve things.</p><h3>Our Process</h3><p>At Farewill we believe that good research makes us faster as a team, and leads to better products. So we take it seriously, and weave it throughout our process.</p><p>We started by arranging phone calls with couples who made wills with us. Our aim was to understand not only how they thought about wills generally, but also their experience with our product.</p><p>Three groups of findings emerged from our notes:</p><ul><li>Behaviour before starting their wills</li><li>Writing their wills</li><li>Payment and our update service</li></ul><p>By understanding the gap between people’s mental models (their beliefs about wills and expectations of our product) and our implementation, we could identify what changes to make.</p><h3>What we discovered</h3><p>Couples often own things jointly (bank accounts, houses and so on). This idea is perpetuated by everyday imagery — just look at what happens when you search ‘couple’ in google images.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xcoa56qMeordWFJK" /></figure><p>Perhaps because of this, many couples expect their wills to be joint too.</p><p>However, for legal and other reasons, wills are made by individuals. It’s also better if everyone has their own individual account — it means they are in total control (for example, if they get separated), and can also leave personal gifts and messages.</p><p>From this, our challenge became to reconcile people’s existing mental models with the reality of each partner having a separate will.</p><p>This insight became the fuel for a cross-company sketching session, resulting in a prototype of a brand new journey. Watching fresh users clicking through it gave us the final raft of insight and ideas, and helped us firm up the journey that’s now live.</p><h3>Some of the changes we made</h3><h4>Being laser-focussed in our copy, imagery and interface</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ccEeTuD_iIYgxHts" /></figure><p>From our research, we hypothesised that saying ‘you get two wills, not one’ at key points in the journey would help bridge the gap in people’s mental models.</p><p>This starts right from the headline on the landing page — ‘Get both your wills sorted’, through to buttons and bits of microcopy.</p><p>We backed this up with an illustration of two wills together at points where this could add clarity — for example, the payment page (where you can choose to pay for both wills).</p><p>However, words and images aren’t the only way to ‘say’ things. The way interactions and interfaces are designed gives people a picture of how the product works behind the scenes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ll-V6y2vnEglu_qj" /></figure><p>For example, previously people had to sign up and then invite their partner. By bringing these two steps together into the same screen, we’ve reinforced the idea that each person has a separate account.</p><h4>Meeting people’s mental models where we can</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Hl-b9Mw-20INlZrY" /></figure><p>One of the other things we learnt from our formative research is that most couples have a joint bank account, and the majority had paid for their wills from this account. We’ve simplified our couples payment process so that the first person to complete their will can pay for both at the same time, better matching people’s expectations.</p><h3>Success?</h3><p>Right at the beginning we decided that success meant fewer questions to our Will Specialists, and more couples signing up for both their wills with us.</p><p>I’m happy to say that we’ve exceeded our expectations on both these fronts, with half of all wills bought last week being for couples, and the team receiving no questions about how to make a couples will.</p><p>It’s also been exciting to see the things we’ve learnt along the way trickle down through the company, and start to influence the rest of the business.</p><p>If you’ve got any thoughts or questions about how we do design at Farewill, drop us a message below! We’d love to hear from you</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f800d377d503" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farewill/wills-for-couples-a-look-at-how-design-works-at-farewill-f800d377d503">Wills for couples — a look at how design works at Farewill</a> was originally published in <a href="https://medium.com/farewill">Life at Farewill</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How (and why) we built our new probate service on customer needs]]></title>
            <link>https://medium.com/farewill/how-and-why-we-built-our-new-probate-service-on-customer-needs-fc78d6f5b228?source=rss----e1959b290f5e---4</link>
            <guid isPermaLink="false">https://medium.com/p/fc78d6f5b228</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[death]]></category>
            <category><![CDATA[probate]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Tom Hiskey]]></dc:creator>
            <pubDate>Tue, 05 Mar 2019 12:51:27 GMT</pubDate>
            <atom:updated>2019-03-05T12:51:27.677Z</atom:updated>
            <content:encoded><![CDATA[<p>Today’s a big day at Farewill — we’re soft-launching our <a href="https://probate.farewill.com/">probate service</a>.</p><p>Probate is needed after about half of deaths in England and Wales — it’s an official document obtained from a probate registry. We’ll be taking away the hassle and worry by dealing with all aspects of the probate application on behalf of our customers. It’s Farewill’s second major offering, joining our hugely successful <a href="https://farewill.com/">wills product</a>.</p><p>We’ve worked hard over the past few months to build a probate service that’s based on problems — problems faced by families after the death of a loved one, at a time when probate is often the last thing they want to deal with. Here’s how we approached it.</p><h3><strong>Discovering user needs</strong></h3><p>It was important to us to discover problems for ourselves. Not copy other probate services, not assume others were doing it right, not base our plans or hearsay or guesswork.</p><p>Early on, we ran a focus group with bereaved relatives. Focus groups get a bad rap sometimes (maybe I’ll blog about it sometime). But in the right circumstances, they’re fantastic. For us, it provided detailed, honest insight into 5 strangers’ unique experiences with grief and probate. It helped us frame the problem and base decisions on first-hand evidence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Go1ay_zmFX8Cx3R17d7JOw.png" /><figcaption>A quote from a focus group participant about dealing with banks after a death</figcaption></figure><p>We gathered market research — some of which is surprisingly helpful on a qualitative (a more individual) basis, with quotes and case studies. It’s crucial on a quantitative (big numbers) level too — for example, knowing that 70% of deaths in the UK are uncomplicated from a legal/financial point of view helps us focus on the majority and hone in on what matters. We did other research, from speaking at length to people and organisations in the sector to mystery shopping. It all helped build a picture of our prospective customers.</p><h3><strong>Defining user needs</strong></h3><p>We had our research — what next? We wanted something tangible and usable; something to keep us focused on the big picture without having to remember every bit of data. Something to bring our research to life and bring colleagues along on the journey.</p><p>That’s where these things come in:</p><ul><li><a href="http://www.myddelton.co.uk/blog/discovery-block-diagram">Discovery block diagram</a></li><li>User stories / job stories</li><li>Personas</li><li>Red routes</li><li>Service blueprint</li></ul><p>As a team, we reviewed the evidence and ran a workshop where we expressed that evidence as job stories. A job story follows this format:</p><p>When I ____<br>I want to ___<br>So I can ___</p><p>Job stories help us express needs from the customer’s perspective. We wrote about 50, which we sense-checked, refined, filtered and grouped.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*49yh1fKMgwOa3pL2iGMAgg.jpeg" /><figcaption>Our probate job stories on a virtual whiteboard</figcaption></figure><p>You might have heard of user stories — they’re a similar idea, with a different format. In our case, we thought the job story format would be more useful.</p><p>The job stories formed the backbone of a ‘persona’. A persona is a fictional person — a representation of evidence, expressed as an individual, to help stay focused on customer needs. We prioritised the job stories, re-worded them and arranged them into goals, motivations and frustrations. We gave the persona a photo, a bio and a name — Carly. Carly represents our customers — we speak of her often, and refer back to her when making decisions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vy6Xr9z4XlW22nIxMncSTQ.jpeg" /><figcaption>Extract from our probate persona, Carly</figcaption></figure><p>Carly will no doubt change as we learn more from our customers, and we’ll add more personas as our target audience widens and/or becomes more defined.</p><h3><strong>Bringing others along on the journey</strong></h3><p>We have a dedicated product team for probate (<a href="https://twitter.com/tomhiskey">me</a>, <a href="https://twitter.com/emilyisacke">@emilyisacke</a>, <a href="https://twitter.com/ConstanceMantle">@ConstanceMantle</a>, <a href="https://twitter.com/lozzyrobinson">@lozzyrobinson</a>). We run daily stand-ups and weekly retros to discuss progress, raise issues, plan the next week and be clear on what we’re all doing.</p><p>But it’s never just about the core team. It’s important for us to bring every member of Farewill on the journey. From customer service to marketing, from brand to partnerships — everyone has something to contribute, and everyone is vital to the product’s success.</p><p>So we over-communicated. We have weekly rituals at Farewill like ‘All hands’ (an hour on Tuesdays where everyone meets up) and ‘Friday fives’ (an end-of-week retrospective, again with everyone present) — we use these to keep our colleagues up to date with the purpose, vision and progress of the probate product, and to get their input. We run workshops not only with the core probate team but with others too, and asked for feedback regularly from the wider team.</p><h3><strong>Learning and testing</strong></h3><p>For the moment, our probate service is almost entirely non-digital, so we decided not to do any usability testing before launch. But we’ll be doing some soon (on the website), and learning as much as we can from our customers. We’ll feed this evidence and research back into the product, and keep improving and learning.</p><p>Farewill’s mission is to change the way the world deals with death. Our probate service is a hugely exciting step on that path. Now comes the most important part — providing the best possible service to families when they need it most.</p><p><strong>Want to join us? </strong><a href="https://farewill.com/careers"><strong>We’re hiring!</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc78d6f5b228" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farewill/how-and-why-we-built-our-new-probate-service-on-customer-needs-fc78d6f5b228">How (and why) we built our new probate service on customer needs</a> was originally published in <a href="https://medium.com/farewill">Life at Farewill</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why we’re changing our colours]]></title>
            <link>https://medium.com/farewill/why-were-changing-our-colours-4ae9a412e542?source=rss----e1959b290f5e---4</link>
            <guid isPermaLink="false">https://medium.com/p/4ae9a412e542</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Zoe Colley]]></dc:creator>
            <pubDate>Tue, 21 Aug 2018 21:52:04 GMT</pubDate>
            <atom:updated>2018-08-22T11:37:55.845Z</atom:updated>
            <content:encoded><![CDATA[<p>We want Farewill to be accessible to as many people as possible. Breaking down barriers for people with disabilities is key to this.</p><p>I believe inclusive design makes better and more flexible products for everyone. In this post I’ll be focussing on a change that could help our blind and partially sighted users.</p><h3>Colour contrast</h3><p>A key part of visual design is colour contrast. Colour contrast is the visual difference between two colours. It can affect how easy text is to read.</p><p><em>But how much contrast is enough?</em></p><p><em>What is the minimum and what should we be aiming for?</em></p><h3>How much contrast is enough?</h3><p>There’s something called the <a href="https://www.w3.org/WAI/intro/wcag.php">Web Content Accessibility Guidelines (WCAG)</a> that get published by the <a href="https://www.w3.org/]">W3C</a>. These guidelines include all sorts of information on how to make your website accessible to the most people.</p><p>One part of these guidelines is specifically about colours, colour contrast and the ratio you should aim for between foreground and background colours for text.</p><p>There are multiple levels of compliance to the guidelines, described with AA and AAA. The more A’s the better.</p><p>Based on WCAG 2.0 the minimum ratio is <strong>4.5:1 for AA compliance and 7:1 for AAA compliance</strong>.</p><p>Below is an example of contrast ratios of colours with white:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/421/1*ceTTCufqHrtexZg2-fThdg.png" /><figcaption>Black with white is a ratio of 21:1. Grey with white is a ratio of 4:1. White with white is a ratio of 1:1.</figcaption></figure><p>For larger text it changes to allow for less contrast. The bigger or bolder text becomes the easier it is to read. For AA you need a ratio of 3:1 and for AAA you need a ratio of 4.5:1.</p><h4>Tools to help</h4><p>Their guidelines and formulas are quite confusing and to be honest I don’t even know how these colours are calculated. There are some tools to work this ratio out:</p><ul><li><a href="https://contrast-ratio.com/">contrast-ratio.com</a> by <a href="http://lea.verou.me/">Lea Verou</a></li><li><a href="https://snook.ca/technical/colour_contrast/colour.html#fg=FFFFFF,bg=FC7E84">Colour contrast tool</a> by Jonathan Snook (my personal favourite)</li></ul><p><em>Do you use tools for this? Let me know</em></p><h3>Farewill’s colours</h3><p>We have two main colours for our user interface. Our primary colour, yellow, has great colour contrast with black:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/361/1*Ec-UYF0zLUPdgLdOPANHfw.png" /><figcaption>Yellow (#3E487D) with black has a ratio of 18.3:1 which passes AA and AAA.</figcaption></figure><p>Our secondary colour is used a lot across the site. You can see a comparison of what we had before and what we changed to below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wC1WJdCpmmEunLEV4lsBdw.png" /><figcaption>Screenshots of the Farewill user interface. Left the colours before, right the colours changed</figcaption></figure><h3>Is it better?</h3><p>The original pink/red with <strong>2.5:1</strong> was not great for colour contrast, it’s under the minimum of 4.5:1 by quite a bit.</p><p>The new blue at <strong>8.5:1 </strong>is far above passing the WCAG AA criteria at 4.5:1 and even better the AAA criteria at 7:1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/665/1*eJ8wlYxKrvkHuBS-JM7hXQ.png" /><figcaption>The pink (#FC7E84) with white has a ratio of 2.5:1 which fails AA and AAA. The blue (#3E487D) with white has a ratio of 8.5:1 which passes AA and AAA.</figcaption></figure><p>Colours are a complicated topic and contrast ratio shouldn’t be the only thing you consider. <a href="https://ux.shopify.com/in-plain-sight-5639c9afb4c6">Shopify wrote up a great post</a> on how some colours can often look more legible when the ratio is still low.</p><h3>Making a product for as many people as possible</h3><p>We’re trying to improve the accessibility of Farewill so it can be used by as many people as possible. This is one step towards that future.</p><p>From making the website keyboard accessible, all the way to making our wills legally binding for blind and partially sighted users, we have lots of exciting challenges to work on next.</p><blockquote><em>Want to join us at Farewill? </em><a href="https://farewill.com/careers"><em>We’re hiring! 🙌</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ae9a412e542" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farewill/why-were-changing-our-colours-4ae9a412e542">Why we’re changing our colours</a> was originally published in <a href="https://medium.com/farewill">Life at Farewill</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>