When Everyone Owns the Work, Who Makes the Call?

Shared ownership can stall work when nobody has authority to decide. Learn how clear roles for decisions, execution, and follow-up keep cross-functional teams moving.

A handoff can look complete and still be stuck. The checklist is filled out. The right departments are included. Everyone understands the customer’s goal. Yet a consequential question remains unanswered because nobody knows who has permission to answer it.

This is the weakness in saying “we all own it.” Shared commitment is valuable, but it does not establish decision authority. When participation, execution, and approval are treated as interchangeable, collaboration can become a waiting room.

The solution is not less teamwork. It is a clearer agreement about three responsibilities: who decides, who does the work, and who follows up.

Hypothetical: A Customer Launch Waiting for Permission

The following scenario is entirely hypothetical.

A software company is preparing to move a new customer from implementation into ongoing support. Configuration is complete, training is finished, and the implementation manager has circulated the handoff checklist.

One issue remains: a reporting feature will not be ready for launch. The customer could begin using a manual workaround or postpone the rollout.

Implementation considers the account ready to transfer. Support will accept it once someone approves the workaround. The account executive wants to preserve the launch date but assumes the product leader must approve any missing functionality. The product leader has explained the technical limitation and believes the customer-facing team will make the business decision.

The checklist names all four teams. It names nobody authorized to choose between launching and waiting.

By the next afternoon, the customer still has no answer.

Nobody has refused to work. The failure is more specific: responsibility for contributing has been mistaken for authority to decide. Another request for a status update will not resolve that ambiguity.

Who Makes the Call?

The first intervention is to write down the unresolved decision:

May this customer launch with the documented workaround, or must the launch wait?

That question is narrower and more useful than “Who owns the customer?” It identifies the trade-off that requires authority.

In this hypothetical, the company designates its customer-success director to make that call within established boundaries. Product explains the technical limitations. Support assesses the service burden. The account executive explains the customer’s priorities. Their input matters, but providing input does not make each contributor a final approver.

Atlassian’s DACI framework provides useful language for this distinction. The Approver makes the decision; Contributors supply expertise and recommendations. The Driver gathers the necessary information and moves the decision toward its deadline.

Give the authority boundaries

Naming a decision-maker does not give that person permission to bypass existing controls. The director’s authority should specify which business trade-offs are permitted and which issues require additional approval. Security requirements, contractual commitments, and other established constraints remain in force.

GitLab’s directly responsible individual guidance recognizes that additional approvals or a separate decision-maker may be necessary in some circumstances. Clear ownership should clarify those requirements, not erase them.

Before requesting a decision, document the required input and the decision deadline. If a prerequisite approval is missing, name the person who must provide it and the escalation path. Otherwise, the organization has merely moved the ambiguity up a level.

Who Does the Work?

Continue the hypothetical: the customer-success director approves proceeding, subject to customer acceptance of the workaround and a documented support procedure.

That approval establishes a path forward. It does not complete the handoff.

The decision now needs to become concrete assignments:

  • Account executive: Confirm that the customer accepts the workaround. Completion evidence is the customer’s written acknowledgment.
  • Implementation manager: Document and test the workaround. Completion evidence is the finished procedure and recorded test result.
  • Support lead: Review the support procedure and accept the account when the conditions are satisfied. Completion evidence includes a named support contact and recorded acceptance.

In the actual handoff agreement, replace these role labels with the assigned individuals’ names. A department can supply resources, but “Support” is not a sufficiently precise answer when someone needs to know whose commitment is outstanding.

Each assignment also needs a completion deadline. “Before launch” is useful only if the launch timing is understood and the receiving team has enough time to review the work.

Keep execution responsibility distinct from decision authority. GitLab’s guidance separates responsibility for completing work from ultimate accountability; someone else owning the final decision does not eliminate an executor’s obligations.

A decision without assignments is an intention. An assignment without completion evidence is an assumption.

Who Follows Up?

Even a sound decision and clear assignments can leave a handoff unfinished. Someone must keep the commitments connected until the receiving owner accepts the work.

In this hypothetical, the implementation manager remains the follow-up owner until support explicitly accepts the account. This is a proposed operating practice, not a universal formal role. It extends the coordination function described in DACI, which also calls for communicating outcomes, assigning action items, and documenting the final decision.

The follow-up owner should:

  • Publish the decision, its conditions, and the agreed deadlines.
  • Check that each promised deliverable has the required completion evidence.
  • Surface missed commitments while there is still time to respond.
  • Escalate unresolved blockers to the named decision-maker.
  • Record the receiving owner’s acceptance before closing the handoff.

This person is not automatically responsible for performing everyone else’s work. The responsibility is to keep the handoff visible and moving, not silently absorb every unfinished task.

The escalation rule matters. If the workaround fails testing or the customer does not accept it, the implementation manager should return that blocker to the director rather than treat the conditional approval as unconditional permission to proceed.

In the hypothetical’s resolution, the customer provides written acceptance, implementation documents and tests the procedure, and the support lead records acceptance with a named support contact. Only then does the implementation manager close the handoff.

The approval message was a milestone. Acceptance completed the transfer.

A Short Handoff Agreement

The practical tool is a short written agreement, not another elaborate reporting system. Put it wherever the participating teams already coordinate their work.

Use this checklist before transferring consequential work:

  • Decision needed: State the unresolved question in a sentence that can be answered.
  • Decision-maker and authority limits: Name the person authorized to decide, the boundaries of that authority, and any additional approvals required.
  • Required input and deadline: Identify the necessary contributors, when their input is due, and when the decision must be made.
  • Execution owners and deliverables: Name each person, the promised output, its deadline, and the evidence that establishes completion.
  • Follow-up owner: Name the person responsible for tracking commitments and keeping the handoff open until acceptance.
  • Receiving owner and acceptance criteria: Specify who accepts the work and what must be true before that acceptance occurs.
  • Escalation trigger and destination: Define which missed deadline, failed condition, or unresolved blocker requires escalation—and to whom.

These responsibilities do not require separate people in every case. The implementation manager in the hypothetical both executes work and coordinates follow-up. What matters is that each responsibility is explicit and feasible.

Clarity Supports Collaboration

Clear authority is not an argument for excluding expertise. It gives contributors a defined way to influence a decision without leaving everyone uncertain about who can make it.

Google’s research on team effectiveness identified structure and clarity—including understanding expectations and the process for meeting them—as important within the teams it studied. That provides supporting context, not proof that this particular handoff agreement will improve performance everywhere.

Likewise, DACI and GitLab’s guidance are practical frameworks, not guarantees. Their value here is in helping teams distinguish participation from authority and execution from coordination.

The distinction matters in customer operations, cybersecurity, and AI governance alike: technical expertise should inform a decision, while authority and required approvals remain explicit.

Keep the Work Collaborative. Make the Decision Explicit.

The answer to unclear ownership is not to make everyone less responsible. It is to make the responsibilities unmistakable.

Before your next consequential handoff, write down three answers: Who can make the call? Who will carry it out? Who will make sure it reaches completion? Then add the deadlines, authority limits, acceptance criteria, and escalation path.

Do not close the handoff because a message was sent or a checklist was circulated. Close it when the receiving owner has accepted the work. That is the difference between distributing responsibility and completing a transfer.

Browse all insights · Contact Bart McDonough