<?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 Sam Evans on Medium]]></title>
        <description><![CDATA[Stories by Sam Evans on Medium]]></description>
        <link>https://medium.com/@sevans_85792?source=rss-a0cf6e3e10bd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*57ugcZLN3NwoGaM9UytzGw.png</url>
            <title>Stories by Sam Evans on Medium</title>
            <link>https://medium.com/@sevans_85792?source=rss-a0cf6e3e10bd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:57:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sevans_85792/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[10 Steps to help you transition into service design]]></title>
            <link>https://medium.com/practical-service-design/10-steps-to-help-you-transition-into-service-design-4f234072bb62?source=rss-a0cf6e3e10bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f234072bb62</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Sam Evans]]></dc:creator>
            <pubDate>Mon, 26 Mar 2018 15:51:01 GMT</pubDate>
            <atom:updated>2018-03-26T15:51:01.326Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MghTioR7umbUceMevZbqsA.jpeg" /><figcaption>Ascot Racecourse App Designs</figcaption></figure><p>In an earlier article, I discussed <a href="https://www.rawnet.com/insights/what-is-service-design-and-why-is-it-important">why Service Design is important</a>. In this post, I’m sharing our experience of adopting Service Design and offering up some advice to those looking to do the same.</p><p>Changing your own skillset, business proposition, and internal day to day processes to focus on Service Design (SD) is a challenge. Making that transition from an insular user experience focus to that of a wider-arching service focus, while keeping digital at the forefront, yet providing measurable value is tough, but can be hugely rewarding. Bringing SD to the forefront of the industry will benefit agencies and their clients alike.</p><p>During the past year we have been going through this transition. We faced many challenges and learnt a lot along the way. The following sums up the lessons we have learnt and advice we have taken onboard. Our learnings have been invaluable and whether you work in house or agency side, we hope this will help you find some context and spur you towards a kind of Service Design adoption that works for you.</p><p>I love this quote from <a href="https://amplitude.com/">Amplitude</a> the product analytics company. They use it in their sales deck when pitching.</p><blockquote>All companies are turning into digital product businesses</blockquote><p>Simple? Yes. Obvious? Yes. However, is anyone truly ready to design the service for this clear migrational shift to digital product businesses? Not quite. Time to take some ownership.</p><h3>1. Start with your users, dive deep front and backstage</h3><p>I know, I know, you’ve read this a thousand times, but it’s still true. Yes, get your business context and stakeholder insights together, but bulk load your research and testing plan with users. Remember though, a user isn’t just a customer, the company workforce is also a user. A happy employee equals a happy customer. Backstage is the next level struggle though. Understanding, consulting on, and adapting processes, technology, and culture is key to changing a service.</p><p>Don’t be afraid to ask people awkward questions or put them on the spot. It has the same effect of talking to someone after a few drinks. The truth tends to flow and you will gain some fresh insights. Try not to influence people or put words in their mouths, simply put them at ease and facilitate. Then it’s your job to listen for the gold dust.</p><p>One of the most important things though is to prepare properly. What questions do you need to know the answers to? Asking these at the right time will come with practice but at the very least, observe, observe, observe. What personality traits do users have? Where is empathy required? Where are their frustrations? What is the one key thing they strive for?</p><h3>2. Work visually</h3><p>In my years in the industry I have come to learn that a great designer cannot explain an idea without a layout pad and a sharpie. There’s a reason for this, visual language is a thousand times more powerful for a consistent understanding with context. It’s much easier to align people with imagery, diagrams, audio and video than with words alone.</p><p>Use these mediums to find clarity amongst complex scenarios by building a workshop toolkit. From this toolkit you can select your armoury. There are loads of resources out there, but find an underpinning value that is consistent and works within your business ethos. Use this toolkit to define a discussion session that is more visual than it is textual. It will promote focus and allow you to engage with stakeholders and users on a consistent level.</p><h3>3. Co-work</h3><p>The more you think you know the more you actually don’t. You are not going to have all the answers, and you shouldn’t be expected to. Whenever you are working, try and work with others. You will cover ground faster, learn more, make more contacts, and gain more empathy for the cause. All of this helps you out in the long run. When you are in the office, work with colleagues from design and technical teams. When you are in the field, work with as many users and stakeholders as you possibly can. Obviously, you will need some downtime but pick and choose those moments wisely. Where possible, connect the service users, mix designers, and end users, work with stakeholders and technical teams and hidden opportunities will arise.</p><p>I was lucky enough to be part of a team working on a service design programme for <a href="https://www.rawnet.com/our-work/itv-studios">ITV Studios</a>. We completely transformed their B2B sales process with on and offline screening, next level event technology, client management and reporting. It was a huge piece of work and one that ran over four years. Without working so closely with ITV’s Sales, Marketing, Events, Management &amp; Acquisition teams on location at their London based Studios, and at their two major client events in Cannes, we simply wouldn’t have gained the combined group context required to deliver such a great solution. A solution that successfully catered to their varied business needs and has seen a massive 20% increase in revenue since implementation.</p><h3>4. Provide context whenever, wherever</h3><p>You can never know too much, so talk about the service you are representing to anyone and everyone that will listen to you. Tell your Nan, tell your mate Gary, tell the Big Issue lady—they will have an opinion, they will hone in your context and provide you with future discussion points—it supports a productive co-working environment too. I cannot put enough emphasis on gaining contextual feedback adjustments through storytelling, it gives you a more robust justification when making or validating decisions.</p><h3>5. Don’t start at the end</h3><p>This is where I personally struggled to begin with, it’s a hard habit to break because thinking about the end result is pretty natural. You have to get there eventually but take small steps that can be balanced with commercial expectation and pace.</p><p>Capita sum up SD in a nice way on their website:</p><blockquote>Service design is driven by the needs of the user. It delivers compelling multi-channel services that customers find both usable and desirable, while significantly reducing the operating costs, and delivering greater revenues</blockquote><p>Thinking about that holistically, how can you start at the end? Creating the final service at the beginning has never worked and it never will. Understand, ideate and validate or whatever you choose to call your agile-style iterations. We know it works, and that it doesn’t come without its challenges, but make sure you can justify all features back to your research. Check off users, values and objectives in that justification and you won’t go too far wrong.</p><h3>6. Learn and adapt as you go</h3><p>We have kind of covered this one but it needs its own point, it’s important to highlight the fact that you will never learn more than when you release an iteration of the service to its intended audience. Stick to that iterative agile process, work in small chunks, create your MVP, and validate. This keeps you on the straight and narrow. A wise man in the 1995 classic movie Under Siege 2 once said “<a href="https://www.youtube.com/watch?v=7rr88Szc5q0">Assumption is the mother of all f***ups</a>”. Ignore this high brow theory in the world of Service Design and you will end up in a world of trouble. Don’t be afraid to adapt, it’s ok to be wrong. Have a plan, have a process, but know when to adapt this for the benefit of the service.</p><h3>7. Welcome ambivalence</h3><p>Opinions, everyone has one, right? Meh! Opinions make our lives in Service Design harder, they mean we may need to change direction, they mean I may not feel as confident in the deliverables as I once did. Yes, opinions can cause unwanted change, but learning to accept opinions is one of the most important Service Design mindsets to adopt. Becoming too attached to the service and trying to justify every decision made means you will inhibit project progression. Learn to ignore your false consensus bias. Users do not think like you and they don’t want the same things. Accept that change is going to be a thing and accept it in a positive manner. Observe and listen with empathy and find ways to make it work for all involved.</p><h3>8. Measure and justify value</h3><p>Service Design is a tough sell, just like UX was 5 years ago:</p><blockquote>“We need to talk to our users? Don’t be daft I’m the Head of Marketing, I know what our customers want.”</blockquote><p>Imagine someone saying that today? You’d laugh in their face, but the scary fact is that SD is in this place in the minds of business stakeholders. They feel like they know what the service needs. Adding value to a service does not come cheap and a business paying for your consultancy on a hefty day rate, is at every point, having to justify your value. If key stakeholders haven’t joined you for the ride they will not always appreciate the time and effort that has gone into the research and design.</p><p>From the very beginning work out what the service objectives are and how they can be measured. Second to that, always make sure you have the company mission and values defined. Being able to show the effect you are having on both of these is paramount to demonstrating your value. Try to be as quantitative as you can. Quantitative bottom line figures will always trump qualitative research feedback in a CEO’s eyes.</p><p>The good news is that once you have done this the first time, the next time round you already have a good case study and the experience in knowing what sort of KPIs to record and how to make yourself a pain in the ass (in a good way) to get the information you need.</p><h3>9. Catalyse trust</h3><p>Trust is the key component to any relationship, and relationships build a great service. Not just the alliance between yourself and the client, but amongst all members of the service interaction. Don’t mess people around, keep your promises, stay transparent—people see straight through facades. As we know, SD can be a tough sell and a tough service to justify—if the trust goes, progress will either stop or become painfully slow. It will take time to build up any sort of productive pace again. With trust comes effective velocity.</p><h3>10. Have fun</h3><p>Lastly, practice what you preach (to some extent). Yes, we are here to deliver results, but enjoy the process as best you can from start to finish, it’s not going to be a short journey. If you are not comfortable in a workshop environment, don’t enjoy meeting new people or find presenting a challenge, SD is not for you, but if you enjoy the above then it’s going to be fun. Make this part of your life in a balanced way. A happy Service Designer equates to a successful process.</p><p>The transition is hard but enjoy it and remember we don’t have to search fearfully for disruptive solutions, there is plenty of room for positive growth within non-disruptive creation.</p><p><em>P.S. I don’t really think Under Siege 2 is a classic.</em></p><p><em>Sam Evans is Strategy Director at </em><a href="https://www.rawnet.com/"><em>Rawnet</em></a><em>. Follow Sam on Twitter at </em><a href="https://twitter.com/samgoodevans"><em>https://twitter.com/samgoodevans</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*8xQxcPsn30nvCtuU1Be7YQ.gif" /><figcaption>Clap if you liked it!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/1*JfuHxQhpVOEJYpQ4n84NZQ.png" /><figcaption>Continue the conversation, and join the global Service Design Community of Practice in Slack at <a href="http://www.practicalservicedesign.com/community">www.practicalservicedesign.com/community</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f234072bb62" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-service-design/10-steps-to-help-you-transition-into-service-design-4f234072bb62">10 Steps to help you transition into service design</a> was originally published in <a href="https://medium.com/practical-service-design">Practical by Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Service Design and why is it important?]]></title>
            <link>https://medium.com/rawnet/what-is-service-design-and-why-is-it-important-22e348b30488?source=rss-a0cf6e3e10bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/22e348b30488</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[insights]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Sam Evans]]></dc:creator>
            <pubDate>Thu, 23 Nov 2017 12:06:49 GMT</pubDate>
            <atom:updated>2017-11-23T12:06:49.473Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WKpLbURQ3o8DE5zDY0Fv_g.jpeg" /></figure><p>Service Design, a discipline on most radars in the agency and client world is picking up pace. What’s it all about? Well, for those not in the know, let’s start with a definition.</p><blockquote><em>Service Design is the activity of planning and organising people, infrastructure, communication and material components of a service in order to improve its quality and the interaction between the service provider and its customers.</em></blockquote><p>There’s a lot in there that’s not really to do with digital right? So why are digital agencies jumping on this? Well, it’s all about giving value and getting results. It’s true that a service and the application of the design is never 100% digital, however digital can solve the majority of the disconnects, challenges and brick walls services face.</p><p>Prosperous tangible benefits though are tough to prove to old-school CEO’s who sit at 100% on the ROI justification scale. We do know, from the Design Value Index Study, that those who invest in Service Design win, and they win BIG. S&amp;P 500 companies that have adapted their culture to a service focus have seen a value increase of 211%, to those that haven’t. Surely that’s enough justification for a CEO? Well, no, because “that’s not my business and we run different verticals”. She’s right. I’d be sceptical too. The truth is taking on a Service Design culture is not for everyone and, as with the justification that was required around the benefits of UX, it will take time. We’ve heard it all before “we know what our customers want”. It gets boring. Well, you do, but probably only about 80%. The other 20% is the chocolate that allows a service to differentiate and provide the real value and growth opportunity.</p><p>It’s an important decision to make as those who take the gamble are likely to win.</p><h3>The current state of play</h3><p>Albeit not a new practice, Service Design is being adopted by the digital world to aid their clients who are not stuck in the short-termism trap. We are seeing Service Design go through the same changes we saw UX go through over the past 10 years. In 2005 we just made websites and then in 2015 we added another string to the bow and made UX focussed websites with justifications for users and business objectives.</p><p>However, as the world moves on and expects more, we, as an industry, need to step up and Service Design principles appear to offer the next part of that process. When I say the next part though, it is, in fact, the antepenultimate part of the process (that’s the one before penultimate, I Googled it, whatever), the bit before we jump into the user experience research and design. It’s time to evaluate and adjust those market propositions and internal focus.</p><p>The truth is, if you have been doing anything decent in digital over the last 5 years you will have been a conduit to Service Design without really knowing it. Start with the problem and the tech, conduct your research then jump into UX, iterate and then test throughout the rest of the process. We have slowly and kind of unknowingly been offering our clients the digital transformation they needed in the last 3 years through Service Design thinking.</p><h3>What the early adopters who provide Service Design tell us</h3><p>Companies find it difficult to design a good service. Why? Well, many are stuck in the product mindset. Products are a catalyst to silo departments and its users experience the service in those silos. If the sales team are not aligned to the marketing team and the marketing team to the digital team, friction, at many parts of the interaction, will be experienced, both internally and externally. The point being, companies organise themselves in a way that actually massively hinders them from offering a good service.</p><p>I read lots about user relationships and talking this stuff through with certain mindsets and personalities is tricky, but those that accept the benefits of studying users as personas, their journeys and associated pain points learn a lot. It’s also important to remember that a service’s users are not just it’s customers. When staff are let down by applications and processes they get frustrated, that frustration floods out into the customer realm. Happy Staff = Happy Customers.</p><h3>How do you get value in the real world?</h3><p>It’s a case of trying to cut through the bullshit 381 different workshop canvases that you may well use or be offered and find the real value. No one ‘should be’ interested in that, it’s not tailored and it’s not focussed. We find at Rawnet that every client, user base and requirement is different. Sounds cliché I know, but you do have to tailor a process for relevance with old and new project specific tricks.</p><h3>5 steps to help you adopt service design thinking</h3><ol><li>Co create throughout as much as you can. Bring everyone that is useful to the output together as much as you can. It’s short term cost at long term gain. If a team or type of persona has not been involved when creating the service it will come back to bite you. Whether that’s prior or post launch.</li><li>Be sensible, release and test your iterations frequently. Doing so at the end of a project is a pain.</li><li>Build up a rapport with everyone involved. Trust and transparency is key to the delivery of a successful project. Service Design is a tough sell throughout. Record and demonstrate the successes you have to prove the value you are offering.</li><li>If you are not getting the success evaluate and adapt. It’s ok to be wrong, but to be wrong for a long time is not cool for your reputation or that of Service Design.</li><li>If you work exclusively in house where Service Design has been adopted or you are slowly introducing the practice it’s easier to take more time to add value. It’s likely that value will be minimal, and it will take time to find it. If you work for a brand where perfection trumps ROI though, go for it.</li></ol><p>Service Design at its core is decent, it’s cool and it adds a whole new level of interest and fun to a client/agency/user delivery journey. In summary, as with the majority of life it’s about finding the right balance.</p><p><em>Originally published at </em><a href="http://www.rawnet.com/blog/what-is-service-design-and-why-is-it-important"><em>www.rawnet.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22e348b30488" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rawnet/what-is-service-design-and-why-is-it-important-22e348b30488">What is Service Design and why is it important?</a> was originally published in <a href="https://medium.com/rawnet">Rawnet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>