About

This isn't a repeat of my resume. It's the why behind it — why operations, why leadership, and what I actually believe makes a company scalable.

I got into operations because I liked the kind of problem where the answer isn't obvious and the stakes are real — how do you keep a company's promises to its customers as it triples in size? I stayed in leadership because I found out I liked building people more than I liked building processes; the processes are just how you prove you trust your team to run without you standing over their shoulder. What motivates me now is the same thing that motivated me at Intermap twenty years ago: taking something chaotic and giving it a shape that holds.

Clarity over control

Hover to read

A dashboard doesn't run a company — a decision made confidently, at the right level, at the right time, does. I build KPI systems and executive reporting not to police performance, but to give the people closest to the work the clarity to act without waiting on me.

Systems outlast heroics

Hover to read

Anyone can save a bad quarter through sheer effort once. Doing it every quarter is a system problem in disguise. Rolling out Lean principles and ISO 9001 across eight international offices wasn't a compliance exercise — it was building a company that performs the same way whether or not I'm in the room.

Accountability without micromanagement

Hover to read

The teams I build know their numbers, own their numbers, and don't need me checking in to hit them. That only works if accountability is built into the system — clear metrics, clear ownership — instead of enforced by me personally. Micromanagement is what happens when that system is missing.

Global doesn't mean generic

Hover to read

I've built and led operations across the U.S., Canada, Germany, Czechia, India, Indonesia, Malaysia, and Thailand. The lesson that never stopped being true: a process that works in Denver doesn't automatically work in Bangalore. Standardize the outcomes you need. Stay humble about the path to get there.

Technology should remove friction, not add reporting

Hover to read

I'm deep into AI-enabled workflow automation right now, and the test I hold every tool to is simple: does this give someone their time back, or does it just generate another dashboard nobody asked for?

Experience

Not paragraphs about what I was responsible for. Proof of what actually happened — and the case studies behind the headline numbers.

Global operations footprint

8 COUNTRIES · 3 CONTINENTS

Built and led operations across the USA, Canada, Germany, Czechia, India, Indonesia, Malaysia, and Thailand.

Insights

Short takes from 25 years of scaling teams, systems, and myself along the way.

KPI Governance

Why KPIs fail

Hover to read

Why KPIs fail

Almost never because the metric was wrong. They fail because the instinct with any new KPI system is to use it to grade people. Resist that. The dashboards I build are meant to show a team the truth about their own operation — faster than they'd find it themselves — so they can fix it before it becomes a crisis. The moment a metric becomes a weapon, people stop trusting the data, and you're flying blind with extra steps.

AI & Automation

AI will not replace great operations leaders

Hover to read

AI will not replace great operations leaders

Every AI workflow tool I champion gets judged by one question: does this give someone their time back? Not "does it look impressive in a demo." The highest-leverage automation I've implemented is the kind nobody notices — it quietly removes the reporting, reconciling, and status-chasing that used to eat a manager's week. That frees leaders up to lead, which is the part AI still can't do.

First 90 Days

The first 90 days as an operations executive

Hover to read

The first 90 days as an operations executive

Growing an office from one person to fifty in ninety days exposed every weak assumption in my operating model almost immediately — there's no time for slow feedback loops. What I took from that wasn't a playbook for speed; it was a sharper sense of which three or four things actually matter in the first week of any new operation, and which can wait.

Lean & Process

Lean is a leadership philosophy, not a toolkit

Hover to read

Lean is a leadership philosophy, not a toolkit

Most Lean rollouts fail because they're treated as a toolkit — value stream maps, kaizen events, a binder of new procedures. The ones that stick start as a mindset shift: everyone on the team owns waste, not just the process owner. Rolling out ISO 9001 across eight offices only worked because we sold the thinking first and the documentation second.

Connect

If you're scaling an operation, wrestling with a KPI system nobody trusts, or trying to figure out where AI actually belongs in your workflow — I'd like to hear about it. Open to select executive engagements, advisory work, and honestly, just a good conversation about operations.