I find the problemworth solving,then ship the fix.

I like problems that show up badly defined. Most of the work I care about started that way. At Lilly, nobody could tell me which manual workflow was costing the department the most, so I spent the first stretch interviewing people until it was obvious. Yale was two summers with no scope at all, where the hard part was choosing which questions deserved the time.

After the analysis, I can usually build the thing too. I've shipped full-stack applications, data pipelines, and LLM systems that had to be reliable enough for people to trust the output. So when I recommend something, I already know roughly what it takes to build it. Nearly all of that has been in healthcare and technology.

Two of the things that taught me the most don't look like work experience. I captained Brown to its first national volleyball championship, and I've spent three years running a healthcare publication that now has eight editorial teams under it. Both come down to making calls without enough information and living with them.