Design & UX Workflows
Streamline design handoffs, asset management, and collaboration between design and development teams.
Design Handoff Workflow Inside Story
Complete the entire design-to-development handoff process within a single story ticket, ensuring nothing is missed.
Workflow Structure:
- Designer Checklist:
- Wireframes created and reviewed
- Mockups finalized
- Zeplin/Sigma/Figma link shared
- Design specifications documented
- Dev questions answered
- Responsive breakpoints defined
- Accessibility requirements noted
- Attach File Triggers - Required design assets
- Design files (Figma, Sketch, Adobe XD)
- Asset exports (icons, images, SVGs)
- Style guide references
- Animation specifications
- Blocker Trigger - Dev tasks only become active after designer marks handoff complete
- Change Assignee + Notify - Auto-assigns to dev and pings #design-handoff channel
🎨 Seamless Handoff: All design assets and context in one place, eliminating back-and-forth emails and Slack messages.
Design Review & Iteration Process
Structure design reviews with clear feedback loops and approval gates.
Workflow Structure:
- Initial Design
- First iteration created
- Design files attached
- Blocker → Stakeholder Review
- Product manager review
- Engineering lead review
- User research team review
- Notify Trigger - Alerts stakeholders when review is ready
- Feedback Collection - Comments and feedback tracked in checklist
- Blocker → Design Iteration - Designer addresses feedback
- Final Approval - All stakeholders approve
- Blocker → Handoff to Development
Design System Compliance Checklist
Ensure all designs follow your design system standards before handoff.
Compliance Checklist:
- Uses approved color palette
- Follows typography guidelines
- Uses standard spacing system
- Components match design system library
- Accessibility standards met (WCAG AA)
- Responsive design patterns followed
- Animation guidelines adhered to
Blocker: Design cannot be handed off until all compliance items are checked.
Automated Asset Management
Use attach file triggers to ensure all required design assets are included before handoff.
Required Assets:
- Design Files - Source files (Figma, Sketch, etc.)
- Exported Assets - Icons, images, illustrations in required formats
- Specifications - Spacing, sizing, color values
- Prototypes - Interactive prototypes for complex interactions
- Style Guide References - Links to design system documentation
Best Practices
- Always include attach file triggers for critical design assets to ensure nothing is missing
- Use blockers to prevent development from starting before design is complete and approved
- Configure notify triggers to alert development team when handoff is ready
- Include design system compliance checks as a mandatory gate before handoff
- Use change assignee triggers to automatically transfer work from design to development
- Structure design review checklists to include all relevant stakeholders