Service transformation strategy
We prioritise steel threads that span the whole user experience. On that foundation we deliver more complex user journeys.
Building new capabilities block-by-block risks building services that reflect our own structures - not based on what users are trying to do. It also takes longer to get new services into the hands of users, increasing our risk.
These principles guide our decisions for delivery:
- Focus on user needs even over internal requirements.
- Prioritise direct user value even over generic capabilities.
- Deliver smaller, quicker increments even over larger, complex releases.
- Make longer-term product and tech decisions even over short-term fixes.
On this page:
# Service transformation, digitisation and digitalisation
Service transformation is more than digitisation and digitalisation:
- 'Digitisation' is about going from an analogue to digital format (for example, a paper form to a PDF).
- 'Digitalisation' is using technology to change business model and processes.
- 'Service transformation' is about improving people's experiences by building services that meet their needs.
Transforming a service means improving the whole experiences for people, not the individual parts. It also requires us to improve the platforms and experience of people in government that support the service.
- Digitisation: "Welcome to the online version of our paper form. Your permit will be issues by mail in 30 days."
- Digitalisation: "We've redesigned our operations. Everything is more efficient and smooth. Thanks for using our online form. Here's your permit."
- Service transformation: "No more form - we've got data from other agencies you deal with. We've determined your risk level and you don't need a permit. By the way, you also qualify for this grant."
# Human-centred design
We follow human-centred design. This means we involve the people we are designing for in every stage of the process.
We start with developing empathy for people. We test lots of ideas (hypotheses) with these people to work out what we should build. As we build, we keep testing our service with people to make sure we're building the right thing.
As we release we keep listening to people to work out how to make the service better.
# Design thinking
The design thinking mindset is a way of defining and solving complex problems by taking a human-centred approach.
Think of it as a methodology that helps you to identify and scope problems, understand people, challenge assumptions, and find new ways to solve problems.
# Agile approaches
We use agile approaches, rather than one fixed framework (such as SAFe)."
Agile is an umbrella term that refers to frameworks, practices, processes and mindsets. What they have in common is their intent to:
- optimise work to create the greatest value
- identify and adapt to change
- keep on improving.
Agile frameworks are generally used by teams. But agile can scale from individuals to multinational organisations.
Teams that follow agile approaches work in the open. This means they encourage engagement, validation and feedback of their work. As a result, teams build from an evidence-based foundation. They also refine their approach based on new knowledge.
Agile works for many different things. This includes, policy, education, manufacturing, military and other specialist fields.
Learn about the benefits and principles of agile delivery.
For more info, read the department agile playbook in SharePoint.