Work
I work on the IBM Cloud Infrastructure Center team, designing tools that make mainframes usable for modern teams—plus a larger stealth product I can't say much about yet. The work lives at the intersection of legacy technology and modern design: taking enormously powerful systems and making them approachable.
I got here from the other side of corporate. My career started in fast-moving startups—where my current design team is larger than the entire headcount of some companies I used to work for. Joining IBM meant unlearning much of what I knew about pace and process; the first six months were mostly just learning to navigate the enterprise. It starts to make sense once you understand the legacy of the technology and its potential—and working with people from very different cultural backgrounds has taught me more than design ever could.
I design better when I know why something matters, so I start by defining success, documenting the process, and staying radically open to feedback. I lean on first-principles thinking and weigh second-order consequences before proposing a solution—and I work best in close partnership with engineers and PMs, the kind where we fight over ideas, not each other. A lot of what I've learned came from wise people inside and outside IBM (I won't say Reddit); there's more on how I operate in my work user manual.
The product work behind these systems sits alongside the side projects I build to scratch my own itches—you'll find both, case studies and tools, on my Projects page.