Lenny's PodcastDaniel Lereya: How a 30-column rival reset monday's ambition
When a competitor shipped 30 column types while monday.com had only six; radical transparency, impact over output, and live dashboards reset every team.
CHAPTERS
- 0:00 – 4:34
What great PMs optimize for: relentless impact, not more features
Daniel opens with his core product philosophy: great PMs are relentless about achieving measurable impact, even when the best move is not building something new. This frames the rest of the conversation around outcomes, focus, and customer value.
- •Impact is the real finish line, not shipping output
- •Validation matters: confirm the impact actually happened
- •Sometimes the highest leverage is improving accessibility of existing value
- •Feature-building can be a distraction from the real problem
- 4:34 – 11:23
The wake-up call: a competitor ships 30 “columns” and resets the bar
Lenny and Daniel revisit the pivotal moment when monday.com realized competitors were moving dramatically faster. The shock wasn’t just speed—it revealed a focus problem and forced a rethinking of how the organization builds product.
- •They felt productive—until they saw a competitor launch 30 new column types
- •Hard truth: doing “a lot” didn’t mean doing something transformative
- •The team stepped out of the office to confront what wasn’t working
- •Competition became a forcing function to rethink execution and focus
- 11:23 – 16:05
Ambitious goals as a forcing function: from 4 months to 1 day per column
Daniel explains how they set an almost absurd goal (25 columns in a month) specifically so old methods wouldn’t work. The key breakthrough was shifting from brute-force effort to smarter architecture and radically different execution.
- •Ambitious goals prevent “work harder” thinking and require new approaches
- •They defined what a column is and standardized capabilities (export, filter, sort)
- •Built shared infrastructure so teams only focused on the unique value per column
- •Ran a hackathon: each developer implemented a column in one day
- 16:05 – 17:45
Real speed vs. fake speed: focusing only on what moves the needle
The conversation distinguishes between cutting corners and true organizational speed. Real speed comes from choosing the right work, avoiding invented scope, and aligning teams around what creates customer and business impact.
- •Fake speed = skipping quality or stages; real speed = doing the right things right
- •Most acceleration comes from better focus and decision-making
- •Goals should make it obvious you can’t succeed with the current approach
- •Confidence compounds once teams achieve “impossible” targets
- 17:45 – 21:37
Impact over output: how monday defines PM excellence and team success
Daniel lays out monday.com’s operating system for product work: start with the customer problem, define measurable outcomes, and keep teams honest through metrics. This reframes PM work from solution advocacy to outcome ownership.
- •Great PMs create shared understanding of the opportunity and success metrics
- •Teams spend more time in the problem space before narrowing on solutions
- •Success is measured by customer value and business outcomes, not effort
- •Sometimes impact is GTM enablement or discoverability—not new features
- 21:37 – 32:06
Operationalizing impact: quarterly “what will be different?” + daily numbers
Daniel shares concrete rituals that keep teams focused: forcing functions at regular intervals and metrics delivered as a daily push. An AI Blocks story illustrates how the biggest impact can be unlocking access rather than building more.
- •Quarterly exercise: ‘How will the product be meaningfully better in 3 months?’
- •A ‘smell for death’: vague goals like “enhance/augment/extend” without metrics
- •Daily numbers updates in Slack keep teams living inside the metrics
- •AI Blocks example: adoption was low because of TOS gating—so they unblocked it fast
- 32:06 – 34:39
From 4M ARR to $1B ARR: the scale monday reached and what it enables
Daniel provides context on monday.com’s growth from early days to today’s scale. The segment also reframes “work management tools” as critical infrastructure for how real-world teams operate.
- •Crossed $1B ARR and ~250,000 paying customers
- •Grew from ~30–40 employees to ~2,500
- •Customers span 200+ verticals, largely non-technical users
- •These tools power everything from tech teams to airplanes and cruise ships
- 34:39 – 41:05
Radical transparency: sharing dashboards, KPIs, and even public-company constraints
Daniel describes monday.com’s unusually deep transparency culture—sharing key numbers broadly and treating employees as true partners. He explains how they preserved transparency after going public via role-based access and 10b5 plans.
- •Pre-IPO: dashboards visible in the office with churn, signups, and paying accounts
- •Transparency builds partnership and distributes problem-solving across the company
- •Public-company adaptation: internal app with role-based confidential sections
- •Product roles get broader access; 10b5 programs reduce insider-trading concerns
- 41:05 – 45:40
How to start being transparent: daily company numbers + visible office dashboards
Moving from philosophy to practice, Daniel offers simple steps startups can implement quickly. He emphasizes that fear—not operational difficulty—is usually the biggest blocker to transparency.
- •Publish daily company numbers (upgrades, downgrades, collections) with minimal effort
- •Use visible dashboards to spark continuous conversations and alignment
- •Create “living” metrics (even sounds/alerts) to reinforce what matters
- •Transparency reduces second-guessing about what can be shared
- 45:40 – 51:06
Bold risks that reshape reality: announcing five products at once
Daniel shares a high-stakes strategic bet: shifting from a platform sold like a project management tool to a multi-product suite—by launching multiple products simultaneously. The move created friction but accelerated learning and repositioned the company.
- •They saw customers building CRM and other systems on top of monday’s platform
- •Counterintuitive execution: announce five products at the same time
- •Some products took off (e.g., monday sales CRM); others were merged back
- •Lesson: not taking bold risks is itself a major risk
- 51:06 – 1:00:00
Timeboxing and shipping early: why more time often makes products worse
Daniel argues that longer timelines create more assumptions, complexity, and invented scope. He advocates “deadline traps” that force focus on the core value and encourage teams to get real feedback earlier—even if it’s negative.
- •Score work by time, not effort—timeboxes force clarity and prioritization
- •Use external deadlines (e.g., earnings) as “traps” to ship a coherent first version
- •Early negative feedback can be priceless signal and a sign you shipped fast enough
- •Customer feedback must be contextualized—not every request leads to the best product
- 1:00:00 – 1:04:44
Leadership evolution: when your former strengths become liabilities
Daniel reflects on how his role changed repeatedly as monday scaled, and how behaviors that worked early (owning every detail) can hinder you later. He shares how feedback and reflection helped him adapt his communication and leadership style.
- •Scaling creates a new job every phase—skills must evolve accordingly
- •Detail mastery helped early; later it can slow teams and distort priorities
- •A QBR moment: “I explained everything” vs. “I understood nothing” forced a shift
- •Executives often need the 3 key issues, not exhaustive detail
- 1:04:44 – 1:10:41
Imposter feelings, resilience, and culture: staying grounded through hypergrowth
In a candid stretch, Daniel describes doubt, emotional whiplash, and the mental habits that help him recover quickly. He emphasizes vulnerability, continuous learning, and culture as a scaling advantage rather than a fuzzy concept.
- •Leaders routinely wonder if they’re the right person for the next stage
- •Mindset: ‘Future me in 6 months’—what did I learn and how did I evolve?
- •Bounce-back routines: exercise, resetting, returning with energy
- •Culture becomes more important (and harder) as the company scales
- 1:10:41 – 1:17:27
Crisis and strategy: performance breakdowns and building MondayDB as an edge
Daniel recounts a recurring crisis: board performance issues as customers pushed monday’s scale limits. After repeated spikes, they made a strategic bet—pulling top talent off features to build foundational infrastructure that became a competitive advantage.
- •Boards evolved from small tables to massive datasets with extreme usage patterns
- •They treated performance as ‘the #1 feature’ for sustained adoption
- •Created MondayDB: a long-term data infrastructure project built for 100x scale
- •Lesson: turn existential risks into differentiators, not just band-aids
- 1:17:27 – 1:22:12
AI in work and life: from MRI explanations to competitive research in hours
Daniel shares practical examples of using AI personally and professionally. The key takeaway is productization: the technology is powerful, but the real opportunity is making it accessible and usable for everyday workflows.
- •Personal use: interpreting MRI results and iterating with follow-up questions
- •Work use: rapidly synthesizing competitor pricing and market landscape
- •AI’s advantage: interactive deep dives without fatigue or friction
- •Product lens: the challenge is packaging AI so non-technical users can benefit
- 1:22:12 – 1:32:06
Lightning round and closing: books, principles, and where to find Daniel
The conversation closes with quick recommendations and personal principles. Daniel shares favorite books, a leadership motto, and how listeners can reach him and share what they implement from the episode.
- •Book recs: ‘No Rules Rules’ and ‘Nonviolent Communication’
- •Favorite product: Google Photos; favorite show: Drive to Survive
- •Life motto: stay positive—optimism as a performance advantage
- •Where to connect: LinkedIn; call to action: share dashboards and experiments
