People Around Peax: Patrycja on Bridging Code and Creativity Through Design Systems
- weronika110
- 7. Apr.
- 4 Min. Lesezeit

At peax, we are constantly surrounded by talented individuals who shape the design and tech industry in inspiring ways. Our “people around peax” series shines a light on these professionals, giving them a space to share their insights, experiences, and visions.
This time, we’re excited to introduce Patrycja Radaczyńska from Babbel, a senior engineer and longtime design systems advocate with a passion for bridging design and development. With deep technical roots and a people-first mindset, she’s been shaping systems thinking long before it was mainstream, combining precision with empathy to build more inclusive, collaborative products.
00 What Is a Design System?
"A design system is a collection of standards, documentation, and reusable components that guide the development of digital products, ensuring consistency and efficiency across projects. It serves as a unified framework for design and development teams to create cohesive user experiences".
A design system is the heart of a digital product that holds its unique visual identity in the form of components, rules, documentation, guidelines for both designers and engineers.
01 Systems Thinking Before It Had a Name
Patrycja’s journey into design systems began in 2016 at Brainly, when the term wasn’t yet part of everyday UX and engineering conversations.
“We were just a small frontend team trying to work better with design. We built component libraries for ourselves and shared design assets built in Sketch. Eventually, we tried exporting components from code back into Sketch, just to stay aligned.”
That early project - HTML Sketchapp - was a turning point. We felt like we were really doing something completely new and innovative. It wasn’t just about building faster. It was about creating one source of truth and a shared language between disciplines. That sense of connection and alignment became the foundation of her passion for systems.
“Design systems, to me, are about connection, bridging the gap, speaking the same language. They make collaboration easier, more inclusive, and more human."
02 From Side Projects to Strategic Enablers
In those early days, most design systems were passion projects - built after hours and without formal support.
“We knew we were saving time and reducing redundancy. But getting leadership buy-in? That was the hard part.”
Patrycja learned quickly that advocacy is part of the job. To gain traction, system builders need to tie their work to real outcomes: faster shipping, better quality, happier teams.
Today, she sees this shift happening across the industry. Companies are waking up to the fact that design systems are not “nice-to-haves” - they are critical infrastructure.
03 Challenging the “Systems Kill Creativity” Myth
One of the most common misconceptions? That systems limit creative freedom.
Patrycja disagrees strongly.
“Design systems exist to solve repetitive problems and set the guidelines on how to solve them in a consistent way. If you never have to design a modal from scratch again, you get to spend more energy solving user problems.”
She argues that a good system doesn't constrain creativity; it channels it. By taking care of repetitive design work, it creates space for real innovation.
But that doesn’t mean systems are static.
“Established patterns represent the status quo and the status quo should be challenged. Designers should feel empowered to evolve the system when the product demands it.”
In her view, systems should be flexible, collaborative, and open to change - never treated as a rigid rulebook.
04 Getting Designers and Developers to Rally Around the Same System
Patrycja approaches adoption as a dual challenge because engineers and designers engage with systems differently.
“Developers are used to building code in a modular way. Reusing components is already part of their mindset.”
But for designers, especially those who’ve worked solo, systems can feel foreign at first. That’s where tools like Figma have helped shift the dynamic.
“Figma changed the game. It made collaboration feel natural. Now, I see designers genuinely excited about systems. They want to contribute.”
Still, adoption doesn’t happen automatically. It requires trust, communication, and a culture that encourages feedback.
“If people don’t feel heard, they’ll work around the system. The greatest threat to a design system is disconnection.”
05 Diversity in Engineering Isn't Optional - It's Essential
Patrycja has spent her career in rooms where she was often the only woman.
“It’s changed a bit over the last 10 years, but not enough. Being the minority in engineering isn’t just hard emotionally, it affects everything from collaboration to product quality.”
She believes diverse teams build better products, period. Why? Because products reflect the people who build them. Without diversity, your product will silently reinforce exclusion.
“Imposter syndrome is real. I’ve felt it many times. But what helped was having mentors and communities who believed in me, sometimes more than I believed in myself.”
Patrycja is a strong advocate for mentorship, visibility, and inclusive hiring, but also for cultures where difference is seen as a strength, not a deviation.
06 The Future: AI, Experience Systems & Dynamic Accessibility
Looking ahead, Patrycja sees the role of design systems evolving dramatically.
“In 10 years, I don't think we'll be manually building components. AI will handle that. Our job will be to guide and curate.”
She envisions a world where systems become experience frameworks, connecting product, marketing, and even physical spaces, far beyond static UI kits.
“Maybe they’ll become self-healing. Maybe they’ll adapt to user needs in real time. But the heart will stay the same: making experiences more human.”
She also hopes accessibility and inclusivity will stop being add-ons and start being core design principles - baked into systems from the ground up.
07 Final Thoughts: Ask, Speak Up, Take Space
Patrycja’s advice for anyone, especially women, thinking about stepping into technical roles?
“Ask questions. Speak up. Don’t wait for permission to take space. Your perspective is your superpower.”
She reminds us that tech isn’t just about code: it’s about people, systems, and shared purpose. And the future of design systems will be shaped by those who dare to bring their full selves into the work.
At peax, we’re inspired by people like Patrycja Radaczyńska , who redefine what it means to work at the intersection of engineering, design, and inclusion.
If you enjoyed this, explore more interviews with boundary-pushers who are shaping the future of product and experience design. Until next time! 🙂
Comments