Monday.com teams can use DACI to speed cross-functional decisions

DACI gives monday.com teams a cleaner way to make calls

Cross-functional work gets messy fast when everyone feels responsible and no one is actually accountable. That is where DACI earns its keep at monday.com: it turns vague alignment into a decision structure that names one Driver, one Approver, the right Contributors, and the right people to keep Informed.

The appeal is practical, not theoretical. monday.com runs on coordination across product, engineering, sales, operations, and customer-facing teams, and the company says more than 250,000 customers worldwide use its platform while about 2,900 employees build and support it. When a company at that scale is handling 2 million board actions every day, even small decision delays can ripple into launch timing, customer commitments, and internal handoffs.

Why consensus often slows the work down

A lot of workplace friction starts with a familiar failure mode: too many stakeholders, too many opinions, and no clear final owner. Teams revisit the same options in Slack threads, wait for “alignment” that never quite arrives, and mistake broad input for a decision. DACI is useful because it separates collaboration from authority instead of pretending they are the same thing.

Atlassian’s framing is blunt and useful. DACI stands for Driver, Approver, Contributors, and Informed. The Driver corrals stakeholders, collects information, defines scope, and keeps the decision moving by an agreed date. The Approver is one person, not several, which matters because committees often dilute accountability until no one can tell who actually made the call.

That distinction matters inside monday.com because many work-management problems are really decision-right problems. If product is debating a launch tradeoff, engineering is weighing implementation risk, and sales is hearing pressure from a strategic prospect, the issue is not a lack of ideas. It is a lack of clarity about who owns the final decision and who is simply advising it.

How DACI fits monday.com’s business

monday.com is not a single-product startup anymore. Its platform now spans four end-to-end product areas: work management, CRM, software development, and services, all on the same AI layer. That kind of breadth makes clear decision-making more valuable, not less, because different teams can easily pull in different directions if roles are fuzzy.

The company’s origin story helps explain why this framework resonates. Co-founders Roy Mann and Eran Zinman built monday.com after experiencing the strain of scaling organizations quickly. They launched in 2013 from a vacated apartment in Tel Aviv with their first 6 customers, then grew into a public company when it officially went public on Nasdaq on June 10, 2021.

That path from scrappy startup to large public SaaS company creates a specific kind of pressure. The larger the customer base and the broader the product surface area, the more expensive indecision becomes. monday.com’s own numbers underline that point: fiscal 2024 revenue reached $972.0 million, up 33% year over year, and fourth-quarter 2024 revenue hit $268.0 million, up 32% year over year. The company also said it surpassed $1 billion in annual recurring revenue.

Where DACI can help the most

DACI is strongest in the places where teams are most likely to confuse input with ownership. For monday.com product managers, that can mean sharper launch planning and less product churn when a feature needs sign-off across design, engineering, go-to-market, and support. For engineers, it can reduce endless debate over architecture or implementation choices by making clear who gathers input and who closes the loop.

Sales teams can use the same logic in deal work, pricing changes, and customer escalations. A deal owner is not the same as a pricing approver, and neither is the same as the specialist who contributes context on margins, packaging, or legal risk. DACI makes those distinctions visible before the conversation turns into a bottleneck.

• Driver: owns the process, corrals stakeholders, and pushes the decision to a date.

• Approver: makes the final call, and there should be only one.

• Contributors: provide expertise, evidence, and scenario testing.

• Informed: stay updated, but do not stall the decision.

That structure is especially useful in a company like monday.com, where the platform itself is built to make work more visible. If the company asks customers to track ownership, status, and timing in boards, internal teams can and should use the same discipline for decision-making.

Why accountability makes collaboration better

One of the common objections to frameworks like DACI is that they sound rigid. In practice, they usually do the opposite. Clear ownership often makes collaboration easier because people know when they are expected to speak, when they are expected to decide, and when they are expected to step back.

Atlassian’s Confluence DACI template says the method helps avoid analysis paralysis by putting someone in charge of making sure the decision actually gets made. That is the core benefit for monday.com teams: less circular debate, fewer ambiguous handoffs, and a cleaner path from discussion to execution.

That lesson becomes more important as the company scales. In second-quarter 2024, monday.com said it closed an 80,000-seat agreement, the largest deal in company history, and that the quarter marked its first GAAP operating profitability. Big deals and improved profitability both raise the stakes for fast, clean decisions. When the business is moving that quickly, a framework that clarifies who drives, who approves, who contributes, and who needs to know is not bureaucracy. It is operating discipline.

What good DACI usage looks like at monday.com

The best use of DACI is not to create more process for its own sake. It is to make sure every important decision has a visible owner and a real deadline. For monday.com teams, that means using DACI around product launches, customer escalations, pricing changes, and cross-functional initiatives where delay is more expensive than disagreement.

The practical test is simple: if the team cannot quickly answer who drives, who approves, who contributes, and who needs to know, the decision is not ready yet. That clarity can save hours of back-and-forth, protect launch momentum, and keep high-growth teams from mistaking discussion for progress.

For a company that grew from six customers in a Tel Aviv apartment to a public SaaS platform serving hundreds of thousands of customers, DACI fits the moment. The company’s scale, product mix, and pace of execution make clear decision rights more valuable every quarter, and the teams that adopt them will move faster because of it.