Non-functional requirements

By Marita Purins


There are a set of non-functional requirements that will help your project achieve the consistency and quality of design required to meet brand expectations.

These should be captured, agreed and documented as part of the formal project documents and specifications that will inform Build and Test.

Over time, these requirements will support Digital to operate sustainably and respond more rapidly.

The standard set of requirements to build optimally using the GEL are:

  • Comply with the specification provided in the agreed design deliverables to ensure the user experience maintains its integrity and customer centric intent.
  • Comply with browser and operating system guidelines.
  • Meet or exceed the required accessibility compliance (AA) level.
  • Ensure development and design aligns with the Design System to better embrace adaptive or responsive approaches.
  • Use a single source of code for development builds to maintain multiple brands and devices.
  • Deliver solutions that are ‘flexible’ enough to future-proof brand updates without extensive reworking or development.


  • Discuss and agree with the Project Owner and Build Team Lead, the level of engagement with the GEL and what needs to be done to achieve a quality outcome.
  • Make sure that you secure skilled UX and Visual Designers and Front-End Developers.
  • Engage with Build teams during the conceptual design phase — gain their input to optimise the experience, there might be some interactions that need some extra attention to deliver to while achieving performance targets.
  • Plan for UX and Visual Designer involvement during build to solve design execution challenges and provide user interface quality assurance reviews.