Sean Lauer

Before launching a product, it's important to conduct thorough testing and validation. Gathering feedback from the target audience can reveal valuable insights that can be used to improve the product. When collecting feedback, focus on product functionality, overall experience, and perceived value. * Closed alpha or beta tests with a select group of trusted customers or partners can uncover bugs, usability issues, or potential enhancements. It's important to include participants with a diverse range of user personas to capture different use cases. * Conducting pilot programs or limited releases can provide insights into longer-term product use and value. This involves allowing potential customers to use the product in real-world scenarios, often at a reduced price or for free. It's important to gather feedback not only on technical aspects, but also on users' understanding and perception of the product's value proposition. This information can inform marketing and sales strategies. Maintaining open communication channels with participants, acknowledging feedback, and demonstrating responsiveness can help build trust and transform early testers into product champions upon launch.

When entering a competitive market, it's crucial to carefully evaluate your launch messaging to ensure maximum impact. There are three key factors to consider: 1. Clarity and relevance - your message must be clear and address the primary pain points of your target audience. Avoid jargon and buzzwords that may confuse your value proposition. 2. Differentiation - it's important to clearly articulate what sets your product apart from your competitors, highlighting unique features or benefits. 3. Resonance and memorability - your message should emotionally connect with your audience and be memorable, leveraging relatable stories or scenarios. By effectively incorporating these three factors, you can increase your product's visibility and desirability in an already crowded market.

As the first Head of PMM in a startup, you should use a structured approach over your first 30, 60, and 90 days: * Day 0-30: Learning & discovery—Focus on learning as much as possible. Don't worry about your impact at this point. It's your job to learn in order to make more informed decisions and build an effective plan. * Key actions: * People * Familiarize with company tech, culture, people * Stakeholder and customer conversations * Meet and assess marketing team * Understand sales, marketing, and product roles and responsibilities * Establish rhythm of business & team culture Product * Product and metrics deep dive * Understand customer journey * Analyze marketing data and effectiveness * Market & competitor analysis Plan * Review existing sales and marketing materials and strategy * Day 31-60: Strategic planning & alignment—Now that you have a basic understanding of the landscape, it's time to start thinking about strategy and diving deeper into the GTM motion. * Key actions: * People * Ongoing customer & stakeholder conversations Product * Further market & competitor analysis * Examine tech stack and operations Plan * Assess marketing objectives * Evaluate resources (people, tech, budget) * Understand revenue model * Day 61-90: Execution & optimization—It's time to start creating some small wins as you build toward a more comprehensive strategy. * Key actions: * People * Celebrate team wins and reinforce culture Product * Additional customer conversations Plan * Optimize existing PMM efforts * Upgrade tech stack * Monitor revenue model * Key deliverables by day 90 (draft or final state): * Ideal Customer Profile (ICP) * Positioning and messaging framework * Product release process, including tiering structure * Customer testimonials/quotes * Competitive landscape overview * Website and core asset inventory and analysis * Plan for next quarter

There's nothing that says gathering intel in standard ways isn't ethical or fair. There are definitely some tactics that might straddle the line and a few that go way over the line that should obviously be avoided. I would rely on approaches that are very common, ethical, and effective: * Win/loss interviews * Seller interviews * Analyst inquiries * Analyst category/industry analyses * Investor resources * Using competitor products (if possible) * Competitor websites * Competitor community forums * Industry community forums * Social media * YouTube * Media reviews This is just a start, but there are many ways to gather intel that will work no matter your product. Also, check out a product like Crayon that will help you supercharge your efforts if you have limited capacity.

When managing a PMM team that covers multiple products or is matrixed, high-level or aggregate metrics are key. While more granular data may be needed to drive specific metrics, you need to measure the team at a higher level to measure overall team health. By looking at team-level metrics, leaders can get valuable insights into how their PMM team is doing. Here are some examples: * Team NPS (by internal stakeholder groups) * Adoption of new features * Product usage (DAU or MAU) * Customer retention * Lead gen and/or conversion rates * Sales revenue and growth Then measure at the team level and drill down to understand drivers. A mix of high-level and granular metrics gives you a complete view of the PMM team’s performance so you can see the impact of your strategies and initiatives across the business while also zooming in on areas that need attention and optimization. By using these metrics PMM teams can align to company goals, drive real outcomes and continuously add to the company’s success. When showing the impact of a PMM team through these metrics there are a few approaches: * Regular reporting through a single source of truth or dashboard (i.e. Google Sheet, Slides, Notion doc, etc.) * Case studies and success stories to make it more concrete * Customer research and reporting to quantify the impact beyond the metrics * Education to explain how PMM impacts the customer journey and company direction

Once you see messaging that was created with AI, you start to see it everywhere. There are also tools that allow you to scan messaging to determine if it was written with AI (so it can be confirmed). It's placed even more importance on the ability to speak to your audience as a human would speak to them. Words and phrases that don't sound like typical spoken language when you read them out loud are going to feel AI-created and forced. If you want messaging to land, speak it before you write it. That's the best way to prevent yourself from sounding like a robot!

When setting up a PMM team consider: * Who is the product for and is it a single use case or multiple audience’s * Do you need deep technical knowledge to understand and market the product * The product management team structure * The sales team (or lack thereof) * The current and future marketing functions in the company * What drives the product growth, is it sales, marketing, the product itself or a combination of these, Product-Led Growth (PLG) or Sales-Led Growth (SLG)

A lot of people will sum up the role of PMM as "the voice of the customer." However, this explanation falls short of clearly defining swim lanes and also crosses into other areas like customer marketing, content marketing, research, etc. In my opinion, the simplest way to describe the PMM role is "the voice of the product." Here's why: * As the voice of the product, you need to be focused on both the inbound and outbound sides of PMM * As the voice of the product, you need to be the connective tissue amongst all teams that touch the product or sell the product * As the voice of the product, your role is more clearly defined when working with other marketing stakeholders—PMM drives or is the approver of work related to the voice of the product

When managing a PMM team that covers multiple products or is matrixed, high-level or aggregate metrics are key. While more granular data may be needed to drive specific metrics, you need to measure the team at a higher level to measure overall team health. By looking at team-level metrics, leaders can get valuable insights into how their PMM team is doing. Here are some examples: * Team NPS (by internal stakeholder groups) * Adoption of new features * Product usage (DAU or MAU) * Customer retention * Lead gen and/or conversion rates * Sales revenue and growth Then measure at the team level and drill down to understand drivers. A mix of high-level and granular metrics gives you a complete view of the PMM team’s performance so you can see the impact of your strategies and initiatives across the business while also zooming in on areas that need attention and optimization. By using these metrics PMM teams can align to company goals, drive real outcomes and continuously add to the company’s success.

Ideally, your narrative should actually be doing the heavy lifting when it comes to differentiation. Features can easily be copied. As this question states, it often leads to products being essentially the same across a competitive set. The components of your narrative—the story and the reason why your product exists—can be the difference maker in conversations with prospects. What does your product stand for? What is the driving force behind your product strategy and the value you want to create for users/customers? You may have the same features as a competitor, but my guess is you don't have the same vision for solving your customers' problems. When that vision resonates with more customers, you'll find that it can make the difference between winning and losing.