The 'Future-Back' Impact Audit
by Daniel Lereya • Chief Product and Technology Officer (CPTO) at Monday.com
Daniel joined Monday.com when it had roughly 40 employees and $4M ARR, guiding the product and technology organization through hyper-growth to over 2,500 employees and $1B+ in ARR. He has overseen the transition from a single product to a multi-product platform.
🎙️ Episode Context
Daniel Lereya shares the internal transformations Monday.com underwent to scale from a small startup to a multi-product public company. The conversation centers on a pivotal moment where competitor speed forced them to reinvent their engineering culture, the implementation of 'radical transparency' to turn employees into partners, and the necessity of shifting from feature-output to impact-outcomes. He also discusses the counterintuitive risks of not taking bold leaps and how to operationalize ambition.
Problem It Solves
The 'Build Trap' where teams ship many features but cannot articulate or demonstrate tangible business value at the end of a cycle.
Framework Overview
A planning and review mechanism that forces teams to work backwards from a concrete future state rather than forwards from a feature list.
🧠 Framework Structure
The One-Year Slide: Start the year wi...
The Quarterly Reality Check: Ask, 'Ho...
Bi-Weekly Highlights: Individuals wri...
Define 'Needle Movement' First: Befor...
When to Use
During quarterly planning or when a team feels busy but leadership questions the ROI of their work.
Common Mistakes
Confusing 'shipping a feature' with 'impact.' The goal is not the release; the goal is the metric change the release caused.
Real World Example
Daniel uses a specific slide at the yearly kickoff that states, 'When I stand here a year from now, X will be different.' He holds himself accountable to that specific slide the following year.
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.
— Daniel Lereya