Most governance breakdowns do not announce themselves as failures. They emerge quietly through a series of reasonable, well-intended decisions that only reveal their cost when delivery stalls, trust erodes, and remediation becomes unavoidable. Governance initiatives rarely fail because of lack of rigor or bad design. They fail at the point of execution, where frameworks encounter real delivery timelines, real handoffs, and real human decision making. Tredence operates precisely at this last mile, where strategy becomes operational reality and design assumptions are tested by lived experience.
This paper examines a recurring pattern observed in large-scale data programs. It explains why these issues require far more time and trust to repair than it would have taken to design a framework that is responsive to delivery realities from the start. The following sections describe this pattern, which will later be illustrated through a single, extended scenario to show how these dynamics compound in practice.
This paper does not propose a new governance framework or operating model. Instead, it surfaces a recurring pattern that must be addressed for any solution to succeed.
The Friction Contract
In large-scale delivery environments, teams routinely absorb additional rules, process, and coordination in order to move work forward. Over time, this creates the Friction Contract: an implicit agreement where teams accept added constraints and effort today in exchange for the expectation of safer, clearer, or faster delivery later.
This implicit agreement quietly shapes how governance is experienced in practice, long before any issues surface. Governance asks teams to absorb additional rules, review cycles, coordination, and rework in their day-to-day execution. These demands are intentional and expected. They are a normal part of operating in complex, regulated, and highly interdependent environments. Even when governance is functioning as designed, it introduces additional effort into the system, and that effort is absorbed by the people accountable for outcomes.
The friction contract holds as long as people believe the effort is worth it.
Teams accept this added effort because they expect tangible benefits in return. The constraints are understood to be an investment that reduces risk, clarifies meaning, and makes work easier. When governance aligns with how work is actually done, it creates shared understanding, predictable guardrails, and confidence that decisions made today will hold over time. The payoff is not perfection, but momentum: fewer reversals, fewer surprises, and a greater ability to scale work without renegotiating fundamentals.
When the Friction Contract Breaks
Teams adapt to regain momentum
A broken friction contract is a Breach. Not of policy or compliance, but a breach of the implicit agreement that effort will be met with meaningful return. When it occurs, teams do not respond with resistance or disengagement. They adapt. They seek ownership and clearer decision paths to regain momentum. Governance teams respond by reinforcing consistency and control to manage risk. Analytics teams translate and reshape data to preserve usability. Engineering teams optimize for coherence and internal logic to restore stability. Each response is locally rational and grounded in professional responsibility, even as these well-intended adaptations begin to pull the system in different directions.
These adaptations are rarely coordinated. Each team is responding to the same pressure in different ways, optimizing for the outcomes they are accountable for. The result? Shared understanding erodes and previously aligned decisions diverge. Translation work increases and confidence in upstream choices weakens. Progress in one area can create friction elsewhere. Not because the actions are wrong, but because teams no longer share a common frame of reference. Taken together, these responses are not signs of dysfunction, but of a system operating without a shared mechanism to reconcile competing, well-intended priorities.
As these adaptations take hold, coordination, alignment, and decision-making become harder rather than easier. Local decisions relieve immediate pressure, but the framework for reconciling those decisions across teams is insufficient or absent. Without shared authority, shared language, or a common forum for resolution, misalignment persists even after recognition. The work continues, but with increasing friction, as the framework no longer supports alignment and effort shifts from enabling delivery to introducing workarounds that compensate for divergence.
Executives adapt to regain certainty
Executives experience a broken friction contract differently, but no less acutely. For them, it represents a breach of the implicit agreement that if we accept this friction now, we will gain confidence later, and that the data will hold up when decisions matter. Governance costs are immediate, visible, and cumulative. The benefits are expected to emerge later, as increased trust in data, clearer decision confidence, and sustained delivery momentum. When those benefits do not materialize within the timeframe executives are accountable for, their confidence in the framework begins to erode, even as effort remains high and delivery continues.
The organization continues to pay the price of added coordination, rework, and delay, while the promised payoff remains uncertain or deferred. The question executives begin to ask is not whether governance is well-intentioned or theoretically sound, but whether the organization can continue absorbing near-term cost without corresponding near-term signal. What initially felt like prudent investment starts to feel like open-ended carrying cost.
When this shift occurs, executives do not respond by abandoning governance or rejecting its goals. They adapt. They seek greater certainty, clearer accountability, and stronger signals that decisions made today will hold. Leaders compress timelines to protect delivery commitments. They introduce escalations to regain visibility, tighten controls, and centralize decision authority to prevent further divergence. Each of these responses is locally rational and grounded in executive accountability for budget, credibility, and delivery, even as these adaptations further amplify friction elsewhere in the framework.
As with team-level adaptations, these leadership responses are rarely coordinated with the adaptations happening elsewhere in the framework. Efforts to regain certainty at the top can unintentionally increase friction below, just as local optimizations at the team level can undermine executive confidence. The result is a reinforcing loop: increasing control in response to delayed payoff, and increasing workaround behavior in response to that control. The framework continues to function, but with growing strain, as effort shifts from enabling delivery to managing the consequences of increasing divergence.
Scenario: When the Friction Contract Breaks
Scenario: When the Friction Contract Breaks
When the friction contract holds, governance effort translates into shared meaning, decision confidence, and sustained momentum. Constraints feel purposeful rather than burdensome, and coordination costs decline over time rather than compounding. Governance does not disappear. It recedes into the background as trust accumulates and decisions stabilize.
What follows is how that contract begins to break.
The following scenario is not a case study of a single organization or implementation. It is a composite pattern drawn from repeated observations across large-scale data initiatives. The specific technologies, roles, and structures may vary, but the sequence of events is both common and repeatable.
This scenario is intended to make visible how the friction contract breaks in practice. It does not break through failure or resistance, but through the interaction of rational decisions made under pressure.
1. The Contract Is Accepted
An organization launches a major initiative to consolidate customer data into a unified environment. Because the data will be used for high-stakes decisions, a rigorous governance framework is put in place. Data assets must have named ownership, documented lineage, and verified quality before they are promoted into production use.
Delivery teams absorb this added structure without resistance. The additional reviews, documentation, and coordination introduce friction into day-to-day execution, but the trade-off is understood. The expectation is that once the data is governed and live, it will be trusted, stable, and require less downstream correction.
The friction contract holds. The effort feels like an investment.
2. Friction Accumulates Faster Than Payoff
As delivery moves into the later stages, execution begins to slow. Small changes require multiple handoffs. Adjustments made for performance, integration, or sequencing must wait for review cycles designed for stability rather than iteration.
Teams remain accountable for timelines and outcomes. To keep work moving, they make local adjustments: temporary structures, parallel logic, and interim processes intended to bridge gaps while formal approvals catch up. These choices are pragmatic and reversible. They are not attempts to bypass governance, but to preserve momentum.
Elsewhere, downstream teams encounter data that no longer cleanly aligns with certified definitions or expectations. To maintain usability, they introduce their own translations and checks. Each adaptation solves a local problem. Collectively, they begin to introduce divergence.
The friction contract weakens, quietly.
3. Leadership Reframes the Cost
From a leadership perspective, progress is visible but uneven. Coordination effort is increasing. Rework is becoming more common. Delivery continues, but the promised reduction in friction has not yet materialized.
What changes is not commitment to governance, but the mental framing of its cost. What initially felt like prudent investment begins to resemble ongoing carrying cost. Confidence in the framework’s ability to produce timely payoff erodes, even as effort and delivery remain high.
The question shifts from “Is this the right approach?” to “Can we continue absorbing this cost without clearer signal?”
4. Rational Adaptation Collides
Leadership responds as accountable leaders do. Decision authority is tightened. Escalations are introduced to restore visibility. Timelines are compressed to protect delivery commitments. Controls increase in an effort to reduce ambiguity and prevent further divergence.
These actions are locally rational and responsibility-driven. They are not reactions against governance, but attempts to restore certainty when the framework no longer provides it.
At the same time, delivery teams respond to increased oversight by further insulating execution from delay. Workarounds become more durable. Parallel paths harden. The adaptations on both sides begin to interact.
5. The Reinforcing Loop Takes Hold
These responses are rarely coordinated across layers. Efforts to regain certainty at the top increase friction below. Local optimizations below further undermine confidence above. Control increases in response to delayed payoff. Workarounds increase in response to control.
The framework continues to function, but with growing strain. Over time, effort shifts away from enabling delivery and toward managing the consequences of increasing divergence.
No one has acted in bad faith.
No one has ignored responsibility.
The pattern emerges anyway.
This scenario does not illustrate a failure of governance intent, rigor, or effort. It illustrates how, in the absence of a mechanism to reconcile timing, authority, and trust, well-designed frameworks can produce reinforcing friction rather than sustained momentum.
The remainder of this paper explores what is missing. Not in rules or structure, but in how governance engages with human decision-making under pressure.
The Fundamental Capability Gap
When this pattern repeats across different industries and technologies, it suggests that the breakdown is not a failure of structure, technology, or individual behavior. It is not that the rules are wrong or the teams are resistant. Instead, the scenario reveals a fundamental gap in how large-scale programs function under the weight of their own complexity.
If every participant is acting with professional responsibility and the framework still diverges, the missing element is the capability for sensemaking and reconciliation under pressure.
Current governance models are built to monitor and enforce, but they lack a mechanism to translate the reality of the last mile back into strategic intent as work unfolds. There is no shared way to make sense of why a workaround was necessary or how to reconcile that local choice with the organizational need for certainty. Without this capability to bridge intent and execution, accumulating friction is not an exception. It is the predictable outcome.
Friction is a signal that the framework can no longer align the people responsible for the work under current conditions. It indicates that the organization can no longer engineer its way out of a trust problem through additional rigor or stricter gates. The gap is not in the rules, but in the framework’s ability to engage with how decisions are actually made when delivery is at stake.
What the Gap Reveals
What this gap reveals is a need for a different kind of engagement, not more governance. One that recognizes that decisions are not made in isolation, nor executed in sequence, but negotiated continuously across roles, pressures, and constraints. When governance frameworks cannot participate in that negotiation, they default to control. When delivery teams cannot surface meaning upward, they default to insulation. When executives cannot distinguish between productive adaptation and unmanaged risk, they default to escalation. The resulting friction is not accidental. It is the natural consequence of misaligned sensemaking.
This is why additional rigor, tooling, or escalation rarely restores trust once it has eroded. These mechanisms are designed to enforce compliance, not to reconcile competing truths as work unfolds. They can measure adherence, but they cannot explain divergence. They can surface violations, but they cannot make sense of why those violations occurred. As a result, governance becomes something that happens to teams, rather than something that works with them.
The Human-Centric Pivot
This is the gap Human-Centric Data Governance is designed to address. It is not a rejection of governance, nor a call for fewer standards, but a recognition that modern frameworks lack the capability to engage with human sensemaking under pressure.
Human-Centric Data Governance begins from this recognition. It treats governance not only as a structural discipline, but as a human one, concerned with how people interpret intent, make trade-offs, and sustain trust under delivery pressure. It reframes governance not as a system of control imposed on execution, but as a discipline that must work with the realities of the last mile, where decisions are negotiated in motion and meaning must be continuously reconciled.
AUTHOR - FOLLOW
Kelle Luoma
Senior Manager, Data Engineering
