Turning Complexity into Beautiful Software.

01 / Design Philosophy

Great Design starts long before the UI.

Beautiful software isn't the result of Figma designs or CSS wizardry. It comes from understanding the user’s work, the decisions they need to make, the information they rely on, the business rules underneath it, and the technical constraints shaping what’s possible.

A polished interface can make a product look resolved, but it won’t make a clunky workflow feel seamless.

02 / Software Development

I learned Design alongside Code.

I took my first graphic design course in college while I was learning JavaScript. I loved both the creative playground of design and the logic of code, so I chose to pursue web design.

Fast forward over a decade later, that combination has shaped the way I’ve approached products ever since. I understand that a product has architecture, state, data, APIs, constraints, dependencies, and consequences. That helps me ask better questions earlier, recognize tradeoffs sooner, and work closely with developers without treating implementation as something that happens after design is finished.

It also means I’m comfortable staying involved as an idea moves from rough concept to working software.

03 / Transformation

Transformation is more than a digital glow-up.

Moving a spreadsheet, paper form, or physical workflow into a software application isn't digital transformation. Before even teaching code, design should be asking:

• Can we anticipate instead of react?
• Can we surface what matters instead of making people hunt for it?
• Can we connect work that used to be fragmented?
• Can we remove steps that no longer need to exist?
• Can we make a difficult decision easier to understand?

That’s the part of product design I find most interesting: not simply translating an existing process into a new interface, but asking what the product can become. I’ve worked on these kinds of problems across energy trading, supplier risk, tendering, engineering operations, and supply-chain intelligence.

04 / Leadership

Use Design as strategic leverage

Design is most valuable when it connects people who see the problem from different angles—users, domain experts, product managers, developers, data specialists, and executives.

When design enters the conversation early, it can do more than improve an interface. It can help uncover opportunities, frame better problems, challenge assumptions, clarify tradeoffs, and shape the direction of the product itself. That’s how I think about leadership: creating the conditions for design to have that kind of influence, while taking ownership of the outcomes that follow.

For me, that means understanding why the product should exist, what outcome it needs to create, and where design judgment can change the direction—not just the appearance.