Systemic IT Consulting is built on two decades of hands-on IT systems work and a genuine belief that the way we think about technology determines how well it serves us.
With over 20 years in IT systems engineering, I've had the opportunity to build, support, and optimize the technology that powers real businesses — from small teams to large, complex organizations. That breadth of experience has given me a ground-level understanding of what actually breaks, what actually scales, and what actually makes teams more effective.
My background spans infrastructure, identity and access management, business process analysis, integration architecture, and organizational systems design. I've worked across industries and org sizes, which means I bring pattern recognition — and healthy skepticism for one-size-fits-all solutions.
I founded Systemic IT Consulting to offer the kind of engaged, thoughtful consulting I wished was more available when I was on the other side of the table: a partner who understands the technology deeply but never loses sight of the business it's meant to serve.
End-to-end experience across infrastructure, identity, integration, and business systems in diverse organizational environments.
Technical depth across hardware, software, IAM, automation, process design, and organizational systems — all connected by a systems-first perspective.
Comfortable working in fast-moving organizations as well as mature enterprise environments — each with their own constraints and opportunities.
Consulting informed by real-world implementation experience — not just strategic recommendations, but the knowledge of what it takes to execute them.
The name Systemic IT Consulting isn't just branding — it reflects a genuine conviction about how technology problems should be approached. Systemic thinking means understanding that every component of an organization's technology exists within a web of relationships: with other tools, with processes, with people, and with the business goals those systems are meant to serve.
Most IT problems aren't actually technology problems. They're design problems — cases where a system was built without fully understanding how it would interact with everything around it. Fixing them at the surface creates more complexity. Fixing them at the root changes things for good.
"You can't understand a system by looking at its parts in isolation. You have to look at how they relate — and what happens when you change one of them."
No two organizations are the same. Every engagement starts with listening and observation — mapping what actually exists before proposing what should exist.
Solutions are evaluated not just on whether they solve the immediate problem, but on how they fit within — and strengthen — the larger system.
A system that works on day one but can't be maintained, scaled, or transferred isn't a success. Sustainability is part of the design.
The measure of any technology system is whether it helps the business accomplish its goals — not whether it's elegant, novel, or technically impressive.