
About me
HOW I THINK
I’m most energised when working through complex problems — especially when things don’t quite make sense at first.
I enjoy untangling messy systems, understanding how different parts of a product connect, and figuring out what’s actually causing an issue rather than jumping straight to solutions.
In my experience, the first solution presented is rarely the right one. Users often describe what they think they need, and product teams are often driven by business or delivery pressures — but neither always reflect the full picture.
I focus on identifying the real problem first.
Sometimes the solution is small — changing a label, adjusting a flow, or refining an interaction.
Other times it requires rethinking an entire system.
That unpredictability is what I enjoy most — the process of figuring it out.
HOW I WORK
I approach projects with a balance of independent thinking and collaborative problem solving.
I usually start by deeply familiarising myself with the product or problem space, identifying gaps, and forming the right questions. From there, I bring people together — whether that’s product, engineering, or other teams — to align on understanding before moving into solutions.
Clear communication is a big part of how I work.
In cross-functional teams, I often find myself acting as a bridge — translating between different disciplines to make sure everyone is aligned. Different teams often use the same words to mean very different things, and without clarification, that can lead to misunderstandings that affect the final product.
I’ve seen this first-hand lead to delays, unnecessary rework, and even roadmap changes that could have been avoided with clearer alignment earlier on.
I tend to favour conversations and collaboration over heavy documentation.
I’d rather over-communicate early than fix misalignment later.
WHAT I VALUE IN A PROJECT
I do my best work in environments where problems are clearly defined, but the path to solving them is open to exploration.
I value teams that:
Start with the problem, not the solution
Communicate openly across disciplines
Question assumptions early
Treat design as product thinking, not just execution
Structure is important to me — clear goals, defined responsibilities, and thoughtful planning all help projects move forward effectively.
At the same time, I think a certain level of exploration and iteration is necessary. Not everything can be fully defined upfront, and some of the best solutions come from working through that ambiguity.
I’m particularly motivated by projects where design plays a role in shaping the product — not just delivering visuals, but helping define how things should work.
I’m less interested in purely visual or marketing-focused work, and more drawn to product challenges where design contributes to structure, usability, and long-term scalability.
Contact
If you’d like to talk about a role, collaboration, or project, feel free to reach out.
Email: ruta@rueta.design
LinkedIn: www.linkedin.com/in/ruta-rackauskyte


