Order is my profession
I lead a design system at a large IT company, working where product design, documentation, and the hard reality of engineering meet.
A design system as a working language
For me, it means components, patterns, documentation, and agreements the team uses every day.
- 01
Design leadership
I help designers get to decisions faster and avoid drowning in endless variations of the same button.
- 02
Design systems
Components, states, patterns, and rules that make a product feel coherent and easier to evolve.
- 03
Complex scenarios
I break complex scenarios down and turn them into interfaces people can understand without a twenty-page manual.
- 04
Design and engineering
I shape solutions for both mockups and code, because code is where the real constraints appear.
Rules make arguments shorter
A design system helps the team agree faster and keeps the product from falling apart into disconnected pieces. When everyone knows what the interface is made from and which rules hold it together, decisions come calmer.
Energy stays with the real problems: scenarios, constraints, rare failure paths, and quality. I assemble components and explain how to use them, where their boundaries are, and why they are built that way.
Meetup recordings
Talks about design, frontend, Figma, cognitive bias, and design systems, all available to watch publicly.
