Overview
Enova International was in need of Design System documentation for UI elements to ease development and consistency issues. The new documentation would be used in training for onboarding new software engineers.
Challenge
Create a design system documentation with limited resources and no additional budget.
Solution
With these restrictions in place, I started researching options for documentation. At Enova, we have an internal Wiki for documentation purposes, but quickly discovered this wasn't a suitable option for hosting and maintaining a design system. While it would be able to hold general documentation, it wouldn't have been able to scale-up in the future to host code documentation.
The ideal solution would have incorporated live code snippets for the back-end users, however, at the time we had limited available Dev resources to work on this project. The process that was created helped provide consistency to the organization with the limited time and resources that were available.
Final Thoughts
While the Adobe XD created Design System does help with providing examples and documentation for software engineers, there are more robust solutions on the market. In the future, I would have worked with the Studios and the CMO to budget a solution that allowed for live components for software engineers, using Storybook and Zeroheight for documentation.
Note: I have since implemented Design Systems using Storybook, Zeroheight, Figma, Adobe XD, and Material UI.
Role: UI Designer
Timeframe: 1 month
Tools: Adobe XD
Team: Self-Driven
Process: Market research, user testing,
accessibility, prototyping, visual design
accessibility, prototyping, visual design
column
