Service management in practice: public sector and cloud services

The key concepts of this course apply everywhere, but they look different depending on the setting. This lesson applies them to two settings that most learners will meet: public-sector services, where consumers often cannot choose another provider and services are shaped by law and public policy, and cloud services, where many organizations now get most of their technology. It uses examples from government digital services and cloud contracts to show value, roles, offerings, utility, warranty, relationships and experience in action.

What makes public services different

Government services share the basic shape of any service: a provider facilitates outcomes for consumers while taking on specific costs and risks. Yet several features make them distinctive:

• Limited choice: residents cannot usually switch to another passport office or tax authority, so poor services can persist without losing "customers".
• Legal mandate: many services exist because a law requires them, and their rules are set by legislation and policy, not only by consumer demand.
• Universal access: services must work for everyone eligible, including people with disabilities, limited literacy, no internet access or complex circumstances.
• Many stakeholders: taxpayers, elected officials, oversight bodies, the media and the public all have an interest in how services perform.
• Public value: success includes fairness, trust in government and social outcomes, not only efficiency.

These features make the consumer roles especially interesting. A resident applying for a benefit is a user. The legislature that funds the program acts much like a sponsor. The department accountable for the program's outcomes plays the customer role on behalf of the public. Balancing these roles is a central challenge of public service management.

Government digital services

In Canada, the federal government sets direction for service and digital through the Treasury Board's Policy on Service and Digital, in effect since April 2020, which requires departments to design services around clients, manage information and data as strategic assets and use technology securely. The Government of Canada Digital Standards set out ten principles: design with users; iterate and improve frequently; work in the open by default; use open standards and solutions; address security and privacy risks; build in accessibility from the start; empower staff to deliver better services; be good data stewards; design ethical services; and collaborate widely. Service Canada provides many services directly to residents, such as Employment Insurance and passports, and the Canadian Digital Service, which became part of Employment and Social Development Canada in 2023, helps departments build user-centred digital services. Shared Services Canada, created in 2011, is an internal shared services provider that consolidates email, data centres and networks for federal departments.

Whatever the country, government digital programs have pushed the ideas in this course into the mainstream: design with users, measure outcomes and experience, iterate in small steps, and treat services end to end rather than as separate departmental systems.

Shared services as internal providers

Shared services organizations, in government and in large companies, are a clear example of the provider role inside one organization. They consolidate common services such as email, networks, data centres, payroll or procurement and provide them to many departments. The promise is lower cost and better quality through scale. The risk is that departments, which cannot easily choose another provider, feel the shared service ignores their needs. The concepts from lessons 3 and 7 apply directly: identify customers, users and sponsors in each department; describe offerings in a catalogue; agree service levels; and invest in relationship management so that consolidation does not cost the trust of consumers.

Cloud services and the key concepts

Cloud computing is now the main way many organizations get technology. In ITIL terms, a cloud offering is largely access to resources (computing, storage and software owned by the provider), combined with service actions (support, managed operations) and sometimes goods (hardware appliances for on-site use). The three common service models divide responsibilities differently between provider and consumer:

The shared responsibility model is a practical form of the provision and consumption split from lesson 7. Many cloud security failures happen not because the provider failed, but because the consumer misconfigured storage, left default passwords in place or gave too many people access. Understanding which side is responsible for what is essential.

Utility, warranty and cost in the cloud

Cloud providers publish service level agreements, usually for availability, with service credits when targets are missed. As lesson 6 showed, credits rarely compensate for lost business, so consumers design for warranty themselves, for example by running across several availability zones or regions. Cloud also changes costs: instead of buying hardware up front (capital expense), consumers pay for what they use (operating expense). This flexibility removes the cost and risk of idle hardware but imposes the risk of unexpected bills if usage is not controlled. The discipline of managing cloud spending is often called FinOps.

Cloud and public sector together

Governments use cloud services too, under rules that reflect the sensitivity of public data.

In Canada, federal departments use cloud services under Treasury Board direction and guidance on data residency and security, and the Canadian Centre for Cyber Security assesses cloud providers' security controls so that departments can use them for protected information. Provinces and municipalities set their own rules, and privacy laws such as those in British Columbia and Nova Scotia have historically placed limits on storing certain public-sector personal information outside Canada. Public bodies should check the current rules in their jurisdiction.

Common lessons from public and cloud services

Experience across many government and cloud programs points to a few recurring lessons that connect back to the key concepts. First, start with users: services designed around the structure of the organization rather than the needs of the people using them tend to fail, however good the technology. Second, measure outcomes and experience, not just outputs: a website launched on time is an output; residents completing a task easily is the outcome. Third, mind the supply chain: many high-profile service failures came from dependencies, such as an overloaded identity verification step or a supplier's outage, rather than from the main system. Fourth, keep humans in the loop: automated and digital services need clear routes to a person when something unusual happens.

Keeping these lessons in mind helps practitioners in any sector avoid repeating well-known mistakes.

Whichever sector you work in, these patterns repeat, which is why the key concepts are worth learning well.