Selected Work

I listen. I ask why. Then I build.

I'm a builder who listens first. I see broken processes, I go toward the people, and I find the real problem underneath the one they described. Then I build the fix, sometimes enterprise-scale, sometimes a Python script. The domain changes. The approach doesn't.

Listen

Before I touch anything, I go toward the people. Not to gather requirements. To understand what's actually broken, which is almost never what they said at first.

50 interviews before building at Sauk County At a parade in North Chicago Focus groups at Peapod before touching the dashboard Stakeholder interviews that rewrote the Salesforce scope Fort Leonard Wood · talking to operators, not specs

→

Ask Why

The presenting problem is rarely the real one. I keep asking until I find the thing underneath: the policy vacuum, the broken trust, the data standard nobody questioned.

Policy vacuum, not a tools problem · Sauk County Nobody trusted the model · Peapod Data standards don't transfer globally · ENSITE Training approach was wrong · Salesforce Gov Civic participation gap wasn't about information · North Chicago

→

Build

Then I build the fix. Sometimes enterprise-scale. Sometimes a Python script. Sometimes a policy framework that has to exist before any technology can. The scale changes. The instinct doesn't.

HIPAA-compliant RAG on AWS Bedrock 127-requirement Salesforce implementation Global data standards for the US Military 2,400-book library automation in Python Bilingual community research report