» Context helps to make a service good as opposed to simply existing

» By not consciously designing our services, we instead force our users to link actions together

» Outcomes for users are core user needs that a service helps them to meet

» A starting point can be to ask different teams what ‘good’ looks like to them

A service:

» is defined from an external end user’s point of view

» describes something someone would want to do, in their language

» has an outcome that relates to the organisation’s goals

» includes all the steps between the user and provider

» includes all the parts involved in delivering it

» Service maps help teams and stakeholders to understand interactions with a service across touchpoints over time

» They provide a visual representation of an abstract and often wide-reaching process

» Think of your service like a theatre: front stage, backstage and behind the scenes

» Service mapping helps your team to tell their story to the wider organisation

When companies set out to redesign a product or service, the results can sometimes be underwhelming. Instead of delivering service transformation, the team recommends only minor efficiency tweaks. If this has been happening to you, there can be many underlying causes. I’ve identified a few common problems and what you can you do about them.

» 6 core concepts of systems thinking will help you start solving complex problems

» Systems thinking complements the more familiar analytical (reductionist) thinking

» It is a way of creating a shared understanding of how something works

» It provides useful tools for surfacing and breaking reinforcing cycles of blame