What it feels like to move from product management to product marketing

what-it-feels-like-to-move-from-product-management-to-product-marketing

What it feels like to move from   product management to product marketing

My first real experience in product management (PM) did not come from a perfectly defined product manager role. It came through a freelance project with a Boston-based client while I was still early in my career and working as a software engineer. 

I spent close to a year on that project alongside my full-time job, working with a team of about 15 people across seven time zones. I made mistakes, probably overcomplicated a few things, and learned how difficult alignment becomes when everyone has a different context, as it was my first PM role. 

Somewhere in the middle of all of that, I realized that I genuinely enjoyed product work because I always questioned why I was building this, or why one should care about this. I liked the ownership, the ambiguity, and the constant problem-solving for customers. 

There was always another question to work through: Why was the user struggling here? What should we prioritize? Was this actually a product problem, or were we solving around the wrong assumption? How do you get design, engineering, and business stakeholders moving toward the same outcome when everyone sees the problem differently?

That experience eventually pushed me further into product. I later joined Airtel in my first formal product role and then moved into startup environments where I had even more ownership. 

For a long time, I assumed the product was where I would stay because I liked being close to what was being built and having influence over the decisions behind it. But over time, I started becoming increasingly interested in a different question. I was used to asking, “What should we build?” and “What problem should we solve?” 

What started pulling me toward product marketing was the question that came after that: Why should the customer care? 

I was also working with PMMs on the team. I realized that you can build something useful and still explain it badly. You can solve a real customer problem and still struggle with adoption because people do not understand the value. That part of the product journey started becoming more interesting to me.

I did not really understand what PMMs did either

I should probably admit that when I was a product manager, I did not fully understand what product marketing managers did. From the product side, I sometimes wondered why PMMs needed so much information about a feature. 

  • Why do you need another conversation about the customer? 
  • Why do you need to know exactly when this is launching? 
  • Why are we talking about positioning already? 
  • Why are you asking again how this is different from the previous version? 

From the outside, what I mostly saw were the outputs: emails, launch communications, content, social posts, sales decks, and customer education. It was easy to assume that PMM was mostly about taking whatever product had built and then figuring out how to market it.

Once I moved closer to PMM, I realized how incomplete that picture was. The email or launch post is just the final output. The harder work usually happens much earlier. Someone has to understand which customer actually cares about the feature, what problem it solves for them, what they are comparing it against, what message will resonate, what objection sales might hear, and whether the feature is even important enough to lead with. 

That gave me a completely different appreciation for all those questions PMMs used to ask me. They were not asking because they wanted another meeting. They were trying to understand whether there was actually a story worth telling and, if there was, what that story should be.

PM and PMM overlap, but the center of gravity changes

The transition did not feel like starting completely from scratch because there is a lot of overlap between PM and PMM. As a product manager, I was already talking to customers, conducting research, understanding pain points, thinking about adoption, working cross-functionally, and participating in go-to-market conversations. A lot of that carries into product marketing too, but the center of gravity changes.

In product management, I spent much more time thinking about whether something should be built, how it should work, where it belonged on the roadmap, and what deserved priority. At Airtel, for example, I was close to enterprise customers and received a large amount of user feedback. 

The questions were often around what needed to change in the product, what was slowing customers down, and which improvement would have the most impact. 

In product marketing, I started looking at the same product from another angle.

  • Who is this actually most valuable for?
  • What do they care about most?
  • What are they comparing us against?
  • Which part of the feature matters enough to talk about?
  • What does sales need to explain it confidently?
  • What should we leave out because it adds complexity without adding value?

Sales enablement was one of the clearest new muscles for me. As a PM, I cared deeply about whether the product solved the problem. As a PMM, I also had to care about whether someone outside the product team could explain that value correctly. 

A product team might spend months building three new capabilities and naturally want to talk about all three. A PMM may look at the same release and realize that only one of those capabilities belongs in the headline. That does not make the other two unimportant. It simply means the customer does not need to carry all the internal context that the product team has accumulated.

I realized I did not want the creative side of me to disappear

There was also a more personal reason why PMM started feeling natural to me. I have always been curious about how products and companies communicate. 

Even when I was more focused on product, I would find myself reverse-engineering things outside of work. I would look at a landing page and wonder why the company had chosen that headline. I would compare two companies solving similar problems and ask why one felt immediately clear while the other required several minutes of reading. I would look at a launch and think about who the company was really trying to speak to.

I loved ownership in product, but I also realized that I really enjoyed storytelling and creative problem-solving. Not storytelling in the sense of making something sound more exciting than it actually is. 

I mean taking something complicated, finding the part that genuinely matters, and explaining it in a way that another person can understand without needing all of your internal context. PMM gave me a way to stay close to the product and the customer without giving up the part of the work where I could shape how the story was told.

The more PMM work I did, the more I realized that creativity and structure were not opposites. You can come up with ten great messages, but you still have to decide which one supports the business objective, which one reflects the customer insight, and which one deserves attention. That brought me back to something product management had already taught me well: prioritization. More on this later.

Internships helped me test whether I liked the reality of PMM, not just the idea of it

One reason I was careful about making the transition was that I did not want to fall in love with a version of product marketing that existed only in my head. I wanted to experience the work in different environments before deciding that this was the direction I wanted to keep moving in. Working across different PMM internships and roles let me see the function at very different stages and scales.

At ABC Fitness, for example, I worked much closer to launches for the Trainzer mobile app, customer education, adoption, and enablement. 

Instead of thinking only about whether a feature worked, I had to think about how coaches would understand it, what information they needed, what message would resonate, and how we could help people actually use what had been built. 

Smaller startup environments taught me something different. When a company is early enough, there may not be an established messaging framework, launch process, enablement library, or perfectly defined ICP. You have to help create that structure while the product itself is still changing.

Those experiences also showed me the less glamorous parts of PMM. Not every day is brainstorming positioning. Sometimes you are rewriting the same sentence because it still does not make sense. Sometimes you are trying to get five stakeholders to agree on one message. Sometimes the product changes close to launch. Sometimes a customer says something that completely invalidates the wording you spent hours working on. I still enjoyed the work. That mattered to me much more than simply liking the title.

Product management changed how I approach marketing now

Now, when I work with product managers from the product marketing side, I notice how much my product experience still influences how I think. The biggest thing is probably prioritization. Marketing has no shortage of things it could do. There can always be another campaign, another email, another story, another channel, another enablement asset, or another launch moment. 

Product taught me that having a backlog does not mean everything belongs in the roadmap, and I think about marketing the same way. Not every feature deserves a major launch. Not every product benefit deserves equal space on the page. Not every customer segment needs the same message. Sometimes the strongest marketing decision is deciding what not to say.

My product background also helps me understand why product managers can be protective of the details. They have lived through the trade-offs, the technical constraints, the edge cases, and the reasons certain decisions were made. I have been that person. 

So when I work with PMs now, I do not want to show up at the end and simply ask them for a list of features to market. I want to understand the problem, the user insight, the reasoning behind what was built, and what changed along the way. At the same time, PMM has taught me when to push back. The customer does not need the full history of how the feature was built. They do not need to know how many Jira tickets existed or how complicated the implementation was. They need to understand what changes for them.

What being on both sides taught me

Having worked on both sides of the table, I now think product management and product marketing are often looking at the same product from different distances.

Product is naturally closer to how something works, what should be built, what the constraints are, and which trade-offs need to be made. Product marketing steps back and asks how that product fits into the customer’s world. For example:

  • What are they comparing it against?
  • What do they already believe?
  • What will make them pay attention?
  • Which part of the value actually deserves to be communicated?

Neither perspective is enough on its own. If PMM only appears once the product is finished, it can easily become a feature-to-content function. If product works without enough market context, a team can build something useful and still struggle to explain who it is really for. 

The best collaboration I have experienced happens much earlier, when PMM understands enough about the product to avoid empty marketing language, and Product stays close enough to the customer and market to avoid assuming that shipping automatically creates value.

For me, moving from PM to PMM did not feel like abandoning product. It felt more like widening the lens. Product taught me how to go deep into a problem, make trade-offs, and decide what deserves to be built. Product marketing taught me how to step back, understand how the market sees that work, and decide what deserves to be said.

I still find myself using both ways of thinking. But the question that ultimately pulled me toward PMM was the one I kept returning to after the product conversation was supposedly finished: Why should the customer care? That is still the question I enjoy working on the most.

If you loved this, connect me on LinkedIn 😄

Total
0
Shares
Leave a Reply

Your email address will not be published. Required fields are marked *

Previous Post
is-gemini-38-flash-a-new-workhorse?-part-2:-priority-inference-and-provisional-throughput.

Is Gemini 3.8 Flash a new workhorse? Part 2: Priority inference and Provisional throughput.

Next Post
should-pmms-turn-into-ai-engineers-now?-a-look-inside-possible-future-scenarios-for-product-marketing

Should PMMs turn into AI engineers now? A look inside possible future scenarios for product marketing

Related Posts