End-to-end platform design for a global law firm's internal know-how system
Lawyers across the firm needed fast, reliable access to precedent and internal expertise, but every new platform request went through weeks of unstructured back-and-forth between users and developers before anything got built. I owned this platform end-to-end: defining what it needed to do, delivering developer-ready requirements, testing the resulting builds with real users, and signing off on final design.
Product design & development
Figma · HighQ · SharePoint
March 2025
enterprise SaaS
B2B
knowledge management
design systems
I ran discovery sessions with lawyers and business teams to understand how they actually searched for and used internal know-how – what they needed to find, how fast, and why existing tools failed them.
The pattern that emerged wasn't a UI problem. Teams generally knew what they wanted, but there was no shared language to translate that need into something a developer could build – every project restarted this translation from zero, costing weeks per request.
I designed the interactive know-how database from concept through shipped interface – structuring information architecture around how lawyers actually searched (by matter type and practice area, not internal filing logic), then prototyping and testing navigation and search patterns directly with end users before finalizing the design.
The bigger structural fix sat upstream of any single interface: I built a standardized requirements framework that translated business need into developer-ready specification in a single, repeatable pass – effectively a lightweight design system for how any team scopes a new build.
Average project turnaround, before and after the requirements framework was introduced:
reduction in project turnaround time
standard adopted beyond the original project
through direct usability testing, not assumed requirements
previous
next
.svg){kind=icon}
© Agata Czerniak 2026
