<?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[Services and service organisations - Medium]]></title>
        <description><![CDATA[About the design and management of services and the organisations that provide them - Medium]]></description>
        <link>https://medium.com/services-and-service-organisations?source=rss----810cafc5bfc---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Services and service organisations - Medium</title>
            <link>https://medium.com/services-and-service-organisations?source=rss----810cafc5bfc---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:58:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/services-and-service-organisations" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How executives can support teams and change institutional ways of working]]></title>
            <link>https://medium.com/services-and-service-organisations/how-executives-can-support-teams-and-change-institutional-ways-of-working-d397497bb08b?source=rss----810cafc5bfc---4</link>
            <guid isPermaLink="false">https://medium.com/p/d397497bb08b</guid>
            <dc:creator><![CDATA[Kate Tarling]]></dc:creator>
            <pubDate>Mon, 01 Jun 2020 11:38:31 GMT</pubDate>
            <atom:updated>2020-05-29T15:59:36.938Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fCOBpevfigJ0COX_de0TBQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@sloppyperfectionist?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Hans-Peter Gauster</a> on <a href="https://unsplash.com/@ldn123/likes?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Executives who bring in agile service design teams don’t always know what’s needed to support these teams to deliver outcomes at scale.</p><p>It’s not realistic to expect to change the culture of an organisation while requiring new teams to work within existing IT portfolio management, target architecture or operating models and red-amber-green project control.</p><p>In this post I’ll explain tactics for executives to help tackle key problems with organisational structures and practices that get in the way of creating good products and services. Try these and there is more chance you’ll avoid well intentioned but ultimately wasted effort.</p><p>Here are six things you can work on this week:</p><ol><li>the target operating model<em> is</em> continuous improvement of services</li><li>govern with real life performance data</li><li>the goal is outcomes and performance, not revenue and cost</li><li>portfolio management is service improvement, at scale</li><li>set goals that everyone works on together</li><li>change the language to change the organisation</li></ol><h4><strong>1. The target operating model is continuous improvement of services</strong></h4><p>Someone brand new to your domain should be able to read a list of the services your organisation provides and fully understand what people <em>outside </em>your organisation are trying to do.</p><p>People inside the organisation should be able to see how well these services perform, which teams provide which parts, as well as how they’re being improved. This is not another list of all the internal activity or a diagram of your IT systems. It means gathering evidence on service performance through user research and cost analysis. Then providing the means and designing the work to radically improve them over time.</p><p>Traditional target operating models often remain fiction when so much can change or be discovered before you get there. Improving how you operate persistent services for your customers while occasionally adding new ones, is a target that’s more closely linked to useful outcomes. See also ‘<a href="https://blog.mattedgar.com/2015/01/23/the-last-target-operating-model-youll-ever-need/">the last target operating model you’ll ever need</a>’ by Matt Edgar.</p><h4><strong>2. Govern with real life performance data</strong></h4><p>Rather than review red-amber-green (RAG) project statuses, executives should challenge why it is they don’t have access to dashboards of real life service performance. You need this to be able to challenge investment decisions.</p><p>You don’t necessarily need a new design authority to drive digital transformation. It can be more revealing to bring in digital practitioner skills to the main boards. You need people in the room representing specialisms like product development and management, modern technology, design and research. This will bring appropriate and different intervention. And from now on, only make key hires if they’re used to working in digital ways.</p><p>Some key governance questions for boards should be:</p><ul><li>Why don’t you have a plain english list of services your organisation provides for customers?</li><li>Why can’t you tell how much it costs to run these services?</li><li>Why are you presented with internal views of projects without knowing whether they tackle the biggest customer problems and opportunities?</li><li>How does work in your current portfolio relate to reducing costs or increasing revenue?</li><li>Which teams work on which cross cutting services? Do they know the pain points that matter most, that result in greatest cost?</li><li>Are teams talking about outcomes or only delivery of predetermined solutions?</li></ul><p>A good start is to have someone prototype an actual service dashboard — something indicating success and error rates, time and effort, even if through best guesses and proxies for now. Present it at the next board to provoke discussion. Is any current work set up to be able to improve performance in these ways or is it merely to ‘control’ delivery? Ask the PMO, operations and finance leads to pair up with people with experience of digital ways of working. Make it their joint responsibility to adjust practice to support service improvement and ask them to present this at a key conference or internal leadership session.</p><h4><strong>3. The goal is outcomes and performance, not revenue and cost</strong></h4><p>Money is a lag indicator. It’s not instructive to brief teams to go at cost or revenue directly. Teams need to be able to tackle changes in behaviour, rather than revenue or cost. Make a template for all current and future business cases that identify clearer outcomes to achieve. For example, in a coronavirus pandemic, improve the rate at which contact tracers can track down contacts. Or reduce the proportion of transactions that aren’t solved first time. The goal is to figure out what’s really needed and how to deliver it sustainably or profitably, by the best means possible.</p><p>One public organisation I worked with successfully reduced the cost of transportation in a service by outsourcing to the lowest bidder, only to find their own costs increase because more cases needed intervention. <a href="https://vanguard-method.net/beyond-command-and-control-book/">John Seddon’s work</a> with service organisations challenges this traditional cost-cutting practice. Successful organisations study actual demand in a service, focusing on what’s valuable for customers and measuring performance in terms of what works for the people outside your organisation. Efficiency follows.</p><h4><strong>4. Set goals that everyone works on together</strong></h4><p>What’s needed is differently skilled and knowledgeable people working together, contentedly, to improve services for people outside the organisation. To encourage this you need the often missing view of what your organisation does, as well as what it fails to do, for people outside it. This has to be presented in a way that allows <em>everyone</em> to figure out how to do it better from within.</p><p>Rather than pick an architecture model or management practice to follow, you need a diagram of what people outside your organisation are actually trying to get done. Find out what goes wrong with this and what good outcomes look like for your customer and your organisation. Don’t worry about how it currently works.</p><p>Identify one big, important service and set a hefty ambition for radical improvement. Say, ‘reduce the time it takes us to deliver X outcome for users from 10 days to 10 minutes’. Say, open a bank account or transfer ownership of a freehold. But don’t predetermine how to do it.</p><p>Invite the relevant, experienced teams to figure out what it means for each of their areas and support them to work together to achieve it over time. This includes operations, fraud, back office, front line, technology, design, security. Improve and consolidate ideas with input from experts with internet era skills and knowledge — assuming that’s not yet default in all teams. Iterate ideas as you learn more over time and use this picture as the overall direction to design the individual work. This means starting, stopping, and changing existing projects. Set up regular forums to get all teams continuing to work together to improve and redesign it by default.</p><p>Write blog posts of improvements along the way, authored by colleagues across teams who don’t normally do this. Champion the collective effort to improve services, not just the ‘digital’ effort.</p><h4><strong>5. Portfolio management is service improvement, at scale</strong></h4><p>If yours is a service organisation, your portfolios are mostly service improvement projects. Large organisations typically have hundreds of projects at any one time, rightly or wrongly. Pull out the ones that directly relate to services that people outside your organisation use, including any common products and platforms.</p><p>Map each of these against steps in your end to end services to see where the work fits and where there are gaps. Compare this with what are the biggest pain points for customers, as well as the biggest areas of cost for your organisation and general service performance. Have teams write down how their work aims to improve the service it’s a part of. Stop the less obviously impactful projects and initiate new work to address the gaps.</p><p>Work to remove the barriers that stop your organisation providing great services. For example:</p><ul><li>rather than updates on commitment to a shipping date, ask teams to show what they’ve done to increase the chance their work will improve an overall service and achieve better outcomes</li><li>instead of budgets that lock teams in to predefined features, invest in ongoing teams focused on agreed outcomes, with regular reviews over spend and progress</li><li>give experienced people the oversight and data that reveals demand across a whole service. Empower them to shape the work to improve it, not merely a centralised committee or IT department in isolation</li></ul><p>Reporting, budgets and governance are hard for an individual practitioner or team to change, but will thwart the efforts of all teams if you don’t address them.</p><h4><strong>6. Change the language to change the organisation</strong></h4><p>Set the direction by developing new, shared language for services and their constituent parts. This establishes relationships and hierarchy, so that all work is given an outside-in context. Here’s an <a href="https://hodigital.blog.gov.uk/2016/12/21/creating-a-common-language-to-describe-services/">example of words to describe services </a>from the UK government’s Home Office.</p><p>Label and describe projects by what they intend to improve and who for, in plain english. Talk about work internally and externally in terms of how it improves overall services, outcomes and performance. Show examples of what’s actually happening in your organisation. Communicate about the new reality often, to embed specific behaviour among teams.</p><p>Much of the work to improve services is communication. But few organisations support it to work well between roles and teams and across tasks. This is particularly important for those all working on the same service. Hire a specialist who can specifically help communicate and facilitate collaboration on services across your organisation.</p><h3><strong>Build better service organisations together</strong></h3><p>Hopefully I’ve shown, or at least reminded you of, a few practical ways you can support all teams working on products and services. Don’t leave incoming agile service design teams to cope alone. Trying these will help you build better service organisations over time and avoid investing in effort that’s prevented from having real impact.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d397497bb08b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/services-and-service-organisations/how-executives-can-support-teams-and-change-institutional-ways-of-working-d397497bb08b">How executives can support teams and change institutional ways of working</a> was originally published in <a href="https://medium.com/services-and-service-organisations">Services and service organisations</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Defining services]]></title>
            <link>https://medium.com/services-and-service-organisations/defining-services-4b9d5854ebb0?source=rss----810cafc5bfc---4</link>
            <guid isPermaLink="false">https://medium.com/p/4b9d5854ebb0</guid>
            <category><![CDATA[services]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Kate Tarling]]></dc:creator>
            <pubDate>Mon, 30 Sep 2019 11:22:26 GMT</pubDate>
            <atom:updated>2019-09-30T11:17:57.720Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Written by </em><a href="https://medium.com/u/cb252e06ed8c"><em>Kate Tarling</em></a><em> and </em><a href="https://medium.com/u/e5d669f64a9f"><em>Matti Keltanen</em></a></p><p>Traditional organisations are increasingly recognising themselves as service providers and talking about service design. Defining the services an organisation offers is a good way to start being a better service provider.</p><p>It’s not just about putting the things an organisation does in a list. It’s about recognising what it takes for an organisation to see and manage itself better. To expose what wasn’t visible before. To organise its work and conceive of performance in a way that puts the focus outside itself. To deliver better and more valuable services to people, more efficiently.</p><p>Services aren’t usually viewed or organised in anything like the ways we’re talking about here. It’s surprisingly easy to get wrong and to miss opportunities. This is a definitive guide to helping organisations define, shape and scope services well.</p><h3>A service:</h3><ol><li>is defined from an external end user’s point of view</li><li>describes something someone would want to do, in their language</li><li>has an outcome that relates to the organisation’s goals</li><li>includes all the steps between the user and provider</li><li>includes all the parts involved in delivering it</li></ol><p>You can immediately see problems with these criteria. What if ‘what someone wants to do’ is beyond what an organisation does? Or outside of the public, or private sector? What if what someone wants to do is in conflict with what the service provider wants its users to do? What about services for internal users?</p><p>To understand and protect the value that comes from defining services well, let’s take each point in turn.</p><h3>1. A service is defined from an external end user’s point of view</h3><p>Organisations have purpose. They exist to change or achieve something outside themselves. Yet their focus is often on internal functions or departments. Or portfolios, projects and IT systems. This misses the connection between the work of the organisation and what users are doing. Problems, opportunities and avoidable cost can be invisible. When an organisation focuses instead on providing great services to external users, better outcomes, cost-saving or revenue follows.</p><p>We still need to think about the work an organisation does internally. It’s just that we don’t think about it as a service in its own right. For example, when working on a (external) service, you need to think through how it’s delivered. This includes all the processes, tools and other things teams need to make their jobs possible, or easier. As well as all the systems and other parts, automated or not. There is much to improve, design and make decisions about. In the UK, when an internal part is re-designed in the style of GOV.UK it can cause confusion if it’s then <a href="https://www.gov.uk/service-manual/service-assessments/check-if-need-to-meet-service-standard">assessed as if it itself were a service</a>. It’s more helpful to see these as the <a href="https://hodigital.blog.gov.uk/2017/04/20/building-internal-systems-v-providing-services/">supporting components of an external service</a> with end users outside the organisation.</p><p>Organisations do other things that are like a service, but where end users or stakeholders aren’t exactly external. For example, when a team finds information or prepares reports for a minister’s office or for parliament. You might think of these as internal-to-government services, of sorts. Although they’re similar, we don’t want to confuse what are internally focused activities with the services for end users that we’re defining on here.</p><p>Every organisation recruits people. The end users of this are often external to the organisation. Things like ‘recruiting people’, ‘getting a job’, ‘become an employee/member of our team’ should absolutely be considered, designed and managed, end to end. But they’re more self-serving than the external services we’re defining.</p><p><strong>Example</strong></p><p>These are not external services in the way that we’re talking about:</p><ul><li>procurement</li><li>the on-boarding of new staff</li><li>the intranet</li><li>a new HR management system</li><li>the way performance reviews work</li><li>recruitment of people</li><li>an internal wifi service</li></ul><h3>2. A service describes something someone would want to do, in their language</h3><p>Services should be recognisable to someone with that need, described using plain english and starting with a verb. The UK government’s digital service described what they mean <a href="https://gds.blog.gov.uk/2018/04/04/what-do-we-mean-when-we-talk-about-services/">when they talk about services</a>, following Lou Downe’s <a href="https://designnotes.blog.gov.uk/2015/06/22/good-services-are-verbs-2/">good services are verbs</a>.</p><p>Often what are called ‘services’ still reflect internal organisational structure and remit. This doesn’t define or design services at a level that is about what someone actually wants to get done. For example, ‘starting a company’. In the UK, you still have to complete tasks with 7 different organisations to do this. This isn’t tackling the whole goal or problem for users.</p><p>What a ‘whole problem’ is isn’t obvious, though. It doesn’t tell us what size of problem to aim for. On the one hand we want to define services around things that someone ultimately wants to do, like ‘buy a house’ or ‘have enough income to live on’. But to define services practically, we need to identify parts of them an organisation can actually do something about.</p><p>If you zoom in too far or stick with how your organisation currently sees things, your focus could be too narrow: things like ‘submit a form for a licence’, or an IT system that issues certificates, or any other individual part of an organisation.</p><p>You can zoom out too far too. Say, ‘get an education’ or ‘healthcare’. It’s vast. It’s unlikely you’ll be able to manage and deliver practical change at this level. Not unless you’re a Secretary of State with budget, an excellent team and political support.</p><p>Defining the whole problem well is not straightforward. Take ‘buying a house’ or ‘selling land’. There are many organisations involved, both public and private sector: banks, solicitors, agents, local authorities, buyers and sellers. Should government guide you through the whole process? Should it help you find good solicitors or even houses — things that aren’t a part of government? Is it enough to define a service for government as ‘buy a house’, and assume users will understand that parts of it aren’t government? Or do you define an individual service more precisely as ‘register a change in ownership’? Assuming that someone will tackle the 100+ year old policy on land ownership and redesign it all to work better, with new or fewer services in time. Should there be a master list of services for the public sector that ignores the remit of each institution? Yes. But that doesn’t help organisations and services right now.</p><p>The distinction is whether your organisation or team sees itself as the ‘main’ one that helps glue a wider service together. Including all the work of others. Or whether you define your organisation’s job as just doing its part within a wider context. It’s an important choice, whether consciously or unconsciously made. Either way, an organisation still needs to visualise what it does itself, as well as its role in wider services, so that it can evaluate performance, manage work and navigate priorities and budgets.</p><p>For government, it makes sense to design and operate services that increasingly solve whole problems for users. This is because government has a policy interest in achieving better outcomes, which results from making things simpler, faster or better. This could include directing people to where they can do other things they need to do, even where government doesn’t provide the whole service. In the UK, <a href="https://www.gov.uk/employ-someone?_ga=2.75136274.1095563056.1569172221-720949039.1569172221">step by step guides</a> and <a href="https://gds.blog.gov.uk/2019/01/28/what-service-communities-are-achieving-across-government/">whole service communities</a> are an example of work to support this. It’s now even a part of the <a href="https://www.gov.uk/service-manual/service-standard">Government Service Standard</a>.</p><p>For the private sector, whether to provide a “whole problem” service or to focus on doing one part is a choice. It depends on the strategy, positioning and business model. Services are defined at a level that works for both user and provider, for the most mutual value. So it could be that ‘get a mortgage’ is a more practical level to operate a service at, than ‘buy a house’. ‘Insure your business’ more than ‘run a company’.</p><p>None of this means you don’t ever reconsider the whole thing from first principles. Whether that’s through good research about a high level human need, a life event, or specifically how to redesign a sprawling, cross-cutting theme from scratch. It’s vital to do this to get to better outcomes, whatever sector you’re in.</p><p>The purpose here is to define services to help an organisation see its work and impact from the outside-in. At a scale that makes sense for the larger services to be operated on an ongoing basis, actively improved over time by permanent, empowered teams. Not just one-off redesigns.</p><p><strong>Example</strong></p><p>Services in the public sector are things like:</p><ul><li>find childcare</li><li>drive a vehicle</li><li>get training</li><li>become an apprentice</li><li>work in the UK</li></ul><p>Where the service is explicitly a part or subset of a larger whole service, you can link it with what someone actually wants to do:</p><ul><li>buy a house — register a change in land ownership</li><li>get a passport — get a passport for a child</li></ul><p>A team can then focus on improving, or on removing these parts. While working with all the other organisations to redesign how the broader goal (e.g. buying a house) works for the better. They can also be lobbying for someone to own and prioritise work along the whole thing, across government.</p><p>Whole services are not things like ‘apply for a licence’, ‘book a driving test’, ‘submit a statutory return’ or ‘register a car SORN’.</p><p>Services in the private sector are things like:</p><ul><li>get a mortgage</li><li>insure a business</li><li>rent a car</li></ul><h3>3. A service has an outcome that relates to the organisation’s goals</h3><p>Services don’t exist purely because someone wants them. There are reasons organisations operate particular services. For the public sector, it’s about why government is interested. Such as:</p><ul><li>a wider policy intent or organisational goal. Like making sure that roads are safe</li><li>a specific outcome this particular service is aiming to achieve. Like access to good driving education and appropriate testing before granting a licence to drive</li></ul><p>In the private sector it’s about how the service relates to an organisation’s strategic and regulatory goals, as well as the value it provides to people and the resulting revenue.</p><p>Describing the wider intent helps you know whether a service is supporting it. As well as how it’s performing in terms of its specific job for users and the organisation. This is a stronger place from which to (re)consider the best way to design and deliver it. Teams that don’t spend time understanding these are going to find it hard to talk about service performance.</p><p>Services can run across several policy, operational areas, or organisations. They can each have different desired outcomes. If you only think about the services your organisation or area provides currently and in full, you miss the real picture, and interesting opportunities.</p><p><strong>Example</strong></p><p>A government policy intent could be to ‘prevent people from falling into poverty’. A related service might be ‘get support because of low income’. A successful outcome for this service might be ‘a successful and eligible payment of the right benefits’. For this all to work, the impact of this service outcome should support the policy intent. Which means people should be able to continue living safely and well, without spiralling into poverty and debt when something happens.</p><p>Another policy intent could be to minimise harm to animals while supporting legitimate use of animal research. The organisation might also have other goals, like increasing public trust and confidence in regulation and reducing overhead to the taxpayer as well as industry. A related service could facilitate licencing for appropriate research.</p><h3><strong>4. A service includes all the steps between the user and provider</strong></h3><p>A service includes all the interactions between a service user and a provider. Whether that’s online, paper, phone, text, face to face or any other way.</p><p>Most services in the organisations we’re talking about already exist. The work is to make them radically better. We often don’t mean building new ones. Many haven’t recently been improved, don’t work well yet online or haven’t been looked after. This doesn’t mean they’re not a service. More often, they’re the result of other decisions or delivery in pieces.</p><p>While it doesn’t have to work online to be a service, there is likely major room for improvement if it doesn’t. You can identify which services are most in need of investment to improve. It’s just as important to know about valuable and well-running face to face services, as well as costly, paper-based services that can be designed more efficiently.</p><p>Services also encompass all the steps it takes, whether that’s between people or computers. For a user, these are things like ‘find out how to do something’, ‘choose the best option’, ‘apply’, ‘get something’. For a provider, it’s things like ‘check eligibility and suitability’ or ‘make a decision’.</p><p>Different types of service have common steps. Knowing these helps an organisation identify and categorise common needs and problems. It doesn’t mean you can develop a single way of, say, ‘checking eligibility’ for all services — how that’s done is often completely different in important ways. But knowing the steps can help to place genuinely common components in context. Such as customer data repositories, ways of <a href="https://www.notifications.service.gov.uk/">notifying users</a> about something, <a href="https://www.payments.service.gov.uk/">taking payment</a>, customer support or physical real estate.</p><p><strong>Example</strong></p><p>‘Adopt a child’ or ‘foster a child’ are still services even if they’re mostly face to face, and most of the transactional parts are done on paper. The online application, contact centres and interview rooms for ‘work in the UK’ are all part of a single service. They can also be shared capabilities across many services.</p><p>Work in the UK government <a href="https://gds.blog.gov.uk/2015/07/13/lets-talk-about-permissions/">around licencing</a> lead to the identification of a ‘do something with permission’ type of service. This permissions type of service is similar to many services in the private sector, where certain checks are made to see if someone is eligible for something. Like ‘open a bank account’, ‘get a credit card’ or ‘get a loan’. There’s much to learn from teams working on <a href="https://medium.com/leading-service-design/types-and-stages-of-services-cd6d839e6e22">services of the same type</a>.</p><h3>5. A service includes all the parts involved in delivering it</h3><p>Services include all their constituent parts. The internal capability, activities, tools, systems and relationships are a part of its delivery. The way in which an organisation holds data. Or the contractual arrangements and service levels agreed with an outsourced provider. It isn’t only the bits the user sees and interacts with.</p><p>This also means a service is not a component part in and of itself. It’s not a website, a database, identification or authentication. Nor what internal team A does for internal team B. Not if you want to re-think how things work more fundamentally.</p><p>Much of these internal things are needed for a service. But they’re often shared across services. So the way your organisation does access and authentication, or its customer data repository, is a part of a set of services. In addition to being a component in its own right.</p><p>For those that think of what organisations do as capabilities, a service isn’t one. Though it might draw on existing capabilities to operate. It might create the need for new capabilities for it to work better. The work involved in a service could create capabilities that other services could draw on.</p><p><strong>Example</strong></p><p>The whole ‘get a passport’ service includes contact centres, passport offices, casework systems and reminder text messages. It’s how well the physical passport works in other countries. It’s the work of fraud teams. It’s the arrangements with logistics and fulfilment suppliers, including high street photo booths. As well as how you can apply for a new passport on screen.</p><p>IT systems aren’t services in the way we’re talking about. Rather, things like data repositories, content management systems, payment processing tools or certificate-issuing systems are usually a part of a wider service, or services.</p><h3>Defining services well</h3><p>If organisations don’t have well defined services, their internal efforts and priorities won’t be aligned with what it takes to operate them successfully. Without a clear understanding of real world service performance, it’s too easy to become a bad service provider — and not be able to see it. Organisations that define them well, aligning their internal work to services and their outcomes, are the ones that will become, and remain, the better service providers.</p><p><strong>Credit</strong></p><p>This draws on <a href="https://medium.com/u/cb252e06ed8c">Kate Tarling</a> and <a href="https://medium.com/u/e5d669f64a9f">Matti Keltanen</a>’s individual work with different organisations in the public and private sector. It’s also building on the work and writing of many people involved in government in the UK, including <a href="https://twitter.com/louisedowne?lang=en">Lou Downe</a> and their posts like ‘<a href="https://gds.blog.gov.uk/2016/04/18/what-we-mean-by-service-design/">what we mean by service design</a>’, ‘<a href="https://designnotes.blog.gov.uk/2015/06/22/good-services-are-verbs-2/">good services are verbs, bad services are nouns</a>’, <a href="https://twitter.com/steph_marsh81?lang=en">Stephanie Marsh</a> and ‘<a href="https://gds.blog.gov.uk/2018/04/04/what-do-we-mean-when-we-talk-about-services/">what we talk about when we talk about services</a>’, <a href="https://twitter.com/kateiw?lang=en">Kate Ivey-Williams</a> and ‘<a href="https://gds.blog.gov.uk/2017/11/30/building-end-to-end-services-into-gov-uk/">building end to end services in to GOV.UK</a>’. It relates to recent changes to <a href="https://www.gov.uk/service-manual/service-standard">the UK government service standard</a> and particularly point 2 ‘<a href="https://www.gov.uk/service-manual/service-standard/point-2-solve-a-whole-problem">solve a whole problem for users</a>’. The intention is to gather collective thinking, develop it through individual work with different organisations, put it in a single place, and make it relatable to both the public and private sector.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b9d5854ebb0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/services-and-service-organisations/defining-services-4b9d5854ebb0">Defining services</a> was originally published in <a href="https://medium.com/services-and-service-organisations">Services and service organisations</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Clearing the fog]]></title>
            <link>https://medium.com/services-and-service-organisations/clearing-the-fog-eed699f26bfc?source=rss----810cafc5bfc---4</link>
            <guid isPermaLink="false">https://medium.com/p/eed699f26bfc</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[organisation]]></category>
            <dc:creator><![CDATA[Matti Keltanen]]></dc:creator>
            <pubDate>Mon, 30 Sep 2019 07:53:35 GMT</pubDate>
            <atom:updated>2019-09-30T12:02:41.401Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zZcoFJfTcHrV9o-PyiIapg.jpeg" /><figcaption>Illustration by Rebecca Grace Jones | <a href="http://www.rebeccagracejones.com/">www.rebeccagracejones.com</a></figcaption></figure><h4>Using outcomes to focus organisations</h4><p>Written by <a href="https://medium.com/u/e5d669f64a9f?source=post_page-----4b9d5854ebb0----------------------">Matti Keltanen</a> and <a href="https://medium.com/u/cb252e06ed8c?source=post_page-----4b9d5854ebb0----------------------">Kate Tarling</a></p><p><em>Note: this article was originally posted under the name “Kate Tarling and Matti Keltanen”, and later re-posted under a single name to better suit Medium‘s publishing model.</em></p><p>Governments and other very large organisations are complicated things, often the product of decades of accumulated bureaucracy, structure, and habits. Those who work within them can feel how all the parts don’t always fit, or quite work, together. At their worst, they have all the structure and process of a hundred different organisations, competing and conflicting, while attempting to operate as one giant.</p><p>One problem is that organisations are not usually structured around their underlying purpose, or the core jobs that they fulfil, in the best way. It’s rare within a large organisation to hear a commonly understood sense of what exactly the organisation does and why, or see universal language in use that describes it. In light of this, it’s typical for different parts of the organisation to craft their own narratives and sense of what it means to be productive and to deliver good work.</p><p>In this article we look at root causes of why large organisations can fail to act effectively when designing, building and running services, and make recommendations for how to improve them. It’s based on years spent working with some of the largest, most change-resistant organisations (both private and public sector), re-positioning them to design and operate radically better products and services. This also builds on the ideas and work of many others, most notably <a href="https://twitter.com/ayeshamoarif">Ayesha Moarif</a>, <a href="https://twitter.com/RossDudley">Ross Dudley</a> and <a href="https://twitter.com/Theo_TB">Theo Blackburn</a>.</p><h3>A difficult problem to solve</h3><p>There are many very high level indicators of overall success for large organisations — stock price for a listed company, a broad policy area goal (like crime rate or public health statistics) for a public body, as well as often used secondary indicators such as net promoter score or customer satisfaction. The problem with large measures like these is it can be impossible to draw direct causal connections between most things happening in a large organisation and such broad overarching metrics. This makes them rarely directly useful in influencing any practical decision about what to do.</p><p>There are also many more specific (and sometimes competing) things that different parts of an organisation want to achieve. Some of it is by design: different professions hold different values and world-views. Some deeply value excellence of craft within their own field, some focus on keeping work on time and budget, some want to minimise risk, and so on. Individuals can be more or less proactive in relating their day to day work with any broader context or goals, for a variety of reasons.</p><p>The existence of each unit, project and team can also be easily justified on its own terms. The presence of self-contained units such as comms, marketing, strategy, operations, security, infrastructure management, IT, procurement, business management or a project management office, can be reassuring for some in a traditional context. However these entities are often working with their own internal agendas and working practices. Organisations that then add digital capabilities to the cast — technology specialists, product management, designers — may recognise that ‘they work in different ways’. But merely introducing whole new sets of people evidently doesn’t compel a large organisation to change their existing ways of working in all overlapping, lateral and vertical areas, especially if the leadership isn’t yet sure what exactly ‘working in different ways’ really means for their organisation. And so they continue to accumulate new layers, new teams, new departments, new practices. This can create an atmosphere of conflicting and overlapping goals and interests. It’s no wonder organisations don’t always work with a coherent focus.</p><p>All of this results in actual bottom-line problems, many of which are well-documented (and often the source of ongoing pain to the organisations themselves), like:</p><ul><li>“cost-shunting” — such as when central government makes cuts in welfare costs, which creates new burdens on local authorities</li><li>on-time delivery being seen as more important than whether a solution is needed or useful</li><li>services that many people try to use becoming so complicated, confusing and disjointed that users waste time and make easily avoidable mistakes (or even break the law in some government contexts)</li><li>increased costs — which are often significant — caused by problems with a service, resulting in the need to offer additional support, for example through contact centres for those who wouldn’t ordinarily need it, deal with people failing to do the right thing in other ways, or taking enforcement action, rather than just designing services better to avoid or minimise these problems</li></ul><p>There are plenty of examples. For some organisations, these kinds of structural issues multiply and reinforce each other, to the point where organisations become <a href="https://twitter.com/tomskitomski/status/1048866968290381824">unable to provide a viable working product or service</a>. The common problem is that the goals of a single part of an organisation can seem sensible in their own context while being harmful to, or missing opportunities to improve the whole.</p><h3>What to do</h3><h3>Have a shared definition of success</h3><p>The first step is to establish shared organisational goals that reflect the outside performance of the organisation instead of its inside structure. Ones that everyone knows, aligns to, and bears in mind alongside the specific aims and goals of their team, unit or profession.</p><p>We’ve likely all seen bad examples of high level statements — woolly or hypocritical mission statements, platitudes, or things that aren’t relevant to anyone’s actual job. So it’s important that these shared goals are both specific enough to be useful for decision-making and stated in plain English so they make just as much sense whether you are inside or outside the organisation.</p><p>One way to define success precisely enough for the many organisations that mainly provide services is to start by defining these services through their successful outcomes. A successful service outcome should mean that a user had their needs met, while a core business or policy goal was achieved.</p><p>This may sound like a simple idea, but it’s generally not how large organisations and governments look at things. Instead success is defined in all manner of other ways except successful outcomes, such as:</p><ul><li>very broad aggregate figures, e.g. stock price, crime rates, education levels</li><li>things that aren’t really useful for anything in themselves without context or explanation, e.g. number of people doing a particular thing, or ‘satisfaction’ with something</li><li>things that are about how something is done, rather than about good outcomes, e.g. proportion of times something is done digitally, or on a mobile device versus another channel</li><li>things that sound like success metrics that can become perverse incentives, e.g. only thinking of cost cutting rather than fundamentally redesigning root causes (so we cut valuable aspects of a service, shunting costs elsewhere), numbers of newsletter subscribers (so we make it hard to unsubscribe), minimised numbers of support calls (so we make the phone number hard to find, making the overall service worse) — in short, aiming at anything but actual overall success.</li></ul><p>As an example of a better way to define success, take the UK passport office. A way to describe its main purpose is to ‘provide a secure way for British citizens to be identified when travelling between countries’. In practice, this boils down to providing a service: getting citizens secure passports, that work where and when they need to, in time for when they need them. This is the central premise by which the entire organisation evaluates itself: the whole organisation has been successful each time that job is successfully done. And to define ‘successful’ means understanding what e.g. ‘a secure passport’ that ‘works’ means to the various interested parties — users, security and fraud experts, border control in the UK and other countries, the travel industry, suppliers — but the ultimate shared goal remains the same.</p><p>Something to watch out for is that it’s not uncommon for people in large organisations to assume the whole organisation is doing just fine. They may point to a customer satisfaction survey or commercial success as proof of this. Or there might be units, functions, projects, bodies or forums tasked with ‘making the organisation or portfolio more cohesive’, such as oversight, governance, or assurance, that suggests that there are full or reasonable efforts to do this. And these initiatives may indeed help — but they can also be only partially effective despite their best efforts, or at worst a fig leaf for organisational dysfunction.</p><p>The more unexamined the belief that everything is working “just fine”, the greater the likelihood of invisible, unaddressed problems continuing to fester.</p><h3>Evaluate the whole (to connect the parts)</h3><p>So far we’ve defined success for the whole organisation in terms of it meeting both user needs and core business/policy goals. Now we can move on to evaluating how well the whole organisation is performing using those outcomes.</p><p>For organisations that provide services, here are some useful questions:</p><ul><li><strong>How many people could or should be using this service</strong>? (Size of audience / market)</li><li><strong>How many potential users are aware that they can or should do so</strong>? (Is there an awareness problem?)</li><li><strong>How many potential users are doing something about it</strong>? (Is there an activation problem?)</li><li><strong>How many potential users find their way to the service</strong>? (Is there a discovery / routing problem?)</li><li><strong>How many users get through all the stages</strong> to successful completion without dropping off on the way for any reason? (How is the service performing?)</li><li><strong>How much time and effort does it take</strong> to get to the right outcome?</li><li><strong>How much time and effort is expended by the provider</strong> to get each client, user, customer or situation to the right outcome? (Is there an internal efficiency problem?)</li><li><strong>Is performance lower for any group of people</strong> for avoidable reasons, such as lack of support for access needs? (Is there a service performance problem that is potentially all the worse for being discriminatory?)</li><li><strong>Where are we seeing confusion, failure, drop-offs, wasted time, mistakes or need for help or support</strong>? Often these accrue in handover points between different organisations or parts of organisations.</li><li><strong>Are there parts that are generally known to be ‘just awful’, but don’t get fixed because they still ‘just about work’</strong>? Often bad solutions persist because the impacts of their problems are indirect, hard to measure and felt by someone else. But organisations shouldn’t accept they operate poor services, even if it’s difficult to quantify the harm in terms of success, inclusivity, satisfaction, increased support costs, drop-offs, reputational or brand damage, reduced advocacy, or other possible negative effects.</li></ul><p>And, most fundamentally:</p><ul><li><strong>What would be the best way to get to the successful outcome?</strong> Is our current way really the best, simplest way to get there? Are we missing significant opportunities to do things differently? How could it be better, faster, and have fewer points of possible failure?</li></ul><p>You can look at the performance — the rate of successful outcomes — for most services as a funnel, with a sequence of possible drop-off points. As a general rule: taking away effort, complexity, and room for confusion in the service gets more people to a successful outcome, which means a better success rate for the whole organisation.</p><p>The key point is that individual parts of the organisation that are delivering or building services don’t typically view things from the whole organisation or whole service point of view. They could see their immediate tasks or historic working practice as taking precedence, they may be under pressure from stakeholders to be ‘heads down’ and focus on their tasks at hand. It is important for leadership and middle management, as well as people working in various parts of an organisation, to proactively choose to focus on the shared outcomes.</p><h3>A small manifesto</h3><p>Many of us work with and within imperfect organisational setups. Many leaders recognise the need for radical change in their organisations but aren’t sure where to start.</p><p>One compelling argument for how to address this is that government and large organisations should — and can be — radically re-structured around the things they need to achieve and deliver, for example <a href="https://public.digital/2018/09/25/making-government-as-a-platform-real/#questions">by building new ‘digital institutions’</a>. If service design was <a href="https://en.wikipedia.org/wiki/Conway%27s_law">not constrained by our organisational divisions and structures</a>; if we had more shared, stable infrastructure that allowed flexibility of design and speed of implementation, government and other organisations could be more efficient, effective, transparent and significantly cheaper to run. This would mean organisations that are more fit for purpose, that make better use of the possibilities of the internet era, and are more ready for what’s likely to come.</p><p>This level of radical change takes time and is often outside of anyone’s individual control. In the meantime, there are practical things we can do today to set and maintain our organisation’s focus on its fundamental shared goals — and the products and services through which they’re achieved:</p><ul><li><strong>Clearly identify what the organisation does</strong>, using ‘view from the outside world’ language and plain English, so that it makes sense to everyone, including users. Example: a UK government department, the Home Office, made <a href="https://ukhomeoffice.github.io/coe/service-list/">a list of services</a>. Not as it knew them previously from an internal perspective, but as end users would know them, with each one underpinned by clear policy goals and intent.</li><li><strong>Consider significant changes made to policy or strategy in terms of outcomes to achieve </strong>and the services, products or interventions through which to do it. Separate the strategic intent from the means to achieve them, to avoid ham-stringing expert teams and allow room to learn what works best over time.</li><li><strong>Understand how services are really provided across organisations</strong>, unpicking the layers of technology, operational support, shared products, suppliers. Work to make this internal complexity invisible to the user as much as possible and wherever appropriate. Avoid only having views of a service from just one perspective (e.g. only technical architecture, or only what users see, or only data flows, or only which organisational actors are involved). Work together with others to do this. Example: step by step overviews of how a service works or will work, so that everyone comes together to figure out how to prioritise improvements.</li><li><strong>Find out how well services are performing</strong>. That is to say, whether everyone (in the real population of users) manages to do what they need to do without complication, confusion, error or wasted time — and where problems arise and why. And whether everyone, and every ‘thing’ behind the scenes (e.g. database, system, interaction, algorithm, protocol, process, procedure, mandate, infrastructure) are taking the right actions, without wasted time, without avoidable error and in a way that doesn’t make humans hate their jobs and human users hate their lives. Remember that just because we don’t usually get to see direct measurements of these things without trying hard, or that some things are hard to measure, doesn’t mean that performance is unknowable.</li><li><strong>Make performance visible across the organisation. </strong>Take it into account to inform decisions about strategy and investment and drives for efficiency or improvement. Stop the kind of discussions that focus only on one abstracted section of a service (e.g. outsourcing a collection of processes, converging technical architecture, implementing a helpdesk system, or debating whether something should be an app or a website) while ignoring how it impacts service outcomes.</li><li><strong>Describe all the work the organisation is doing clearly and simply</strong>, and where at all possible using the outside world context. Articulate assumptions about how proposed work could make your organisation better meet its goals, how it improves service(s) and how we are likely to be able to know this. If someone external to your organisation wouldn’t understand the language and concepts you use to describe your project or your business case, the chances are you don’t have enough clarity to manage it well either.</li><li><strong>Invest in new work only on the condition</strong> that it is likely to be a good investment in making an organisation successful towards its shared, specific, goals</li><li><strong>Manage ongoing investment</strong> (i.e. continue to fund, change or stop work) based on whether the work is proving that it’s likely to increase success on the same basis — not just whether it’s on time to deliver certain outputs.</li><li><strong>Prioritise fixable problems</strong> that contribute to services underperforming. Use a variety of mechanisms to do this. For example a) continuously funded service teams with a backlog of improvements to make for one or a collection of services, b) specific one-off change or redesign projects to make a defined improvement, c) including service improvements as part of other work, such as shared product or infrastructure changes. Be clear about what should change, why, the evidence for and against it and your assumptions.</li><li><strong>Use shared goals to define success and justify work</strong>. Internal teams, including operations, should be able to explain their existence and how they contribute to the shared specific goals, wherever applicable. Stop reporting numbers that really just describe ‘how busy we’ve been’ in favour of showing ‘how we are working towards outcomes in better ways’.</li><li><strong>Use desired outcomes as the basis for (re)designing services</strong>. This is a higher cause than serving our existing organisational structures. The best service is usually the shortest and most direct path to the right outcome. Asking ‘how could we achieve this outcome more successfully’ is more constructive than asking ‘how do we innovate’, ‘how do we use artificial intelligence’ or ‘how do we make the experience more compelling’, even if some of those end up happening. Or coming at it another way, evaluating all the bright ideas, to examine whether they’ll have the most significant impact on desired outcomes, compared to something else we could do.</li></ul><p>If the existing structures of an organisation are not yet elegantly aligned to such top-level shared outcomes and goals, but we still want to work in and with them, we have to set out a clear sense of purpose together. And to maintain this clarity, we have to work doubly hard to avoid being distracted and confused by the noise of organisational complexity, different working cultures, us-versus-them worries, or local incentives — whether you’re a product owner, a front line worker, a board member, a technical architect, a user researcher or from the project management office.</p><p>And when you look at it this way — when you keep your sense of purpose clear, and keep relating everything you see back to the shared goals, helping everyone around you to do the same — maybe we’ll find we’re all working together after all, even when organisations feel complex, difficult or reluctant to change, and the products and services we work to provide will get better for everyone as a result.</p><p><em>This article isn’t exhaustive, and we will continue to improve the points discussed. We’d love to hear about other things you’ve tried that may help organisations build better products and services, and we particularly welcome the challenge and critique needed to make this a useful shared resource.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eed699f26bfc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/services-and-service-organisations/clearing-the-fog-eed699f26bfc">Clearing the fog</a> was originally published in <a href="https://medium.com/services-and-service-organisations">Services and service organisations</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>