Examples of operational systems I’ve built, stabilized, or maintained to help legal teams gain visibility, reduce friction, and sustain adoption over time.
A lot of my work begins the same way: a workflow is no longer serving a team’s needs, and they need a fresh set of eyes to review and improve it.
I step into those situations to understand how the work is happening today, identify where things are breaking down, and build the structure needed to support it. Sometimes that means designing a new system. Sometimes it means stabilizing an existing one.
“Chaos wrangler” is a joke, but only partly.
Repeatable infrastructure built to support recurring workflows, connected tracking, and sustainable operational visibility.
Problem: The pro bono team manages 50 to 60 clinics per year, each requiring registration, participant tracking, MCLE coordination, and logistics setup.
System: Built a repeatable workflow that provisions the operational structure for each clinic, including registration tracking, participant information, and reporting views.
Impact: Saved hours of administrative work and standardized setup across dozens of annual clinics.
Problem: Tools supporting knowledge and innovation, library, and some practice management functions were tracked across separate records and systems, making it difficult to understand relationships between products, contracts, and budgets.
System: Designed a connected ecosystem using unique product identifiers to track products, contracts, and budgets independently or holistically while preserving historical data.
Impact: Created a more unified view of the department’s technology environment and vendor spend over time.
Systems designed to improve oversight, reduce waste, and make operational information easier to manage at scale.
Problem: Thousands of litigation, patent, and news alerts needed oversight to avoid unnecessary spend, outdated subscriptions, and unclear ownership.
System: Built a governance tracker and self-service interface allowing attorneys to request cancellations, modifications, or visibility into who else receives the same alerts, with requests routed to the library team.
Impact: Improved subscription governance and reduced friction in maintaining alert coverage.
Problem: As platform usage expanded, the firm needed stronger standards around ownership, retention, and sustainable usage.
System: Supported governance, training, and platform adoption for 300+ licensed users across practice groups and departments.
Impact: Helped scale usage while encouraging more consistent data management practices.
Recovery and coordination systems built to bring structure, momentum, and accountability to difficult rollouts.
Problem: A documentation automation rollout went poorly, ownership was unclear during a firm reorganization, and the implementation lacked structure and accountability.
System: Built a centralized dashboard and supporting trackers to coordinate stakeholders, monitor issues, manage QA, and keep vendor responses moving.
Impact: Helped rein in a chaotic rollout, restore working relationships, and regain control of the implementation process.
Systems that support transaction visibility, workload awareness, and practice insight without exposing sensitive information.
Context: A centralized tracker used to monitor active and completed corporate transactions, participation across seniority levels, and capacity signals such as associate workload.
Role: Took over technical stewardship of an unstable system, improved reliability, supported integrations with internal financial systems, and created 90+ slides of documentation for users ranging from novice to experienced.
Impact: Technical issues are now rare, and the platform continues to support operational insight into transaction flow and staffing.
Information architecture work that connects tools, documents, and guidance into more usable internal resource environments.
Problem: Internal guidance, tool information, and practice resources often lived across multiple systems and were difficult to locate quickly.
System: Maintain and build intranet pages for departments and practice groups, resurfacing organized data from the DMS, introducing pages for new tools, and refining existing content to improve usability.
Impact: Improved discoverability of internal resources and made operational knowledge easier for teams to access and maintain.
Problem: Users needed a clearer way to navigate document resources connected across systems rather than hunting through isolated repositories.
System: Helped shape a document library experience connected to the DMS, Smartsheet, and a UI layer, with an emphasis on structure, visibility, and cleaner inputs.
Impact: Improved the usability of document-related resources and supported a more organized internal knowledge experience.