A leadership team decides to pursue larger customers while keeping delivery standardized. The next sales proposal exposes a choice the strategy did not settle: how much customization may sales promise, and who will support it? Sales, product and operations can each follow the stated priorities and still produce plans that do not fit together.
Approving this proposal may solve the immediate problem. But if the approval gives no guidance for the next customer, the same trade-off will return. The operational cost is not just another meeting. Teams may already have made customer promises, scheduled product work or reserved capacity on incompatible assumptions.
How an open choice becomes repeated work
Alignment Debt is the accumulated cost of unresolved disagreement, inconsistent interpretation and weak commitment to shared strategic choices. It is an OutcomesLab principle for examining a pattern of work, not a measured financial balance. The useful question is whether teams keep paying to interpret or reconcile a choice that should guide more than one decision.
Take the larger-customer situation as a hypothetical example. Sales offers a tailored implementation to advance a deal. Product schedules a standard release, while operations plans staffing for a fixed delivery model. An exception could be the right commercial choice. If leaders approve it without deciding when tailoring is allowed, however, sales faces the same uncertainty on the next proposal. Product and operations may have to revise plans after another promise has been made.
The burden can grow when assumptions become commitments. Changing a proposal before it reaches a customer is different from changing a signed offer, a release schedule and a capacity plan. That is why a recurring disagreement deserves attention even if each individual exception seems manageable. The claim is a practical interpretation of how work can spread; the research cited here does not establish that these costs necessarily compound or put a price on them.
Some of the waiting and rework may contribute to Execution Drag: the cumulative loss of speed and effectiveness caused by unclear ownership, overloaded processes, weak coordination and unresolved dependencies. The principles describe different parts of the problem. Alignment Debt concerns the unresolved shared choice; Execution Drag concerns the broader loss of delivery capacity that may result. Treating every delay as misalignment would miss other causes, such as an overloaded specialist team.
Peter M. Senge’s The Fifth Discipline offers another reason a strategic announcement may not settle the matter. People can use the same goal while working from different assumptions about what it requires. Discussion can bring those assumptions into view before they become plans. But shared understanding is not the whole answer. Raymond Caldwell’s critique of learning-organization accounts points to a question that dialogue can leave underexplored: who has the authority to decide when interests conflict? For leaders, the implication is to hear the different interpretations and then make the consequential boundary clear.
A study of Objectives and Key Results, or OKRs, illustrates the difficulty of translating a shared goal into team decisions. Jenna Butler, Thomas Zimmermann and Christian Bird studied goal-setting in one unnamed software organization of approximately 4,000 engineers and program managers. More than half of surveyed managers reported difficulty turning higher-level goals into actionable team goals or measures. Managers and individual contributors also reported different impressions of how frequently goals were communicated. The authors list Microsoft as their affiliation; the paper does not identify Microsoft as the organization studied. The study does not measure Alignment Debt, but it cautions against assuming that a common goal format gives teams enough guidance to act consistently.
Trace the decision beneath the symptoms
Strategic misalignment is easier to investigate through decisions than through a judgment about culture. Look at recent work for signs that the same choice remains open:
- Teams use the same priority to justify incompatible customer or resource decisions.
- A new priority is added, but the work it was meant to replace continues.
- Teams fund overlapping solutions to the same need.
- Customer promises repeatedly require exceptions to the delivery model.
- The same trade-off returns to senior leaders after earlier approvals.
- One team changes its plan after another has committed.
- Local targets reward actions that work against the shared outcome.
These are prompts for investigation, not a diagnostic score. Overlapping solutions may serve distinct needs, and escalation may be appropriate for an unusual customer request. The test is whether several incidents lead back to an unanswered question. In the hypothetical business, a leader could review a handful of large-account proposals alongside the product changes and delivery exceptions they prompted. Did each case reveal something new about customers, or did each reopen what the business is willing to tailor?
There is a strong case for leaving some decisions local. Sales needs room to respond to a customer; operations needs room to manage capacity. A rule that prescribes every response would slow work and discard relevant judgment. The distinction is between discretion within an understood boundary and repeated negotiation over the boundary itself. If every substantial proposal requires leaders to decide anew whether growth takes precedence over standardization, teams have not been given usable authority.
Set a boundary, then watch the next decisions
For the hypothetical business, leaders might authorize specified forms of tailoring within an agreed capacity limit. A request beyond that limit would go to a named decision owner before sales makes a customer commitment. Product would know what remains standard, and operations could plan for the variation the business has chosen to support. Those limits are illustrative, not a prescription: leaders would need to decide what the actual offer and capacity can sustain.
That decision also has to reach the operating plan. Authorizing tailored work while leaving staffing, product commitments and performance targets unchanged may simply move the conflict elsewhere. Record the choice, who can approve an exception, which teams must act on it and what evidence would justify a review. This is a practical decision record, not a new framework or a calculation of total loss.
Then examine the next few proposals. Can people act within their authority without reconstructing the strategy? Do product and operations understand the variation they must support? Are exceptions bringing new information, or repeating the old argument? Fewer escalations alone would be a weak test: people might have stopped raising conflicts. A better sign is that ordinary decisions fit together while genuinely unusual requests still surface.
Start with one trade-off that keeps returning through customer commitments, plans or resource decisions. Set its operating boundary with the people responsible for its consequences, and check whether the next teams can use it. The aim is not to eliminate disagreement. It is to stop making each team settle the same consequential choice for itself.