I'm a little obsessed with foundations. Most broken processes are missing theirs. Show me one everyone has learned to live with, and I cannot leave it alone.
When someone brings me a problem, I don't start with solutions. I pull apart what they tell me until I find the root, then I ask what the fix breaks before I build it. That's how I make sure what gets delivered is what was actually needed, not what everyone assumed it was before anyone dug in.
The method is the easy part to explain. Caring whether it actually works for the person it's built for is the part you can't fake.
A four-hour daily workflow that everyone had learned to live with, taken down to under twenty minutes. The real fix was nowhere near the work itself. It was a clean data source sitting four screens away that nobody was reading from.
View project →Four years in human services SaaS, centered on the gap nobody owned: the translation between what a caseworker needed and what the platform could do. The fix was not a better process. It was a team built deliberately, around people, to live in that gap.
View project →A psychiatric nurse practitioner launching a cash-pay telehealth practice from nothing, across Virginia, Maryland, and DC. The engagement runs across business model design, financial modeling, multi-jurisdiction regulatory planning, employment transition, and technology selection, doing the operational work instead of recommending it from the outside. The work is ongoing.
View project →Someone once said,
"If Dustin wanted to become the broccoli-eating champion of the world, he would become it."
Ridiculous example. Accurate point. When I care about a problem, I stay with it until the answer actually works.