I help uncover what's truly broken ... and fix it

I combine a deep technical background in computer science and IT, hands-on experience with electronics, and many years of working with teams. That lets me talk with engineers in the details, while also working with company leadership on strategy, culture, and decision-making. I’ve published my take on these principles on my website .

I’ve held every seat on the technology leadership path, from network architect to CEO. That journey taught me that building software is about building products, not writing code — and that the most expensive mistakes are usually technically elegant solutions that ignore operational reality, customer workflows, or the economics of the business. The job is seeing the entire system, and getting technology, product, people, and execution to pull in the same direction.

I’m not the consultant who arrives with a deck of industry “best practices” and tells you to copy whatever your competitors are doing. Best practices are too often how good companies quietly drift into mediocrity. The teams that endure forge their own structure — and they take the harder, principled path precisely because that’s the one that holds up under pressure.

I think about engineering the way the best businesses think about profit: not as value extracted, but as value created — the surplus of human flourishing  a company leaves behind for its customers, its people, and the world it works in. Architecture, healthy teams, and predictable delivery all serve that. If a shortcut buys a quarter but quietly mortgages the mission, it isn’t a win — and I’ll say so.