Like most people working in DriveWorks, my early projects were about getting something working. They did work, but as those systems grew, I started to see which decisions held up and which ones made future changes harder. Logic spread across multiple places, models took on responsibilities they weren’t designed for, and rules existed because they seemed reasonable at the time, not because they were clearly defined.

DriveWorks doesn’t make judgment calls. It just executes what it’s given. If decisions aren’t made up front and put in the right place, automation still works, but the system becomes hard to maintain.

Design Minds Consulting was created around that way of thinking. I work with organizations implementing new DriveWorks systems, extending existing ones, or bringing structure to implementations that have grown organically. The goal is to build a foundation that can support change as products evolve, pricing updates, and teams grow.

Sometimes that work happens alongside internal engineering teams. Other times it means leading the effort until clarity and ownership are in place. In every case, the objective is the same. A DriveWorks system that’s understandable, maintainable, and able to grow without constant rework.

When an implementation is successful, the impact isn’t dramatic on day one. It shows up over time. Fewer interruptions to engineering, more predictable quoting, and the ability to add new products without revisiting old decisions.