“Where It Began, I Can't Begin To Knowing. But Then I Know It's Growing Strong” - My Path Into Product Management

Song Inspiration - “Sweet Caroline” by Neil Diamond

I became a product manager years before I actually ever held that title.

In this blog post, I want to share my journey into product management, exploring the reasons why I love this field and the impact it has had on my professional and personal growth.

No, I did not study to become a Product Manager

I did not take a professional course to become a product manager. I am Pragmatic Marketing (Level 2) and am a certified Pragmatic Certified Product Manager Badge; but I took those courses after I was already working in Product Management.

For what it’s worth, I was a Computer Science major my first year of college before switching to International Relations. Product Management was definitely not on my radar then, or even when I graduated. The first time I heard of the role, it was in San Francisco in 2013 - in the context of tech careers after I graduated from business school. The career path seemed to be - Engineering undergraduate and/or Masters, and MBA = Product Manager. I had an MBA - but was not an engineer. I shrugged it off - joined a startup where I wore multiple hats and carried titles of “Business Development” or “Strategic Analysis”. But at the center of my work was understanding the art of building something users wanted and would pay for, and the science of how to match those needs with engineering experiments. I would brainstorm demo concepts - working with the development teams how to present our prototype. I would work with users to help them grasp the novelty of our new product, and how to ensure their experience with it was seamless and delightful.

When I left the startup world three years later, I decided to gain more experience by working at businesses that had already established an estabilished product. and were seeking growth and expansion while keeping their core product. I was properly introduced to the world of B2B software products – where user experience was not necessarily the most important trait of a successful software, as much as the ability to sell the software to the users with the greatest pain. Process simplification, historical record keeping were the critical components of success. Because of my previous titles of “Business Development”, the jobs offered to me were primarily in Product Marketing. I enjoyed it very much — but after years of pitching to startup investors and business partners, I felt left out of the action. I wanted to actually be out in the field, talking to customers, and selling them on the value of the product.

While startup pitches and enterprise sales require one to be bold and clear, they have fundamentally different processes. A big challenge I faced in my deals was bringing different departments within a client organization together to sign enterprise-wide deals. I observed how decisions on enterprise software products were often finalized by one part of a business that may have no idea of the realities of the department that actually ends up using that system.

My work in policy gave me the perspective to approach software sales and development in a way that broke those silos, and connected different teams towards the same end-goal. I was proud to have a record number of closed deals for a rookie. However, the same sales experience also brought out my inner problem-solver. I was a proactive relationship builder with my clients - getting into the weeds with them, probably a bit more than the average SaaS account executive would. But I knew I needed to bring in the real experts too. So, I began to work closely with our product management teams in gathering requirements for improvements or new features. I found myself drawn to the strategic aspect of product management, where I could use my technical knowledge to identify market opportunities and develop innovative solutions.

The timing also favored me because of the growing emphasis on platforms and integrations, and the trend of self-service, user-friendly product onboarding within enterprise products. Suddenly it mattered less to have an engineering major, as much as a customer-centric go-getter, who was willing to learn something new every day. So after working in enterprise sales and marketing for about two years, I found myself welcomed into product management. And it really did feel like home.

But was it San Francisco, or did it all really begin in DC?

One of the aspects of product management that I love most is the opportunity to work cross-functionally with teams from different disciplines. Whether collaborating with engineers to bring a new feature to life or working with designers to create a compelling user experience, I thrive on the diversity of perspectives and ideas that this role offers.

Another reason why I enjoy product management is the opportunity to have a real impact on the world around me. By creating products that solve real problems for users, I feel like I am making a tangible difference in people's lives, which is incredibly fulfilling.

Looking back though, the most challenging experiences I had in building collaboration while working with different teams was in Washington D.C. Most people working in D.C. are driven by a mission and promise for change. Could it have been the years of working with agencies and elected officials to pitch and drive consensus - to find the smallest thing in common to push for innovation and progress ? Could my time working in policy have actually set me on the path of product management?

Where I am now

My Product management career has has been driven by a passion for innovation, a love of collaboration, and a desire to make a positive impact. I am grateful for the opportunities that this field has afforded me and look forward to continuing to grow and learn as a product manager.

Today I coach and mentor aspiring product management professionals who connect with me via Linkedin. I am also the host of a Product Management podcast “Product Talk” where I love to interview Chief Product Officers, Product Management and Technology leaders, and even Startup Founders about their career journey. I started this blog “Product Notes” to document my experiences and observations so that others may benefit. I work with anyone who is serious about taking their idea to reality.

I once believed the Product career path was not for me. I was wrong, and others helped guide me to my first Product role. I want to create a splash, a massive ripple effect. I thrive in helping others think more broadly and creatively about what a career in building, and launching products may look like for them — no matter where their career journeys began!

Previous
Previous

“Will They Tell Your Story” -Understanding User Stories for Product Development