Tell me what the product is and where it is stuck.

Enterprise SaaS and operational platforms: procurement, media localization, commercial real estate, connected hardware, loyalty and gamification. The common thread is data-dense, multi-role workflow software: admin tooling, approval chains, dashboards built around decisions. Earlier work covers consumer social, marketplaces, and games. And whatever the domain, they should look the part; enterprise is not an excuse.

Principal or lead product design roles where I can lead a design team and still ship work myself, and embedded engagements of roughly three to nine months owning a defined surface area. I also take on design system foundations and audits. I am not the right person for purely managerial roles, marketing sites, visual refreshes, or brand identity work.

Embedded engagements run three to nine months, owning a defined surface area end to end: usually a platform rebuild, a data-heavy module, or a workflow that has resisted several attempts. In-house roles are open-ended. Either way I stay through delivery rather than handing off at specification.

I design against the component library the team already has (on recent platform work that meant extending MUI and AG Grid rather than replacing them) and document every component twice: the UX intent, and how and why it deviates from the framework default. I am fluent enough in component logic, state, and accessibility constraints that reviews are about feasibility rather than translation.

Product design strategy documents, information architecture and domain models, tokenized component libraries documented from both the UX and the engineering side, tested prototypes, and decision logs that keep the reasoning auditable. The consistent property: engineering can build from them without a translation step.

Both. Recent projects included a three-week discovery sprint across regions, stakeholder workshops, contextual observation, and usability testing. Every outcome figure on this site states how it was established: measured, modeled, or usability tested.

The turn: the meeting where a screen everyone called complicated starts being called obvious. Getting there is domain archaeology, learning how procurement buyers or dubbing coordinators actually think until the structure falls out. Then the finish. A dense table with composed typography and motion that explains itself is, to me, a genuinely beautiful object. I realize this is a niche taste.

Yes. It is usually where the work starts. On the localization platform I authored the product design strategy that aligned product, engineering, and operations leadership; on the procurement platform, design decisions were presented to leadership quarterly in operational terms. Prioritization under governance and compliance constraints is part of the day job.

Yes. The most common shape is establishing or repairing a tokenized foundation where a third-party component library is already in production and cannot be replaced, including the adoption and governance model that keeps it from forking.

Procurement and retail, media and localization, commercial real estate, IoT and safety hardware, loyalty, fintech and private banking, security and intelligence tooling, healthcare AI, automotive, gig-economy marketplaces, and gaming. The case studies cover the first four in depth.

Poland, working across European time zones. Currently at Open Loyalty and open to conversations about principal and lead roles or embedded platform engagements. Email is the fastest route and I answer it myself.