Designing systems for operational product work.

Together with another designer, I helped establish the design system for SIXT's back-office applications. The work was not just component cleanup. It meant creating a shared foundation that could support dense internal products and still stay practical for engineering teams.

I worked with engineering on implementation and wrote the first draft of the component guidelines. That documentation helped turn the system from a Figma layer into a usable product foundation: clearer rules, more consistent components, and better shared language between design and development.

In the revenue-management department, I worked as the solo designer across applications that depended on dense information, operational constraints, and business-critical decisions. The redesign was not a visual refresh alone. It was a restructuring of product behavior around clearer flows, better hierarchy, and a more coherent component language.

By introducing component and UX patterns across the applications I designed for, the work improved overall usability and made the experience feel less fragmented. The design system became a practical way to raise product quality across related tools, not a separate library sitting outside the work.

As AI tools entered the product workflow, I worked the design system into my AI process so prototyping could move faster without losing consistency. The important part was not using AI as a shortcut around design judgment, but giving the tools better structure: components, rules, product context, and clearer links between Figma and the codebase.

I improved the design-to-code workflow by connecting Cursor, Claude, and Figma more deliberately, then helped other designers and POs with Claude and Cursor skills and rules that made their prototyping and AI workflows more consistent. Later, after taking over PO responsibilities for the team I was working in, I continued prototyping directly in the codebase and improving the team's workflow with AI tools.