CaseWorthy UI Refresh

Project Details

Client Work | My Role: Product Manager & UX Designer | Time: 6 Months

Items I delivered

  • Business Requirements
  • Functional Requirements
  • Design Specifications/Documentation
  • Sketches
  • Wireframes
  • High Fidelity Prototypes

Teams I Collaborated with:

  • CaseWorthy Product Team
  • Software Development Team
  • Documentation/Training Team
  • Software Testing Team

Software I used

  • CaseWorthy Internal Application
  • ProductShare
  • Azure
  • Invision
  • Sketch

Meet CaseWorthy

What is CaseWorthy?

CaseWorthy is a true partner with each of their clients. Their dedicated team of analysts, support representatives, account managers and executives have a background in human services and therefore understand the needs of our clients and their communities. CaseWorthy was built around the idea that case management software should support the needs and workflows of the staff and organization rather than dictate how they work.

Click here to go to their website

Understanding the Problem

With the release of the latest CaseWorthy New UI project (Q2 2020), form elements have been exposed as being out dated and lacking the properly functionality and usefulness that they serve to our users. By making changes to their designs, we can give these elements a more modern and refreshed looked in our efforts to continue modernizing the CaseWorthy application.

By addressing form elements, here’s what we aim to achieve:

  • More modern and streamlined approach to match existing redesign efforts
  • More intuitive and responsive feedback loop to how users interact with parts of our system
  • Increased visibility and efficiency
  • Improve areas that can cause eye strain, tiredness, and accessibility issues

This project entails the following:

  • Dashboard Widgets
  • Form Bakgrounds
  • Spreadsheets
  • All Basic Form Elements
  • Various Advanced Form Elements

In total all Dashboards, Forms, Widgets and Spreadsheets were improved, and over 50+ Form Elements were tasked with being redesigned and utilized across three application themes for a more usable and modern approach in the CaseWorthy Application.

User Research

User research is an important aspect to any project, as it helps teams focus on understanding user behaviors, needs, and motiviations. Since this project is focusing on creating and implementing more useful and functional elements that users interact with throughout their day, multiple members, associates, customers participated in user interviews to help me identify and address common issues.

Here is a list of common issues identified:

  • Ambiguous User/System Interaction - users often struggled with understanding how the system would respond to their actions.
  • Accessibility Issues - users with ADA issues experienced constraints with being able to successfully read and identify buttons, icons, and other various functional aspects within the system.
  • Outdated UI - both the buisness and users stressed how parts of their system felt incredibly outdated and inconsistent with other software solutions available on the market.

My Action Items:

  • Ensure that system is implementing a proper feedback look with the user's action, so that users no longer struggle to understand the system's expected output.
  • Accessibility Issues - address and correct many ADA issues thorughout the system, implement documentation and standards that the buisness should follow to ensure ADA compliance in the future.
  • Apply a more modern design to many forms and form elements throughout the CaseWorthy Application.


Sketch was the primary design application tool used to create and implement mockups and high fidelity wireframes for this project.

Documenting requirements in Jira & Collaborating with Others

As the Product Manager and UX Designer for this project, I successfully documentated all of the following:

  • User Stories
  • Functional Requirements
  • Technical Requirements
  • Acceptance Critiera
  • All Design Specification & Mockups

All documentation was contained within a PRD (Product Requirement Documentation) and then broken down into multiple tickets in Azure, and then across multiple teams(Software, Marketing, etc) within the company. Those tickets where then divided up into sprints and were maintained and updated as the development process progressed.

Caseworthy Documentation