These rules eliminate rework, inconsistent output, and subjective quality debates.
Design Standards
All design work must meet:
- Brand consistency
- Proper spacing / hierarchy / layout standards
- Mobile-first considerations
- Proper file prep for dev
- Component-based structures
- Figma organized, named, grouped
- Accessibility best practices
The Project Lead reviews all design work before client delivery.
Development Standards
All dev work must meet:
- Clean, readable code
- Follows internal standards/frameworks
- Responsive across breakpoints
- Cross-browser tested
- WCAG accessibility awareness
- Minimal external dependencies
- Documentation for complex logic
- Version-controlled commits
For the full developer best practices and standards, see the factor1 github wiki
Copy Standards
Copy must be:
- Clear, concise, and client-appropriate
- Follows StoryBrand and brand voice guidelines
- Free of jargon unless required
- Runs through Grammarly at minimum
- Reviewed by PM or Lead for accuracy
QA Checklist
Before launch or delivery:
- Functionality tested
- Forms, payments, logins tested
- Error handling verified
- Mobile and desktop QA
- Cross-browser testing
- Page speed checked for major issues
- Accessibility scanned
- Metadata and SEO basics implemented
Pre-Launch Checklist
Before any go-live:
- All QA passed
- PM approved
- Team Lead approved
- Rollback plan documented
- Access credentials verified
- Backups completed
Post-Launch Checklist
Within 48 hours of launch:
- Monitor uptime
- Check analytics
- Confirm client has access/logins
- Document the final build
- Add to retainer backlog (if ongoing)
- Schedule post-launch review