Radical transparency and impact-driven product transformation at monday.com

Share every metric with every employee to turn the entire company into problem-solving partners.

Before IPO, monday.com displayed real-time dashboards of churn, sign-ups, and revenue in the office lobby; post-IPO they built an internal app (Monday Morning) with role-based confidential sections so PMs still see financials.

Why: Transparency converts potential demoralization into deep partnership and distributes cognitive load across the whole team instead of isolating leadership.

"We really have an approach of very radical transparency about everything. Instead of demoralizing people, I think that this is something that gives them a sense of deep partnership."

Define success by the measurable change for customers, not by features shipped.

Teams set goals as “what will be different for customers in 3 months” and measure via daily Slack updates of key metrics; PMs are judged on relentless validation of impact.

Why: Without a clear impact metric, teams default to building more features that may never be used, whereas impact goals force prioritization of the highest-leverage work.

"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."

Set goals so aggressive they force a complete rethink of process, not just harder work.

After seeing a competitor ship 30 new column types, monday.com gave itself one month to add 25 columns (previously 4 months each) and achieved 30 in six weeks by redesigning architecture and running a one-day-per-column hackathon.

Why: Stretch goals break incremental thinking and unlock architectural simplifications that make future work orders-of-magnitude faster.

"We received a gift from our competitors. They showed us that it's possible. Use your competition, know it and take it and set ambitious goals and believe in yourself. And you can do amazing things."

Scope work by fixed time, not fixed scope, to stay focused on core value.

Teams use “Deadline Traps” tied to external events (e.g., next earnings call) to force ruthless scoping; first versions are shipped early to gather real feedback instead of polishing unused features.

Why: More time often creates more invented requirements; constraints surface the true essence of the product and accelerate learning loops.

"Many times spending more time on working on something will not yield to better results or to better products."

Let go of the superpowers that got you here when they no longer fit the next scale.

Daniel realized that mastering every detail, once a strength, became a bottleneck; he shifted to conveying only the three most meaningful things leadership needed to know.

Why: Skills that succeed at one company size can actively hinder the next; conscious unlearning is required to scale yourself with the organization.

"What got me to this phase is not necessarily what's going to make me successful in the next phase."

Not taking risk is the bigger risk; make simultaneous bold moves to learn faster.

monday.com launched five new products at once instead of one-by-one experiments, accelerating market learning and reshaping competitive positioning even though some products were later folded back in.

Why: Sequential small bets can mislead; parallel big bets reveal true market signals quickly and prevent false negatives from slow iteration.

"Not taking bold risks, not making bold moves, it's a risk for itself."

Filter feedback by who pays and who uses, not by volume or enthusiasm.

Early on monday.com avoided free trials to ensure feedback came only from paying users whose incentives aligned with real value; later they still triage feedback by business impact.

Why: Unfiltered feedback can pull the product in directions that optimize for noise rather than the cohort that drives revenue and retention.

"We really wanted to hear feedback about a product only from people that the product means something to them. The best proxy for that is that they are paying."

Start every planning cycle by describing the future state for customers, then derive the work.

Annual kickoff slide: “When I stand here next year, what will be different for our customers?”; teams do the same every quarter and every two weeks in public updates.

Why: Backward planning keeps effort tied to outcome and prevents incremental drift; it also creates a clear accountability checkpoint when the period ends.

"How do I imagine the company and the product is going to be different and better for our customers in a quarter from now? And from that, work it backwards."