Sigalit Sadeh | Lusha | Takhles Episode: How Do You Know What Will Drive the Most Impact?
Host: Eyal David · Guest: Sigalit Sadeh · About the host
To know which problem will drive the most impact, Sigalit Sadeh, Director of Product at Lusha, runs opportunity sizing with three questions: how many users the problem affects and what its business value is, how painful it is (must have or nice to have), and how often people run into it. The answers feed a formula that produces a score for each problem, and each problem's solutions are then ranked with ICE, impact versus effort. A painful problem that happens once every six months, or only to niche customers, is probably not worth solving.
In this episode
- Opportunity sizing rests on three questions: how many users the problem affects and what its business value is, how painful it is (must have vs. nice to have), and how often people run into it. A painful problem that happens once every six months, or only to niche customers, is probably not worth solving.
- Prioritize problems first and solutions second: pain, frequency and segment size go into a formula that scores each problem, and the two or three solutions for each problem are ranked with ICE, impact versus effort.
- At Lusha, an initiative you can attach business value to gets room even if it isn't part of the company's metrics, because in the end product managers are here to bring business value.
- Any feature can be quantified, not just technical features that save money: with good assumptions and a ballpark you know how many customers will come back and what their subscription is worth, and in hindsight you measure conversion, sign-ups and upsells.
- There are exceptions, but you need to be mindful of all the measures before deciding a problem is worth solving.
Listen to this episode
Episode Description
In this Takhles episode, Sigalit Sadeh of Lusha tackles which problem or opportunity is most worth focusing on. She lays out the three sizing questions: reach and business value, pain intensity, and frequency. The conversation then turns to an initiative that brings money but isn't tied to the company's metrics: at Lusha, if you can attach value to it, the PM gets to move forward. Sigalit explains how to quantify any feature's business value, before and in hindsight, through assumptions, a ballpark, conversion and upsells, and how it all comes together in a formula that scores problems and an ICE ranking of solutions.
Chapters
Full transcript with speakers and timestamps
Selected quotes
“It's a terribly painful problem, but people deal with it once every six months, then we probably shouldn't solve it.”
“Because in the end product managers are here to bring business value.”
“In the end you really can use the same framework to understand how much business value you brought to the organization, also in hindsight”
Questions & answers
How do you know which problem will drive the most impact?
Answer three questions: how many users it reaches and what its business value is (including whether you can monetize it), how painful it is (must have or nice to have, and whether users try to solve it themselves and fail), and how often they run into it.
When is a painful problem still not worth solving?
When it only happens to niche customers or very large ones that don't represent the customer base, or when people run into it only once every six months. There are exceptions, but you need to be mindful of all the measures.
What do you do with an initiative that brings money but isn't tied to the company's metrics?
At Lusha, if there's a dollar sign and you can attach value to the feature, the PM is allowed to move forward even outside the company's or group's metrics, because product managers are here to bring business value.
How do you quantify a feature's business value?
With good enough assumptions and a ballpark: how many customers the feature will bring back and what their subscription is worth. In hindsight, look at the conversion, sign-ups and upsells that followed the feature.
How do you compare problems and solutions?
Problems get a formula combining pain, frequency and segment size that produces a score, which decides which problems to pick. Each problem's solutions are then ranked with ICE, impact versus effort.
People & resources mentioned
Companies & orgs
Tools
- ICE (Impact, Confidence, Ease)
Related Episodes
Why I Talk Less About Product Now | Coffee with Eyal
00:06:55 · October 7, 2026
"Coffee with Eyal" is a short, informal series in which Eyal David opens the mic over a cup of coffee and shares insights, things he is building and w...
"I was afraid AI would take my job. It sharpened it instead" | Shira Moyal (imagen)
00:43:40 · May 10, 2026
Shira Moyal leads a product team at imagen, a startup that built a personal AI model which learns a professional photographer's editing style and edit...
How to Build AI at the Edge of the Device — Ori Katz, Hailo
00:40:49 · March 5, 2026
Ori Katz, who leads the AI SoC domain at Hailo, tells the story of how an Israeli chip company became a serious player in AI at the edge — smart camer...
Amit Slutzky | Trullion | “I Left Figma and Went Into the Field — It Changed Everything”
00:41:22 · February 24, 2026
Amit Slutzky, Director of Product at Trullion, on one of the most important muscles for product people: understanding what's really going on with the...