TRIALKIT
B2B Legal-Tech Platform for Case Management
TrialKit is an AI-powered workspace that helps defense attorneys organize, review, and search case materials efficiently.
Team
CTO, PM, Developers, Lawyers
TIMELINE
May 2025- October 2025
Responsibility
Covered a six-month maternity leave implementing new features and refining existing UI while proactively improving usability and clarity through thoughtful hierarchy, component, and library updates.
design system
Product design
UI design
Prototyping
Handoff
While integrating new features into an active product, I also focused on strengthening the system’s visual hierarchy and structural clarity.
Each task became an opportunity to refine the platform’s consistency and usability without interrupting ongoing development.
#1
Limited Context Visibility in the AI Panel
"When I’m reviewing a document, I want to see the file description right away - I don’t want to click into another tab just to understand what it’s about."
What I Noticed
The information panel opened on the Entities tab, while the file description - the most important context - was hidden under Details.
The overall layout was also hard to scan, making it difficult to quickly understand key information.
WHAT I DID
I made the 'file description' persistently visible at the top of the panel and turned 'Entities' and 'Details' into a toggle bar positioned right below it.
I also reorganized the information structure to improve hierarchy and scanability, helping users read and refine AI insights more easily.
IMPACT
Improved clarity and reduced cognitive load during document review, allowing attorneys to focus on the content rather than navigating the interface.
#2
Users reviewing legal case files struggled
to move between documents.
"When I’m inside a document, I want to open other files in the same batch without losing my place."
What I Noticed
The top panel communicates system location. Showing the file name there mixed two separate hierarchies - system and file.
Users had no visual clue where the current file sits within the case.
The current navigation (on the bottom) behaved like paging within a file, not browsing across documents.
WHAT I DID
I separated the system and file hierarchies by adding a second breadcrumb layer below the top panel, and moved the page navigation controls there.
I also explored two design directions with different levels of complexity:
Option 1 – Scrollable Inline Thread (Short-Term Solution)
A lightweight approach that adds a scrollable thread above the document viewer.
It allows quick access to adjacent files without leaving the current view — fast to implement and ideal for early release.
Option 2 – Collapsible Side Panel (Long-Term Solution)
A more robust solution that expands a file hierarchy panel next to the sidebar.
It provides a clear overview of all related documents and supports future capabilities like sorting, filtering, and drag & drop.
#3
Building the Timeline Feature Under Tight Schedule
"We needed to ship the first version fast, using a pre-defined code base without a full UX phase."
Focused on clarity, hierarchy, and visual consistency while preparing developer-ready layouts and interaction specs for a smooth handoff.
