Real-Time Integration Management Console
The Real-Time Integration software allows Tuition Management Systems to exchange live data such as payment plan enrollments and payments with partner schools.
I was asked to design a GUI for RTI's configuration and management process to save time onboarding schools, allowing TMS to offer the RTI solution to a wider set of clients.
Background
RTI configuration is a complex process that involves configuring a set of required and optional parameters. There are several different types of connections that can be set up, depending on what information needs to be exchanged, and the process relies on several large and highly relational SQL databases.
The configuration also varies significantly based on whether the school uses Banner, Peoplesoft, or Datatel software to manage its student information.
Challenges
The key challenge of the project--and also what made the project so fun and rewarding for me--was to design a simple and intuitive front end for an extremely complex and technical back-end system.
Moreover, the final software needed to be usable by three user groups--one primary group, one secondary group, and one group of potential future users--all with different roles and widely varying levels of technical expertise, business experience, and familiarity with the RTI system.
To overcome these challenges, I interviewed the various user groups at the start of the project and worked closely with them throughout the project to show them mockups and work-in-progress designs.
I studied the API documentation for the RTI system, familiarized myself with the underlying database schemas, and read extensive documentation to learn how our employees were currently performing school setup. My background in technical consulting and my experience developing database-driven Web sites were very helpful in synthesizing the large bodies of technical information for this project.
Time was another challenge. I was originally asked to attend a meeting or two as a design consultant while I was primarily allocated to a different project. Because I loved the project and felt that additional user experience work would help it succeed, I worked with my manager and both project teams to free enough time in my schedule to continue to work on the RTI project.
I ended up traveling routinely to the Rhode Island office and doing all the HTML, CSS, and JavaScript front-end development for RTI, often during slow periods in my primary project. In the end, both projects released on time.
Design
The original design proposed by the development team closely reflected the underlying database architecture. I felt it would be highly usable to the IT group, the most technical of the target audiences, but less intuitive to the other two groups.
We also considered and rejected a wizard-style approach; while it would be intuitive for new users, it would also be slow for the primary user group, who would be using the software daily.
After analysis and talking to the other user groups, I recommended a new design that incorporated integrated guidance text for less experienced users, with advanced configuration options available to the more technical groups using role-based security.
The final design made extensive use of AJAX-style interactions for an interface that was quick and responsive for the daily users, while also minimizing distractions and allowing room for hint text.
On my recommendation the development team also created extensive default configurations that should work in the majority of cases with a minimum of modification, to minimize setup work and to make the process easier for less experienced users.
We also created a process for copying an existing configuration to make it easier to set up a new school that would be similar to an existing school.
Throughout the project we worked closely with the primary and secondary user groups to design software that would suit their needs and be simple and intuitive to use.
Results
The software released on time and is currently in use for school configuration and management. It has saved significant amounts of time in school configuration and has also greatly reduced the need for IT intervention during school setup.
RTI was one of the most challenging and also most fun projects I've worked on as an interaction designer.
Although I'm very proud of the final product, perhaps the thing that I'm proudest of is that at the end of the project one of the developers said, "I don't know how we've ever done this without someone like you!"
Responsibilities
- Performed initial analysis and research, including interviewing user groups and reading API specifications for the RTI software
- Worked with team of .NET developers under tight deadlines in an Agile development environment
- Created initial design mockups and reviewed designs with users and other stakeholders
- Developed HTML and CSS prototypes for implementation by developers
- Created final visual design
- Wrote all interface copy, including help and hint text
- Developed production JavaScript for rich interactions using Prototype framework
- Assisted developers in implementing and testing final interface
Tools
- Photoshop
- XHTML
- CSS
- JavaScript (including DOM scripting/DHTML)
- Prototype and Scriptaculous libraries
- Firebug
- Firefox Web Developer Toolbar
- Internet Explorer DOM Explorer
