One of the most disorienting experiences in delivery is watching a program fail while every team involved can honestly say they performed. Timelines were met. Budgets were respected. Quality held up. And still, the outcome the organization needed didn't arrive. This essay is about what actually happened and why the diagnosis almost always points somewhere other than people.
"The system broke not because one team failed, but because two teams succeeded in incompatible directions. No single actor was wrong. The architecture was."
The Invisible Breakdown
The failure arrives without a clear author. The project closes, the teams report completion, the dashboards show green, and still the business outcome that the whole effort was meant to produce hasn't materialized or arrived damaged, delayed, or misaligned with what the organization actually needed. The retrospective searches for accountability and finds none that fits neatly, because no individual team dropped the ball in the conventional sense.
This pattern, recognizable to almost any delivery professional who has worked across functions, has historically lacked a structural name. The language now emerging calls it horizontal misalignment: the gap between teams that are aligned vertically to their function's goals and teams aligned horizontally to shared delivery outcomes. Organizations consistently achieve the former. They routinely fail at the latter.
Horizontal misalignment is not a coordination failure. It is an architectural condition: the predictable result of building organizations around functional performance without building the structural connective tissue that allows functions to produce collective outcomes. The consequences are measurable. Research from the Center for Creative Leadership and Gartner both point to the same finding: organizations experiencing high collaboration drag are significantly less likely to achieve delivery goals. The cost of horizontal misalignment is not abstract. It shows up directly in outcomes.
Vertical vs. Horizontal Alignment
Vertical alignment is what most organizations are built to produce. A function has a goal. The leader sets targets. Teams are measured against those targets. Resources flow toward activities most likely to hit them. This is a well-understood system with well-understood incentives, and most organizations are reasonably good at it.
Horizontal alignment is structurally different. It requires teams whose goals, timelines, and success metrics are set by different leaders, funded through different budgets, and measured through different reporting lines to nonetheless produce a coherent collective outcome. Nothing in the vertical structure creates this. It has to be designed separately and in most organizations, it is not.
- Goal set within the function
- Success measured at the functional level
- Accountability runs upward through the hierarchy
- Optimization is local by design
- Conflict resolves through management chain
- Goal shared across functions
- Success measured at the system level
- Accountability runs across boundaries
- Optimization requires cross-functional coordination
- Conflict has no structural resolution mechanism
The critical observation: vertical alignment does not prevent horizontal misalignment. It often produces it. When each function is optimizing against its own goals, the incentive to absorb cross-functional cost for the sake of system-level outcomes is low. The team that slows down to enable a dependency it does not own is accepting a local cost in service of a collective benefit its metrics will not capture. Most teams, operating rationally within their vertical structure, will not make that trade consistently. This is not a failure of values or intent. It is a structural incentive problem.
The Anatomy of a Local Win
Consider a scenario recognizable in almost any complex organization. A VP of Operations delivers a strong quarter. Vendor consolidation reduces procurement costs by 12%. The savings are real, documented, and celebrated in the quarterly review. The VP receives a strong performance rating. The function has performed.
In the same quarter, the VP of Sales' team loses three major accounts. The reason: the consolidated vendor base created supply constraints that operations had modeled as acceptable, based on historical demand patterns. The sales team's pipeline, which had shifted toward a segment with different delivery timing requirements, was not in the model. Nobody told operations. Operations did not ask. There was no structural mechanism that required the conversation before the decision was made.
Both leaders performed within their vertical accountability. Both were operating rationally given the information and incentives available to them. The system broke because the decision operations made was architecturally adjacent to a condition sales depended on, and there was no horizontal structure that surfaced that dependency before the decision was finalized.
This is the anatomy of a local win that produces system-wide chaos. Neither team failed. The architecture failed. And because the two leaders were measured separately, the failure had no single owner and no structural home.
The Alignment Tax
Every organization with horizontal misalignment is paying an alignment tax: the accumulated cost of work that has to be done, redone, or worked around because structural coordination did not happen at the right moment. Unlike most delivery costs, the alignment tax is largely invisible in standard reporting. It does not appear as a line item. It appears as friction, rework, delay, and lost outcomes attributed to other causes.
Decisions made within one function alter conditions another depends on, without a structural trigger for the conversation. The dependency surfaces only when the impact is already in motion.
Functions are measured on indicators that are structurally in tension. No shared metric exists at the system level to create a common reference for tradeoff decisions.
The point where one function's output becomes another's input is where misalignment most often crystallizes into failure. No one owns the handoff. The gap between the parts belongs to no one.
Cross-functional meetings exist. Alignment sessions are held. But the meetings don't produce decisions, and real decisions happen outside the formal coordination structure. The appearance of alignment coexists with its structural absence.
These patterns are cumulative. An organization with all four active is not paying four separate taxes. It is paying a compound tax: each pattern makes the others more expensive, because coordination gaps concentrate at the same structural weak points.
The Structural Correction
The standard response to horizontal misalignment is to add coordination: more meetings, more alignment sessions, more stakeholder management. This treats the symptom. Alignment theater produces more coordination activity without producing the structural conditions that make coordination productive. The meetings multiply. The misalignment persists.
The structural correction requires designing the conditions for horizontal alignment rather than scheduling around their absence.
The horizontal structure needs its own goals: outcomes that cannot be owned by any single function and that all contributing functions are jointly accountable for. These shared outcomes need to be named explicitly, not inferred, and they need owners with authority across the contributing functions.
Escalation paths resolve conflicts after they have surfaced. Dependency triggers are structural mechanisms that surface potential conflicts before decisions are made. When a function is about to make a decision architecturally adjacent to another function's operating conditions, the trigger creates the conversation before the impact is felt.
The gap between functions is where the alignment tax is most heavily charged. Closing it requires explicitly assigning accountability for handoff quality: not just completing the output on the sending side, but ensuring the receiving side has what it needs to use that output effectively.
What gets measured gets managed. If the only measurements in the system are functional, the system will optimize functionally. Adding shared metrics at the delivery system level, measuring outcomes that require multiple functions to produce, creates the structural incentive for horizontal coordination that individual performance metrics do not.
When horizontal misalignment produces a delivery failure, the post-mortem question should not be "which team dropped the ball?" It should be "what structural condition allowed this dependency to remain invisible until it produced harm?" The distinction shapes whether the organization learns anything durable from the failure.
The delivery leaders who are most effective in complex organizations have learned to hold both frames simultaneously: accountability for their own function's performance and accountability for the structural conditions that allow their function to contribute to collective outcomes. The second accountability is harder, less visible, and less rewarded by most organizational systems. It is also the one that determines whether the system works.
The question that matters at the end of every cross-functional delivery is not whether your team performed. It is whether your team's performance, combined with every other team's performance, produced the system-level outcome the organization needed. Local wins mean nothing if the system they belong to is producing system-wide chaos.
The PM Reality Check
Weekly strategies for the human side of delivery. Plus the free Stakeholder Field Guide on signup.