To be actioned once #2416 is completed.
Summary
Following the completion of the Design Operations research phase, this ticket focuses on converting the team's approved recommendations into formal documentation. The aim is to establish a clear, maintainable, and accessible set of Design Operations guides that standardise how we work while remaining flexible enough to support different project needs.
This work will transform the research findings into documentation that becomes the team's reference for ways of working with Figma.
Why
The research phase should have identified opportunities to improve consistency, efficiency, and collaboration across the Design team. To realise these benefits, the agreed principles now need to be documented in a way that is easy to understand, maintain, and reference during day-to-day work.
Well-written documentation will:
- Create a single source of truth for Design Operations.
- Reduce ambiguity and inconsistent working practices.
- Support onboarding of new designers and contributors.
- Enable future updates as our processes and design system evolve.
Outcome
This ticket marks the transition from research into implementation. The completed documentation will become the Design team's source of truth for agreed ways of working, enabling greater consistency, improved collaboration, faster onboarding, and a foundation that can evolve alongside Figma, workflows and Design Operations practice.
Documentation Deliverables
- Ensure documentation follows a consistent structure, tone and terminology.
- Add diagrams, examples and screenshots where they improve clarity.
- Documentation reflects the outcomes of the research phase and team alignment.
- Documentation is published on the WebDev drive.
To be actioned once #2416 is completed.
Summary
Following the completion of the Design Operations research phase, this ticket focuses on converting the team's approved recommendations into formal documentation. The aim is to establish a clear, maintainable, and accessible set of Design Operations guides that standardise how we work while remaining flexible enough to support different project needs.
This work will transform the research findings into documentation that becomes the team's reference for ways of working with Figma.
Why
The research phase should have identified opportunities to improve consistency, efficiency, and collaboration across the Design team. To realise these benefits, the agreed principles now need to be documented in a way that is easy to understand, maintain, and reference during day-to-day work.
Well-written documentation will:
Outcome
This ticket marks the transition from research into implementation. The completed documentation will become the Design team's source of truth for agreed ways of working, enabling greater consistency, improved collaboration, faster onboarding, and a foundation that can evolve alongside Figma, workflows and Design Operations practice.
Documentation Deliverables