Service Community

A service community is a network of people organized around a user journey, often across organizational boundaries. GOV.UK’s Service Manual describes it as a way for policy, operations, digital, and other participants to understand users and coordinate improvements. Members bring different priorities, responsibilities, and funding arrangements. The network gives them a place to work through those differences; it does not automatically acquire their organizations’ decision authority.

An internal dataset-access journey may involve a platform catalog, a service-desk ticket, a data owner’s approval, and identity synchronization. If a blueprint records three days of waiting, investigate which steps contributed, using timestamps and participants’ accounts. A shared elapsed time does not establish that the delay is jointly owned or that any one team can remove it. A community can help the relevant parties assign investigations and changes. Execution still needs named owners, permissions, and time in the affected teams’ plans.

What it takes to start one

GOV.UK recommends checking for an existing community, defining the problem and purpose, and inviting participants. Aim to include the organizations with a stake, both people who understand delivery and people who can influence decisions. Starting with available participants and expanding is acceptable; less formal collaboration can also be useful. A purpose statement helps invitees decide whether and how to contribute.

Agree objectives, facilitation, meeting cadence, and how information and research will be shared. These arrangements can be documented in terms of reference or another accessible working record. Map the service landscape and user journey together, then connect proposed improvements to action owners and a backlog. Shared channels and documents help communication where participants can access them; distributing findings through existing channels can also work. Reuse relevant research while checking whether gaps or changed conditions need further investigation.

What it is not

A community of practice develops knowledge through a shared area of work or concern. A service community centers its work on a particular user journey. Their participants and purposes can overlap: people improving a journey may also develop a shared practice. Choose the arrangement from the work to be done, rather than requiring a separate group for each label.

Use the service blueprint and measured problems to focus discussion, then distinguish advice from authority to act. A community may recommend a change that its members cannot approve themselves. Record the receiving decision-maker, the approval needed, the implementation owner, and what happens if organizations disagree. Terms of reference can describe this process but cannot confer powers the organizations have not delegated. A useful outcome can be an implemented change, an approved investigation, or a reasoned decision to retain the current arrangement with a review condition.

How a platform connects this work with capability ownership and relationships with its consumers is covered in Beta for Two Years, Retired in a Changelog.

References:

• GOV.UK Service Manual, Working across organisational boundaries with service communities (Open Government Licence v3.0).
• GOV.UK Service Manual, Map and understand a user’s whole problem (Open Government Licence v3.0).