Standard Operating Procedures for DesignOps
01
DesignOps is the practice of planning, defining, and managing a design practice within an organization.
Benefits of DesignOps
- Central library components/design tokens for development
- Central design system for rapid prototyping
- Standardized tools and processes
- Team is centralized and can adapt to organizational design needs
- Managing and prioritizing requests
02
Design System
PEAK UI is the shared design system of components used by all Ascent products.
- An Angular Material Design foundation
- Coded components live in Storybook
- Design version of components live in Figma
- Component design incorporates corporate branding with usability lead design decisions
03
Centralized Tools
- Figma – Design system/shared components, wireframing/prototyping
- Storybook – shared UI component library “PEAK UI”
- Microsoft Teams – Communication tool
- Fullstory – Analytics/user experience tool
- Notion – Location of Product Design SOP
04
Communication
- One Centralized Team – Communication with business and work requests come through team leadership
- Microsoft Teams – Multiple channels to organize communications
- Daily Communication – Design team discuss work for the day and any impediments, brainstorm, feedback
- Weekly Design Jams – Team work together on providing feedback and brainstorm ideas on individual designs
05
Lean UX
- Integrate – into agile dev team structure
- Collaborate – with stakeholders and dev in design process
- Quick – put flat mockups in front of team for feedback sooner
- Test – prototypes with users along the process
- Iterate – changes can be made more quickly before they go to development