Designing a clearer route from access request to active user.
Service design for user onboarding and access management within a complex public-sector technology environment.
Consulting work delivered while supporting UKHSA and Accenture focused on the onboarding and access-request model for the DaSH Data Analytics & Surveillance Hub.
The work connected the user journey with approval processes, service-desk activity, access provisioning, stakeholder responsibilities and supporting technology.
User needs access
A user requires access to the DaSH service or supporting capabilities.
Submit request
Required information enters the onboarding and access management process.
Check requirements
Service teams confirm the request is complete and ready to progress.
Authorise access
Relevant approvals and access decisions are completed.
Configure access
Service and technology teams complete the required provisioning activities.
Active user
The user receives access and can begin using the service.
Onboarding into a complex digital environment is not simply an account-creation task. It is a service involving users, approval decisions, service desks, technology teams, access controls and multiple operational hand-offs.
The DaSH work focused on making that end-to-end service easier to understand and manage.
Service-design methods were used to connect the user journey with backstage processes, stakeholder responsibilities, access provisioning and supporting systems. The aim was to create a more structured model for handling access requests from initial need through to active use.
Users experience onboarding as one journey , even when delivery depends on multiple teams, approvals, systems and suppliers behind the scenes.
One user journey. Multiple operational dependencies.
Access management crossed organisational, technical and operational boundaries, creating a need for clearer service ownership and process visibility.
Different access needs
User requests needed to contain enough information to move through the service without unnecessary clarification or rework.
Multiple delivery teams
Requests could move between service-desk, operational, supplier and technology teams.
Responsibilities needed clarity
Teams needed to understand where responsibility changed and who owned individual parts of the process.
Users needed a coherent journey
The operational complexity behind access provisioning should not become unnecessary complexity for the person requesting access.
Connect the visible user journey with backstage delivery.
A service blueprint perspective helps show why onboarding depends on more than the form or interface the user sees.
User provides the information required to request access.
Additional information may be provided if clarification is required.
Approval activity occurs behind the service.
Technology activity converts an approved request into access.
User reaches the intended onboarding outcome.
Capture the access request and required data.
Clarification or status information where required.
User-facing indication that approval is progressing.
Service progresses toward account activation.
User receives the information needed to begin.
Request enters operational workflow.
Completeness and service requirements are checked.
Required approval decisions are completed.
Access is provisioned through the relevant technology process.
Operational responsibility moves into ongoing support.
Request intake and coordination.
Check request conditions and dependencies.
Confirm appropriate access.
Carry out required system activities.
Resolve issues following activation.
Make the whole onboarding service visible.
The work combined process, experience and organisational perspectives rather than treating access management as an isolated technical workflow.
Structure the service
Bring together the core onboarding, access-management and service-integration views into a shared service model.
Map the end-to-end workflow
Document account requests, approvals, provisioning, dependencies and operational hand-offs.
Clarify who does what
Map the organisations, teams and suppliers involved in moving a request through the service.
Improve onboarding flow
Consider request submission, approval, activation and support from the user’s point of view.
Align delivery teams
Create clearer collaboration between service desks, operational teams and technology providers.
Connect design to delivery
Support implementation, workflow alignment, risk consideration and operational readiness.
Clarify the people and organisations behind the journey.
The project involved UKHSA, Accenture, ATOS and other service providers operating within the onboarding and access environment.
Access requester
Needs a clear path from access need through to successful activation.
Service & operational teams
Participate in service operation, request handling and organisational access requirements.
Delivery participation
Supports elements of the digital and operational service environment.
Technology delivery
Supporting technical teams and suppliers participate in account and access activities.
Shared responsibility
The user outcome depends on all participants working through a connected service model.
Reduce ambiguity between request and access.
A structured onboarding model creates clearer stages, responsibilities and service transitions.
Request
Capture the right user and access information.
Validate
Confirm the request is complete and ready to progress.
Approve
Route the request through the required authorisation.
Provision
Complete the technical actions needed to provide access.
Activate
Confirm the user can access the required service.
Support
Provide a clear route for ongoing access issues or changes.
Give teams a shared view of how onboarding works.
The engagement combined service-design, process, participation, UX and delivery artefacts.
Service Design Pack
A structured view of onboarding, account management and access provisioning.
End-to-end process maps
Visibility of request, approval, provisioning and service interactions.
Participation diagram
Clearer understanding of stakeholder roles, relationships and responsibilities.
Onboarding journey
A user-centred view of request submission, approval and activation.
Delivery responsibilities
Greater visibility of where teams and suppliers participate in the service.
Implementation framework
A more structured basis for delivering and evolving the onboarding service.
The work established a more structured view of the DaSH user-onboarding and access-management service, connecting the user journey with operational processes and stakeholder responsibilities.
Process and participation models made the dependencies between request handling, approvals, service-desk activity, provisioning and activation easier for teams to discuss together.
The available project material describes improvements to request handling, stakeholder clarity, access control and the scalability of the onboarding model. No verified quantitative performance measures are published here, so the case avoids unsupported percentage or cost claims.
Complex onboarding becomes easier to improve once the whole service is visible.
If your organisation is dealing with fragmented onboarding, unclear ownership, complex approval processes or difficult operational hand-offs, tell us what needs to work better.
Start a project ↗