[Task] Research & Define the standards for design ticket writing

[archibald-ebi]

Summary

The Design team is establishing a shared approach for creating, structuring and maintaining design tickets across GitHub, Jira and other project management tools.

The objective is to ensure tickets communicate clear scope, context and outcomes regardless of who creates them, improving collaboration between Design and Engineering.

Areas of focus could include:

• Standard ticket structure and formatting
• Writing clear problem statements and objectives
• Defining scope, acceptance criteria and deliverables
• Separating Epics, Issues and Sub-issues
• Documenting design decisions and dependencies
• Linking supporting artefacts and documentation

Why

Well-written tickets reduce ambiguity, improve planning and enable smoother collaboration across disciplines. A consistent approach allows anyone in the team to understand the purpose, progress and expected outcome of a piece of work without relying on additional context.

These standards should simplify ticket creation while improving communication throughout the product development lifecycle.

Working Document

We are using the attached working document to capture research, examples, proposed templates, discussions and best practices as they evolve.

Outcome

This ticket marks the initial research and definition of our design ops principles regarding writing tickets. The outcome is to share suggestions for additional guidance or standards that would improve consistency, scalability and usability across our ticket management platforms.

Guidance and standards that help us with;

• Ticket writing principles
• Standard templates and examples
• Documentation and communication guidance
• Discussion points and future improvements

As the work evolves, this ticket and the accompanying document should become the source of truth for how Design scopes, documents and communicates work.

[archibald-ebi]

Dale - Research Brief - Ticket Writing Standards
Clear, well-written tickets help everyone understand the purpose, scope and expected outcome of design work. The objective of this research is to define best practices for writing and refining design-focused tickets that communicate effectively with designers, developers, product managers and stakeholders. While our primary focus is GitHub, the principles should be transferable to Jira and other project management tools.

Research tasks

• Review the existing ticket templates and documentation, identifying opportunities for improvement.
• Research industry best practices for writing design, UX and product tickets.
• Define the information every design ticket should include, from context and objectives through to deliverables and acceptance criteria.
• Suggest standards, templates or guidance that improve clarity, consistency and collaboration across the team.