Based in Kürten, near Cologne

Hey! I'm Jackie,Media designer & media computer scientist

I create and develop AI-powered design systems, prototypes, and websites following Atomic Design and taking user experience (UX) into account.

12 years

Freelancer

6 years

Developer

4 years

Designer

2 years

Active volunteer work

This English version of the site was translated with the help of Claude (Anthropic).

User Research & Data Analysis

Through user research I see where there's demand or something isn't working, even if I don't yet know why. To understand that, I turn to qualitative methods like contextual observations, interviews, and usability tests, planned partly with Microsoft Forms or Google Forms. I prioritize my findings with frameworks like the MoSCoW method or the Kano model, turning them into clear recommendations.

PostHogMicrosoft Forms / Google Forms

Also familiar with:Google Analytics

UX Design & Full-Stack Development

UX design and full-stack development are hardly separate steps for me anymore. I sketch prototypes directly in code with Claude and turn them into reusable components based on the principle of Atomic Design, keeping the whole product consistent. My own portfolio came together that way, built with React and Tailwind CSS and analyzed with PostHog.

ClaudeReactNode.jsTailwind CSSGitHubNetcup

Also familiar with:FigmaFigma MakeLoveableAdobe IllustratorAdobe LightroomAdobe PhotoshopDrupalWoltLab

Projects from my portfolio

My projects range from UX evaluation and user research with data analysis to prototyping with Claude Code and Figma, all the way to corporate design. Feel free to browse the references below. If one of them made you curious, write me or just mention it, and I'll tell you more in a conversation.

Corporate Design & Print1 reference

Websites4 references

Illustration6 references

Latest Posts

1. Mai 20263 min readI'll be running for board secretary of the German UPA

I was invited to the German UPA's strategy workshop in Frankfurt because I'll be running for board secretary. For me, it was mainly about understanding how strategic decisions come about within the association and what they're built on.

Keep reading

20. Juni 20263 min readWhen are personas actually worth it?As part of my studies, I looked closely at personas. My starting point was the question of why personas get created in many projects but don't always make it into everyday use. In theory, they're a central tool for making users tangible and supporting decisions. In practice, it often looks different.

10. Mai 20263 min readThoughts on Dev Women Cologne 2026An evening among women in IT turns out differently than expected and raises a question that goes far beyond the topic itself: what role does behavior play in collaboration, and why do we so often underestimate its impact?

1. März 20264 min readRecap of the UX Winter School 2026The Winter School that KMH GmbH made possible for me is now over, and all four workshops were super exciting and very hands-on. I learned something new in every single one and met a lot of new, inspiring people. Susan Rittel, who I attended UX Summer School 2025 with, was even there too!

View all posts

What we can talk about, professionally

You're welcome to talk to me about any of these topics at any time. I'm curious to hear your experiences and views.

When is switching to prototyping in code worthwhile, and when is it better to skip it?

For me it comes down to time, budget and people first. An ROI calculation shows whether the effort pays off. For web applications, prototyping in code is a natural fit, for physical products it rarely gets you far. I'm curious where others draw the line.

How does a team change its way of working without things falling apart?

I believe it needs free capacity, and small steps help. I improve something by one percent every day until the goal is reached. An additional specialist can speed that up. Which approaches have worked in other teams?

How do we deal with reservations about a new way of working?

I understand when someone has learned their craft and is suddenly asked to work differently. Talking, evidence instead of hearsay and the chance to try something new without feeling replaced help me. Mandated changes without a visible reason risk frustration and, in the worst case, resignations. I'm always glad to swap experiences on this.

Which tools or technologies do we become dependent on, and how do we limit that?

With tools, I know the pattern that they start out cheap or free and later cost a lot more. With AI, there is a risk of handing over solutions and thinking less creatively yourself. A design system based on Atomic Design and quick reactions to change limit dependencies best, in my view. Which dependency do we underestimate the most?

What does a development background bring to a design team?

I know Atomic Design from development, and I understand the interface between design and code. In my experience that saves friction and time. For interactive prototypes I rely on AI and code because it works more reliably for me. I'm keen to hear where design teams miss that closeness to development today.