I didn't start in technology. I started on a factory floor.

Before I ever touched an enterprise system, I was working third shift in a manufacturing plant — learning how businesses actually operate from the inside. How decisions made in a boardroom land on the floor. How the gap between leadership's vision and frontline reality is almost always a people problem, a process problem, or both.

That environment taught me something no certification ever could: that technology is only as good as the humans using it and the processes built around it.

From there I moved into business consulting — sitting across from hundreds of company owners, watching what made organizations thrive and where they quietly came apart. Those conversations became the foundation of how I think. The patterns were always the same. When something wasn't working, it traced back to one of four things: the wrong people in the wrong seats, unclear processes, no way to measure success, or decisions being made without understanding the financial impact. That's where the Ironclad Framework was born — not in a classroom, but in the field.

Over the years I moved through roles that most people treat as separate careers. IT operations. Helpdesk and infrastructure. Telecommunications and AV. Vendor management. Global policy and compliance. HRIS. Enterprise architecture. Business applications spanning HR, Finance, payroll, procurement, and FP&A. I've led implementations, survived audits, managed through acquisitions, and built structure in places that had none.

Each role was a different lens on the same fundamental challenge — how do you get an organization's people, systems, and strategy to actually work together?

What I discovered is that the companies who struggled weren't lacking tools. They were lacking alignment. And the companies who thrived weren't necessarily the ones with the biggest budgets — they were the ones who were honest about where they were broken and willing to do the work.

That's what Ironclad is built on. Not a methodology borrowed from a textbook — a philosophy forged across industries, roles, and real situations with real stakes.

I've sat in the IT chair, the HR chair, the Finance chair, and the executive briefing room. That range isn't accidental. It's the whole point. Because when I walk into your organization, I'm not looking at your systems — I'm looking at your business. And my only measure of success is whether I leave it better than I found it.