BETA This playbook is in BETA, we think it’s good enough to be useful right now, but there are gaps that need filling – your feedback will help us to improve it.

Navigate this page
Back to Our Digital Principles

Contents

Undertaking ‘customer research’ to learn the full context of what the user is trying to achieve

DescriptionRationaleImplicationsTools / Methods / ResourcesMaturity / Check List

Description

Undertaking ‘customer research’ to learn the full context of what the user is trying to achieve, not just the part where they have to interact with the Council, and continue to get feedback on designs, through to deployment, and beyond.

inset-text

Understanding as much of the context as possible gives you the best chance of meeting users’ needs in a simple and cost effective way.

Focusing on the user and the problem they’re trying to solve – rather than a particular solution – often means that you learn unexpected things about their needs.

The real problem might not be the one you originally thought needed solving. Testing your assumptions early and often reduces the risk of building the wrong thing.

GOV.UK Service Standard

Rationale

Building successful products and services that meet people’s actual needs will mean that they will be used; ‘failure demand’ will be reduced, so that intended outcomes and cost-savings are achieved.

Tracking the ‘customer journey’, can find opportunities for making joins across council services and other Somerset partners, so that information is collected once, and delivery is coordinated.

Implications

The ‘users’ of a digital service should be defined, and segmented, for example

  • Digital Customer
    • residents, visitors, local businesses, workers, families, carers, minorities etc
  • Digital Council
    • employees, home-workers, visiting officers, members, managers, contractors
  • Digital Place
    • partners, community assets, voluntary, employers, investors

Tools / Methods / Resources

  • user research, secondary research and analysis
  • co-design with users
  • user centred design
  • build quick, safe to fail prototypes to test hypotheses.
  • build representative ‘panels’ of key user types, to give feedback to proposals
  • analyse data to understand actual use patterns

Maturity / Check List

  • Have the ‘users’ been determined?
  • Have user needs been understood and addressed?
  • Have opportunities for joining up the user’s experience been explored?
  • Can users provide feedback, and suggest improvements?
  • Can take-up/success/failure be monitored over user groups?

Last reviewed: July 14, 2023 by James

Next review due: January 14, 2024

Back to top