Not frameworks I read somewhere. Things I've learned by doing the work.
Always be prototyping in real code. If it doesn't run in a browser, it's still an idea. Ship early, ship often, learn from what's real.
Get people in a room and talk. A 15-minute conversation beats a 15-page document. Write things down after you've aligned, not instead of aligning.
A good designer should be good at designing. Visual output, tweaking, polishing. If you're not proud of what you shipped, you haven't done your job yet.
The world's greatest Figma file means nothing if the user doesn't have the same experience. What the user touches is the only thing that matters.
What I believe
I've spent the last decade leading growth design teams. Here's what I've learned.
You can optimize every button and still lose. The best growth design balances what people do with why they do it. Lean too hard on conversion metrics and you lose the brand. Lean too hard on brand and you stop learning. The sweet spot is both.
I help people identify where they want to develop, then I make sure they get the work that lets them do it. Feedback and 1:1s matter, but what matters more is strategically putting people in position to succeed and learn.
What initiative has the biggest possible impact? Where are we leaving money on the table? Where could we be better? I like messy landscapes where the work is figuring out what to do, not just how to do it.
I'd rather show you how I think than tell you. Happy to walk through any of this in a conversation.