List view
## What Drive consistency and governance of the system by seeking opportunities to improve. Perform audits across British Gas sites and internal Nucleus tools to identify gaps, redundancies, and opportunities for improving design system adoption and accessibility. ## Why Without visibility into how and where the design system is (or isn’t) used, inconsistencies and inefficiencies will persist. Auditing enables proactive improvements and enforces standards. ## Value & Measure Improved consistency and quality across digital experiences. Reduced duplication and technical debt. Clearer governance and accountability. Stronger foundation for scaling the design system.
Due by December 31, 2025•8/11 issues closed## What Gain a clear understanding of the business’s organisational structure Engage leaders to actively advocate for the adoption of the Nucleus design system. ## Why Without leadership advocacy, design system adoption will be come fragmented and deprioritised. Embedding Nucleus into strategic planning ensures it becomes a foundational part of how teams build and deliver. ## Value & Measure Stronger alignment between UX, product, and engineering leadership. Increased visibility and prioritisation of the design system. A unified approach to design and delivery across the organisation. Greater momentum and consistency in adoption. Proof of multi-brand capability.
Due by December 31, 2025•1/1 issues closed## What Ensure every component in Nucleus conforms to the latest WCAG 2.2 AA compliance – or better – to support inclusive, accessible digital experiences. ## Why Accessibility is a non-negotiable foundation of good design. It can also be a legal requirement. Proactively addressing it ensures our components are usable by everyone, regardless of ability. ## Value & Measure Promotes digital inclusion by embedding WCAG 2.2 AA standards into every (50+) components. Reduces risk of non-compliance and retrofitting costs Builds trust with users and stakeholders through inclusive design practices.
Due by December 31, 2025•4/4 issues closed## What? Strengthen relationships with engineering and cross-functional teams by embedding UX expertise into shared initiatives and improving collaboration practices. ## Why Embedding UX early and building strong partnerships ensures better outcomes, shared ownership, and scalable design practices. It has been highlighted that there is likely a need to improve the UX consideration within the the P&E products offering. ## Value and Measure Improved usability and efficiency across at least 2 teams Scalable UX practices through toolkits and embedded support (Material available in central resource e.g. in a centre of excellence). Increased UX maturity rating and awareness across departments. A better quality experience for the user.
Due by December 31, 2025## What? We should have a single managed github org. All Nucleus repositories to be migrated to a single github org. Explore new productivity tools to enhance team efficiency. ## Why? Fragmented tooling and scattered repositories create friction in collaboration, onboarding, and visibility. A unified platform will reduce context switching and improve team alignment. ## Value & Measure Improved developer experience and faster onboarding. Clearer ownership and governance of code assets. Enhanced collaboration through intuitive, modern tooling. Measurable gains in productivity and team satisfaction. E.g. Estimated productivity gains: Xhrs saved per developer per week = £XXXX, £ per month, £ per year...
Due by December 31, 2025•1/2 issues closed- No due date
- No due date
- No due date•74/77 issues closed