💡

InsightHunt

Hunt the Insights

D

Daniel Lereya

Episode #70

Chief Product and Technology Officer (CPTO)

Monday.com

⚡Execution👥Team & Culture🎯Product Strategy

📝Full Transcript

15,786 words
Daniel Lereya (00:00:00): ... 8:00 PM basically for me is someone that is relentless until he gets this impact, until he validates that this impact is in place. In some cases, doing the biggest impact is not developing another feature, it's about making the current value more accessible. Lenny Rachitsky (00:00:15): You've been at this for eight years, you said there's 250,000 customers at this point. What would you say is the most counterintuitive thing you've learned through this journey of building Monday? Daniel Lereya (00:00:25): We really have an approach of very radical transparency about everything. Before we went public, we actually shared every bit of information with our employees. Instead of demoralizing people, I think that this is something that gives them a sense of deep partnership. We really want everyone's brains in the challenge, and not just one centralized brain and a lot of working hands. Lenny Rachitsky (00:00:48): You basically realized that your competitors were shipping a lot faster than you were, that made you shift the way you think about product and the way you operate. Daniel Lereya (00:00:58): Some of our competitors did something that we can only imagine. We said, "Okay. We need to treat it differently." We received a gift from our competitors. They showed us that it's possible. Use your competition, know it, and take it, and set ambitious goals, and believe in yourself, and you can do amazing things. Lenny Rachitsky (00:01:14): Today, my guest is Daniel Lereya. Daniel's currently chief product and technology officer at Monday.com. He joined when they were just around 40 employees. And, a few years in, Daniel and the exec team realized that their competitors were able to move a lot faster than they were and ship a lot more often than they were, and that's spurred a transformation in how they build and operate their teams. Very few companies are able to transform like this, and even fewer recognize that something is wrong. In our c...

💡 Key Takeaways

  • 1Treat competitor speed as a 'gift' that proves what is possible, rather than a demoralizing factor.
  • 2Set 'impossible goals' (e.g., 25 features in one month) not to burn people out, but to force a complete rethink of the 'how' behind execution.
  • 3Radical transparency—sharing churn, revenue, and failures—creates deep partnership; shielding employees from bad news alienates them.
  • 4Infrastructure challenges shouldn't just be patched; they should be reimagined as strategic competitive advantages (e.g., MondayDB).
  • 5Use 'Time Traps' to force focus: set a strict deadline and cut scope to meet it, rather than extending timelines to perfect the scope.
  • 6As a leader, the skills that got you to your current level (e.g., knowing every detail) become liabilities at the next level; you must let go of former superpowers.
  • 7Don't build features to 'enhance' or 'augment'; build them to move specific numbers, and obsess over those numbers daily.

📚Methodologies (3)

⚡ Execution

A framework for shattering velocity plateaus by setting a target so ambitious that current workflows are mathematically impossible to use, forcing the team to reinvent their underlying infrastructure and process.

Core Principles

  • 1.Identify a 'gift' from the market: Use a competitor's achievement to prove that a higher velocity is possible.
  • 2.Set a non-linear target: Instead of '10% faster,' aim for '4 months of work in 1 month' to break the mental model of 'just work harder.'
  • 3.Build the infrastructure first: Spend the initial phase defining the abstract product architecture (e.g., the generic structure of a column) so specific instances can be built in hours, not weeks.
  • +1 more...

"If we're going to add 25 more, multiply it by four months... we are lost. So we said, 'Okay, we need to take upon ourselves an ambitious goal, like 25 columns in one month.'"

#'impossible#goal'#execution
View Deep Dive →
👥 Team & Culture

A system of extreme data openness that exposes every employee to raw business metrics (churn, revenue, bugs), treating them as partners who can solve problems autonomously rather than just 'working hands.'

Core Principles

  • 1.Democratize the 'Dark Side of the Moon': Share the scary numbers (churn, missed targets) so leadership isn't alone in worrying about them.
  • 2.Visual & Auditory Feedback: Install physical dashboards in the office and use sound cues (e.g., Simpson's sound for sales, specific alerts for churn) to create a shared sensory environment.
  • 3.Daily Number Obsession: Every team must publish a 'Daily Numbers' update in Slack, analyzing their specific metric (e.g., AI actions used) rather than feature progress.
  • +1 more...

"We really want everyone's brains in the challenge, and not just one centralized brain and a lot of working hands."

#'shared#brain'#transparency
View Deep Dive →
🎯 Product Strategy

A planning and review mechanism that forces teams to work backwards from a concrete future state rather than forwards from a feature list.

Core Principles

  • 1.The One-Year Slide: Start the year with a single slide describing exactly how the customer's life is different one year from today. Review this exact slide a year later.
  • 2.The Quarterly Reality Check: Ask, 'How will the product be different in 3 months?' If the answer is 'enhanced security' or 'more features' rather than a specific customer change, the plan is weak.
  • 3.Bi-Weekly Highlights: Individuals write highlights every two weeks focusing on impact. If a team struggles to list meaningful impacts, it flags a focus problem.
  • +1 more...

"If you can't answer that and you say, 'Listen, I'm doing so much,' but you can't point to this exact thing [that transformed], you have a focus problem."

#'future-back'#impact#audit
View Deep Dive →
← Browse All Episodes