How monday.com Scaled Product Impact and Speed

TL;DR

Set ambitious, timeboxed goals that force teams to rethink their methods, then measure success by customer and business impact rather than feature volume. monday.com combined this approach with radical transparency, company-wide access to real-time metrics, and lessons drawn from faster competitors, helping it scale to more than $1 billion in ARR and roughly 245,000 customers worldwide.

Transcript

A great 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. You've been at this for 8 years. You said there's 250,000 customers at this point. What wo... Read More

Key Insights

• monday.com’s competitive wake-up call came when a rival released 30 column types while its own team had only five and was developing a sixth. Because each column had taken about four months, the competitor’s release exposed a fundamental difference in execution speed.
• A competitor’s success can serve as evidence that an apparently impossible result is achievable. monday.com treated the rival release as a gift because it removed the excuse that rapid expansion was impossible and forced the team to investigate how its methods needed to change.
• Ambitious goals can force a team to redesign its approach instead of merely working harder. monday.com targeted 25 new columns in one month, then produced 30 in roughly a month and a half by thinking differently about product definition, engineering, and execution.
• High output does not necessarily produce meaningful product transformation. The team had lengthy weekly updates filled with completed work, yet struggled to identify the single most meaningful achievement from the previous three months, revealing that activity had obscured a deeper focus problem.
• Product focus requires identifying how the product will be transformed within a short period. Daniel argues that if a team cannot name the specific change that will meaningfully transform the product during the next three months, its many concurrent activities may indicate weak prioritization.
• Great product management is defined by relentless pursuit and validation of impact. The highest-impact decision is not always another feature, because teams can sometimes create more value by making existing capabilities easier for customers to discover, access, or use.
• Radical transparency can create partnership rather than demoralization. Before going public, monday.com shared extensive business information with employees, and the company also made real-time metrics broadly visible, aiming to involve everyone’s judgment in challenges instead of centralizing thinking among executives.
• Timeboxed deadlines called traps are used to strengthen focus and limit scope growth. Combined with impact-oriented goals, these deadlines encourage teams to distinguish essential work from optional additions, move faster, and judge delivery by the result produced rather than by the quantity of features shipped.

Questions & Answers

Q: How did competition change monday.com’s product strategy?

Competition changed monday.com’s strategy by demonstrating that a dramatically faster development pace was possible. A rival released 30 column types while monday.com had five and was coding its sixth, with each one previously taking about four months. The team treated that release as useful evidence, acknowledged that its existing approach was insufficient, and set a much more ambitious goal that required entirely different thinking.

Q: How did monday.com build 30 columns so quickly?

monday.com first set a target of building 25 columns in one month, even though its previous process required about four months for each column. The company could not reach that target by simply multiplying its established workflow, so the team reconsidered how it defined and developed the work. About a month and a half later, it had produced 30 columns, then applied the same exercise to other building blocks.

Q: Why does monday.com prioritize impact over output?

monday.com prioritizes impact because a large volume of completed work can create a misleading sense of progress. The team once presented long weekly updates containing many accomplishments, yet could not clearly identify the most meaningful thing it had produced over the previous three months. Daniel’s standard for strong product management is therefore persistent pursuit of a measurable result, including validation that the intended impact actually exists.

Q: What does radical transparency mean at monday.com?

Radical transparency at monday.com means broadly sharing business information and real-time metrics so employees can understand the company’s actual challenges and results. Before the company went public, it shared extensive information with employees rather than limiting it to a small executive group. Daniel says this openness created a deeper sense of partnership and allowed the company to apply more people’s judgment to important problems.

Q: How can ambitious goals improve product execution?

Ambitious goals improve execution when they make the existing method obviously inadequate and force a team to invent a different approach. monday.com could not reasonably create 25 columns in one month using a process that took about four months per column. Setting the larger target shifted attention from incremental optimization to structural change, and succeeding gave the team confidence that other seemingly impossible platform expansions could also be achieved.

Q: How can a product team tell that it has a focus problem?

A product team may have a focus problem when it completes many tasks but cannot name the specific achievement that meaningfully changed the product. Daniel suggests asking how the team will transform the product during the next three months. If the answer is only a long list of activities, rather than a clear and consequential outcome, the organization may be confusing visible effort with strategic progress.

Q: When should a product team avoid building another feature?

A product team should avoid building another feature when greater impact can come from making existing value more accessible. Daniel argues that a strong product manager remains relentless until the desired impact is achieved and validated, rather than treating feature delivery as the endpoint. This means examining whether customers can discover and use current capabilities effectively before assuming that additional functionality is the best investment.

Q: What are traps in monday.com’s product process?

Traps are timeboxed deadlines that monday.com uses to create focus, prevent scope creep, and accelerate delivery. A fixed time boundary forces teams to decide which work is essential to the intended impact and which additions can be excluded. The approach supports the broader operating principle that teams should pursue meaningful outcomes efficiently, rather than allowing expanding requirements or feature volume to become substitutes for validated results.

Summary & Key Takeaways

• monday.com recognized a serious execution problem when a competitor released 30 new column types while each comparable addition had been taking its team about four months. Rather than dismissing the comparison, the team treated it as proof that much faster development was possible and reconsidered its entire approach to building the platform.

• The company responded with an ambitious target of creating 25 columns in one month. Although the team ultimately needed about a month and a half, it delivered 30 columns by changing how it approached the work. It later repeated this method with dashboards, widgets, automations, and other platform building blocks.

• Daniel Lereya connects monday.com’s growth with radical transparency, impact-oriented product management, timeboxed deadlines called traps, and a willingness to replace methods that no longer fit the company’s scale. These practices helped align employees, sharpen focus, challenge scope growth, and support expansion beyond $1 billion in ARR.