Work

Stretto · Q4 2024–Q1 2026

Best Case Desktop Version 29

Modernizing a mission-critical legacy platform without competing with the cloud roadmap.

The first major Best Case Desktop release in more than five years, delivering 14 research-informed improvements to a platform serving the majority of Stretto's bankruptcy-software customers.

Client
Stretto
Year
Q4 2024–Q1 2026
Role
Principal Product Designer, Design Lead
Scope
UX Strategy, Research, Product Design, Release Strategy, Go-to-Market
Team
Product Design, Product, Engineering, QA, Support, Marketing, Legal
Disciplines
Product Design
  • 14UXR-informed improvements
  • 75%Active customer firms
  • 85%Product portfolio revenue
  • 22%Fewer credit-report reorder support calls

Best Case Desktop hadn't had a major release in more than five years. It still served roughly 75% of Stretto's bankruptcy-software firms and represented about 85% of product revenue, even as the company invested in Best Case Cloud. So this was more complicated than giving the old desktop software a facelift. We needed to solve problems for people using it every day without making the eventual move to Cloud less appealing. I'd already established a recurring UX survey combining UMUX-Lite, feature-specific questions, and invitations for follow-up interviews. More than 200 customer responses, AI-assisted qualitative synthesis, and follow-up interviews helped turn that feedback into a research-backed release strategy rather than a collection of unrelated feature requests.

One of the more interesting parts was figuring out how much we could improve a Clarion desktop interface without rewriting the thing. Working with a developer, I explored a third-party theming plug-in and found we could customize far more of it than initially expected. That opened the door to new light and dark themes, scalable type, and a substantial icon refresh while keeping familiar workflows intact. I personally led the design of 12 of the release's 14 improvements, with two other designers supporting the remaining work. We also improved self-service renewal, credit-report reordering, and several everyday case-management tasks.

There wasn't a dedicated project manager, so my role extended into coordinating reviews, QA planning, shifting release scope, and the customer-facing launch. Six months after release, support reported that calls related to credit-report reordering were down 22% compared with the prior annual average. That's a meaningful signal, though not proof the redesign alone caused the change. Looking back, I'd still give the supporting designers more ownership of presenting and defending their work. That is one part of leading a project I would handle differently.