Our CRM data hygiene and billing integration is a disaster, but both Sales and Finance insist it belongs in the other department, leaving this data seat completely orphaned. How do we force clear ownership on our Accountability Chart for a cross-departmental administrative function that nobody wants to own?

Question

Tyler Smith · Accepted Answer

In EOS, every function essential to executing your business plan must live somewhere on the Accountability Chart. If a function lives nowhere, it gets done poorly, reactively, or not at all. Cross-departmental functions like CRM data hygiene, system integration, or pipeline audits often fall into the cracks because they require coordination between Sales, Operations, and Finance. When both department heads point fingers, the Integrator must step in and make the structural call.

First, look at the output of the seat, not the inputs. Who suffers the most direct commercial consequence when the data is wrong? If dirty CRM data leads to missed revenue targets or unbilled renewals, the seat belongs inside Sales or Finance, not floating in limbo.

Define the seat with five clear, measurable roles. For example: CRM Data Hygiene, System Integration Audits, User Field Compliance, Data Enrichment, and Weekly Accuracy Reporting.

Once the seat is defined on the chart, identify who has the GWC to own it. That means they Get It, Want It, and have the Capacity to do it. If nobody on the leadership team wants it, the Integrator assigns it to the seat where operational failure causes the most pain. That leader becomes accountable for the seat. They do not have to execute every manual field clean-up task themselves, but their neck is on the line for the scorecard measurable tied to data accuracy.

If neither leader has the capacity to execute the work, automate the data hygiene with AI tools or delegate the tactical tasks to an administrative seat. Accountability, however, remains squarely in one department.