I genuinely think curiosity is my unofficial job title. My brain struggles to accept “that’s just how it works.” If something feels confusing, inefficient, or unnecessarily complicated, I immediately want to know why, who designed it this way? what problem were they trying to solve? Is there a better way?

​

Maybe that’s why I ended up in product management. It’s basically a career where being nosy is actually encouraged. Whether I am working on financial platforms, AI-powered solutions, or helping scientists solve problems in genomics, I am always asking questions; not to challenge people, but because the best products usually start with someone being curious enough to dig deeper.

​

I have learned that behind every feature request is usually a bigger story. A scientist asking for a small workflow change might actually be struggling with a bigger process problem. A customer asking for a new button might actually be asking for a simpler experience. I love uncovering those hidden stories. Basically, I am professionally allowed to ask “but why?” all day, and honestly, it’s great haha.

My brain is constantly playing a game of “connect the dots.” I am the person who can look at a messy problem, a hundred opinions, and a spreadsheet full of chaos and think, “Okay… there’s probably a pattern here.”

​

I have worked on products where the challenge was not just building a solution but aligning users, engineers, designers, business teams, and sometimes people who all had completely different ideas of what “good” looked like. Somehow, my job became translating different languages: turning technical conversations into user value and turning user pain points into things teams could actually build.

​

I still plan everything though. Trips, projects, my week, even what I am eating tomorrow haha. Future me is always grateful that present me occasionally has a plan.

Product has taught me that nothing is ever as simple as it looks. Someone says, “It’s just a small change,” and suddenly you are three meetings deep discussing dependencies, users, timelines, risks, and why the small change is actually connected to twelve other things. 

​

There have definitely been moments where I have looked at a problem and thought, “Wow… this one came with extra seasoning.” But that’s where resilience comes in. I have learned not to panic when things get messy; instead, I grab my imaginary detective hat, start asking questions, and work through it one step at a time.

​

Whether it was moving teams away from manual processes, improving scientific workflows, or helping build products from unclear ideas, I have learned that progress does not always look like a straight line. Sometimes it looks like a few wrong turns, some lessons learned, and a lot of “okay, let’s try this again.”

​

The goal is not to avoid challenges, but becoming the kind of person who can face them, laugh a little, learn quickly, and keep moving.

At the end of the day, I love building things that actually help people. Not just things that look impressive in a presentation deck with fancy words like “innovation” and “transformation”; but real impact.

​

For me, the best part of product is not launching a feature. It’s seeing someone’s day become easier because something you helped create solved a real problem. It’s seeing customers spend less time fighting a process and more time doing meaningful work for themselves. It’s seeing a customer have a smoother experience because someone cared enough to understand their frustration.

​

I am motivated by the little moments where you realise, “This actually made a difference.” Whether it’s improving a workflow, creating better experiences, or helping teams work smarter, I like knowing my work has a purpose.

​

I am not trying to just build products, but build things that people can look at and say, “Yep, someone actually thought about the person using this.” And if I can do that while making a few jokes along the way, even better haha.