What is expected from an Interaction Designer in Live

During the live stage the focus is on operating, improving, and scaling a service that is already in production. The emphasis is on whether the team has built a sustainable, high-performing service that meets the GOV.UK service standards.

The purpose of live is to ensure that the service:

• meets all user needs identified in discovery and alpha
• has been tested, iterated and improved during beta
  is ready to operate as a sustainable, long-term service

It is the gateway to move into the live business as usual (BAU) phase of service delivery.

Interaction design involvement

As an interaction designer, much of the core design work will be completed by this stage, but you may still be involved in:

• minimum code prototype iterations based off user research, analytics and live feedback
• ensuring the service can be operated sustainably over the long term
• confirming that adequate resources and capacity are in place to support continuous improvement
• establishing clear operational roles and effective BAU support arrangements
• reviewing beta performance data and service metrics
• demonstrating that the service is performing as intended against user needs and service standards
• ensuring the service meets the latest published WCAG standards to ‘AA’ standard
• supporting through testing and quality assurance prior to release
• maintaining or completing a design history to document how the service has evolved over time, capturing what was created, why decisions were made, and how

In short, live stage interaction design is about embedding good interaction design into day-to-day delivery and operations, while adapting minimal changes to the service to meet user needs and government priorities.

What outputs are expected from an Interaction Designer in Beta

Interaction designer outputs should include the design artefacts appropriate to the phase and needs of the service, for example:

• rapid, code prototyping informed by pilot insights and user research
• annotated user flow map
• technical feasibility risk log, as and when appropriate
• contribute to a risks and constraints log
• document any custom components and patterns, and share within NHSBSA, NHS and GOV.UK communities

---

Improve the playbook

If you spot anything factually incorrect with this page or have ideas for improvement, please share your suggestions.

Before you start, you will need a GitHub account. Github is an open forum where we collect feedback.