Design implementation

I like working close to the final product, not just the design file. For me, implementation is part of the design process, because a lot of interaction quality only becomes real once something behaves like a real product. That includes how components respond, how content adapts, how layouts scale, and how logic shapes the user experience.

Because I also work in implementation, I can make design decisions with more realism and precision. I think about constraints, reusable structures, responsive behaviour, and how something will actually be managed after launch. That often leads to cleaner systems and more durable solutions than designing in isolation.

This is especially visible in projects where design and implementation were closely connected, such as Milo, State of Sustainability, and Bibliotheek Rotterdam. In those projects, I worked not only on interface and flows, but also on the component logic, CMS structure, and real behaviour of the product.