1 / 33

Building Seamless UX with Springhare Solutions

Building Seamless UX with Springhare Solutions. Using User Experience (UX) Design To Elegantly Integrate LibCal With Your Own Systems. J. Robert Van Pelt and John and Ruanne Opie Library Michigan Technological University. Randy Harrison. Mies Martin. The Challenge.

syshe
Download Presentation

Building Seamless UX with Springhare Solutions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Building Seamless UX with Springhare Solutions Using User Experience (UX) Design To Elegantly Integrate LibCal With Your Own Systems J. Robert Van Pelt and John and Ruanne Opie Library Michigan Technological University Randy Harrison Mies Martin

  2. The Challenge • Libraries are struggling with how best to move toward the digital/mobile/cloud • With the complexity of information management, organizations rely on turnkey solutions • If it’s important to design our systems with our users in mind, and every context is different… • How can we implement turnkey solutions while still foregrounding rich user experience / interaction?

  3. Turnkey solution Digital application or suite of applications built by a third party and adopted (usually purchased) for its ready integration into extant business systems and workflows. Turnkey solutions represent a trade off between the powerful functionality they offer (prohibitive to develop in house), and their ability to fully address the needs of an impossibly wide range of users

  4. Turnkey (Out of the Box) No branding No clear navigation Interface is cluttered and kind of a usability nightmare out of the box

  5. Turnkey (minimal customization) Some branding Unclear navigation Interface is cluttered and still a usability nightmare out of the box

  6. Turnkey + UX

  7. The key to design project mgmt What the Stakeholders Believe Users Need What the Project Leader Understood What the Programmer Built

  8. …communication and flexibility Adapted from: Kelly Goto’sWeb ReDesign 2.0: Workflow That Works How the Project was Documented How the Project was Supported What the User Really Needed

  9. Agile UX + Turnkey • Why UX Design principles and conducting usability testing are crucial to any [re/]design—especially for implementing a turnkey solution, and from the beginning • How to use an agile framework for project management to work quickly and efficiently • How we applied Agile/UX in our own implementation of the LibCal system

  10. The Agile Manifesto Source: agilemanifesto.org Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan

  11. Agile Framework Core Principles: Iterative and incremental design—rapid prototyping, constant user and designer testing Project Plan as a living document—doc-sharing to assess the project in real-time (butavoid scope creep) and adjust course where necessary Small-team, close-collaboration--flatten those asymmetrical relations of power and open multiple avenues of realtime communication

  12. Project Plan Share your project plan Continually add/change/revise your plan Project Plan is the place to capture all your changes

  13. DUX Team

  14. Overlapping Skillsets Management Skills Coding/ Programming UX Design Usability Testing Graphic Design Library Systems Knowledge

  15. UX Design The best UX come from user interfaces which: Are consistent in both form and function Are easy to understand, learn, remember Provide feedback to the user and allow the user to provide feedback to the system Are aimed at helping the user accomplish his/her goals—not ‘use an interface’

  16. Rapid Prototyping Brainstorm a very low-fidelity wireframe Arrange the functions your users need in a general layout

  17. Rapid Prototyping Build a low-fidelity mockup Do NOT perfect the design… Do your best work and then leverage users to help you improve it

  18. Rapid Prototyping Your final design is GOING to look different It is also likely to be better if you let users help you

  19. LibCal Instructions—1st Iteration

  20. Usability Testing—Do this early! • You are part of a group of 5 chemistry students. Your group needs a study room in the library and you have been asked to book it because you told the group you remembered seeing a university announcement that students could book their own study rooms. Book an appropriate study room for 5 hours on August 30th. • You’ve run into some problem with booking the room. Contact someone for help. • Jaspreet, from your Chemistry study group, needs to practice a presentation for the group on a large monitor. Book the best room available for this. • Now that you’ve booked a room, you realize you made a mistake with the times. Rebook the room moving the time back 2 hours (e.g., from 4pm to 6pm).

  21. LibCal Instructions Mockup

  22. Still not done (HINT: you’re never done!)

  23. More tips for UX Design What follows are a number of ways we improved our initial LibCal Room Booking system to better serve audience needs

  24. Provide a Clear Feedback Mechanism

  25. Provide Clear Calls to Action

  26. Simple Action Verbs

  27. Create Your Own Menus

  28. Wayfinding/ Paths to Success Make help easily accessible Always provide multiple paths to success

  29. Continual Assessment

  30. Leverage Conditional Logic 1. From the Dashboard menu, navigate as follows: Admin Stuff > Look &Feel > {choose tab: System-wide Settings} 2. In the “Custom JS/CSS Code” box, add this css: <style type=“text/css”> .public_pagediv#footer { display: none; } </style>

  31. Takeaways Work in small teams with flattened hierarchies Work in parallel, not in isolation Try things out and have an exit strategy if they fail Don’t get stymied by your own tools—The point is to develop a product, not master a tool

  32. Takeaways You are not your users—listen to (and more importantly) watch your users use your website Don’t make your users think (too much) Create ways to listen to users—Feedback buttons and forms, periodic assessment Prototype—build a good first iteration and leverage users to help you perfect it

  33. Resources Additional Resources (books and web) http://bit.ly/additional_resources Mies Martin miesmart@mtu.edu Randy Harrison rsharris@mtu.edu

More Related