What we have with Gopicca isn't a typical UX designer success story.
It's not a story about someone who was lost and found their way. It's not about someone who didn't know design and learned it. Gopicca was already a strong designer before we ever spoke. What happened in the four months she spent with us was something different - a sharpening of instincts that were already there, a structuring of leadership qualities that were already present but hadn't found their language yet.
In my eyes, Gopicca is a designer en route to becoming a product leader. Not because she wants the title. Because the way she thinks about products - how they're identified, built, developed, and defended - is already operating at that level. The title will catch up. It always does for people like her.
Gopicca - a designer en route to product leadership
Where She Started
Gopicca came to design from textiles. The switch happened early. A practical decision, made clearly, that happened to lead somewhere remarkable.
By the time she connected with Xperience Wave in early 2026, she had about three years of product design experience across two very different domains: pharmaceutical products and an AI-powered customer support platform.
The first time I heard her talk about the AI platform she was working on, something was immediately clear: this was not someone who just designed screens for a product. She knew the product inside out - its business model, its strategic direction, its organisational operational capabilities, its competitive positioning. She had been part of strategic conversations to set direction over an extended period. She understood not just what the product did, but why it existed and what needed to change for it to succeed.
That kind of depth doesn't come from a job description. It comes from a person who refuses to stay in the lane they were assigned.
The Fight She Was Already In
Here's the part that every designer working in India will recognise.
Gopicca had seen firsthand what happens when organisational leaders treat design as decoration - as the process of adding beauty to screens that have already been planned, scoped, and decided upon by people who don't understand users. She had sat in rooms where design decisions were overridden by people whose authority came from their position, not their understanding. She had experienced the quiet dismissal that so many Indian designers know intimately: being asked for your input and then watching it get ignored.
She hadn't accepted any of it.
That was the first thing I noticed about her. Gopicca was a fighter. She knew she didn't have an easy say in these conversations - the hierarchy wasn't built for a four-year designer to challenge the assumptions of a director or a VP. But she also wasn't going to let it pass without resistance. She pushed. She questioned. She brought evidence when she could and conviction when she couldn't.
If you're a designer reading this and thinking "I know exactly what that feels like" - the internal struggle of knowing you should have a voice but not knowing how to use it, feeling like an imposter while also knowing your instincts are right, not knowing where to draw lines or when to say no - know that you're not alone in it. This is the lived experience of nearly every designer working inside Indian organisations where there's no UX leader to shield them or model what good looks like. We wrote about why this environment exists in The UX Career Ladder Is Broken in India - the culture, the hierarchy, the gap between titles and reality.
Gopicca was navigating all of that. And she was doing it without a senior design leader in her organisation to learn from.
What the Four Months Were About
When Gopicca joined the Current program, the work wasn't about teaching her to design. She could already design. It wasn't about giving her more tools or techniques. She had enough of those.
The work was about two things that she was already doing instinctively but hadn't yet structured into a repeatable practice.
The first was process ownership.Gopicca naturally thought about the full product lifecycle - not just the design portion. But she hadn't yet built a framework for articulating that thinking to people who didn't think like a designer. The gap wasn't in her understanding. It was in her ability to translate that understanding into language that business leaders, engineering teams, and product stakeholders would act on.
We worked on structuring how she framed problems, how she positioned design direction in terms of business outcomes, and how she navigated the political dynamics of organisations where design doesn't have a natural seat at the table. The goal was to take the fighter instinct she already had and give it a more effective weapon - not louder advocacy, but sharper framing.
The second was leadership identity.Gopicca was already a leader - in the sense that she influenced outcomes, challenged assumptions, and drove quality. But she didn't see herself as a leader in the formal sense. She was waiting for the title to validate what she was already doing.
We worked on dismantling that dependency. A design leader isn't someone with "Lead" or "Manager" in their title. A design leader is someone who shapes how their team and their organisation think about design's role in the product. Gopicca was already doing that. She just needed to own it - explicitly, confidently, and without waiting for permission.
What Changed
The shift was visible within weeks.
How she talked about her work changed. Before, Gopicca would describe her projects in terms of what she designed - the flows, the screens, the research. After, she described her projects in terms of what problems she identified, what direction she set, what business outcomes her design decisions were connected to. Same work. Different framing. The framing is what makes people listen.
How she handled organisational resistance changed.The fights she'd been having with stakeholders who dismissed design - those didn't disappear. The organisation didn't suddenly become design-mature. What changed was her approach. Instead of pushing against the resistance with conviction alone, she began framing her arguments in terms her stakeholders valued: risk reduction, operational efficiency, customer retention. She stopped arguing that design matters. She started showing what it costs when it's ignored.
How she thought about AI changed.This is worth calling out specifically. In early 2026, the design industry was in a state of collective anxiety about AI - where am I getting left behind? Recruiters were asking for "AI skills" without knowing what that meant. Designers were scrambling to learn tools without understanding the principles underneath.
Gopicca was ahead of this. Her experience with the AI-powered customer support platform had given her real exposure to machine learning, natural language processing, and human-in-the-loop design patterns. But during our work together, that exposure deepened into genuine fluency - understanding probabilistic thinking, knowing when an autonomous model serves users better than a human-guided one, and being able to evaluate AI use cases not just as a designer but as someone who understands the technology well enough to challenge product decisions about it. We wrote about why this kind of AI fluency matters in 5 Things Senior Designers Should Be Doing With AI - Gopicca was already living it.
Where She Is Now
Gopicca recently moved into a role at a substantially higher compensation than her previous position.
I want to let that sit for a moment. Not because salary is the measure of a designer's worth - it isn't. But because a jump like that doesn't happen by learning a new tool or adding another case study to a portfolio. It happens when the market recognises that you're operating at a fundamentally different level. That you're not just a designer who makes things. You're a designer who shapes direction, navigates complexity, and makes products better in ways that are measurable.
She's aiming now for a piece of product ownership - not abandoning design for product management, but expanding into the overlap where design leadership and product ownership converge. We explored this path in detail in Can a Designer Turn Into a Product Manager?- and Gopicca is a living example of the argument we made there: you don't have to leave design to own products. You have to become the kind of designer whose influence naturally extends beyond the design function.
What Designers Can Learn From Gopicca's Journey
I'm not sharing Gopicca's story to sell a program. I'm sharing it because her journey illustrates something that most UX career advice gets wrong.
You don't need to start from zero. Gopicca came from textiles. She didn't treat that as a weakness - she used the visual thinking, the material sensitivity, and the production awareness from her textile background as a foundation. If you're a designer from a non-traditional background, read how experienced designers switch to UX without starting over. Your past isn't a liability. It's a differentiator.
Being good at design isn't enough.Gopicca was already good when she came to us. But "good at design" and "recognised as good at design" are two different things. The gap between them is communication - how you frame your work, how you position your contribution, and how you make your value visible to people who don't think in design terms.
Fighting alone is expensive.Gopicca was already a fighter. But fighting without a framework is exhausting, and fighting without allies is unsustainable. What changed wasn't her willingness to fight. It was her effectiveness - the ability to pick the right battles, frame them in the right language, and build the credibility that makes people listen even when what you're saying is uncomfortable.
The title follows the behaviour.Gopicca didn't wait for a leadership title to start leading. She led first - in how she challenged problems, in how she influenced product direction, in how she brought evidence and conviction into rooms that weren't designed for her voice. The title, the salary, the recognition - these followed. They always do for people who operate at this level.
A Note From Me
I don't write about every designer I work with. But Gopicca is someone I genuinely believe the industry should pay attention to.
Not because of the salary jump - though that's remarkable. Because of who she is as a practitioner. She combines the depth of a researcher, the craft of a designer, the strategic thinking of a product leader, and the resilience of someone who's navigated hostile environments without losing her integrity or her curiosity.
She's an upcoming experience transformer. And if the design industry in India is going to produce the kind of leaders it desperately needs - the ones we talked about in Design Leadership Is in Turmoil - Gopicca is one of the people who will lead that charge.
I'm glad we got to work with her. And I'll be watching what she builds next.
If Gopicca's journey resonates with where you are right now - a designer who's strong at the craft but struggling to make the leap into leadership, ownership, and recognition - that's the exact transition our mentorship programs are built for. Not to teach you how to design. To help you become the designer you already are, but louder, sharper, and impossible to ignore. Book a strategy call.
Further Reading on Xperience Wave
- The UX Career Ladder Is Broken in India. Here's the Path That Actually Works.
- 5 Things Senior Designers Should Be Doing With AI
- Can a Designer Turn Into a Product Manager? What Does the Preparation Actually Involve?
- I've Been a Visual / Graphic / Motion Designer for 2+ Years - How Do I Switch to UX Without Starting Like a Fresher?
- Design Leadership Is in Turmoil. And No One's Talking About It.
About the Author
Shaik Murad is Co-founder and Head of Product & Design at Xperience Wave, a UX design studio based in Bangalore, working across designer mentorship, UX services for businesses, and a design community of 1,370+ designers.
- Murad, Co-founder & Head of Product & Design, Xperience Wave
