I'm a software designer with a bias for action and judgment over process. Craft matters, but knowing when something is worth building, when the problem needs reframing, and shipping to learn is the part I find most interesting.

What shapes how I work:

• Run experiments that become features to define a product's vision

• Work at the quality and context layer of AI, not just the interface

• Read data fluently enough to inform my decision making

• Write monthly about what I'm figuring out in it depends