A Design System for More Efficient Production
Pattern libraries help to keep everyone on the same page with quick visual confirmation of how elements and components should look and behave.
Senior development staff and I worked on defining and creating front-end controls that improved the speed at which developers could develop new features.
Waterfall development made for costly revisions. By introducing LEAN UX principles and low-fi or quasi-functional prototyping, we were able to learn and iterate sooner.
I worked with a talented team of developers and designers, all focused on improving the application and the end user experience.
Once I was able to assess the problems the company faced, I then had to explain to the business and other IT heads how UX fit into the organization and how they would benefit from it.
I conducted interviews with BA's, Devs and QA's to better understand their issues. Once I had a strategy together, I was able to quickly produce wireframes and lo-fi prototypes to validate, learn and iterate quickly.
Once we had made iterations from wireframes and lo-fi designs, we began prototyping hi-fidelity versions and process walk-throughs to further refine our concepts.
Not everyone is familiar with a design system, so education was important to user adoption and business buy-in.
From login, to policy creation, everything needed to adhere to the new UI standards, user-centered design process and behavior. The details mattered.
Building a pattern library helped shape the design direction. I've found its one of the best places to figure out what works and doesn't work together visually, sooner.
BA's, Dev and QA's all had one guide to follow and adhere to. Teams could focus on solving user problems, rather than communication issues.
Teams that are on the same page work more efficiently, reducing the cost and resources required for rework, kickbacks and inconsistencies.
Both the business and agent users benefited from the team's new efficiency, as more time was spent on innovation and improvement, rather than fixing inconsistencies.
© 2017 Shane Close