About

I'm Matthew Gullicksrud, a technologist who spends most of his time on the part of technology nobody puts in the demo: getting people to actually use it.

I've watched a lot of good tools fail. Not because the software was broken, and not because the business case was weak, but because the tool never became part of how the work gets done. It sat in a tab nobody opened. It produced a report nobody read. It answered a question at the wrong moment, for the wrong person, with data nobody trusted.

That gap between "it works" and "it's working" is where I have spent my career.

Where I come from

I started my career in healthcare, where I learned that a perfect clinical guideline means nothing if it doesn't reach the right clinician at the point of care. Then I moved into development and permitting, and found the same problem wearing a hard hat. Different industry, same physics: complex systems, high stakes, lots of handoffs, and a public that just wants a clear answer.

My path has run through nearly every side of the table: consulting, then sales and product roles at two of the largest health IT companies, then a healthcare AI startup, and now local government. Each stop taught me something different about what it takes to get technology adopted, from selling it, to building it, to scaling it fast, to rolling it out where the stakes are public.

Today my work sits where business problems meet technical solutions: data engineering, reporting, platform administration, product ownership, and lately, putting AI agents into real public-sector workflows. I'm comfortable with discussing techincal architecture while laying out the ROI with the business owner, and I think the best work happens when someone can translate between the two.

What I'll try to share here

Long-form essays, organized into series, on:

• Why technology adoption is a people problem first
• How I use my experiene to cross industries
• Putting AI in play, beyond the pilot
• Where are we heading over the next five years
• Ramblings that may or may not end up related to all of the above

I will try to share the way I think I talk: direct, specific, and with as little jargon as I can get away with.

Outside of work

I live in Denver with my partner, our kid, and our dog. When I'm not writing about workflows, I'm usually in the wood shop, under the hood of an old truck, or building something on a Raspberry Pi that probably didn't need to be automated.

Get in touch

The best way to reach me is on LinkedIn. If something here resonates, or you think I've got it wrong, I'd like to hear about it.

Views are my own and do not represent any current or previous employer.