Improving the UX of your Design System
As part of his work at Zeroheight, contributing UX Booth writer Luke Murphy has been talking to teams across the world about what makes good documentation sites, from small 2-3 designer companies through to large enterprises corporations. The common thread across the successful design systems is that the team managing the design system are treating their system as if it’s a product, complete with KPIs and ways to measure, a full product design process and enough resource to achieve their goals. Unfortunately, this doesn’t mean that anyone can provide a standard template for how to build an effective Design System, as the problems, needs and measures of success for any single design system will be different. However, there are some standard processes and common wins that can help.
Build Better Requirements Documentation: Why, Who, and How
Great products are built from great plans. They require research, a comprehensive strategy, and roadmap. Defined and documented requirements are a key part of the process for the development of a new or complex system. To ensure the product meets users’ needs, it needs to be understood, captured, and agreed upon. Knowing what is required and communicating it in a clear way is a critical part of any new project.