5 Simple Hacks to Build Influence as a PMM
Get everyone to do the work for you.
A simple but powerful hack for building influence as a PMM is learning how to get teams to work with you instead of feeling like they are being dragged into your work.
As a product marketer, so much of your success depends on people you do not directly manage.
You need product managers to share context, prioritize the right features, and help you understand what is actually being built.
You need sales teams to share objections, customer insights, competitive feedback, and what prospects are really saying on calls.
You need designers to bring campaigns, landing pages, decks, and product visuals to life.
You need executives to approve direction, align on positioning, and trust the strategic decisions behind your launches.
You need customer success, support, content, growth, and sometimes even finance or operations to help make the work stronger.
But the tricky thing is that these people already have their own goals, deadlines, meetings, blockers, and priorities, which means your launch, campaign, messaging project, or positioning work may be incredibly important to you but still feel like “one more thing” to them.
This is why PMM influence is not just about being strategic, creative, or good at writing positioning docs.
It is about making people understand where they fit into the work, why their contribution matters, and how helping you also helps the business move forward.
Here are my 5 simple hacks for gaining more influence as a PMM
1. Offer options instead of forcing one answer on everyone.
For example, instead of going to executives or product teams with one version of website copy and expecting them to approve it immediately, it is often more effective to bring two or three strong directions and explain the thinking behind each one.
You can say something like, “Option one is more conversion-focused and speaks directly to the pain point we keep hearing in sales calls, option two is more category-building and helps us position the product more strategically, and option three is simpler and clearer for first-time visitors who may not understand the product yet.”
This kind of approach makes collaboration easier because people are no longer reacting blindly to your work or trying to rewrite everything based on personal preference.
They are choosing between strategic directions, which gives them a role in the decision-making process and makes them feel included rather than overruled.
2. Explain the value of the work before asking people to commit their time, energy, or resources.
A lot of PMMs make requests like, “Can you review this by Friday?” or “Can you send me customer examples?” or “Can we prioritize this feature for the launch?” without first explaining why the request matters and what business outcome it supports.
But when people do not understand the value behind your request, it can easily feel like extra work that is interrupting their own priorities.
Instead, you can say, “We are preparing the messaging for the next campaign, and the quality of this positioning will directly affect how clearly sales can explain the product, how confidently marketing can drive demand, and how well customers understand the value of what we are launching.”
When you frame the request this way, people can see that you are not just asking them to help with a random task; you are showing them how their input connects to revenue, adoption, customer understanding, launch quality, or internal alignment.
It also helps to give people some control over how they contribute, because collaboration works better when people feel respected.
Instead of assigning deadlines without context, you can ask, “Based on your current priorities, what timeline works for you to review this?” or “What would be the easiest way for us to get your input without slowing down your current sprint?” or “What level of detail do you think is realistic for this stage of the project?”
This does not mean you abandon urgency or let every project become loose and undefined. It means you create shared ownership by allowing people to shape the scope, timeline, and collaboration process in a way that makes sense for their workload and expertise.
This is especially important when working with product managers, because PMMs often need product support but can easily come across as if they are only asking for more features, more context, more documentation, more demos, or more time.
If you want a product manager to take your request seriously, do not just say, “We need this feature,” or “Customers are asking for this,” or “Sales said this is blocking deals.”
3. Show the DATA first.
Bring the customer feedback, the sales call notes, the support tickets, the competitor examples, the drop-off data, the revenue risk, the adoption gap, or the launch dependency that explains why the request matters.
A stronger way to approach the conversation would be, “We have heard this objection in several sales conversations, it is showing up repeatedly in customer feedback, and it seems to be affecting how confidently we can position this use case in the market, so I believe it is worth exploring how this should influence the roadmap or at least be addressed in our messaging.”
That kind of framing is more effective because you are not positioning yourself as someone who is simply demanding product or positioning changes. You are acting like a strategic partner who is bringing market evidence, customer context, and business reasoning into the conversation.
4. Give people a clear role to play
Remember that people usually do not care about your work as deeply as you do, especially when its not clear what role they are supposed to play. They are often carrying their own responsibilities and may not remember all the context you have been living inside for weeks.
This is why it is your job to make the context easy to understand, repeat it when necessary, and give people a clear role to play in the success of the work.
If you need sales input, do not just say, “Please send me feedback.”
Say, “You are closest to the objections prospects are raising, so your role here is to help us make sure the messaging reflects what buyers actually care about before we take this campaign live.”
If you need product input, do not just say, “Can you review this?”
Say, “Your role here is to help us make sure we are not overpromising, simplifying the product incorrectly, or missing the strongest technical value in the story.”
If you need design input, do not just say, “Can you make this look better?”
Say, “Your role here is to help us make the value feel clear, credible, and visually strong enough for the audience we are trying to convert.”
When people understand the specific role they play and how that role affects the outcome of the project, they are much more likely to contribute thoughtfully instead of treating the work as a box to tick.
5. Share Impact & Appreciation
It is one thing to say, “Thanks for your feedback.”It is more powerful to say, “Your feedback helped us simplify the homepage copy, and that made the value proposition much easier for first-time visitors to understand leading to higher quality conversions.”
It is one thing to say, “Thanks for reviewing this.” It is more useful to say, “Your product review helped us catch a claim that could have created confusion for customers, so the final messaging is much more accurate because of your input.”
It is one thing to say, “Thanks for sending the sales notes.” It is more meaningful to say, “The objections you shared from recent calls helped us rewrite the campaign angle around the actual concerns buyers are raising, instead of the assumptions we started with and this was the result.”
When you call out the positive effect of each person’s contribution, people do not just feel thanked; they see the impact of their work.
That matters because people are more likely to contribute again when they understand that their input was useful, visible, and genuinely valued.
After a launch, campaign, website update, sales enablement project, or messaging refresh, go back and tell people what changed because of their involvement.
This kind of appreciation makes people feel like contributors to the win rather than background support for your work. And over time, getting their support becomes so much easier.
The best PMMs are not just good at launching, positioning and messaging products externally.
They are good at messaging the work internally in a way that gets people aligned, invested, and moving in the same direction.
Your PMM friend ✌️
Peace