In the higher education field, we’re often asked to create institutional skins or themes for software to ensure the institutional logo, branding, and colors are added to a vendor’s product. When working with open source projects, however, we have the unique opportunity to contribute back to the larger online community with our efforts.
When my institution moved from the learning management system Blackboard to Sakai, we created a basic skin but we also conducted a series of usability tests. This was the first time we had undertaken any user testing, and we observed a great number of usability issues. We had a number of ideas on how to resolve these issues, but we weren’t quite sure where to start or how to get the buy-in necessary to resolve them.
In this session, we will discuss strategies on dividing usability issues into quick wins and long-term fixes. We’ll cover creating a new modular UI from the ground up, creating a style guide and a design pattern library for developers, and how we can then contribute these efforts back to the community. Most challenging of all, we’ll tackle how to bring innovation to a risk-averse culture by successfully changing the UI without alienating users.
What You'll Learn:
- How to conduct usability tests
- How to communicate the results of the tests to generate excitement and commitment to fixing issues
- How to divide solutions into quick wins and long-term fixes
- The best way to organize chaos and build a foundation via a style guide and a design pattern library for developers
- How to use modular design to create a sophisticated and highly customizable skin
- How you can contribute to an open source community and share your efforts
- How to get buy-in from the multitude of stakeholders, committees, and service teams without going insane
- How to bring innovation to a risk-averse IT culture without compromising the design