Skip to main content

Decision Debt in Middle Management: Managing the Backlog of Unresolved Choices

Distinguish deliberate deferral from uncertainty that keeps creating unplanned work.

Decision Debt in Middle Management: Managing the Backlog of Unresolved Choices

Two service teams need to exchange customer records. They agree a temporary format so the current release can proceed, while a shared data model remains under discussion. Six months later, more teams use the temporary format. A manager keeps answering questions about what it supports, which fields are authoritative, and when the wider choice will be made.

The original deferral may have been reasonable. The problem is that its conditions were not maintained as the arrangement spread. New work now depends on assumptions that were never intended to become a long-term commitment.

Decision debt is a useful description for unresolved choices that create continuing consequences. Here it is a management metaphor, rather than a standard accounting category or a claim that delay accrues a predictable rate of interest. Its value is in directing attention to what remains unsettled, what depends on it, and how the organisation will decide what to do next.

Recognise a Deferred Choice Without Treating All Uncertainty as Debt

Some decisions should wait. A team may need evidence from a pilot, a forthcoming supplier response, or a clearer understanding of demand. Committing early can create unnecessary cost or close an option before the organisation has learned enough.

A deliberate deferral has an explanation, an interim operating position, and a trigger for reconsideration. For the data model, that might mean supporting one exchange for the current release while measuring requirements from two further use cases. The temporary format has a stated boundary.

An unmanaged open issue looks different. People cannot explain what information is missing, who can settle the choice, or what event will bring it back for review. Work continues because each team needs an immediate answer, not because the organisation has agreed how to preserve options.

The distinction concerns management of the uncertainty. A decision made quickly can still create substantial future work. A postponed decision can preserve value if its conditions are understood and respected. Age alone is therefore an incomplete measure of the problem.

Identify the Commitment Already Embedded in the Interim Arrangement

The temporary data format may now appear in code, documentation, customer exports, and support procedures. Those uses are evidence of commitment, even if a meeting note still labels the format provisional. A future change needs to account for what people have built around it.

Map the affected uses before deciding that standardisation is the answer. The shared model may still be worthwhile, or the different requirements may justify separate formats with a maintained translation. Consistency should support a defined purpose rather than become an objective detached from the work.

Record who is affected and what would need to change under each option. This turns a vague overdue decision into a concrete question about interfaces, support, migration, and continuing responsibility. It may reveal that the original proposal no longer addresses the current system.

The related discussion of organisational memory explains why the initial rationale matters. Preserve what was known, what was assumed, and why the temporary choice was accepted. A later reviewer needs that context to assess the arrangement fairly.

Explain Why the Work Reaches Middle Management

A shared data decision can exceed one team’s mandate while remaining closely tied to implementation. Managers coordinating several teams may be well placed to identify the issue, assemble evidence, and propose a resolution. That does not mean they automatically hold authority over every contributing function.

In this example, one manager might own service delivery while another controls the shared platform. A data specialist may define the evidence needed to compare options. A sponsor may decide which investment takes priority. The issue can stall if everyone expects a different person to close the trade-off.

Clarify the missing decision separately from the work of tracking it. A manager can maintain the record and coordinate interim commitments while the sponsor retains the resource choice. Naming someone as the backlog owner should not silently transfer authority they do not have.

The Orange Book’s risk-management guidance connects roles, decision-making, escalation, and review. It is a UK public-sector framework. Its relevance here is the need for an operating arrangement around unresolved exposure, rather than a requirement that businesses adopt a particular decision-debt register.

Keep a Small Record That Can Support a Decision

The record should describe the choice still open, the current arrangement, its limits, affected work, and the evidence required. Add the person or forum able to decide, the next review point, and what changes if the review does not resolve the issue.

Separate facts from forecasts. The manager may know that four services use the format while only estimating the effort of changing them. Record the basis and uncertainty of that estimate. Otherwise a speculative migration cost can become the reason a decision is repeatedly postponed.

Link to relevant technical material rather than copy every discussion into the register. The purpose is to make the state of the choice understandable. A long archive that nobody can use will not provide a reliable review route.

Avoid adding every minor uncertainty. Focus on choices that materially constrain another team, create recurring effort, or require authority that is not currently available. The register should expose a manageable set of decisions, rather than become another complete inventory of project work.

Write the open choice as a question someone can answer. A heading such as shared data model may conceal several decisions: which team defines the record, whether existing users must migrate, and who funds the transition. A single broad item can remain open because its participants are trying to settle different questions.

Separate those choices where useful, while preserving their dependencies. The sponsor might assign ownership now, fund a short investigation, and postpone the migration decision until the evidence is available. That creates progress without pretending the whole issue is resolved. It also gives the interim owner a defined contribution, rather than an unlimited obligation to make every unanswered question disappear.

Prioritise by Consequence and Opportunity to Learn

An old item may have little current effect. A new one may be about to influence several releases. Consider the work already dependent on the choice, the rate at which commitments are growing, and the practical consequences of continuing under the interim arrangement.

Also consider what a decision would require. A small clarification of ownership might remove recurring effort quickly. A broader architectural choice may need a bounded investigation. The right next step can be evidence gathering rather than immediate final selection.

Group connected issues carefully. Resolving the authoritative source of a record may inform several interface decisions. Other choices can proceed independently. Identifying those relationships helps avoid waiting for a complete programme of standardisation before making any useful progress.

Use the review to decide which work can expand meanwhile. The manager might authorise continued use within the existing boundary but require a further assessment before another service adopts the format. That preserves an explicit choice about growing dependence instead of allowing the provisional arrangement to spread unnoticed.

Resolve, Retire, or Renew the Deferral Explicitly

A review can produce several legitimate outcomes. The organisation may select a shared model, retain separate arrangements, stop the proposed integration, or defer again while obtaining specific evidence. The outcome should explain the current commitment and who will carry it out.

If the decision requires migration, allocate capacity and identify how the transition will be accepted. A recorded preference for a new model is not the same as a funded plan to change existing services. Keep the work and its dependencies visible until the agreed operating state is reached.

If deferral continues, update the reason, boundary, review trigger, and responsible roles. Reusing the old date while changing nothing else gives little confidence that the issue will return under better conditions. State what the organisation expects to know or be able to decide at the next review.

The article on decision rights provides the foundation for this step. A record becomes useful when it reaches people who can make or obtain the necessary commitment, with evidence suited to that choice.

Prevent Closure on Paper From Hiding Continuing Dependence

Check what teams believe after a decision is recorded. They may still be using an old instruction or waiting for a resource commitment. An issue should not disappear from view simply because a meeting selected an option.

Distinguish the closed choice from implementation that remains open. The manager can stop repeatedly debating the preferred approach while continuing to track migration and exceptions through ordinary delivery work. That separation reduces confusion without pretending that all consequences end at authorisation.

Revisit the pattern when similar items keep appearing. The cause may be an unclear mandate, missing specialist capacity, or plans that routinely start before a shared choice is ready. Improving that condition may be more valuable than repeatedly clearing an expanding list.

Decision debt becomes useful language when it helps the organisation distinguish intentional uncertainty from neglected commitments. The practical work is to maintain the interim arrangement, keep its consequences visible, and make the next choice at a time and level where it can meaningfully guide delivery.