Client churn is spiking during handoffs because neither Sales nor Delivery wants to own our Client Onboarding seat on the Accountability Chart. How do we force accountability and assign this orphaned seat when both departments refuse it?

Question

Tyler Smith · Accepted Answer

When an orphaned function falls between departments, both teams point fingers because handoffs create friction without immediate glory. Sales wants to close deals and collect commission. Delivery wants clean, perfectly scoped projects dropped on their desks. Client onboarding sits in the messy middle, and because nobody owns it on your Accountability Chart, your clients are paying the price.

In EOS®, structure dictates accountability. You cannot have shared ownership. Two names in one seat means no one is truly accountable. Use this sequence to resolve the standoff:
- Define the seat independently: Pull onboarding out of both departments and build it as a distinct functional seat on your Accountability Chart. Document its five core roles, such as client kickoff orchestration, data migration tracking, scope verification, time-to-first-value acceleration, and transition sign-off.
- Assign clear measurables: Attach definitive Scorecard measurables to the seat, such as days from contract signature to kickoff, client onboarding satisfaction score, and percentage of zero-defect handoffs.
- Decide reporting line objectively: Ask which department head has the natural capability to lead, manage, and hold this seat accountable. If onboarding requires aggressive relationship pacing and boundary enforcement, it often sits best under Operations. If it requires technical scoping checks, it may sit under Delivery.

If neither leader will take the seat willingly, the Integrator must step in and assign structural accountability. The selected department head does not necessarily have to do the daily onboarding work, but they must own the seat until they hire or appoint someone who has full GWC™ for it. Indecision is what is driving your churn.