Prioritization Debt Begins When a Decision Is Delayed
Prioritization debt rarely begins with an obviously bad decision. More often, it starts with a reasonable delay. A security initiative is too expensive to approve immediately, a remediation program depends on another project, a legacy system cannot be replaced without operational disruption, or leadership wants one more assessment before committing resources. Each of these is a fair reason to pause. The trouble starts when pausing becomes the habit and the hard choice never actually gets made.
Research on decision inertia helps explain why this happens. May et al. distinguish between simple inaction and a more conflicted state in which action is recognized as necessary but remains inhibited by uncertainty, anticipated regret, fear of blame, or excessive risk aversion. They also distinguish decision inertia from decision avoidance, where the choice itself is actively deferred or ignored. In organizational settings, these two patterns can look almost identical from the outside: the same issue remains open, the same risk returns to the same meeting, and the same decision is moved forward without a clear conclusion.
More Information Becomes a Way to Wait
Decision inertia can emerge from two seemingly responsible behaviors: searching for more information when there is little left to learn, and running through possible outcomes again and again until nothing gets done. This is particularly relevant in cybersecurity, where uncertainty is normal, and additional data is almost always available.
A security team can always request another vulnerability scan, another risk estimate, another architecture review, another threat model, or another financial calculation. Sometimes that evidence changes the decision. Sometimes it simply creates the appearance that the decision is still being worked on.
Here’s a simple test. If new information could change which option you pick, it’s worth getting. If everyone already understands the trade-off, and the real problem is that every option has a cost, more data only delays the moment someone has to choose.
Prioritization debt starts to build when a team keeps gathering evidence but never agrees on how much evidence would be enough.
Complicated Problems Are Easier to Put Off
Security prioritization is rarely a comparison between two clean alternatives. A single decision may involve technical dependencies, regulatory obligations, business continuity concerns, budget constraints, engineering capacity, third-party commitments, customer impact, and competing strategic initiatives. The more interconnected the problem becomes, the more difficult it is to identify a clearly superior option.
Ohms’ 2026 workplace decision-making research provides a useful explanation for what happens under these conditions. The study examines how cognitive biases behave under organizational stressors and finds that task complexity increases cognitive load and exacerbates decision avoidance. Time pressure, meanwhile, increases reliance on faster, heuristic forms of thinking. The paper grounds this in bounded rationality: decision-makers operate with limited time, limited information, and limited cognitive processing capacity, and those constraints become increasingly important as complexity rises.
The Hardest Decisions Can Become Get Harder While They Wait
This creates a particularly difficult dynamic for cybersecurity governance because complexity is often both the reason for delay and one of its consequences.
Go back to that legacy access-control platform. It cannot be replaced because dozens of business applications depend on it. The migration is postponed because the dependency map is already complicated. During the next year, more applications are connected, more exceptions are approved, additional users depend on the platform, and more teams build processes around it. When the migration returns to the roadmap, the original problem has not simply waited twelve months. It has become larger.
The same pattern can occur with cloud architecture, data retention, third-party integrations, vulnerability remediation, privileged access, unsupported software, or accumulated policy exceptions. What appears to be postponement is often an active change in the environment around the decision.
This is why prioritization debt behaves more like debt than like an ordinary backlog. The postponed decision can become more expensive to resolve because the organization continues building around it.
More Analysis Is Not Always the Answer
When complexity increases cognitive load, the instinctive response is often to add even more analysis. Yet more analysis is not always the cure for complexity. It can sometimes increase the number of variables competing for attention.
A useful governance question is therefore not simply whether the organization has enough information, but whether the missing information is decision-relevant. If another assessment will not materially change the choice, commissioning it may only extend the period in which the organization remains undecided.
The challenge is not to eliminate uncertainty before acting. In many cybersecurity decisions, that standard is impossible. The challenge is to identify the level of uncertainty the organization is willing to tolerate and then make the trade-off visible.
Time Changes the Priority You Think You Are Postponing
A postponed item often looks static inside a roadmap. Its title remains the same, the risk description remains familiar, and the deadline simply moves from one quarter to another. That can create the illusion that the organization is preserving the same choice for later.
Martinsuo’s 2026 study of time in project portfolio management shows why that assumption is weak. Portfolio management inherently involves projects competing for shared resources, and decisions therefore include determining which projects proceed now, which are postponed, and which are terminated. The paper also emphasizes path dependency: current decisions influence the options and commitments available in future periods.
A priority delayed today may return in a very different environment. Engineering capacity may already be allocated. A regulatory deadline may be closer. The infrastructure may have changed. A new acquisition may have increased the scope. An incident may have altered risk tolerance. Another major initiative may now compete for the same budget.
The issue may have retained the same name, but it is no longer the same decision.
Every Delay Borrows From the Future
Martinsuo frames time as a scarce resource in much the same way as people and money. Projects compete for it, and overcommitment across too many simultaneous initiatives creates portfolio-level problems. Dependencies also mean that changes in one project can affect the timing of others.
For prioritization debt, this means something important: every unresolved priority becomes a potential claim on future capacity.
Even when no resources are assigned to the item today, the organization may still expect to address it eventually. That future work will need people, budget, change windows, management attention, and operational tolerance. At the same time, new priorities will continue to arrive.
Eventually, a future quarter can become overcrowded with work inherited from earlier periods, not because leadership deliberately chose that portfolio, but because previous decisions were repeatedly moved forward.
The debt becomes visible only when too many postponed obligations mature at the same time.
Decisions You Put Off Keep Eating Up Time
The cost of prioritization debt is not limited to delayed execution. Unresolved priorities also continue to demand attention.
Martinsuo’s review notes that managers have limited time and limited cognitive capacity, and that multiple projects compete for both attention and resources. It also highlights evidence that delayed and new projects can consume more meeting time than projects progressing normally, while switching between multiple simultaneous activities can create additional inefficiencies and overload.
In cybersecurity, that pattern is easy to recognize. A risk is discussed in one quarter, postponed, and then reviewed again in the next. The assessment has to be refreshed because circumstances have changed. Engineering provides a new estimate. Procurement updates pricing. The risk owner is asked whether business conditions have shifted. The same issue returns to the steering committee with slightly different numbers and essentially the same unresolved choice.
None of those activities looks especially expensive on its own.
The cumulative cost can be substantial.
Old Problems Crowd Out New Risks
Security organizations operate in an environment where new work continuously enters the system. Vulnerabilities are discovered, infrastructure changes, new regulations create obligations, third parties introduce dependencies, incidents expose weaknesses, audits identify control gaps, and business teams adopt new technology.
Martinsuo’s contextual view of time is useful here because it emphasizes that project portfolios operate within changing environments characterized by turbulence, complexity, dependencies, and evolving prioritization needs. A portfolio cannot therefore be treated as a static list that merely waits to be executed.
This is where prioritization debt begins to compound. Old unresolved decisions remain inside the portfolio while new priorities arrive around them. Leadership must now evaluate today’s risks alongside yesterday’s unfinished choices, and the decision space becomes increasingly crowded.
The organization is not simply carrying more work.
It’s carrying more decisions nobody has made.
Choosing to Wait Is Not the Same as Putting Off the Choice
There is nothing inherently wrong with deciding that a security initiative should wait. In fact, mature governance requires organizations to make exactly those choices because resources are finite and not every risk can be addressed at the same time.
The distinction is whether postponement is the result of an explicit prioritization decision or a substitute for one.
Portfolio management is an ongoing process in which projects must be evaluated across different time horizons and continuously aligned with strategic objectives. Portfolio evolution therefore requires repeated decisions about selection, timing, allocation, and termination rather than a one-time ranking exercise.
A genuine reprioritization contains a trade-off. One initiative receives resources instead of another. The consequences of the delay are understood. Someone owns the decision. There is a reason for revisiting it later.
Passive postponement looks different. The priority remains officially important, but nobody funds it. The risk remains unacceptable, but nobody accepts it. The work remains on the roadmap, but the date keeps moving.
That is how a critical initiative can remain critical for years without becoming executable.
When Escalating Turns Into Passing the Buck
May et al. identify decision deferral as one component of decision inertia and describe it as passing responsibility to others or postponing commitment. The authors acknowledge that deferral can sometimes be appropriate, particularly where escalation is genuinely required, but excessive reliance on it can weaken accountability and autonomy.
In security governance, escalation is often necessary. A CISO may not have authority to accept a business risk, terminate a major project, or allocate enterprise funding.
But escalation should move the decision toward someone who can make it.
So whenever something gets postponed, ask one simple question: what decision was actually made?
If the answer explains what received priority instead, what consequence is being accepted, who owns that trade-off, and what would trigger reconsideration, then the organization has probably reprioritized.
If the answer is simply that the issue will be reviewed again next quarter, the organization may have postponed the decision without resolving it.
Conclusion: Prioritization Debt Is the Cost of Choices You Haven’t Made
The most dangerous characteristic of prioritization debt is that its creation rarely produces an immediate failure. There is no outage when the meeting ends, no automatic penalty when the deadline moves, and no obvious financial line item labelled “cost of indecision.” Postponement can therefore feel safe.
The research behind the concept suggests otherwise.
May et al. show how decision paralysis, regret, fear of blame, excessive information seeking, and deferral can prevent action even when action is recognized as necessary. Ohms shows that increasing task complexity can intensify decision avoidance rather than automatically producing better analysis. Martinsuo shows that time, capacity, dependencies, and evolving context change the portfolio in which those decisions will eventually be made.
Together, these findings suggest that the real danger is not simply having unfinished work. Every security organization will always have unfinished work.
The warning sign is a portfolio full of priorities that remain too important to remove, too risky to accept, too expensive to fund, and too uncomfortable to decide.
Those items are not merely backlog.
They are decisions the organization has repeatedly carried forward, and every time they move into another quarter without an explicit trade-off, they bring part of the previous quarter with them.
For Further Reading
This blog post is based on insights and analysis from:
- Martinsuo, Miia. “Time in project portfolio management: Objective, subjective, and contextual.” Project Leadership and Society (2026): 100221. https://doi.org/10.1016/j.plas.2026.100221
- May, Brandon, et al. “: how ethics, decision modalities and narrative framing influence decision inertia in a 360 degree extended reality environment.” Cognition, Technology & Work 27.3 (2025): 611-633.
https://doi.org/10.1007/s10111-025-00815-8
- Ohms, Benjamin. “Methodology for investigating moderating relationships in cognitive biases within workplace decision-making.” Frontiers in Psychology 17 (2026): 1705404.