Resources > Articles

The Key Hard and Soft Skills for Product Marketers

Skills for Product Marketers

Skills for Product Marketers

 

The role of soft and hard skills is a hot management topic. But few articles or texts provide relevant information for a specific profession.

Enter Christy Hecht’s real-world description of interconnected skills—three soft and six hard—for PMMs in an AMA via Sharebird, the place to see how people at top companies do product marketing. Hecht is the director of product marketing at Envoy, a privately held, 150-employee visitor management software company in San Francisco.

“There are nine skills that are the most important for a product marketer to have,” Hecht said. “I’ve used these skills as a compass to help me grow in my own career and have turned them into a success guide for my team at Envoy.”

 

Soft Skills

Cross-functional excellence

“As a PMM, you have the opportunity to lead without being a manager of people. A strong product marketer is someone who takes others along with them, rather than telling people exactly what they want them to do. They’re able to create strong relationships across the company, with product managers, engineers, designers, marketers, support folks, and more. They’re natural connectors who know who to go to in an organization to get things done and can influence cross-functional stakeholders to support and prioritize projects.”

Executive presence and clear communication

“As you get more senior, you’ll spend more and more time presenting plans, public speaking, and communicating with executives in the company. Executive presence also means knowing how best to leverage an executive’s skills to get feedback that will help your project, manage their expectations, and ensure they feel like they’re in the loop about work that matters to them.”

A pitch-in, get-it-done attitude

“Being a PMM can be unglamorous at times. Sure, you get to run the big launches, but what people don’t see are the hours you spend writing support macros to ensure the team has what they need to answer incoming tickets, the amount of times a day you have to field seemingly random requests that don’t always fall neatly into your scope of work and how often you get looped into last-minute, urgent projects that you didn’t plan for.

PMMs who can approach this type of work ready to pitch in and help are often those that are seen as the most dependable and trustworthy, which helps them create strong relationships across the company. I’ve always made sure I’m never above doing the grunt work that’s needed to get something across the finish line. While I don’t do it every day, I’m happy to roll up my sleeves to take a screenshot for a help article or write a macro if it means the team will be more successful. I reward members of my team that have the same attitude.”

 

Hard Skills

Market, competitor, and product expertise

“PMMs should know their product inside and out, be an expert on its features, capabilities, and limitations, and be able to help partner teams figure out solutions to customer problems. This takes work, and it shouldn’t be overlooked. On top of that, you should know your competitors’ products almost as well as you know your own. What does the competitor’s product have that yours does not? Where do you lose? Where do you win? How do they position themselves? These are all questions you should have an answer to. Last, you should know your market. What are the trends in the market in which you operate? What are the factors that influence decision-making for your buyers? What’s coming down the line in terms of regulations or industry shifts that your company might want to get in front of? The better equipped you are to answer these questions, the more strategic value you’ll bring to your company.”

Positioning, messaging, and storytelling

“This skill is all about being able to create tight, clear, compelling messaging frameworks that identify the target customer, nail their pain point and the benefits your solution provides, and clearly explain how you’re different than what else is on the market today. A leader I used to work for said, ‘The person who most accurately identifies the problem earns the right to solve it.’ That’s a really clear articulation of how specific and focused you should be in your messaging. You always know when a messaging framework is ready for prime time when you would defend every single line of copy, are able to explain why each line is necessary and can show how each phrase ties back to the feature or product itself.”

Know your customer

“There are two parts: First, knowing your personas. Specifically, you should be an expert in who buys your software, what their titles are, where they sit in an organization, what matters most to them, and how to market to them; and second, connecting that customer persona with actual customers who use your product. If you’re not talking to customers throughout your day-to-day, how can you represent the voice of the customer to the product team? I have OKRs (objectives and key results) for my team to have a certain number of interactions with customers each quarter to make sure that customer empathy doesn’t get lost in the shuffle. The key is getting these customer insights and then doing something with them to make sure that those insights are driving your roadmap and activities.”

Go-to-market planning and execution

“PMMs are responsible for creating unique, impactful, cross-channel GTM (go-to-market) plans that will help your product or feature hit its launch goals and drive sustained adoption and revenue. PMs should understand which channels drive success and identify the metrics they want to move so they consistently hit their goals. Another aspect is studying how other companies run their launches and taking inspiration from that for your own launches to up-level your approach.”

Process management

“It’s often said that PMMs should act as the quarterbacks to a launch. A big part of this is ensuring there’s a process in place within the marketing team and with partner teams in order to make sure that everyone has the information they need and clarity on what’s expected of them to make the launch a success. If there isn’t a process in place, it’s up to the PMM to create and drive new processes to fix problems. It’s also up to PMMs to point out when a process is no longer working for your team.”

Making data-driven decisions

“I wouldn’t call myself a numbers person and I don’t think you need to have the data skills of an analyst to do the job. That said, I do think you need to understand your company’s baseline metrics, be able to pinpoint the data that would help the team make a decision, and back up your plans and initiatives with data that supports your proposal in order to succeed in your role and provide value to your organization.”

Author:

Other Resources in this Series

Most Recent

The image features the term use scenario being revealed underneath a ripped piece of paper
Article

What is a Use Scenario [ +7 Examples]

The purpose of drafting use scenarios is to help your development and design teams to start thinking about solutions. Context is the foundation of innovation, and you’ll be providing a tool that will be the starting point for collaborative and productive meetings.
Article

[Comprehensive Guide] Product Owner vs Product Manager

Learn how to separate the roles of product owner and product manager on Agile teams and uncover some common challenges with confusing these roles. Including a short primer on the Agile revolution.
Article

Use Scenarios are Stories That Provide Context

The problem with today’s user stories is that they aren’t interesting. And they aren’t stories. The solution is use scenarios. It’s a narrative. It explains the problem in the form of a real-life story.
Article

Benefits of Bundle Pricing

Bundle pricing is simply a strategy where services or products are packaged together for one (often reduced) price rather than priced separately. This article covers some benefits of bundle pricing followed by a system for getting started.
Article

A Quick Guide to Value-Based Pricing

Value-based pricing begins with knowing the customer’s willingness to pay based on the perceived value of your product. You can charge less than a customer’s willingness to pay, and they feel like they’ve received an

OTHER ArticleS

The image features the term use scenario being revealed underneath a ripped piece of paper
Article

What is a Use Scenario [ +7 Examples]

The purpose of drafting use scenarios is to help your development and design teams to start thinking about solutions. Context is the foundation of innovation, and you’ll be providing a tool that will be the starting point for collaborative and productive meetings.
Article

[Comprehensive Guide] Product Owner vs Product Manager

Learn how to separate the roles of product owner and product manager on Agile teams and uncover some common challenges with confusing these roles. Including a short primer on the Agile revolution.

Sign up to stay up to date on the latest industry best practices.

Sign up to received invites to upcoming webinars, updates on our recent podcast episodes and the latest on industry best practices.

Subscribe

Subscribe

Training on Your Schedule

Fill out the form today and our sales team will help you schedule your private Pragmatic training today.

First Name*
Last Name*
Email Address*
Phone
Company
Job Title
Location
How can we help you?
Preferred method of contact
Privacy Policy*
Map Your Message to Its Audience with the Communication Compass
Map Your Message to Its Audience with the Communication Compass
Ensure your message hits the mark. This eBook helps you visually map communication styles so you can tailor your design story to a stakeholder or business partner.

Download Ebook

Demystifying Data Projects: A Guide for Business Leaders
While data science is a competitive advantage, data isn’t magic. Learn how to make magic happen by partnering more effectively with data professionals. This eBook delves into types of data projects, sample questions, tools and methods, key points and cautions—so stakeholders like you can initiate data projects with real business impact.

Download Ebook

Define Ebook Thumbnail
What’s the difference between a successful data analysis project and one that falls flat? 

Before you begin working with the data, you need to understand what you’re solving for. Gathering context and aligning around goals with your stakeholders from the outset will help you avoid disconnects and deliver actionable insights. Discover the most vital questions to ask before embarking on a data analysis project in our in-depth guide, “Define: Laying the Foundation for Successful Data Analysis.”

Download Ebook

Download Now