Case history for legal software

Case history for legal software

My Role

User research, design & prototype

Team

1x PM and 2x devs

Tools

Figma

OVERVIEW

More context and faster case overview

More context and faster case overview

Case history is a crucial section of a legal case, keeping track of everything that has happened. Our main goal was to create a more responsive layout with improved hierarchy and scanability. This way we can enable users to understand the case faster and speed up their workflow and with it increase their case completion rate.

PROBLEM

Case clarity takes too long

Case clarity takes too long

MVP version for case history was a standard table with only hierarchy decided by column order, this increased time it took for users to understand and read what happened in the case. Over time the table kept growing until users started having issues seeing all the necessary information.

Iteration and user testing

We held weekly user interviews to gather feedback and include users in the iterative process.

Research

We gathered requirements from every team that uses the software and benchmarked comparable designs to identify best practices.

SOLUTION

A clear hierarchy that reduces cognitive latency

A clear hierarchy that reduces cognitive latency

We replaced the table with a stacked list. From our research we knew lawyers need to most often see the last 10 to 20 actions for context, so this was our focus. We have already received positive feedback from our users on the redesign, however further testing is needed.

REFLECTION

Iterating piece by piece

Iterating piece by piece

Case history was only one part of a bigger re-design project. This increased the difficulty of our process, since there were so many different moving pieces that needed to be considered.

hello@anjaferjancic.com

Anja Ferjančič © 2026

Enter password to view case study (check CV for password)