How Did monday.com Transform Through Radical Transparency, Impact Over Output, and the Path to $1B ARR?

TL;DR

monday.com transformed its product organization by setting ambitious timeboxed goals, measuring customer and business impact instead of feature volume, and sharing real-time metrics across the company. After a competitor released 30 column types, monday.com challenged its four-month development cycle and produced 30 columns in about a month and a half. Read on for the operating principles behind that shift.

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?

A competitor released 30 column types while monday.com had five and was developing its sixth. Because each column had taken about four months, monday.com treated the competitor’s speed as proof that a different development approach was possible.

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

monday.com set a target of creating 25 columns in one month, which could not be reached with its existing process. By rethinking how the work was defined and developed, the team delivered 30 columns in about a month and a half.

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

The team’s long weekly updates showed substantial activity but did not clearly identify the most meaningful achievement from the previous three months. Daniel defines a great product manager as someone who relentlessly pursues and validates impact instead of stopping when a feature ships.

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

Before going public, monday.com shared extensive business information with its employees. Daniel says that this created a sense of deep partnership and brought everyone’s judgment into company challenges instead of relying on one centralized brain.

Q: How can ambitious goals improve product execution?

Ambitious goals can expose when an established method is incapable of producing the desired result. monday.com’s goal of 25 columns in one month forced structural changes because its previous process took about four months for each column.

Q: How can product teams recognize a focus problem?

A focus problem exists when a team completes many activities but cannot identify the achievement that meaningfully transformed the product. Daniel suggests defining the consequential product change the team intends to create within the next three months.

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

A team should reconsider another feature when greater impact could come from making existing value more accessible. The work is not complete until the intended impact has been achieved and validated.

Q: How did monday.com apply its faster development approach beyond columns?

After producing 30 columns in about a month and a half, monday.com repeated the approach with dashboards, widgets, automations, and other platform building blocks. The initial result gave the team confidence that apparently impossible expansion goals could be approached differently.

Summary & Key Takeaways

• Definition: Great product management means relentlessly pursuing and validating impact, not merely completing features.

• Definition: Radical transparency means broadly sharing business information and real-time metrics so employees can participate in company challenges.

• Number: A competitor released 30 column types while monday.com had five and was developing its sixth.

• Number: Each comparable column had previously taken about four months to develop.

• Step 1: Treat a faster competitor as evidence that a seemingly impossible result is achievable.

• Step 2: Set an ambitious target, such as monday.com’s goal of 25 columns in one month.

• Step 3: Redesign the development approach when the existing process cannot meet the target.

• Number: monday.com delivered 30 columns in about a month and a half.

• Compare: High activity can obscure weak focus when a team cannot name its most meaningful achievement from the previous three months.

• Who: Daniel Ara is monday.com’s chief product and technology officer and joined when the company had around 40 employees.

• Number: The discussion says monday.com had 250,000 customers after Daniel’s 8 years at the company.

• Tool: monday.com applied the same expansion method to dashboards, widgets, automations, and other platform building blocks.