How to rebuild trust between departments that blame each other
Rebuild trust between departments by choosing a disputed handoff and making its requirements explicit. Agree what the receiving team needs, who can accept the work, and how exceptions reach a decision. Review the next delivery against that agreement before asking either department to change its attitude toward the other.
Cross-functional trust is a willingness to rely on another department despite exposure to its actions, applying Mayer, Davis, and Schoorman’s 1995 model of organizational trust to an interdependent workflow. This application does not create a separate validated measure. Use the definition to ask where reliance is necessary and what evidence would make it more reasonable.
Trust differs from liking colleagues or approving every request they make. A handoff is an exchange of work with an intended recipient and a completion condition. You can define that condition even while the relationship remains strained. Do not require personal reconciliation before clarifying the work that customers and colleagues are waiting for.
Start with the handoff that interrupts your evening
Consider this composite. You are packing for a short trip with your partner when sales and operations begin copying you into a familiar dispute. Sales says operations is delaying a signed commitment. Operations says the sale never included the information needed to begin. You answer from the bedroom, write “please collaborate,” and return to the suitcase. By morning both teams have separate records showing that the other department failed.
Do not decide which department is generally more difficult. Identify the specific work item, the promise attached to it, and the point where ownership became unclear. Ask for the records that existed before the disagreement. Separate a customer commitment from an internal assumption about what the receiving team would accept.
The scene is a composite. Its value is the recurring operating pattern, not a claim about a real company. If your only effective handoff rule is that both departments must persuade you after hours, the next review should examine your role in the workflow as well as theirs.
Use the shared-handoff agreement
This proposed method converts a relationship complaint into an inspectable work agreement. It is not a substitute for addressing misconduct, discrimination, or other employment matters through the appropriate professional process. Involve employment counsel when those issues arise. Do not use a process workshop to suppress a legitimate complaint.
1. Reconstruct one work item together
Select a representative disputed handoff. Ask each department for the request, supporting information, acknowledgement, changes, and decision history. Put the events on a shared timeline. Mark a missing record as missing. Avoid filling a gap with a claim about what the other person must have intended.
Read the timeline aloud and invite factual corrections. A sales promise may have changed after the receiving team reviewed the original request. An operations requirement may have appeared only after the due point. Neither possibility should be assumed. Establish the sequence before deciding which part of the process needs repair.
2. Define the receiving team’s acceptance criteria
Ask the receiving owner what information and approvals are required to begin responsibly. Make each condition concrete enough for the sending team to check. “A complete brief” is too vague unless the parties agree what completeness means. Identify required fields, decision authority, and the work that remains intentionally unresolved.
Test the list against the disputed item. Ask which missing element would have changed a real action. Remove preferences that add effort without affecting acceptance, and preserve requirements tied to safety, quality, or an actual delivery dependency. Do not lower a necessary standard solely to make the disagreement disappear.
3. Define the sender’s promise
Write what the sending team commits to supply and what it is not authorized to promise on the recipient’s behalf. Identify who can change scope, sequence, or a customer expectation. If the sender needs an urgent exception, give them a route to a person who can approve it rather than an instruction to push harder.
Ask the receiving team to acknowledge the same promise. A requirement that exists only in one department’s internal procedure is not yet a shared agreement. Make the point of acceptance visible to both sides. State what happens when acknowledgement does not arrive, rather than allowing silence to count as consent by default.
4. Close the communication loop
Have the receiver confirm what they understood and identify any discrepancy. Salas, Sims, and Burke’s 2005 teamwork review identifies closed-loop communication among coordination mechanisms. Here, use a simple operational version: request, acknowledgement, and confirmation of the agreed next action. Do not treat a sent message as evidence that the work was understood or accepted.
A proposed confirmation is: “We have the approved scope and the required input. We accept the handoff for the agreed next stage. These unresolved items remain with the sender, and this condition would require us to stop.” Adapt that wording to the work. Keep it short enough that people will actually use it.
5. Establish an exception decision
Define the conditions that require escalation: conflicting commitments, a missing approval, a changed requirement, or an exposure outside either team’s authority. Name the decision owner and what they need to see. State who covers that role when the usual owner is unavailable. A list of escalation contacts without decision authority is incomplete.
Require the exception record to explain the tradeoff, not accuse a department. Ask what will be delayed, changed, or left exposed under each option. Do not reward the person who presents the most dramatic version. Make the decision from the current evidence and record which obligation changed as a result.
6. Review the next handoff against the agreement
Choose the next suitable work item and observe the actual exchange. Check whether the sender could meet the criteria, the receiver could acknowledge acceptance, and exceptions reached the owner. Record where the agreement was unclear or impractical. Repair those points before scaling the method across every departmental boundary.
Ask both teams to identify what became easier and what still requires an informal workaround. Do not demand a positive report because the agreement was your idea. If the method adds duplicate administration without resolving the decision gap, simplify it. The useful result is a more reliable transfer, not a thicker procedure.
Distinguish a broken agreement from a broken relationship
A handoff review may reveal a straightforward process defect. It may also reveal conduct that no checklist will solve: repeated misrepresentation, deliberate withholding, or personal attacks. Keep the categories separate. Do not imply that agreeing new fields erases a concern about how people have been treated.
Equally, do not infer bad intent from every incomplete handoff. Ask what information was available and whether the parties had the same understanding of completion. If the issue remains contested, use an appropriate independent review. A CEO’s preference for one leader’s explanation should not substitute for evidence about the disputed event.
Where both sides have made reasonable choices under incompatible targets, examine the targets. A sender measured on speed and a receiver responsible for unverified exposure may be responding to different instructions from the same leadership team. State the tradeoff you want them to make. Do not ask them to resolve contradictory priorities through goodwill alone.
Give the team an escalation script
Try: “We have a handoff exception, not a decision about which department is more committed. The receiving criteria require this input. The sender cannot supply it by the requested point. Here are the available options, the exposure under each, and the person authorized to choose. We need that choice before the work moves.”
If either side disputes the criteria, pause and establish whether an earlier agreement exists. Do not introduce a new requirement and describe it as something everyone already knew. If a live customer obligation needs immediate attention, separate containment from the longer process redesign. Name what can safely proceed and what remains blocked.
For senior leaders, require the same discipline. Do not let an executive bypass the agreed route simply by copying you. Ask them to state the exception and the decision required. If your own intervention changes the priority, make that change explicit so the receiving department is not later judged against the original plan.
Check whether concerns can travel across the boundary
Morrison’s review of employee voice and silence concerns whether useful work information reaches people above the employee. Apply the question to the handoff: can someone identify a missing condition without being described as obstructive? A procedure is incomplete if its users cannot report that it is not working.
Invite a specific objection before adopting the agreement. Ask the people doing the work which requirement is hard to verify, which acknowledgement is redundant, and where authority is still unclear. Do not assume the department heads can describe every practical step. Include the work owners while keeping accountability for the final design with the appropriate leaders.
Use the broader executive trust process for unresolved relationship concerns. If the discussion becomes defensive, structure the feedback conversation around the disputed event. When the conflict concerns resources or priorities, use a resource-conflict review rather than presenting the problem as a failure of team spirit.
Keep the agreement alive through actual work
After the trial, retain the acceptance criteria, exception owner, and review point in the place people already use to manage the work. Remove obsolete versions. Ask who is responsible for maintaining the agreement when the service, customer promise, or organization changes. A shared rule should not depend on both original authors remaining in their roles.
Review a failed transfer and a successful transfer. The failure may reveal a missing condition, while the success may depend on an unrecorded workaround. Capture the useful lesson without turning every exception into another mandatory field. Preserve enough structure to support reliance and enough flexibility to handle a real change in circumstances.
Your role is to make the interdependence governable. Ask departments to make explicit commitments, verify what arrives, and escalate real exceptions. Let trust develop from repeated evidence about those commitments rather than from an instruction that the teams should simply trust each other more.