Persuading, aligning and leading without authority
10 episodes12 timestamped moments8 guests
Episodes on the soft skills product managers and leaders need: storytelling that sells ideas, presenting to the CEO, negotiation and stakeholder communication.
How to build a partnership with leadership, rally people behind big moves, and lead strategic change without fear.
Roee Froman
You don't sell a feature — you sell a precise problem: start from the customer's real pain, not the solution, and frame it so they say "that's exactly where it hurts".
Go to the episode →
A persuasive story starts with the problem and the why, not the solution. Roee Froman, Product Marketing Director at Taboola, says you don't sell a feature, you sell a precise problem: bring the customer into their own pain first, then connect the product's capabilities to it. In his view, one strong customer quote is sometimes worth more than another chart.
Noa Ganot, founder of Infinity, starts even earlier: tell yourself the story of why you're doing something before you ask others to execute it. The story is built through draft work, sentence by sentence, until the plot has no holes. When a CEO says "I didn't hear anything new here," it can mean you nailed exactly what he meant.
The story can also live inside the product. Shai Shafrank of Empathy argues a good product tells its own story, like a hammer that needs no explanation, and Eden Naftali of Wiz describes how storytelling turns cloud security from something scary into something empowering. Tal Kailler of Evinced applies the same rule to interviews: beginning, middle and end, what the problem was, what you did and why.
To move something big you first build trust and partnership, and only then argue. Noa Ganot says CEOs don't want you to think for them, they want partners, and when they "babysit" the product team it's because they have no choice. Her pushback formula: understand why the idea makes sense to the CEO, reflect back what you understood, and argue only about the trade-off, not the idea itself.
Orly Stern Izhaki, GM at Payoneer, doesn't step into a vacuum: she respects previous attempts, talks to people and customers, and brings every stakeholder into one room from the start. On the onboarding project she used "blitzes", back-to-back one-to-two-day offsites that keep context intact and end with prioritized objectives and alignment.
Shai Shafrank describes leading Fiverr's shift from "I will do it for $5" to "service is a product" while the company was full of worries. He didn't try to dismiss the fear but to bridge over it, with wireframes, a seller survey that drew 150 responses in half an hour, and an internal experiment before release. In his words, rallying an organization behind an idea is "internal sales": hours of decks and data in front of leadership.
Negotiation is first of all goal-based communication, and most of the day we do it without noticing. Neta Luxenburg Naamani, VP Business Development at Ashtrom Properties, reminds us you only ever hold half the picture, so you walk in curious: ABC, Always Be Curious. When engineering says "no", you don't fight it, you find out how thick the no is and where the big rocks are.
Organizational consultant Shani Hai suggests managing stakeholders like a backlog: an influence-versus-relevance matrix you keep updating. Build the message by structure, start with the "why", put the bad news on the table first, and bring interpretation rather than raw data. Every meeting ends with a call to action, an owner and a date.
Roee Froman adds that before a heavy decision you talk to Engineering, Legal, Support, Sales and the CPO, and learn what drives each of them. Eden Naftali of Wiz puts it from the angle of developers with no direct incentive to help: simplify their work, give them context and small wins.
Start from the customer's pain, not the solution: bring them into their problem first, then connect the product's capabilities to it. Roee Froman of Taboola tells of a big deal in the Roaming world that closed fast because the pain was clear, and recommends coming equipped with the company's capabilities rather than ready-made solutions. Go to the episode
Noa Ganot recommends first understanding why the idea makes sense to the CEO and assuming there's truth in it, then reflecting back what you understood until he confirms, and only then raising your concern. Don't argue with the idea itself, only with its timing and priority. Go to the episode
According to Neta Luxenburg Naamani, don't treat the no as a battle. Stay curious, find out how thick the no is, and identify what's truly critical and what can be simplified. Put the other side in the position of being wrong and their goal becomes proving they're right instead of solving the problem together. Go to the episode
Shani Hai recommends bringing interpretation, not raw knowledge: the so-what and the comparison, "compared to what?". Attach the raw data in a read-more format for those who want to dig into the details. Go to the episode
Shai Shafrank, who led Fiverr's shift to "service is a product", didn't try to dismiss the fear but to bridge over it with evidence. He showed concrete wireframes, ran a quick seller survey and tested the change in an internal experiment before release, because in a marketplace you can't take back a feature people love. Go to the episode
Tal Kailler of Evinced says an interview is a micro-cosmos of product management, so you need a short, focused message with a beginning, middle and end: what the problem was, what you did and why. She suggests starting from the value and the why, and practicing a short, medium and long version until you can tell them off the cuff. Go to the episode
Roee Froman
Key takeaway: You don't sell a feature — you sell a precise problem: start from the customer's real pain, not the solution, and frame it so they say "that's exactly where it hurts".
Noa Ganot
Key takeaway: Tell yourself the story of why you're doing something before you ask others to execute it — it's a hard exercise that people avoid, but it's the foundation of any convincing strategy.
Noa Ganot
Key takeaway: Product is a profession, not just a skill — the real impact doesn't come from templates and tools but from the ability to sit comfortably in management discussions, work with the CEO, and rally people around a strategy.
Tal Kailler
Key takeaway: An interview is a micro-cosmos of product management: like a PM who leads without authority, the candidate has to rally people, prioritize, and deliver a short, focused message. Every question in the interview is there to reduce risk.
Orly Stern Izhaki
Key takeaway: The three critical skills of a product manager according to Orly: the ability to rally people around a vision and be the glue that connects everyone, the ability to separate the essential from the peripheral and cut through the noise, and genuine empathy for the customer and their pain.
Eden Naftali
Key takeaway: Storytelling is a real product tool: at Wiz they don't sell fear but empowerment — giving the user context and tools to succeed at security, rather than scaring them.
Shai Shefrank
Key takeaway: When a change touches the core of the product, you first need a new story and strategy: Fiverr shifted from "I will do it for $5" to "service is a product" — a service you can buy in one click at any price.
Shani Hai
Key takeaway: Before an important message — stop to plan it, and if possible write it down for yourself in a few points; you can use AI to distill and condense it.
Shai Shafrank
Key takeaway: A good product tells the story itself — like a hammer that needs no explanation. At the early stage, a large part of product work is distilling a complex world into a simplicity the user grasps at a single glance (Work/Life/Balance at Lili, Empathy as loss in the broad sense).
Neta Luxenburg Naamani
Key takeaway: Negotiation is goal-based communication — and most of the day we conduct it without noticing. The most dangerous negotiation is the one we don't even know is taking place.
