Thomson Reuters Invoice Tracking with User Feedback

The new design for the eBH Tracking Invoice module prototype was presented to several firms on the TR User Board of volunteers. The results of the test highlighted some concerns of missing functionality as well as opportunities for development. After reporting out the feedback and speaking with development, I incorporated a large majority of the user feedback into a new prototype. The new prototype is slated to be tested in August with users from 6 firms.

overview

The eBH Tracking module was tested with a number of firms and various users utlizing a prototype with a set "happy paths" within it. As reported out, the users provided feedback on a variety of opportunities to make the functionality more usable for their needs, as well as opportunities for further enhancements.

step 1 - identify the issues

  • Users need the tracking note capability: Return the Tracking # column into the grid and display its notes at the top level.

  • Users need to see the headers of the grids as they scroll: make all headers of the grids sticky so that they remain at the top as the user scrolls .

  • Users need the capability to turn on and off columns within the grid: find an opportunity to incorporate functionality to turn on and off their views within the UI.

  • Allow the User to save their column view once they have established a preference. Find opportunities either within these screens or within the users the profile to allow them to set up one or more custom views that they can select in some fashion. At the minimum, allow users the ability to retain the last organized view upon returning to the Tracking feature.

resulting revised prototype design

The revised prototype incorporates many of the features that the users suggested or identified as problem areas. I discussed options with development, and they determined that the saving of column views, or adding settings to the Profile or Tracking pages to allow for this would be too much of a schedule and resource burden for the initial launch. However, the development team agreed that the opportunity to turn on and off columns could be developed for the initial launch and has been incorporated into the design (as shown below).

Because the column customization view does not need to be seen at all times and would take up a considerable amount of real estate at the top, I decided to put it in a slidetray that could be expanded when needed and collapsed when column views have been determined by the user.

 

Not only does this design provide opportunities for hiding/displaying this information, but it also allows for more room to add more customization opportunities in future development.