Zelly Update: One month in

It is important to provide staff communications on Zelly, since it is the largest technological and process change at the agency in over a decade.

Purpose of this post: Let you know what we have heard and done in the past month, and what we plan to do in the near future. This is a long email. If you want to skip the history of what we have done, see “What’s in the future.”

First, a “thank you” to all the staff who demonstrated patience and provided constructive feedback. We appreciate it. We are working our way through the queue of requests and challenges.

We knew releasing a major initiative affecting all four divisions (plus specialty groups) and replacing three-existing case management systems would have some challenges, and it has.

Currently, we release significant bug fixes / function tweaks 2-3 times per week (in addition to daily tasks like fixing permissions, adding people or revising/building reports). Releases all involve evening and weekend work to reduce disruption to staff from system downtime.

Release notes: Starting Friday, under the Zelly Information icon, you can find a Release Notes link. It lists all changes made. Usually there is a 1-2 days’ delay in posting.

What we’ve heard and done (highlights):

Bugs: Functions or features not working as designed.

  • When notified by staff notify (or we discover them), we prioritize them, then queue them up for fixing and moving to production
  • Missing date of birth for CASEY participants migrated to Zelly

Permission: People unable to access things they need or in the fashion they need (i.e., I can view this, but I also need to edit it).

  • We address these very quickly based on notification. We adjusted score of permissions, added people, created new access groups.

Documents: Documents attached to TRIS/CMS were missing from Zelly.

  • Huge oversight on our part. As of today, all documents from TRIS/CMS should now be in Zelly

Mobile Access: Functionality in mobile access is too limited. For example, mobile Conflict Check didn’t list “Role,” which impaired utility.

  • “Role” was added as a field in mobile Conflict Check

Templates: Incorrect information in templates (addresses, office names, etc.).

  • Corrected as notified

How do I?: Staff unsure how to do something.

  • Provide guidance, direct them to one of the mini-training videos or the User Guide, or add a new training video or section to the User Guide

What’s in the future:

Based on feedback from staff and our own observations, we will (in addition to ongoing fixes) address four key areas: document viewing, document organization, mobile access functionality, performance.

Document viewing: It is hard to view an uploaded document; you must first download and then open it.

  • We’ll work on letting documents open in the browser for viewing.

Document organization: Since all documents are listed in one directory, it can be hard to segregate only the ones you want (e.g., I don’t care about our templates, I just want to find the police report).

  • We’ll find a solution to enable easier filtering out of documents or some more granular system of grouping documents.

Mobile Access: Staff unable to do what they need on a mobile device (similar to mobile Conflict Check example in the previous section).

We are attacking this in two ways

  • We are already tweaking the mobile interface (where feasible) to add more robust mobile functionality, while keeping it simple and legible on a small screen.
  • We’ll introduce a “Desktop Mode” button that will show everything users would see on the desktop by scrolling, pinching, and zooming on their mobile device.

Performance: Page loading and refresh times can be variable and slow.

We have started looking at performance tuning options to increase and make performance more consistent.

Thank you, again, for all the productive feedback.

Please remember to send ideas, and bugs, to [email protected].

Also, remember: do not use Zelly with the Microsoft Internet Explorer browser (you should stop using it for anything).