Why service designers and data practitioners should collaborate more.
Ever since I joined Snook 4 years ago from a business background, I have been keen to look at how service designers and data practitioners can work together to achieve greater impact.
We share a vision
I’m not suggesting that service designers need to become data analysts, or technologists need to become service designers. We need to know each other well enough so that we can call on each other’s strengths.
When I talk to designers and data practitioners, in particular around open data, it strikes me that we often share a vision. The transparency and transformation agenda have a lot in common. We believe in evidence-based decision making, even if the evidence we specialise in — qualitative or quantitative — varies. We believe in open-ended innovation; that well-designed solutions benefit not only the users but have a positive impact on the wider ecosystem. We believe in continuous improvement.
We need to be aware of each other
As a project manager of a data project, do you ask your client: “Do you have a service design team we can involve?”. As a service design team, do you routinely invite a data team to your project kick-off or include them in your stakeholder mapping?
Something to do: try to find these teams or people. It might not be a formal team; it may simply be someone with an interest. You might find allies who help you deliver better outcomes.
We need to better understand each other
We then need to understand how our disciplines fit together, and what we can each bring to a project. Service designers want to design services as end-to-end experiences that help users achieve their goals, are practical for staff, and are sustainable for the organisation. Data experts help manage the organisation’s data efficiently, so that it can be an asset to enable evidence-based decisions.
Something to do: Interview data technologists to better understand them, in the same way that we interview users and stakeholders to design a service.
What data can we work on together?
When we talk about design and data, designers automatically think of quantitative data to support qualitative insights. However, what we’re talking about here is different.
Firstly, it is about the data that the service needs to function. For example, a service that enables Council to collect council tax from residents needs data about the properties, such as size and location. It requires data about who lives in the property, their age and status. We need to pay more attention to the ‘inside’ of the form: the data that users enter into the forms that we create.
Secondly, it’s the data that the service creates that might be used for the purpose of the service or for other purposes. For example, when businesses pay their tax to the Council, it creates a dataset not only about the businesses and their taxes, but also about the state of the local economy.
We need all the data
To design efficient and effective services, we need to consider the whole data spectrum, not just open data. Open data is the tip of the iceberg — the part that is visible to users outside the organisation — but policymaking and continuous improvement require the full spectrum, including shared and closed data.
If a Council is designing interventions to increase the resilience of the local economy, it needs to know about all businesses; including sole traders, unincorporated associations, and partnerships. Otherwise, it runs the risk of reaching erroneous conclusions. Service designers also need to include in their designs how the service might publish open data safely and efficiently to deliver benefits to wider ecosystem beyond the service users and providers.
Something to do: Do you work with data and service design? I’d love to hear from you and share our practices. Some great work is being done across the sector, but we are only at the beginning of this journey.
