Tal Raviv
10 statements across 1 episodes · 4 bullish · 0 bearish · 1 people on the record · first statement Sep 22, 2024 by Tal Raviv · said 9 times in 2 episodes since 2022 · across every show →
On the record as a speaker too: Tal Raviv's record, appearances and statements → this page counts the times other people say the name.
Mentions by year
brought up most by Lenny Rachitsky (4), Adam Fishman (3), Zevi Arnovitz (2)
tap a year for its mentions
2026 6 mentions in 1 episode
Everything said about Tal Raviv, oldest first
Sep 22, 2024
Sep 22, 2024
Sep 22, 2024
Raviv: The best April Fools pranks exploit leadership's biggest strategic fears
“The best April Fools pranks are the ones that touch just ever so gently on people's biggest fears at that time. So in a work context, like whatever somebody's biggest strategic fear is that quarter or like that March of that year, right? Whatever people are ta…”
Sep 22, 2024 neutral
Raviv: Ignore user backlash to redesigns unless it persists past two weeks
“I think the key there is the two weeks, because if people are still complaining after two weeks, okay, then there's something here. But in those two weeks, there's gonna be a lot of feedback that comes from a resistance to change that they're gonna, you know, …”
Sep 22, 2024 positive
Raviv: Many PM managers eventually insist on returning to IC roles
“And at the same time over the years, I've also noticed that the colleagues that I identify with the most, like the ones where I just feel I most relate to them, many of them have that same pattern where they've gone to, you know, team lead or director and so o…”
Sep 22, 2024 positive
Raviv uses 'product scrapbooking' to cluster early customer evidence
“I call it product scrapbooking where I have this like massive notion database of every opportunity, big or small that's ever come up. And when a, like a piece of evidence, you know, out in the world comes in, it could be like a support ticket or like a CSM sen…”
Sep 22, 2024 positive
Sep 22, 2024 positive
Raviv: AI writes user stories well, but humans must architect task breakdown
“And I would say the thing that.
We still really needed a person for was deciding how to break up this really, really big change into those stories.
Like what is the logical way to split it up engineering wise, which my team lead did.
But once you have that, li…”
Sep 22, 2024