It's rare to meet anyone in this industry who wanted to work in product management at age seven. We all fell in sideways, and the sideways part is usually where the actual skill was hiding.

I have an undergrad in musical theater performance and a master's in jazz – my research was on using vocal improvisation to build communication between expat women, refugee women, and local Dutch women. Today I'm the Director of Product Operations at Solovis. Nobody plans a path like that

We talk about "product" and mean "product manager," but that's a fraction of the org. There's product marketing, product ops, design, research, technical writing – none of it requires the PM title, and all of it requires knowing how you actually operate, so you land in the right seat instead of just any seat.

Three archetypes show up again and again. Keep reading to learn which one you're already living as.

The builder: Creates from scratch

Builders start with a blank page and make something that didn't exist before. They're wired for ambiguity and are genuinely energized by it.

You'll see this in the early-stage PM defining the product and the process at the same time. In the UX designer handed a brand-new surface with zero existing patterns. In the technical writer documenting a product while it's still changing shape underneath them. Builders love a whiteboard. Tell a builder "nobody's tackled this before" and watch them light up.

How it shows up for me: I wrote a book with a friend. I worked as a travel writer across a handful of countries. I built a rock band from scratch in New York City, and then again in Colombia. I moved back to the States and rebuilt my entire life from zero as a single mom – new city, new job, new everything.

Professionally, that translated directly: as a technical writer, I built two help centers from the ground up for products that had no real documentation at all – structure, articles, the whole thing. Then I layered in-app guidance on top using our analytics tooling, so users actually found what I'd built. That work eventually grew into defining full product processes and early adopter programs.

If you've ever built something from absolutely nothing, you already know if this is your zone.

The scaler: Drives growth and reach

Scalers take something that already works and figure out how to make it work for more people, faster. They think in growth curves: activation, retention, expansion into new markets.

A growth PM staring at a drop-off chart is a scaler. So is the senior PM who inherits a working product and pushes it further. So is the product marketer who cracks the message for one segment and then stretches that same narrative across five more. Product ops often gets hired specifically for this moment – a company hits a certain size and suddenly needs someone to standardize the chaos before it breaks something important.

How it shows up for me: I worked with a small music education program in New York and scaled it across new segments and new countries. I took my own music brand and put it on a national tour.

In product ops now, scaling looks like templates – good ones, the kind that let a whole org move faster and more consistently without me in the room. I lean on AI hard for this too, to scale my own output and synthesize information faster than I could alone.

The trick with scaling is staying creative inside the standardization – building a framework loose enough that people can still iterate. Taking an onboarding program and making it self-serve so it can absorb a growing headcount is a textbook version of this.

The force multiplier: Elevates everyone around them

Force multipliers change what the whole team is capable of. They're architecting the operating system the entire org runs on: the rituals, how data surfaces, how decisions get made, how team health gets watched. Once that's in place, everyone performs at a level they couldn't reach alone.

Product ops lives here a lot of the time. So do product-aligned program managers, and honestly, so does good leadership – a great leader is just a force multiplier with a title.

How it shows up for me: I founded Fort Wayne Women in Tech, and that's when this shift actually happened for me. I stopped wanting the spotlight and started wanting to build the stage.

Every time I connected someone who needed an opportunity with someone who could open the door, it felt like magic – women getting promoted, landing new jobs, pulling each other up behind them.

The community became its own engine, generating momentum and clearing blockers without me having to touch every single one.

The real test of a force multiplier: could the thing you built keep shipping if you disappeared tomorrow? If the answer's yes, you've done it right.

Which one are you?

There's no ladder here, no required order. You don't have to be a builder before you're allowed to scale, and you don't have to scale before you're allowed to multiply a team's force. The only thing that matters is what you actually enjoy doing – that's what tells you where you'll do your best work.

Look back at your own career. Find the moment you built something from zero. Find the moment you took something working and made it work for way more people. Find the moment you changed what your whole team was capable of. 

Those moments are your story, and your story is what gets you into the room you actually want to be in.

Taking the next step

Getting to your target role takes real focus, not vague ambition. Put yourself in rooms where people can get to know you – communities do a lot of this work for you, if you let them.

Read the foundational stuff – Marty Cagan, Melissa Perri, Teresa Torres. Listen to product podcasts, scour product publications and resources (like the ones you see here on the Product Led Alliance site) – so you have the vocabulary and the strategic context when you need it. 

And be honest with yourself about the real obstacle: most people don't fail to grow because they lack ambition. They fail because operational work eats every open hour on the calendar.

So block the time. A week out, minimum. Tell your manager what you could do with real focus hours, and then defend that time like it's a client meeting – because it is. It's a meeting with the version of your career you're trying to build.

Looking for more career advice from those who've been there, done that? Join our Slack community of 15k+ product professionals and share network with product leaders around the world.

Join the community