Replacing Legacy Invoicing and Inventory Software with OOUX
Untangling Decades of Complexity
A business running on decades-old invoicing and inventory software had a problem most organizations dread: the system was critical to daily operations, but no one could fully explain how it actually worked. The original developers were long gone, and the software had grown and adapted over the years in ways that had never been properly documented.
Everyone knew it needed to be replaced. But reverse-engineering the old system wouldn't get them where they needed to go—and without understanding what they actually had, scoping a rebuild felt impossible.
THE CHALLENGE
Making the Invisible Visible
To cut through the complexity, I started with an Object-Oriented Sprint—a structured discovery workshop based on Object-Oriented UX, a method for designing systems around the real-world objects users interact with. Over the course of a few weeks, I facilitated remote sessions with the development team, design team, and business stakeholders.
Together, we mapped the system's core objects—things like Clients, Barns, and Invoices—the relationships between them, the actions users could take, and the attributes, or characteristics, that described each object.
Slowly, the fog lifted. A system that had felt like a monolith became something everyone in the room could see clearly and talk about together. By the end the team had a shared understanding of how the system worked, what needed to be in the first version, and how future phases would build on each other.
From Sprint to Multi-Year Rebuild
The object map we created together became a living document that guided the entire project. I maintained and iterated on it throughout the engagement, using it to drive scope, plan phased implementation, and keep the development team aligned as the work evolved over time.
What this meant for the project:
A clear, shared understanding of a system no one could previously explain
A realistic roadmap and scoped budget the team could actually deliver on
A design and development process with far less back-and-forth than a traditional rebuild
Facing a system no one fully understands?
If you're staring down a complex rebuild and need a clear picture of what you're working with before committing to a roadmap, I'd love to help.
Curious about the method itself?
Learn why Object-Oriented UX is the foundation behind every project I take on.