At the start of every new year, people take a moment to reflect on the past. Looking back, 2022 wasn’t just another year for me—it was a turning point.
It was the year I:
📌 Hit my mid-30s
📌 Became a parent
📌 Made a major career shift
📌 Started a new job as a Product Owner
On a personal level, welcoming my child was by far the biggest blessing. But career-wise? Despite feeling “too late” to switch paths, I fully transitioned into a Product Owner role—and it was one of the best moves I’ve made.
But before I get into how it happened, there’s something important to clear up about Product Management in Korea vs. the US.
PO vs. PM in Korea – Why It’s Different
💡 If you’re used to the way Product Management works in the US, you might find Korea’s definitions confusing.
In Korea:
✔ Product Owner (PO) = more like a Product Manager (PM) in the US
✔ Product Manager (PM) = more like a Product Owner (PO) in the US
Why?
👉 The first major Korean company to adopt Agile accidentally switched the two roles when implementing the framework.
👉 Their case studies and books then spread this definition across the industry—and now, it’s the standard.
So, when I say I became a PO in Korea, my responsibilities actually look more like a Product Manager in the US—owning strategy, roadmaps, and cross-functional alignment.
🔹 If you’re an international PM looking to work in Korea, this is something you’ll need to be aware of when job hunting!
Am I Too Late to Become a Product Owner?
If I start talking about my kid, I’ll never stop—so today, I’ll focus on my career transition from business consultant to PO in my mid-30s.
A few years ago, Product Ownership started gaining traction in Korea, and I couldn’t help but wonder:
💭 Can a non-developer become a PO?
💭 Is switching careers in my 30s a terrible idea?
I had no clear answers at the time, but now that I’ve done it, I can confidently say:
👉 No, it’s not too late.
Even though my PO journey is still evolving, one thing is clear: You don’t need to start over from scratch. Instead, it’s about adapting what you already know and applying it in new ways.
You Have More Relevant Skills Than You Think
I started my career as a business consultant, which meant I got my first taste of PO work through internal projects.
At first, I constantly worried:
💭 “I know nothing about this field. Am I setting myself up for failure?”
It was frustrating. There weren’t many resources about how to transition into a PO role, and I didn’t have any mentors in my company to ask for advice.
But once I actually started, I realized that so many of the skills I had developed in consulting were directly applicable.
For example:
1️⃣ Organizational Culture & Mission Alignment
As a consultant, I helped companies define their Mission, Vision, and Core Values. What I didn’t realize back then was how critical this is for building great products.
A product without a clear direction is like a car without a GPS. Understanding how to align a team around a shared mission has been one of the most valuable skills I’ve carried over.
(I’ll probably write a separate post just on this topic.)
2️⃣ Communication & Negotiation
POs talk—a lot. We spend our days aligning teams, getting buy-in, and convincing stakeholders why certain features should (or shouldn’t) be prioritized.
Before working in tech, I did HR consulting, where I ran one-on-one coaching sessions and group workshops. I had no idea that those experiences would one day help me navigate feature prioritization meetings.
A lot of people think negotiation is about closing big business deals. But honestly? It’s more about the day-to-day battles—like persuading your team why Feature A needs to come before Feature B.
3️⃣ Strategic Thinking & Market Analysis
Consultants love frameworks—SWOT, Porter’s 5 Forces, Lean Canvas, you name it.
Back then, I memorized frameworks like my life depended on it. Now? I use them all the time without even thinking. Whether it’s analyzing user data or shaping product strategy, my consulting background has given me an edge in breaking down complex problems.
You Don’t Need to Be the “Perfect PO” from Day One
💡 Product Ownership isn’t one job—it’s many.
Some days, you’re writing a 1-pager or user story. Other days, you’re defining product vision, prioritizing features, or making tough calls on business trade-offs.
Instead of worrying about "Do I have the right skills?", focus on:
✅ Understanding how your product works
✅ Balancing business goals with user experience
✅ Analyzing data to make better decisions
Nobody starts out with every skill. The best POs are the ones who know how to adapt and learn on the job.
Final Thoughts: Age Doesn’t Matter—Your Skills & Mindset Do
💡 If you’re worried about making a career switch in your 30s, don’t be. Even though the culture here in Korea is based on age, it's your skills and mindset that matter the most.
Your past experiences—whether in consulting, marketing, HR, or another field—aren’t wasted. They could actually be your biggest strengths.
Of course, learning product methodologies and frameworks takes time. But if you’re already considering switching into a PO role, chances are you’ve already started the learning process.
Instead of stressing over “Am I too late?”, ask yourself:
👉 "How can I apply my existing skills to product management?"
For me, having a supportive family, mentors, and great colleagues helped make this transition possible. There were definitely tough moments, but looking back, it was 100% worth it.
And if you’re thinking about making this move? I guarantee there are people out there willing to support you too.
🚀 You got this. Let’s go!
What’s Next?
🔹 If you found this helpful, stay tuned—I’ll be sharing more insights on PM life in Korea, work culture, and product strategy.
🔹 Curious about something specific? Let me know in the comments!
💡 In Korea, "Product Owner (PO)" is often used to describe what is typically a "Product Manager (PM)" in the US. Meanwhile, the "Product Manager (PM)" role in Korea is closer to a "Product Owner (PO)" in the US. This terminology swap became widely used due to early Agile adoption. I’ll continue using "PO" since it matches my job title, but know that it refers to a PM-equivalent role in the US.
Comments
Post a Comment