Work
My career started on the other side of corporate—fast-moving startups where my current design team size equals the entire headcount of companies I used to work for. Joining IBM meant unlearning everything I knew about pace and process. It took six months just to navigate the enterprise world.
I work in the IBM Cloud Infrastructure Center team, designing tools that make mainframes usable for modern teams. There's a larger stealth product I can't say much about, but the work sits at the intersection of legacy technology and modern design—making powerful systems approachable.
I use first-principles thinking to understand problems deeply and consider second-order consequences before proposing solutions. I collaborate closely with devs and PMs—the kind of bond where we fight with each other on ideas, not against each other. For a deeper dive into how I operate, check out my work user manual.
The first year was a lot of unlearning and learning. Working with team members from different cultural backgrounds taught me more than design ever could. The process and pace are different from startups, but everything starts to make sense when you understand the legacy of the technology and its potential.
I design better when I know why it matters. So I always start with defining success, documenting process, and being radically open to feedback. With advice from wise people inside and outside IBM (I didn't say Reddit), I've found my footing in enterprise design.