Constraints are a creative springboard, not a hurdle.
The best work I've led happened inside tight boundaries: regulated industries, compliance deadlines, six-figure enterprise contracts, small teams. I build clear processes, shared systems, and agreed ways of working first, so the team spends its energy on the problem instead of reinventing the workflow. Structure is what lets creative people take real risks.

Discovery is where the design actually happens.
Before Figma, I want to understand the user, the business goal, and what "success" will be measured against. I run discovery with clients and stakeholders, synthesize it, and validate before we build. In complex decision-support work, the question logic and user pathing I map at this stage usually determine everything downstream, so I treat it as design work in its own right.

Engineering is a partner from day one.
Some of the best decisions in my career came out of early conversations with engineers about what was actually possible. I bring technical teams in before the concept is locked, use their constraints to find more creative solutions to complex logic, and build shared ownership of the outcome. The result is fewer "oh wait" moments and better products.

I measure success by what users can do, and by who I've helped grow.
Deliverables are a means to an end. I measure my work by what users understand, decide, or feel after using what we built, not by how polished the file is. And I measure my leadership the same way: several designers and writers I've managed have grown into senior roles, and that's the work I'm proudest of.