About

I’ve spent twenty years working at the intersection of technology, operations, and financial management. Seven of those years were as a controller at a data center engineering firm. All of them have been spent building, fixing, and leading technology for companies that make and move things.

What this means in practice: I've sat in most of the chairs in a mid-market company. I understand how a technology decision ripples through accounting, operations, sales, and manufacturing — because I've been on the receiving end of those ripples. I’ve inherited stalled ERP migrations and gotten them to a workable state. I’ve built disaster recovery plans that actually get tested. I’ve walked into companies where the previous technical staff was gone and critical products were running on systems nobody understood, and brought everything back on track.

I’m not a specialist who sees every problem as a technology problem. I’m an operational thinker who happens to be fluent in technology — and in accounting, process design, vendor management, and the particular kind of patience required to sit with incomplete information until the real picture comes into focus.

I’m based in Minneapolis. I work with companies across the upper Midwest, though geography matters less than it used to.

The people I work with tend to say the same things: that I'm pragmatic, that I don't hide behind jargon, and that I have a useful habit of naming what everyone in the room already knows but hasn't said out loud yet.

I also write about technology leadership, operational design, and the gap between how systems are supposed to work and how they actually work. You can find that here.