The organization chart shows who reports to whom, not how work actually gets done. Most enterprise services don’t live inside one team. They move across units, roles, and often partner organizations to produce a single public-facing result.
A handoff is the transfer of responsibility—when work leaves one group’s control and becomes another group’s next action. If leaders don’t define what must transfer with the work (ownership, status meaning, required inputs, timing expectations, and decision rights), accountability doesn’t transfer either. It breaks down handoff by handoff until the real question surfaces: Who is accountable for the outcome end-to-end?
That’s the part many organizations miss—and it’s one of the biggest reasons cross-department outcomes stall. Leaders define the problem as a performance issue in one unit, when the real risk sits in the cross-department handoffs required to deliver the outcome.
In one complex, multi-unit regulatory organization, the problem statement was widely framed in a narrow way: “We issue violations, but closure rates and collected revenue are too low.” Customers experienced this as “nothing happens.” Oversight bodies tracked it as poor performance. Internally, the spotlight stayed on the unit that issued the violations—as if the outcome lived inside that one team. Meanwhile, a large share of organizational time and effort went to fielding complaints, responding to oversight inquiries, and launching well-intended but disconnected attempts to fix the issue.
When I was asked to help improve results by pinpointing what was driving the breakdown—and examined how cases moved from initiation to completion—one thing became clear: the service was being managed and measured like a single-unit problem, but the outcome was produced across multiple teams and partner touchpoints.
That service consistently broke down in two ways:
- Handoffs weren’t managed as part of performance.
- Transfers were treated as routine coordination—not performance-critical moments—so ownership, requirements, and timing weakened each time work changed hands.
- The end-to-end definition of success wasn’t shared.
- Teams did real work, but not from the same definition of “done,” urgency, or downstream requirements. In several places, the work sat inside units whose primary mission wasn’t achieving the end-to-end result—so it was treated as secondary, episodic, or “when we can.”
That combination—handoffs that aren’t managed as part of performance, plus no shared definition of end-to-end success—creates the conditions where accountability predictably disappears. Not because people aren’t trying or performing. Because the workflow was never designed to carry ownership from one handoff to the next.
What the handoffs create: hidden drag and blurred ownership
In many organizations where delivering one service requires multiple departments, it’s common to find that the org chart—and the budget behind it—doesn’t reflect how the work actually flows. Roles, funding, performance measures, and leadership attention stay anchored inside individual units, even when the service outcome is produced across many of them.
Roles, funding, performance measures, and leadership attention stay anchored inside individual units, even when the service outcome is produced across many of them. I call this “Org-chart gravity:” the pull of reporting lines, budgets, unit measures, and role expectations that keeps leaders considering and managing services the “official” way—often limiting how they imagine what’s possible, especially for cross-department services.
That anchoring is exactly what makes modernization and change so hard. Updating the service requires changing how work moves across departments—but org charts, budgets, and performance measures are built to preserve unit boundaries, not redesign work end to end.
As a result, a familiar pattern emerges: the service is cross-unit in reality, but it gets managed as if it belongs to one place. And when the outcome falls short, leaders reach for fixes that match the org chart—more staffing in the “owner” unit, new procedures in that unit, new targets for that unit—while the true sources of delay and rework sit in handoffs nobody is actively managing.
Here’s how that hidden drag shows up:
- The problem gets framed too narrowly. The headline becomes “Unit X isn’t performing,” because that’s where the most visible work sits—even when the outcome depends on steps outside that unit’s control.
- Budgets and priorities reinforce local ownership. Units optimize for what they’re funded and measured to do, not for an end-to-end outcome that isn’t formally assigned to them.
- Cross-unit work has no natural meeting place. Unless someone deliberately convenes it, cross-department work lives in email threads, side conversations, and ad hoc escalations—easy to dismiss as coordination noise rather than a performance driver.
- Symptoms get treated as effort problems instead of design problems. Backlogs, rework, missed windows, and stalled cases trigger “push harder” responses—rather than fixing what must transfer at handoffs.
- Manual workarounds quietly fill the gaps. Separate trackers, duplicate entry, checklists, and follow-ups consume time while remaining largely invisible as “real work.”
- Customers feel the failure first. They don’t experience handoffs; they experience the stall: “nothing happens,” “it’s closed but not resolved,” or “I keep getting bounced around.”
And because systems often aren’t linked, staff still have to bridge gaps manually just to answer basic questions: Where is it now? What’s missing? Who owns the next move? What does “done” mean here?
That pattern is common when no one owns the end-to-end outcome, yet the work remains anchored to the org chart, budgets, and unit measures. Leaders manage what they can see and control—while the handoffs keep driving the results.
What leaders miss: you can’t manage an outcome you haven’t defined
When a service outcome depends—as it often does—on contributions from multiple units, including specialists who support many priorities, performance can’t be managed as if it belongs to one team.
The leadership trap is treating a cross-department service like a single-unit performance problem—pushing harder on the most visible team while the handoffs that determine the outcome remain unmanaged.
That means the fix isn’t “try harder.” The fix is to make two things explicit across the end-to-end workflow:
- What outcome the service must deliver (plain language, measurable, time-bound)
- What must be true at each handoff to keep the outcome on track (so ownership can transfer cleanly)
Without changing what leaders are anchored to—org charts, budgets, and unit measures—the organization keeps treating symptoms, because the shared outcome and handoff requirements never become the basis for managing performance.
What to do: the Service Reset playbook
The challenge is that most organizations try to modernize while staying anchored to yesterday’s structures—org charts, budget lines, unit measures, job descriptions, and ingrained expectations of subordinate leaders—that were never designed to manage end-to-end services across departments in today’s operations.
That’s why the most effective “how-to” starts with leadership behavior: leaders initiate end-to-end modernization by engaging the right people to recognize the service as end-to-end, make the outcome explicit, and improve how work moves between units.
In today’s environment, launching a Service Reset is needed so often that it’s becoming a standard leadership requirement.
1) Define the shared outcome end-to-end
Convene the units—and any partners—who touch the workflow to define the end-to-end outcome together. No single person can write this for everyone else, because each handoff changes what the next step needs and what “good” looks like.
A usable shared outcome has three parts:
- What “resolved” means (the real-world result the service exists to deliver)
- What “timely” means (the timeframe the full workflow is working toward)
- What “complete” means (the minimum requirements each step must meet so the next step can succeed)
Launching this work changes the game. It pulls a cross-department service out of the org chart and into a shared, end-to-end view—so leaders can see where the outcome gets delayed, distorted, or handed off without clear ownership. It also creates a place for cross-unit work to happen on purpose, instead of through escalations and side conversations.
2) Define the handoff contract
For each major transfer, define the minimum requirements that make the next step possible—no guessing, no heroic follow-up, no “it depends.” A handoff contract is short and practical:
- Required information and documentation
- Quality checks that prevent rework later
- Who becomes responsible upon receipt
- What “done” means at that step
- What happens if the contract isn’t met (one standard return path)
This is how you reduce defects and rework without adding bureaucracy.
3) Standardize status language across units
If one unit’s “closed” means “we finished our part,” while another unit’s “closed” means “the case is resolved,” leaders get false confidence—and customers get burned.
Create a small, shared status set that reflects reality end-to-end (units can keep internal sub-statuses). The goal is simple: one meaning for each status, understood the same way across the workflow.
4) Create one shared view of case progress
You don’t need the perfect system on day one. You need a single place where a leader—or any unit in the workflow—can answer:
- Where is it now?
- Who owns the next move?
- What’s the blocker?
- What’s the expected next step and timing?
This can start as a minimal dashboard or disciplined tracking layer that sits above existing systems. The point is shared visibility—because without it, management turns into chasing.
5) Make it stick: reconvene, troubleshoot, and reinforce
This is the part leaders often underestimate: it’s not a one-time workshop. It’s living follow-up. Without ongoing attention, people drift back to familiar workarounds and “how we’ve always done it”—and the Service Reset quietly unravels.
That’s why this move requires named ownership for the end-to-end workflow—not to own every unit’s work, but to keep the shared outcome on track across units and reinforce the new way of working until it becomes normal.
In practice, that means someone (or a small cross-unit group) has responsibility to:
- Reconvene the right players at a regular cadence (short, focused, outcome-based)
- Review a small set of shared measures tied to the end-to-end outcome (closure, timeliness, defects/rework, and where cases stall)
- Make targeted adjustments to handoff contracts, status language, and visibility gaps
- Share results with key stakeholders so leadership attention stays on system performance, not isolated unit performance
- Troubleshoot issues in real time, maintain an escalation path, and sustain ongoing cross-unit communication to support adoption and prevent drift back to old practices
Without this follow-through, the organization falls back to local optimization—and the end-to-end service breaks down again.
Next steps: As the new workflow stabilizes, update the organizational anchors that drive behavior—performance reviews, policies and procedures, job expectations, and (when necessary) team structure—so the end-to-end outcome is supported and sustained. Then identify targeted technology improvements that remove manual work, improve visibility, and reinforce the new way of working.
The payoff
These moves don’t eliminate complexity. They eliminate ambiguity.
They don’t make the workflow perfect. They make it visible—so an end-to-end process buried across units and partner organizations can finally be seen, managed, and improved.
That visibility makes it possible for many units to produce one outcome without constant escalation and manual reconciliation. It also helps leaders move beyond org-chart-limited fixes by showing exactly where the workflow breaks down—and what needs to change to deliver consistently good service.
