LinkedIn Post Ideas for Product Marketers

We A/B tested two homepage headlines for six weeks. Variant A: "Automate your reporting workflow with real-time data sync." Variant B: "Stop spending Sunday nights rebuilding the same report." Variant A was the feature-led copy the founder personally preferred. Variant B was the outcome-led version our team wanted to test. Variant A lost by 38% on trial-signup conversion, across roughly 22,000 sessions split evenly. Not close enough to argue about statistical noise. The founder's reaction, to his credit: "show me the data, then let's talk." We walked through session recordings from both variants. On Variant A, visitors read the headline and scrolled straight to the feature list, comparing us mechanically against competitors. On Variant B, visitors read the headline, then went directly to the signup button — the pain point framing skipped the comparison-shopping mode entirely and triggered recognition instead. What changed after: every new landing page test now runs an outcome-led headline as the control, not the challenger. Feature-led copy is still in our arsenal — it works better lower in the funnel, on comparison and integration pages, where visitors already know they want the outcome and are evaluating mechanics. The lesson wasn't "outcomes beat features" as a universal rule. It was that headline framing needs to match the buyer's mode of thinking at that specific point in the funnel, and the only way to know which mode they're in is to test it, not to defer to whoever writes the best feature spec.

Twelve win/loss interviews in, I finally asked the right question: "if you hadn't chosen us, what would you have done instead?" I expected a competitor name. Eight of the twelve said some version of "probably just kept using our spreadsheet." Our battlecards were built entirely around two named competitors — feature comparisons, pricing objection handling, positioning against their weaknesses. We'd built an elaborate sales deck for a fight that, according to our own win/loss data, was happening in fewer than a third of real deals. The actual competitor, in most losses, was inertia: a homegrown spreadsheet, a legacy tool nobody loved but nobody had budget or urgency to replace. That changes everything about the sales conversation. Beating a named competitor is a features-and-price argument. Beating "we'll just keep doing this manually" is an urgency and risk argument — what does it cost you, in hours and errors, to keep doing this the way you're doing it today. We rebuilt our top battlecard around status-quo displacement: a cost-of-inaction calculator, a specific list of failure modes the spreadsheet approach hits at scale, and messaging aimed at urgency rather than differentiation. Win rate against "no decision" opportunities improved 15 points over the following two quarters, more than our win rate against either named competitor moved in that same window. Before you build another competitor battlecard, check your win/loss data for how often the real competitor isn't a competitor at all.

We launched a major feature on a Tuesday because every launch playbook says Tuesday is optimal for press pickup and social reach. It was. It was also the second day of our sales team's end-of-quarter pipeline review, which meant every AE was buried in forecast calls for the next three days. Inbound interest from the launch — demo requests, trial signups with high intent, a genuinely good press mention — sat in queue for four days before anyone followed up. By the time reps got to the leads, a measurable chunk had gone cold. We pulled the numbers: leads contacted within 24 hours converted to a qualified meeting at roughly 3x the rate of leads contacted after 72 hours. The launch date was optimized for a press cycle and a social algorithm. It was not optimized for the one thing that actually turns interest into pipeline — a human responding while the interest is still warm. What changed: our launch calendar now checks the sales team's capacity calendar first. No launches during the final week of a quarter, none during major sales kickoffs, none during a week where forecast calls eat the whole team's calendar. Press cycle timing is now the second filter, not the first. A launch that generates perfect press coverage and mediocre follow-up isn't a launch. It's a very expensive press release. Who else has watched a great launch evaporate because sales couldn't pick up the phone that week?

My standard sales enablement deck template, twelve slides, refined over three launches. And the one slide reps skip every single time, which took me embarrassingly long to notice. 1. The one-sentence positioning statement. 2. The buyer problem, in the buyer's language, not ours. 3. Why now — the trigger event that creates urgency. 4-6. Three proof points, each with a customer quote or number attached. 7. Objection handling, top five, ranked by frequency from win/loss data. 8. Competitive differentiation, only the two competitors that show up in real deals. 9. Discovery questions that surface the problem this launch solves. 10. Demo script, three screens, five minutes max. 11. Pricing and packaging notes. 12. "Where to find more" — links to deeper resources. The slide reps skip every time: slide 8, the competitive differentiation grid. I used to take this personally. Then I asked three AEs directly why, and got the same answer independently: "by the time we're in a deal, we already know how to talk about the competitor. We need slide 7 and slide 9, not a grid we memorized in the first training." I still build the slide — new reps need it once. But I stopped treating it as the centerpiece. The deck now leads with objection handling and discovery questions, because that's the part reps actually reopen mid-call. Build for what gets reopened during a live deal, not what looks complete in a training session.

I sat silently on 14 discovery calls last quarter, just listening, no note that I was there to grade anyone. What shocked me wasn't that reps went off-script. It was how consistently they went off-script in the exact same direction, independently, without coordinating with each other. Our approved messaging leads with "unified workflow automation." Not one of the 14 reps used that phrase unprompted. What they actually said, across calls with completely different reps in different regions: some version of "you'll stop losing half a day every week to manual handoffs between tools." Nearly identical language, from people who'd never compared notes. They'd all independently discovered, through live buyer reactions, that the abstract framing fell flat and the specific time-cost framing landed. The approved deck was three iterations behind what the field had already figured out through pure trial and error, deal by deal. I'd been treating messaging as something PMM designs and sales executes. What fourteen calls actually showed me: sales is running a continuous, unstructured field test on our messaging every single day, and most of that signal was evaporating because nobody was capturing it systematically. What changed: I now sit in on calls monthly, not as an audit, but as research. And I built a lightweight Slack form for reps to log a phrase that worked, no analysis required, just the sentence. The best messaging on my team didn't come from a workshop. It came from listening to what reps had already proven works and writing it down.

Eighteen months ago, every feature shipped got the full launch treatment: press outreach, customer email, in-app announcement, sales enablement deck, the works. We were exhausted and nothing stood out anymore. Here's the tiering framework that fixed it, scored against three criteria: revenue impact (does this unlock or influence deals in active pipeline), competitive relevance (does this close a gap we lose deals on today), and customer request volume (how many support or sales tickets asked for exactly this). Tier 1 — all three criteria score high. Full launch: press, customer email, sales enablement deck, in-app banner, blog post. We ship 3-4 of these a year, deliberately rare. Tier 2 — two of three criteria score high. Customer email, in-app notice, one-page sales brief. No press outreach, no dedicated enablement session. Tier 3 — one or zero criteria score high, but it shipped. Release notes only, folded into a monthly digest email. The hard part wasn't building the table. It was using it to say no to an engineering lead who genuinely believed their feature deserved Tier 1 treatment, and having a criteria table to point to instead of a subjective argument about whose work matters more. Since adopting this: our Tier 1 launches get measurably higher engagement, because they're no longer competing against a Tier 3 feature announcement sent the same week. Not every launch is Tier 1. The framework's real job is giving you language to say that out loud.

Early in my career, I wrote a 14-page positioning document entirely from internal input: the founder's vision, the product roadmap, a category analysis I did myself from competitor websites. It was elegant. Every section connected logically to the next. I was proud of it. I presented it to leadership. It got approved in one meeting. Then I ran my first customer interview to validate the messaging before rollout, mostly as a formality. Fifteen minutes in, the customer said, about our core differentiator: "honestly I didn't even know you did that, that's not why we bought this." The actual reason she'd bought, and stayed two years, wasn't in my document at all — it was a workflow detail I'd considered too minor to include. I ran four more interviews that week, dreading each one. The pattern held in three of the four. My elegant, internally-approved positioning doc was describing a product that didn't match why real customers actually valued it. We rebuilt it, this time starting from ten customer interviews before writing a single line, and the resulting positioning tested completely differently — messier, less architecturally clean, and it converted better in every test we ran against the original. The fix I still use: no positioning document gets drafted before at least five customer conversations happen, no exceptions, regardless of how confident the internal narrative feels. Internal logic can be perfectly coherent and completely wrong. Only customers can tell you which one you've written.

Our team Slack has had some version of "is AI going to replace product marketing" pinned as a running joke-that's-not-really-a-joke for months. I'll give my actual position. What's already commoditizing: first-draft messaging. I can generate five positioning options for a new feature in ten minutes now, options that would have taken a junior PMM half a day. The drafting labor is genuinely gone. What isn't commoditizing, and I don't think will: — Customer research. AI can summarize ten interview transcripts. It cannot decide which uncomfortable finding in those transcripts matters enough to rebuild a launch around, the way a spreadsheet-competitor discovery did for us last quarter. — Internal alignment. Getting engineering, sales, and leadership to agree on one positioning statement is a political and interpersonal skill. No model sits in that room and reads whether the VP of Sales is nodding or performing agreement. — Pricing and packaging judgment. The data informs it. The call — where three tiers instead of four, what to name "Enterprise," what to bundle — still requires someone willing to be wrong in front of the company. — Launch sequencing and timing judgment, the kind that knows not to launch during a sales team's forecast week. My actual prediction: the PMMs who only ever wrote drafts are at real risk. The PMMs whose value was deciding which draft to trust, and getting a room to agree on it, get more valuable, not less, because the volume of drafts needing judgment just went up.

Seven questions I now ask before agreeing to any launch date, after getting burned by skipping most of them early in my career. 1. "Is the sales team's calendar clear enough to follow up on leads within 24 hours?" If it's forecast week, the date moves. 2. "Do support docs exist, reviewed, not just drafted?" A launch with no support documentation turns day-one questions into support tickets that could have been prevented. 3. "Has a single AE actually demoed this build, not the roadmap version?" Roadmap demos and shipped-feature demos diverge more often than engineering wants to admit. 4. "What's the specific metric that defines this launch as successful, and who agreed to it before launch day?" If nobody can answer this, the launch has no way to be evaluated afterward. 5. "Is there a rollback plan if a critical bug surfaces in week one?" Not "we'll fix it fast" — an actual plan. 6. "Does this conflict with another team's launch or major announcement that same week?" Internal collisions bury both launches. 7. "Has legal or compliance actually signed off, or just been informed?" Those are different states, and the second one has cost me a delayed launch before. Engineering timelines are usually built around code-complete, not go-to-market readiness. These seven questions are how a junior PMM pushes a launch date without needing the authority to just say no outright.

Product marketers, what's your most controversial opinion? Mine first, and I mean it: personas, as most teams build them, are a waste of time. Not audience segmentation — that's essential. I mean the laminated one-pager with a stock photo, a fake name, and a paragraph of "goals and frustrations" that gets built once in a workshop and never touched again. I've built four of these in my career. I have never once opened one during an actual positioning decision. Not once. What I use instead: a living document of actual customer quotes, tagged by the specific decision they inform — pricing objections in one section, feature requests in another, churn reasons in a third, updated after every win/loss and churn interview. Less polished. Infinitely more useful, because it's built from what people actually said instead of what we imagined they'd say. Second opinion, slightly less controversial: pricing strategy should report into product marketing, not finance or product alone. PMM is the only function that sits between customer research, competitive positioning, and packaging decisions daily — everyone else is guessing at two of the three. Your turn. What's the PMM opinion you'd defend in a room but haven't posted publicly? I want the ones that would get pushback from your own team, not the safe ones.