Some things don’t shift until you decide to move. For me, that shift came when I realised that comfort can quietly become a cage. I had built a solid career across people operations, customer success, and project management. I understood systems. I understood customers. I understood execution. But I kept feeling like I was standing just outside the room where the real decisions were being made.
That was how product management found me.
While working in customer support at a fintech company, I saw firsthand how customer complaints translated into product updates. I wasn’t just resolving tickets; I was observing patterns. I was seeing insights. I was noticing how small product tweaks could unlock major value for merchants. One moment in particular stayed with me. A merchant requested a change in their settlement schedule, and I watched a colleague optimise the frequency for them. That was the moment it clicked: I didn’t just want to support the product. I wanted to build it.
Product management wasn’t originally part of my career plan, but curiosity has a way of rewriting plans. I began asking deeper questions about how features were prioritised, how roadmaps were created, and how decisions were defended. Mentors affirmed what I was beginning to suspect — my background in customer success wasn’t separate from product; it was a strong foundation for it.
To build structure around my curiosity, I enrolled in a product management course. The theory was helpful. It gave me vocabulary and frameworks. But it also exposed a gap — there is a wide distance between knowing product theory and practising product ownership. I needed hands-on experience.
That opportunity came through the Women in Tech Internship at Moniepoint. I applied for the Product Management track, unsure of what to expect but certain of what I wanted — proximity to product decisions. When I was accepted, I knew this was the leap out of comfort I had been searching for.
The internship changed everything.
I wasn’t treated like a passive observer. I was given real ownership. Real projects. Real accountability. I was expected to drive outcomes, coordinate across teams, and defend decisions like any other product manager. It was intense, but it was clarifying. For the first time, I wasn’t operating in the background of product decisions — I was shaping them.
Coming from customer success gave me an advantage. I understood users deeply. I knew their frustrations, their language, their behaviours. In fintech, especially in emerging markets, product decisions sit at the intersection of trust and usability. Security must be airtight, but accessibility must remain seamless. Balancing both became one of my most defining challenges.
I found myself optimising onboarding flows, asking tough questions about risk systems, and working closely with engineering and quality assurance teams to improve performance. Product management required me to develop a new level of persistence. Cross-functional collaboration is not automatic alignment. Teams have different priorities, timelines, and pressures. I had to learn to follow up consistently, clarify expectations repeatedly, and influence without authority.
Ownership became more than a buzzword. Projects were handed to me with an unspoken question: Can you handle this? I had to answer not with words, but with delivery. That shift — from executor to outcome owner — was one of the most transformative parts of my journey.
Research became my anchor. Not just reading articles or browsing case studies, but asking people questions. “Has this happened before?” “How did we solve it?” “What are we not seeing?” Staying close to the people doing the work grounded me. Documentation became my growth engine. Every lesson, every misstep, every improvement became part of my evolving playbook.
Being a woman in tech also meant navigating subtle assumptions — that women are better suited to support roles or less technical by default. I chose not to argue with bias. I chose to outwork it. I took ownership. I solved problems. I delivered results. Over time, performance became the loudest rebuttal.
Six months after starting as an intern, I transitioned into a full-time Product Manager role in November 2025. That moment wasn’t just a career milestone; it was proof that stepping back can sometimes move you forward.
If there’s one thing I’ve learned, it’s this: you don’t have to start from zero to pivot. Product management values problem-solving, communication, curiosity, and user empathy. Many of us already carry these skills from roles that don’t have “tech” in their titles.
Sometimes the biggest risk is staying comfortable. I’m glad I didn’t.
And if you’re standing at the edge of your own pivot, wondering whether to leap — start with what you already know. Then build from there.
Leave a Reply