Architecture is a business discipline that happens to use technology

I am a senior enterprise technology professional with more than twenty years of experience across enterprise architecture, cybersecurity, networking, data centers, cloud platforms, Microsoft technologies, and technical program leadership. I am based in Houston, Texas, and work with organizations that need complex technology decisions made carefully — and then delivered.

My work sits at the intersection of three disciplines that are usually staffed separately: architecture, security, and delivery. Organizations bring me in when a problem spans all three — a data center that has to move without breaking a regulated business, a security model that has to change without stopping the workforce, a cloud estate that has to be governed without strangling the teams who use it.

I came up through the infrastructure ranks: network engineering, data center operations, and the unglamorous work of keeping enterprise environments running. That foundation still shapes how I design — I have been the person paged at 2 a.m. by an architecture that looked elegant on paper, and I design so that someone else will not be.

Consulting years followed, leading network, data center, and security engagements across multiple industries. Consulting teaches a specific skill: walking into an unfamiliar environment, finding what actually matters, and earning the trust to change it. The certifications that anchor my practice — two CCIEs, CISSP, CCSP, CISM, PMP, and the Microsoft expert tracks — were earned alongside that delivery work, not instead of it.

Today my focus is enterprise and security architecture: translating business requirements into target states, governing large programs, and helping organizations adopt cloud and AI platforms with discipline. The details of specific roles and engagements are on the experience page.

Business first. An architecture is good when it serves the organization’s strategy, risk appetite, and budget — not when it uses the newest platform. I start every engagement with the business problem, and I am comfortable recommending less technology when less is what the problem needs.

Security is a property, not a department. Identity, segmentation, data protection, and monitoring belong inside the design from the first whiteboard. Security reviewed in at the end is security bolted on — more expensive and less effective.

Operations are the customer of the design. Every architecture is eventually judged by the team that runs it at scale, under pressure, with turnover. Designs that require heroics are failed designs, however clever.

Decisions deserve records. I write down the options, the trade-offs, and the reasons. Institutional memory is an architectural deliverable, and “why did we do it this way?” should always have an answer.

Much of my career has been spent in and around regulated financial services environments, where change control is real, auditors are frequent visitors, and availability is a contractual promise. I have also worked extensively with managed service providers, mid-sized enterprises, and organizations mid-transformation — moving to cloud, consolidating data centers, or rebuilding security programs.

The common thread is complexity plus consequence: environments where mistakes are expensive and “just rebuild it” is not an option.

I am a Microsoft Certified Trainer and have spent years teaching — formally in instructor-led training, and informally in every engagement, because an architecture the team cannot explain is one they cannot defend. I publish research and professional writing on cybersecurity and enterprise technology; my academic work is indexed on Google Scholar (opens in a new tab), and the Insights section of this site carries my ongoing writing.

Right now, the most interesting problems on my desk involve AI security and governance: helping organizations adopt AI services with the same architectural discipline they finally learned to apply to cloud. Alongside that, the perennial work continues — Zero Trust programs that need to reach production, landing zones that need governing, and networks that need to be modernized without anyone noticing.

If your organization is facing decisions like these, I would be glad to talk.