Ron Ratovsky

After 10 years of building Productboard, we're shipping something that feels like magic: an AI agent built specifically for product management. Here's the thing—product teams are drowning in context. Customer feedback lives in 12 different tools. That brilliant insight from last quarter? Gone when someone leaves. And you're still making calls based on vibes instead of the full picture. Generic AI tools? They're helpful until the conversation ends and they forget everything. Spark is different. It lives in Productboard. It remembers. It knows your customers, your product, your strategy, and it gets smarter as your team does. What you can do right now: → Generate PRDs that pull from your actual customer data → Turn messy feedback into clear, lasting insights → Keep competitive battle cards fresh without the manual grind This is organizational memory that actually sticks. Context that doesn't disappear. Clarity without the chaos. #ProductManagement is about to get a whole lot more fun. Ready to try Spark? Join the beta: https://lnkd.in/grDPp_xQ #ProductManagement #AI #ProductDevelopment

216

4 Comments

Is your company's knowledge scattered across a dozen different apps? I know the pain of juggling presentations, docs, Figma files, and spreadsheets. I've also seen so many of you using our new product, #mondayvibe, to solve this exact problem, which inspired me to create this short video. I'll show you how I built a central hub right inside our monday.com account, including: ✨ Embedded Google Slides, Docs & Sheets ✨ Figma designs ✨ monday forms & canvas ✨ A live YouTube video player ✨ Even a map with the best pubs in London for our visitors! The best part? I built this in minutes with zero code. I just opened monday vibe, our #vibecoding product and told it what to do: 'Build a Knowledge Base Portal. It needs a header with a search bar, cards for each link, and category filters on the left. When I click a card, open a preview and embed the link inside it.' This app is secure, scalable, and making changes is as simple as chatting: "Change the color to Pink." ✅ Watch the quick video to see how you can build your own! 👇 I'm always amazed by what you're all building. If you have a cool vibe or an interesting idea, please share it in the comments, I'd love to feature it next time!

82

9 Comments

If you're in product ops you'll immediately recognize this dilemma. A massive copy-paste challenge to maintain a commercialization/marketing view of the world...and a product view of the world. Made 300% harder because someone wants a "simple calendar" of launches. The reality is: 1. Initiatives have a M:1 relationship with Launches 2. Different launch tiers have different launch milestones 3. Calendars must include milestones, launch, and initiatives 4. Initiatives can have multiple releases 5. ...but not all releases are launch related 6. Oh, there are massive internal "launches" that marketing doesn't care about And this is why spreadsheets prevail. God-awful spreadsheets with: 1. Dozens of fields (like 6 dates for milestones) 2. Random manual fields to list multiple initiatives 3. Terrible VLOOKUP date madness 4. Product themes that are distinct from anything product uses A classic example of how there is a "right" model, but the UX complexity kills everyone, so they opt for something crappy. (PS: I love these problems. Hit me up if this resonates)

43

8 Comments

I’ve been reviewing a lot of PM resumes and applications lately, and it’s pushed me to get crisper on what really sets apart the product managers who thrive in 0-to-1 AI building. It isn’t just about what’s on paper - it comes down to a few core traits that make all the difference. The six core characteristics that I keep coming back to when looking for a great AI PM are: ✨ Exceptional product taste & user-centric craft 🌐 Visionary leadership & systems thinking ⚡ Clarity in chaos & empathetic resolve 📖 Compelling product storytelling 🚀 Full-spectrum execution & ownership 🤖 Deep AI intuition & applied creativity 👉 Full post in the comments.

212

22 Comments

Product leadership has changed over the years. The focus is much less on theoretical frameworks and more on clear business results. The energy’s different. The pressure is heavier. We’re leading leaner teams, in tighter markets, with way more eyes on outcomes. Everyone's tired. A few months back, GoldHue asked me to get in a room with other product heads from top tech companies. No agenda. Just honest truth. We wanted to talk about what we could leave behind and what we need to build next. We ran real experiments that tested new ways of working, and focused on simplicity, clarity and results. What came out of it wasn’t just useful. It was clear, repeatable, and it worked. We put everything into a white paper: The New Age of Product. Not another playbook. A practical reset. A few things we found: → Heavy goal frameworks are broken. The best teams are moving toward leaner, adaptable methods that drive focus and execution. → More metrics don’t mean better insights. High-performing teams track fewer, smarter metrics tied directly to strategic goals. → The speed vs strategy tradeoff is more brutal than ever. If you’ve felt the shift too, this is for you. And if you’re leading in the grey and tired of pretending it’s black and white, we hope this helps you. You can find the link in the comments, and thanks to my fellow Product Club members: Randi Eichenbaum, Mell Ravenel, Jamie Landers, Marisa Sires, Colleen Wilson, Jason Butterfield, Tara Goldman, Mackenzie Hughes

74

6 Comments

You can do everything by the book. Define the problem. Ruthlessly prioritize. Explore multiple solutions. Get validation. Ship a beautifully crafted product. As a PM, you feel proud. Rightfully so. But then you realize—building the product is only half the story. The other half? Distribution. 1. How will people discover it? 2. How are you positioning it? 3. Are your value props resonating with the right persona? Take Microsoft. They may not always build the most elegant solution, but their distribution advantage is massive. They can afford to be average in some places because their reach fills in the gaps. At a startup like Enterpret, we don’t have that luxury. Every launch has to punch above its weight. We have to be relentlessly intentional about go-to-market. As a PM, your job doesn’t end at launch. You can’t just toss a feature over the wall to marketing and say, “Done.” You have to be a partner in making sure it reaches the right people, in the right way with the right story behind it.

38

3 Comments

We eliminated 5 unnecessary steps from paywall testing. Most teams spend weeks going from idea to live A/B test. We made it 3 steps: Think it, design it, launch it. When the process is simple, testing becomes natural. Fast iterations, better outcomes. If your A/B testing takes weeks, something's wrong.

27

I am (once again) thinking about roadmapping, and I think my current favorite advice for product managers who are trying to think strategically is to look at your roadmap and rework it around THEMES. Why themes? Features = promises you’ll break. Themes = a story you can steer. Features invite bikeshedding. Themes focus debate on customer outcomes. Features fragment teams. Themes align squads on the same hill to take. What is a theme, anyway? 🤔 A concise, outcome-oriented bet that ladders to strategy. It names a customer problem, the business impact you’re chasing, and the guardrails for how you’ll pursue it. It is not a project list. How to use themes in your roadmap 🗺️ Cap at 3 themes per half (for an average team). If everything is a priority, nothing is. Roadmap Now / Next / Later by theme. Attach outcomes. Triage ruthlessly: if a high urgency ask doesn’t map to a theme, it’s either a hidden theme (rename it) or noise (park it). Common pitfalls ⚠️ Themes that mirror the org chart (“Mobile Team”) instead of strategy. Themes that are actually projects (“Rebuild Billing”)—too narrow. Too many themes—spreads focus and dilutes impact. If your roadmap reads like a grocery list, try rewriting it as a table of contents for your strategy. Your team (and your stakeholders!) will instantly see the plot. 📖

35

3 Comments