Occasional writing on product design practice, design systems, and the workflows that support them. Drawn from real projects rather than theory.
The design engineer is having a moment. But even the most articulate versions of the concept leave a question unanswered. Where, specifically, should the design engineer be contributing? The boundary is not a detail. It is the argument.
In complex software projects, requirements quality is a design responsibility, not a handoff precondition. Designers who treat it as someone else's job are building technical debt by default.
Prototype tables have three rows because keying forty rows into Figma manually is something nobody actually does. Here is the workflow that fixes that.