What I’ve Learned About Overcoming Challenges:

The first real challenge – the kind that knocks the air out of you – isn’t something you plan for. It’s not just a hard task; it’s the moment when everything feels misaligned, like you don’t belong or can’t move forward. I’ve learned that you don’t need motivation to keep going. Sometimes you just need to move – because if you don’t, your ideas, your drive, even your sense of direction gets lost in the dark.

Over time, I’ve stopped expecting everything to feel “right.” Most things change anyway – tools, roles, even people. What matters is re-adapting your mindset. Instead of resisting change, I’ve learned to reshape how I work, think, and contribute – so that even when the system feels outdated, I don’t have to be. That’s how I’ve kept my direction: not by waiting for ideal conditions, but by acting when it’s hard.

What I’ve Learned About Communication:

Communication isn’t what most people think it is. It’s not about talking. It’s not even just about listening. It’s about interpreting – and that’s where things get complicated.

I used to believe that if I phrased something clearly, it would be understood. But like Chomsky said, language isn’t just structure – it’s a system of infinite possibilities filtered through limited understanding. And most of the time, people don’t actually listen. They prepare a response. Or they hear the surface but miss the signal.

Working in tech taught me that communication and code have a lot in common. If your interpreter is off – whether it’s a backend compiler or the mindset of a teammate – you get bugs, delays, misalignment. The same sentence can mean different things depending on the ‘system’ it lands in. That’s why I try to build context, not just content.

I’ve also learned to ask questions, even the “stupid” ones. My back already hurts from trying to sound smart. And honestly? I’d rather ask 1,000 clarifying questions than live in a beautiful misunderstanding. Because clarity isn’t just efficient – it’s human. And in a world where language constantly fails us, the effort to understand each other is a kind of miracle in itself.

What I’ve Learned About Personal Growth:

Growth doesn’t always look like a skill checklist. Sometimes it’s about unlearning – how to slow down, how to explain your thoughts better, how to let go of “perfect” and make space for clarity.

When I joined EBS, I was focused on delivery. I wanted the output to speak for itself. But I’ve learned that personal growth isn’t just about what you create – it’s about how you connect that work to the people around you. Whether it’s looping in the BA team early or simplifying something technical for a non-technical audience, I’ve become better at building bridges – not just blocks of text.

I’ve also shifted from just “writing for conversion” to understanding systems, user flows, and the architecture behind a product. That mindset shift – from execution to strategy – changed how I contribute. It’s not just about the words anymore. It’s about how those words fit into a larger system.

And maybe the biggest growth? Realizing you can be good at your job and still not know everything. That’s not weakness – it’s space to evolve.

What I’ve Learned About Mistakes:

One of the most important mistakes I’ve made was assuming that good work speaks for itself. That if I just poured in the hours, researched thoroughly, and delivered with care – it would be seen, understood, and prioritized.

But I learned the hard way: even great work can get buried if it’s not championed. I once built a whole structure – a feature vision, UX, wording logic – that quietly died on a backlog because I hadn’t involved the right people early enough. I was frustrated, but the real mistake wasn’t the time I invested – it was staying silent when I should’ve explained the value.

Since then, I’ve learned to speak up – not to defend myself, but to connect the dots between what I create and the goals we’re chasing as a team. Mistakes like that hurt, but they shift your posture. They remind you that work is not just craft – it’s context, timing, and advocacy.

Now, I take more credit – but also more responsibility for how my ideas travel. Silence is not humility. It’s a risk.

What I’ve Learned About Innovation:

Innovation isn’t always a eureka moment. Sometimes it’s quiet. Sometimes it looks like simplifying something that was unnecessarily complex. Other times, it’s about spotting the obvious thing no one noticed – because everyone was too busy chasing what looked “new.”

Working in tech made me realize innovation isn’t just about invention – it’s about relevance. You can build the most advanced tool, but if no one can use it, it’s just noise. As a copywriter, I try to bring clarity into that space between complexity and usability. That’s where real innovation lives: in how something is understood, not just how it’s built.

I stay creative by observing – not just users, but systems, gaps, timing, resistance. I also steal from everywhere: philosophy, architecture, bad UX, failed ideas. Everything has a pattern. The challenge is decoding it.

For me, innovation is like writing a sentence that finally clicks – not because it’s clever, but because it unlocks something bigger. That moment where form and function align. That’s the magic. And I’ve learned that if you build with that in mind – no matter your role – you’ll always be contributing to something innovative.