I'm working on a design system and I need to create a budget and scope to produce the…
- User
I'm working on a design system and I need to create a budget and scope to produce the first version of the system. The work will involve creating robust, scalable and flexible Figma components from scratch, translating these into CSS/HTML and Web Components as well as producing design and engineering documentation for each. The scope should consider that accessibility is included, along with QA, and testing. Also, assume that each component will have three variants on average. What would the estimate be in terms of time and resources per component and then multiplied by 22 for the total number of components?
Assistant
For a comprehensive design system with 22 components (3 variants each), here's a realistic breakdown:
Per Component Estimate:
- Design (Figma): 10-12 hours
- Research, base component creation, variants, design reviews
- Development: 20-25 hours
- CSS/HTML implementation, Web Components, responsive behavior
- Accessibility: 6-8 hours
- WCAG compliance, screen reader testing, keyboard navigation, ARIA
- Documentation: 8-10 hours
- Design guidelines, engineering docs, usage examples
- QA & Testing: 8-10 hours
- Cross-browser testing, visual regression, integration testing
- Review & Iteration: 6-8 hours
- Design/code reviews, stakeholder feedback, refinements
Total per component: 58-73 hours (average ~65 hours)
For 22 components: ~1,430 hours
Team Resource Allocation:
- UX/UI Designer: 450-500 hours
- Front-end Developer: 650-700 hours
- QA Engineer: 200-250 hours
- Technical Writer: 150-200 hours
Timeline Considerations:
- With a 3-person core team: 6-8 months
- With a 5-person team: 4-5 months
- Add 20% buffer for project management and unexpected complexity
Additional Factors:
- Initial setup (tooling, standards, infrastructure): +80-120 hours
- Component complexity varies significantly (simple buttons vs. complex data tables)
- Review cycles and stakeholder alignment can extend timelines
- Consider phased delivery to get feedback earlier
This estimate assumes enterprise-grade quality with thorough testing and documentation. Simpler implementations could reduce time by 30-40%.
- Design (Figma): 10-12 hours
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.