After more than ten years in enterprise IT — designing systems, managing teams, navigating compliance requirements, and fighting the same cost battles in different organizations — I’ve accumulated a lot of hard-won opinions.
Not the polished, certification-guide kind. The kind that come from being accountable for a HIPAA audit, from watching a licensing decision turn into a six-figure overspend, from trying to explain to a CFO why the Azure bill doesn’t match the forecast, from being the person whose phone rings when something stops working at 2am.
This blog is where I share those opinions.
What This Blog Is (and Isn’t)
This is a practitioner’s blog. I’m not a vendor advocate, not a conference speaker optimizing for applause, and not a consultant selling frameworks that work great in PowerPoint. I’m someone who has spent the better part of a decade doing this work in healthcare and managed services environments, and I write about what I’ve found to be true in practice.
This is about the intersection of technology and leadership. Cloud architecture isn’t just a technical discipline — it’s an organizational one. The decisions that shape your infrastructure are shaped by budget cycles, compliance requirements, vendor relationships, team capabilities, and executive priorities. I can’t write honestly about cloud architecture without writing about those things too.
This is not vendor-neutral marketing. My background is Microsoft-first — Azure, Microsoft 365, Entra ID, Intune, Defender. I’ll write about what I actually work with, what works, what doesn’t, and when the Microsoft way is the right way versus when it isn’t.
Why Now
I’ve resisted starting a blog for a while. Partly because the internet already has more infrastructure content than anyone can read. Partly because writing takes time I could spend building things.
But I keep finding myself in conversations — with engineers early in their careers, with IT managers navigating their first healthcare compliance audit, with architects trying to make a cost optimization case to leadership — where I wish I had a place to point people. Where I could say: here’s how I’ve thought about this, here’s what worked, here’s what I wish I’d known before we spent three months going in the wrong direction.
This blog is that place.
I’ve spent years operating at the intersection of technical depth and business accountability — owning budgets, driving cost outcomes, making compliance calls, and building teams that outlast any individual. That’s the lens this blog is written from. Writing in public is how I articulate and pressure-test ideas that I’m already living in the work.
What to Expect
I’ll write in six areas where I have genuine, hands-on depth:
Azure Architecture: Entra ID, cold storage design, analytics infrastructure, cost governance, and the architecture decisions that matter in regulated environments. The real trade-offs, not the vendor diagrams.
Microsoft 365: Exchange Online, Teams, SharePoint, Intune, Defender — governance, compliance, and the operational discipline required to run M365 in a way that’s actually secure and auditable.
Healthcare IT & Compliance: HIPAA isn’t a checkbox — it’s an operational posture. I’ve spent six years in a healthcare environment and I’ll write about what compliance actually looks like in practice, what auditors actually look for, and how to build systems that hold up.
IT Leadership: Budget ownership, team development, stakeholder communication, hiring, and the shift from technical expert to operational leader. The skills that matter at the manager and director level are different from the ones that make you a great engineer, and that gap is rarely discussed honestly.
FinOps & Cost Optimization: Cloud cost is one of the most misunderstood problems in enterprise IT. I’ve documented over $127K in savings across licensing audits, environment rationalization, and storage optimization. I’ll share frameworks and tactics that have actually moved the needle.
Security & Identity: Entra ID, Conditional Access, MFA strategy, Fortinet, and zero-trust foundations in environments where compliance requirements make security non-negotiable.
A Note on Perspective
I’m not the most senior person in any room, and I don’t pretend to be. What I am is someone who has owned outcomes — budgets, compliance postures, team performance, cost numbers — and has had to develop both technical depth and operational breadth to do that well.
The perspective here is practitioner to practitioner. If you’re an IT manager, a senior cloud architect, or a technical leader working through the same problems in healthcare or managed services, I think you’ll find something useful.
If this resonates, subscribe via RSS or check back regularly. I write when I have something worth saying.
Let’s get into it.
Discussion
Comments are powered by GitHub Issues via utterances. A GitHub account is required to comment.