A source of truth for design operations
Use Cases and Deployment Scope
The Design, Product, and Engineering teams use Abstract as a point of design collaboration and design/engineering handoff. In addition, the Product Design team uses Abstract to facilitate a feature branch workflow—allowing team members to work on granular elements of larger projects—for sketch files, design reviews, and management of sketch pattern libraries. All communications within Abstract create a captured timeline of interactions that are useful for managers to see how projects progress through the design lifecycle.
Pros
- Feature branch workflow
- Design/engineering handoff
- Design reviews
- Pattern library management
- Source of truth for UI design artifacts
Cons
- People and permission management.
- Sharing particular states (presentation, inspection, etc.).
- New projects from templates.
- Pattern library migration (new users).
Likelihood to Recommend
<ul><li>Large teams with dedicated design operations support</li><li>UX managers that want a facilitated workflow for their teams</li><li>Disciplined teams of individual contributors that want to adopt a process in their UI workflow</li><li>Cross-discipline teams that want a central collaboration space for reviewing and critiquing UI artifacts</li><li>If your files are named "FOR-REALS_FINAL_FINAL_FINAL_Super-Important-Project (copy).sketch"</li><li>If you're managing multiple pattern libraries</li></ul>
