The Product Manager’s Guide to Sharing Work That Actually Gets Noticed

Unlock smarter ways to share your work as a PM—without it feeling like extra work. Learn how to make your launches pop, build excitement across teams, and get buy-in for your next big idea.

Hey friends,

A few years ago, I shipped a feature that I was so excited about. I thought it was a game-changer. A week after launch? Crickets. No one noticed. No one cared.

That’s when I realized, building great products isn’t the hard part. The real challenge? Getting people to actually care about them.

Most PMs don’t struggle with shipping good products. They struggle with making their work visible.

So this week, I’m sharing a few ways I’ve learned to make launches more exciting, without turning into a full-time marketer.

🎤 Lesson 1: The 5-Minute Demo That Builds Hype

At HubSpot, we run a session called Science Fair, where PMs, designers, and engineers get just 5 minutes to:

✅ Walk through a feature they just launched
✅ Share the problem they were solving
✅ Demo the product (!!)
✅ Talk about early wins (or surprises)

No boring slide decks. No fluff. Just five minutes of pure energy, showing off real work to real humans.

And it works. People across the org actually see what’s shipping, get excited, and ask great questions.

🚀 Mini Challenge: Can you run a “5-minute demo” at your next team meeting? No slides, no fluff, just a quick, punchy walkthrough. I promise, people will love it.

💡 Lesson 2: The Best PMs Write A Lot

If no one understands your product, they won’t use it. That’s why great PMs don’t just build, they tell the story of what they built.

Instead of just writing PRDs, try these:

📝 Launch Emails → Frame your feature as a story, not just a list of specs.
📣 Slack Teasers → Share a quick post about what’s coming next.
📊 Before & After Screenshots → Show how your feature improves the experience.

And here’s the best part, you don’t need to be a “writer” to do this. Just focus on clarity, not perfection.

🔥 Try this: Next time you ship something, write a 2-3 sentence update and drop it in Slack. See what happens. (Hint: More engagement, fewer confused teammates.)

🔄 Lesson 3: Don’t Just Launch—Close the Loop

Most PMs move on after a launch. The best ones? They follow up.

After shipping a feature, I always ask:

✅ Did it solve the problem we intended to?
✅ Are users actually adopting it?
✅ What feedback are we hearing?

One simple way I do this? I reply to my own launch message a few weeks later with updates. If it worked, I share wins. If we learned something unexpected, I share that too.

It takes two minutes—but builds so much credibility for future projects.

📅 Try this: Set a calendar reminder for 3-4 weeks after your next launch and post a quick follow-up. Future you will thank you.

🤔 Final Thought: How Does Your Team Share Work?

I’d love to hear! How does your team communicate launches? Do you have a process, or is it more ad hoc?

Reply and let me know 🙂 
I read every response!

Until next time,
Stefanie