I'm drawn to problems that repeat — confusing products, unclear workflows, useful work stuck inside one person's file. When something keeps happening, it's almost never carelessness. It's a missing system.

So I build the missing system. Sometimes that's a product. Sometimes it's a toolkit, a standard, or a tool that catches the problem before a person has to. At Dell I do this on my own, for an org big enough that whatever I build has to work without me around to explain it.
Here's what I'm really after: giving a team an ability it didn't have before. The best systems don't just solve a problem — they break the limits people had been working around for years, hand them a new skill, and let them do better work with a lot less pain. I don't want to save the day once. I want to give people something that makes them better at their jobs — and keeps doing it after I'm gone.