Making the program without adequate sales buy in or guidance.
There's an important balance to strike here: The product marketer should be focused on anticipating the needs to a sales team and solving the problems at hand, rather than reactively responding to inbound requests from the sales team. That means you can't execute on everything your sales team requests the exact way that they want. But that doesn't mean your sales team shouldn't help shape what your enablement program looks like. If they don't, the program becomes something you made yourself that you're asking sales to execute on, rather than something that they're creating with you and committed to.
I've seen product marketers put a lot of hard work into an enablement program and roll it out to the sales org, only to get a lackluster response or, worse, hear about all the ways it won't work for the team. The issue here is not that the marketer created a poor program, it's that they didn't put the work in up front to get sales leads onboard with the plan or get enough feedback on the program to ensure it'll work for the team. To get into the brass tacks, the process that I've seen work well is something along the lines of:
- Loop in sales leads just as you start thinking about your program to talk about goals and listen to their needs and insights. This way, you're shaping the idea and focus behind the program but still getting their thoughts and feedback on priority, pain points, structure, etc that will help you create a program that works well. This meeting should be mostly you asking the leads questions and bringing up topics for discussion, not you showing a full plan that you've already made.
- Once you've taken that feedback and turned it into a plan, get back in a room to discuss and get their thoughts. That way, the sales leads can pinpoint any problems in your plan and give feedback before you start executing. It also has the added benefit of truly making them stakeholders and making them feel like you're listening to their feedback. The more inovlved they are, the more it's on you and them to make the program succeed together.
- When you're starting to execute on work and have drafts of deliverables, make sure that key sales contacts are reviewers on the materials. That way, you can pinpoint any feedback or edits early so you can talk about it, make changes or explain your POV before you're trying to roll it out to the broader team. No one likes watching a sales person's hand go up while you're just starting a program rollout with feedback or thoughts that could have helped 5 weeks ago but are no longer helpful. Get that feedback here, and get it from the right sales leads.
- To launch the program, have a sales lead help with the team rollout. That can be them introducing the program before you talk through it in specifics to talk about why this is so important and help the team feel like this is something they need to buy into or sending an email after the training reinforcing how important this program is for the team. I had a sales lead once reply all to an email I sent saying "If you do not do this, you will not make President's Club, guaranteed" - turns out, people really bought into that program :) No matter how skilled and sly a product marketer is, a sales team is always going to listen to their lead more than they'll listen to you. If you can get them to be the one to say 'Hey this is important, we've put work into it, and we feel strongly about this program' it makes your life way easier.
- Get continuous feedback on the program. Make clear that you'd like sales feedback on how the program is working (and make clear how you'd like that feedback delivered so you're not fielding desk drive bys or a million Slack messages about it). Set expectations about what you'll do with that feedback, and discuss it with your sales leads. Sales teams should feel like they have enablement that works for them but that doesn't work if you give them a program and then walk away from it. You don't need to do every single thing that a sales person asks of your team, but you DO need to make them feel heard and give them a forum to make suggestions. Turns out, some of the suggestions can be really useful.