Complex software, clear interfaces: Sascha Werder joins the product design team at UX&I

Sascha, you joined UX&I as a Senior Product Designer. What attracted you to the role and the work environment?

From the very beginning, UX&I’s professional image struck me as both highly professional and approachable. It’s important to me that I feel comfortable with the people I work with, and that’s exactly how I felt. I also quickly realized that the team possesses a high level of technical expertise. That really appealed to me.

The job description aligned very well with what I had already been doing and wanted to continue doing. At the same time, it presented a real challenge and was therefore the logical next step for me. I found the clear focus on UI design, with the opportunity to also contribute ideas in the UX context, particularly exciting. Added to that was the opportunity to take on even more personal responsibility. I was coming from a traditional full-time position and wanted to work more independently.

Another point was the 4+1 model. 20% of working hours are intentionally set aside for collaboration, learning, and gaining new perspectives, which I hadn’t come across before. The mindset behind it won me over and gives me a great sense of freedom.

What’s your professional background, and why did you decide to focus on UI design?

I originally came from a background in traditional graphic design and have been in the field for a long time. Early on, my focus shifted toward the web and, later, apps. Digital products have fascinated me far more than traditional design.

After a deliberate period of professional reflection, it became clear to me that I wanted to establish a clear focus within design. UI design has given me exactly that. It combines creativity with structure and a close connection to actual usage. Since then, UI design has been my primary focus, with UX topics serving as a complementary aspect.

Many of our clients are under intense time and performance pressure. What role does UI design play in making software truly efficient to use?

For me, UI design is, at the very least, the icing on the cake of a good, intuitive user experience. Software is only used willingly and efficiently when it’s truly easy to use. UI makes concepts tangible and helps users find their way around without having to think about it.

A key point is to prioritize information correctly and not overwhelm users. I pay close attention to details, because in the end, they’re what make all the difference. Or as Charles Eames put it: “The details are not the details; they make the design.”

For me, efficiency also means thinking ahead. What scenarios are there, what edge cases, and how many variants do we really need? When user behaviors are thoroughly thought through and well documented, coordination with the development team becomes much easier and there are fewer follow-up questions. Ultimately, that saves time for everyone.

In enterprise projects, business complexity, technical constraints, and the diverse interests of stakeholders all come into play. How do you navigate these conflicting priorities?

It’s always very case-by-case. Often, compromises are unavoidable, especially when there are technical limitations. I then ask myself: Is this really important right now, or is it something that can be addressed later? The MVP concept plays a major role here.

Once I understand the topic, I usually jump right into the design process. Imposing restrictions too early tends to stifle my creativity. At the same time, I value open communication: discussing ideas, asking questions, and gathering feedback. I work closely with concept leads and share my designs as soon as they feel right to me.

Transparency is crucial so that stakeholders know where we stand at all times. I need to be able to justify my decisions well. At the same time, I don’t fight tooth and nail for a solution. A healthy dose of pragmatism is part of the job. Ultimately, it’s about moving the project forward and not getting bogged down in discussions.

Are there any typical UI issues you encounter in complex enterprise projects?

A very common issue is the desire to cram in too many features. At some point, this leads to UI limitations. On top of that, stakeholders often have differing or unclear ideas. Frequently, they know more clearly what they don’t want.

At the beginning, there’s a lot of freedom, but later on, there’s a major shift back due to internal or political reasons. That’s just the reality of such projects. It’s important to justify your work well while also maintaining some distance from your own design. The first draft is never the final one anyway.

What drives you, especially when projects get complex or tough? And how do you recognize a good product?

I’m motivated by designing products that aren’t just aesthetically pleasing, but also offer real added value. When something works, is efficient, and is fun to use, that’s a huge motivator.

Of course, there are also tough times. When that happens, I try to refocus on the goal and concentrate on what’s already going well. The support from my colleagues helps a lot, as does maintaining a certain level of professionalism as a service provider.

For me, a good product is one where you don’t have to think about how it works. It’s intuitive, streamlined, and not overwhelming. As a visual person, aesthetics naturally play an important role for me. But it doesn’t have to be the newest or the loudest, it just has to be clear, minimalist, and cohesive.

Finally: Do you have a fun fact about yourself?

I’m great at folding fitted sheets.