Daniel Lereya

We went from 4 months to build one column type to 30 columns in a month and a half. The key: we stopped and defined what a column actually *is*, built shared infrastructure for it, then ran a hackathon where each dev built one column in a single day.

The sign you're not impact-driven: you can't answer 'what is the most meaningful thing we did in the last 3 months?' If it takes you a long time to think, you have a focus problem.

A smell that your team isn't impact-driven: they use words like 'enhance,' 'augment,' or 'extend value.' That's not enough. What will change for users, and how will you know it actually happened?

We had AI blocks getting rave feedback, customers loving it — but only a few thousand of our 250,000 customers could access it due to a terms-of-service issue nobody prioritized. Two weeks later, we opened it to 98% of customers. That's the real work of impact.

Every quarter, ask yourself: 'How do I imagine the company and product will be different and better for customers in 3 months?' If you can't point to something specific, you don't have a focus problem — you have an impact problem.

Every team at Monday gets a 'daily numbers update' — a Slack message with all the metrics they care about. We want people to *live* these numbers, not just check them in quarterly reviews.