From the desk of Maik Rieffenstahl
September 2026
I learned the manual way. Now the machines do the manual part.
Hi. If you are here, you have probably seen the work. This page is about how it gets made, and why that matters if you are thinking about hiring me.
I did the work by hand first.Between 2023 and mid 2026 I built two design systems for GARANTIEMAX atom by atom, ran 426 Jira tickets across two boards, mapped every flow before opening Figma and drew the handoff frames myself. At Raptive, before Figma had a Dev Mode, I documented components on manual annotation sheets: spacing, states, behaviour, one sheet at a time. None of it was glamorous. All of it taught me what a working system actually costs, and where the shortcuts hide.
That is why I can tell when the machine is wrong.When I audited both GARANTIEMAX systems in July 2026 with a deterministic extraction, I could read every hardcoded value in the first system and know exactly which shortcut had produced it, because I had taken that shortcut under MVP pressure two years earlier. The same applies to AI output. A generated component, a drafted ticket or a prototype is only as good as the person judging it, and that judgment comes from having done the task without help.
The screen is the smallest part of the system.Insurance coverage that activates on delivery, not on a click, so no screen may ever imply otherwise. A backend that still returns a binary status while the product needs six. Admins and partners sharing one data model with different rights. A swimming club whose parents discover a course on Instagram, phone the office for reassurance and then book. Every product I have worked on was decided outside the interface first. I map the objects, roles, rules and constraints before I design, because that is where most UX problems actually live.
Limited budget is a constraint, not an excuse.Wasserfreunde Spandau 04 has no product team and no budget line for design. In April 2026 an Instagram funnel with 51 tracked clicks produced 20 course bookings and about 5,000 euros in estimated revenue. A membership campaign has 38 tracked sign-ups so far. Attribution is partial, and I say so. The point is not the number. It is that a clear offer, a short path and respect for how people actually behave work at any budget, if someone structures them.
AI took the tedious part. It did not take the decisions.I have worked with AI since summer 2024, first for my own work, then with Figma Make in its first months, then in the company workflow from early 2026. Since mid 2026 my workflow is AI-integrated end to end: a Claude project with a data layer for product facts, seven Figma skills my team runs for reviews and handoff checks, Jira tickets written and updated programmatically, both design systems extracted and diffed per release, a company-wide knowledge base anyone at GARANTIEMAX can set up in five minutes. Documentation, extraction, first drafts, test coverage: the machines do that now, and they do it faster than I ever did. Explaining two options to the CEO and what each will cost, deciding whether a modal or a side sheet fits an admin’s day, noticing that a status colour will fail contrast for someone: that is still mine, and it gets more of my time than it ever did.
What that buys you.Less of my time goes into producing and more into weighing. Proof arrives as working prototypes, not slide decks. Numbers are measured, not eyeballed, and when they are estimates they are labelled. And you get someone who has run the manual version of every process he now automates, so nothing is delegated to a tool that the tool cannot actually do.
Thanks for reading this far.
Maik
The six principles in short
I do the work by hand before I let a tool do it.
Two design systems built component by component, hundreds of specs written for developers, 426 tickets run across two products. That is why I can tell when a tool or an AI hands me something that will not hold up.
I build design systems that can grow.
At GARANTIEMAX the first system covered the phone app only, because the app came first. When the partner platform arrived I extended it to desktop instead of starting again, then aligned both, so they now share 94 names for things like colour and spacing and 26 components.
Most of a product is decided before anyone designs a screen.
Legal rules, what the backend can actually return, who is allowed to see what, and the budget. Those decide more than the interface does, so I map them first and design what the product can really do.
A small budget changes what I build, not how well.
Wasserfreunde Spandau 04 is a swimming club with no design budget and no product team. It still got a booking path that converts and honest numbers to show for it.
AI writes the drafts, I make the decisions.
Documentation, data extraction, first drafts and test coverage run automatically in my workflow. What to build, what to drop and how to explain the trade-off to the person paying for it stays with me.
I report what actually happened, not what looks good.
When a number is an estimate, I label it as one. When a result had causes besides my work, I say so. It costs me a few impressive slides and it is why the other numbers can be trusted.