I help teams decide what to build.
Then I design it.
AI is in every step of my process, but my edge is knowing what's worth building.
(01)
Push back first
Most teams build too much because nobody pushes back. A request for a modal or a line of text doesn't go straight to the design board. First I want to know where it's coming from and what it's actually solving.
(02)
Curiosity without a bottom
I keep asking questions long after most people stop. That's usually where the real problem shows up.
(03)
AI for speed, not understanding
AI is exceptional at speed, synthesis, and pattern recognition. It can't talk to users, push back, or stay curious. That part is on me
(04)
Design can only solve so much
Sometimes the better fix is sending a notification at a different time, or changing a process or incentive. If the answer isn't a screen, I'll say so.
(05)
Progress over polish
Polish is subjective and never finished. The real risk is shipping nothing, because we don't know what helps until users react. There's no "done," just "done for now."
(06)
Engineers from day one
I want engineering involved from the first conversation, so no time is wasted on ideas that break constraints.