Daniel Lereya on Monday.com, Impact-Driven Teams, and Radical Transparency

Daniel Lereya on Monday.com, Impact-Driven Teams, and Radical Transparency

transcriptlennyproduct-managementmonday-comtransparencyscalinggrowth

Daniel Lereya on Monday.com, Impact-Driven Teams, and Radical Transparency

Source: Lenny’s Podcast Speaker: Daniel Lereya Date: ~2024 Link: Episode

Daniel Lereya is Chief Product and Technology Officer at Monday.com, where he has worked for eight and a half years — from ~$4M ARR and 30–40 employees to $1B ARR and 2,500 people. The conversation covers how a competitive shock forced a fundamental rethinking of product velocity, how impact orientation replaced feature shipping, why radical transparency scales even into a public company, and what leaders must let go of as companies grow.

Key ideas

  1. Competitor gift / ambitious goals. Seeing a competitor ship 30 column types overnight (Monday had 5, each taking 4 months) was reframed as a gift: it proved what was possible. The response — build 30 in one month — forced structural rethinking rather than harder work. The result (30 columns in 1.5 months, via a shared infrastructure + hackathon) established a repeatable pattern. Ambitious goals are specifically those you cannot achieve by working the same way, even harder — that is the point.

  2. Impact-driven PM. A PM has two responsibilities: (a) creating shared understanding of what would be impactful for customers, and (b) establishing how the team will know impact was achieved. Without both, building is “songs for the door.” Smell test: language like “enhance / augment / extend” with no measurable outcome signals impact-blind work. The daily numbers update — a Slack channel with live metrics that every team member follows — is the operational mechanism for staying honest to this principle.

  3. Radical transparency at scale. Pre-IPO: office dashboards visible to all, including job candidates; Simpson soundbites triggered by new accounts. Post-IPO: Monday Morning app (part A — public engagement data; part B — role-based financial metrics). Product managers sign 10b5 automatic stock-sale plans so they can retain access to sensitive data without being locked out during earnings windows. The animating belief: “we want everyone’s brains in the challenge and not just one centralised brain and a lot of working hands.”

  4. Deadline traps. Bottom-up planning is inherently fear-driven — teams raise concerns, add scope, and a feature that should take three weeks balloons to two years. The antidote: commit to an external deadline (e.g. an earnings announcement) and cut scope to fit. This is “fake speed vs real speed” — fake speed is working harder or skipping quality; real speed is structural rethinking. The first alpha release to enterprise customers received a “this is premature” verdict, which Lereya considered the ideal outcome: directional validation before over-investment.

  5. Skills evolution and the Daniel-of-next-six-months model. “What got you here won’t get you there”: mastering all details is a strength at 30 people and a liability at 300. Leaders must identify which superpowers are now creating drag, not momentum. The “Daniel of next 6 months” exercise — imagining your future self and asking what you want to have learned — converts abstract growth intent into concrete present-day behaviour. MondayDB (a three-year infrastructure rewrite that turned a recurring performance crisis into a platform competitive advantage) exemplifies the same principle applied organisationally.

Context

Monday.com scaled from $4M ARR / ~40 employees to $1B ARR / 2,500 employees across ~200 business verticals; 70%+ of customers are non-tech. The multi-product bet — launching five products simultaneously rather than sequentially — is cited as a key inflection: Monday Sales CRM is now growing faster than Monday core was at the same stage.