Operational Learning: Reopen Triggers

Third-quarter ops review. The SVP scans the agenda and stops on item four. Capacity allocation.

Again.

Not flagged as urgent. Not escalated through the organizational's proper governance. It's just there. Third month in a row, same line item, same slide.

The room settles. Demand planning opens with it: "I want to revisit the line allocation split. The mix has shifted since we set it." The SVP watches the room.

Nobody asks how much the mix shifted. Nobody asks whether the shift crossed a threshold that would warrant revisiting. They just open the conversation.

Finance makes the flexibility argument. Operations makes the commitment argument. Supply chain asks, again, for a decision that holds long enough to plan against. Same positions. Slightly repackaged data. Thirty-five minutes pass.

The outcome: "Let's take another look and bring updated scenarios next month."

The SVP writes one word in the margin of the agenda. Third. 

Not angry. Just tired of recognizing a pattern nobody else in the room has named yet.

This isn't a crisis. Nobody leaves that meeting frustrated. Nobody calls it a failure. And that's the problem. The most expensive pattern in operational leadership doesn't look like dysfunction. It looks like diligence.

And it persists because most organizations have never named the difference between two things that look the same.

There's a difference between revising a decision and re-running one.

Revision happens when conditions change. New data crops up. A market input moves past an aligned boundary that matters. The original assumptions no longer hold, and a structured review produces a different, better answer.

That's healthy. That's the system working.

Re-running is something else. It's the same conversation returning because the decision never came with terms for when it could be reopened. No trigger. No threshold. No defined condition. So the default trigger becomes someone raising their hand. Not because conditions changed. Because the calendar rolled over and the agenda had space.

The reopening isn't driven by signal. It's driven by absence of the signal. The absence of a clear, pre-committed reason to leave the decision alone.

And that means every decision sits in a kind of permanent draft state, available to anyone with enough authority or persistence to bring it back.

The visible cost of re-decision is easy to spot. Meeting hours. Leadership attention. Analytical rework. Somewhere in the building, a planning team rebuilt a capacity scenario deck for the third time this quarter. That time is real. But it's not the expensive part.

The expensive part is downstream. And it compounds in ways that rarely show up on any dashboard.

The SVP starts noticing it the way you notice a slow leak. Not all at once. In pieces.

The vendor shortlist for a new packaging line has been "almost finalized" for two months. Not formally paused. Nobody issued a stop-work. It just can't close. Because the vendor decision depends on the capacity allocation. And the capacity allocation keeps reopening. So the vendor evaluation drifts. The procurement team runs another round of reference checks to stay busy while they wait for an answer that keeps moving.

Headcount requests for Q1 are sitting with HR. The plant manager submitted a shift restructure proposal that depends on the capacity plan. Can't staff what isn't settled. The recruiting timeline compresses every week the decision stays open. When it finally holds, they'll hire in a rush. Rushed hiring means settling. And the cost of settling is steep. SHRM estimates it can run two to three times the role's annual salary once you fold in onboarding, lost productivity, and replacement. None of that gets attributed to the capacity decision that wouldn't stay decided.

Supply chain has learned to hedge. They're ordering materials on a rolling 30-day window instead of the 90-day commitment that would get them better pricing. It's a rational choice. The last two times they committed long, the capacity decision shifted and they ate the overage. So now they pay a meaningful premium on material spend, every month, because they've stopped trusting the plan. That premium isn't tracked as a re-decision cost. It lives in procurement variance and nobody connects the dots.

This is the re-decision tax. It's not paid in the room where the conversation happens. It's paid across every function that stopped trusting the decision would hold. And it shows up as hedges. Buffers. Timelines that stretch without a clear reason.

Commitments that soften because people have learned that "decided" doesn't mean "settled."

Over time, the tax isn't just financial. It's relational. Functions that have been burned by shifting decisions stop extending trust across the planning boundary. Supply chain stops trusting demand planning's numbers. HR stops trusting operations' timelines. The re-decision doesn't just slow the organization. It fragments the partnerships that make it run.

And it becomes a consistent pattern. When decisions reopen without clear cause, the organization doesn't just lose the time spent re-debating. It loses the willingness of downstream teams to commit. And commitment, once lost, doesn't come back the moment a decision finally sticks. It comes back slowly, after the decision has proven it can survive a full cycle without being reopened.

The SVP pulls a thread. Traces the vendor delay to the capacity decision. Traces the hedged procurement to the same source. Traces the headcount limbo to the same root. Three functions. Three different symptoms. One cause: a decision that keeps opening because nobody defined the conditions under which it should.

Here's what makes this structural, not behavioral.

Most organizations have invested heavily in how decisions get made. Approval workflows. RACI charts. Escalation paths. Governance bodies with charters and cadences. Even in organizations where that infrastructure is imperfect, it exists. The front half of the decision lifecycle gets real investment.

Almost none have invested in the back half.

The part that governs when a closed decision earns the right to reopen.

That's the gap. Not culture, but design. In the absence of reopen criteria, the default mechanism is seniority, volume, or persistence. Whoever has the most authority, the most frustration, or the most stamina to raise the issue again gets the floor. That's not governance. That's attrition dressed as process.

A reopen trigger is a pre-committed condition, agreed at the time of the original decision, that defines what would earn the right to revisit. Not "if things change." Specifically: what change, measured how, crossing what threshold, reviewed by whom. It turns "we should revisit" from an unfalsifiable opinion into a testable statement.

Did the trigger fire, or didn't it?

Without a reopen trigger, a closed decision isn't locked. It's unprotected. And an unprotected decision will eventually be reopened by whoever has the most energy to reopen it, regardless of whether conditions have actually changed.

The distinction matters because it shifts the conversation. Instead of debating whether to revisit, you check whether the conditions for revisiting have been met. The burden of proof changes. The emotional temperature drops. And the downstream teams that depend on the decision can plan against it with a level of confidence they don't have today. That confidence is what turns governance from overhead into velocity. Decisions that stay decided let the organization move faster, not because people are rushing, but because they're not waiting to see if the ground shifts again.

This pairs with signal discipline. Signals tell you what to act on going forward. Reopen triggers tell you when a past action deserves fresh scrutiny. One faces forward. The other faces backward. Without both, you're either ignoring legitimate change or chasing noise that feels urgent because someone made it loud.

The SVP decides to run an experiment with the next ops review. Before closing the capacity decision this time, the room will define the conditions under which it can be reopened.

This is where the discipline gets specific.

Every significant decision should leave the room with at least one explicit reopen condition. If there's genuinely no condition under which you'd revisit, say so. Name that explicitly.

It forces the room to confront whether the decision is actually settled or just tabled. If there is a condition, define it: what metric, what threshold, what timeframe. The act of designing the trigger forces clarity about what the decision actually depends on. Most teams discover that they don't fully agree on the assumptions until they try to define what would invalidate them.

The threshold matters more than the metric. This is where most organizations get it wrong when they try. Everyone can agree on "if demand drops significantly, we revisit." Nobody agrees on what "significantly" means at 2am when a call needs to be made. Quantify the boundary at decision time, when thinking is calm and consensus is available. "Forecast demand below 12,000 units for two consecutive months" is a trigger. "If things change materially" is a wish.

Wishes don't protect decisions.

Reopen triggers belong to roles, not names. When the trigger owner is a specific person and that person gets promoted, moves laterally, or leaves, the trigger dies without anyone noticing. Nobody inherits it because nobody knew it was theirs to inherit. Assign ownership to a role with a clear backup. The trigger survives the org chart.

The SVP proposes three reopen conditions for the capacity decision. Forecast demand drops below a defined unit threshold for two consecutive months. Raw material lead times exceed a specific number of weeks. Customer mix shifts more than a defined percentage from the plan that informed the original allocation. Three conditions. Measurable. Each owned by a role, not a name. Reviewable at the monthly ops review that already exists.

A reopened decision without a fired trigger needs a higher bar, not a lower one. This is the principle that protects the system without making it rigid. Reopen triggers don't mean a decision can never be revisited outside the pre-committed criteria. They mean the burden shifts. If someone wants to reopen and the trigger hasn't fired, that's a different conversation. They're making the case for why conditions warrant revisiting despite the criteria not being met. That conversation is valuable. It's also materially harder than "I just think we should look at it again." The higher bar is the point. It filters out convenience and lets genuine urgency through.

Triggers also need a review cadence, not just a threshold. A trigger that nobody checks is a trigger that doesn't exist. Build the review into an operating rhythm you already run. Monthly ops review. Quarterly business review. Not a new meeting. A line item in an existing one. The cadence ensures that triggers get checked, thresholds get validated against current conditions, and ownership stays active. Without it, the register becomes a document that was useful the week it was created and invisible the week after.

The next time someone in the SVP's ops review says "I want to revisit the line allocation," there's a question to ask first.

Did the trigger fire?

If yes, the decision reopens with structure and purpose. New data, clear criteria, defined scope.

If no, the conversation changes. Not "we can't talk about it." Instead: "What are you seeing that the triggers aren't capturing?" That question is useful too. It either surfaces a gap in the trigger design or reveals an opinion that doesn't have data behind it yet. Both are worth knowing. Neither requires a 35-minute re-run of last month's debate.

It's not bureaucracy. It's actually the opposite.

It keeps governance lean by giving the organization a faster, cleaner way to answer the question that currently consumes 35 minutes of every ops review: should we reopen this?

Something I urge you to think about this week...

What decision are you re-running, and what measurable trigger would earn the right to reopen it?

If the answer comes quickly, you already know where the re-decision tax is highest. Start there. Define the triggers. Assign them to roles. Review them at a cadence that matches the risk.

If the answer doesn't come quickly, that's worth sitting with too. It might mean your decisions are holding well. Or it might mean the re-runs have become so normal that nobody registers them as waste anymore.

Sources

Kahneman, D., Sibony, O., & Sunstein, C. R. (2021). Noise: A flaw in human judgment. Little, Brown Spark.

Society for Human Resource Management. (2022). The real costs of recruitment. SHRM.

Weill, P., & Ross, J. W. (2004). IT governance: How top performers manage IT decision rights for superior results. Harvard Business School Press.