What Is Your Organization Still Doing Because Nobody Has Questioned It?

A recurring process can outlive the conditions that originally justified it. The organization keeps producing the report, obtaining the approval, or reconciling the same information because the work is familiar and its history is difficult to reconstruct. Meanwhile, employees are asked to find capacity for new priorities without a corresponding discussion about what can stop.

I would make that discussion part of leadership's operating responsibility. The question is not whether familiar work is automatically wasteful. It is whether someone can explain the purpose the work serves now, the consequence of removing it, and the evidence that a different approach would still meet the business need.

Ask what the process supports today

Choose one recurring task and ask its owner to identify the decision, service, obligation, or control it supports. Name the current user of its output. Ask that user how the output changes what they do. A process may have several beneficiaries, so the review should look beyond the person who produces the report.

If the answer is unclear, treat that as a reason to investigate rather than immediate permission to stop. The task may support an infrequent but important decision, a contractual commitment, or a dependency that is not visible to the initiating team. Leadership needs enough context to distinguish an obsolete practice from a control whose value becomes apparent only when something goes wrong.

Understand the history without becoming trapped by it

A process may have been introduced after a genuine failure. An additional approval could have prevented an unauthorized commitment. A reconciliation could have exposed inconsistent records. The fact that the original problem is no longer common may mean the control works; it does not establish that the control is unnecessary.

Ask whether the underlying conditions changed. Has a system been replaced? Have decision rights moved? Does another control now address the same risk? Is the organization collecting information twice for different reasons? These questions create a basis for redesign. They avoid treating the age of a process as proof that it should be retained or removed.

Cybersecurity provides a useful example. An approval or review may have been introduced to address a specific risk, but changes in systems, responsibilities, or technical controls can alter how that risk should be managed. Leadership should periodically confirm that the control still serves its intended purpose. That review may support retaining it, redesigning it, or replacing it with an alternative that provides equivalent or stronger protection. The decision must be supported by evidence, not simply by a desire to reduce administrative work.

Identify who would notice if it stopped

Use a hypothetical weekly report as a practical test. Before discontinuing it, identify the people who receive it, the decisions they use it for, and any downstream process that depends on its timing or contents. Ask about exceptional cases as well as routine use. A low readership count alone would be weak evidence if one recipient uses the report for a consequential monthly decision.

The review may reveal that the report should be produced less often, delivered only when a condition changes, or replaced with access to an authoritative record. It may also confirm that the existing report is appropriate. A credible improvement process must allow both conclusions. Otherwise, the exercise becomes a search for cuts rather than a review of business purpose.

Separate the obligation from the mechanism

Where a legal, regulatory, contractual, or policy obligation may apply, have the accountable specialist establish what is required before changing the process. Do not assume that a burdensome implementation is mandated in every detail. Equally, do not assume that a simpler-looking alternative satisfies the underlying requirement.

Document which part of the work must continue and which part is an internal design choice. This article offers no determination about any particular legal obligation. The executive responsibility is to ensure that qualified owners make that determination and that a proposed replacement can be evaluated against the purpose the existing process serves.

Test a bounded change

Select a change with consequences the business can understand and manage. Agree on its scope, the period of observation, the people affected, and the conditions that require stopping or restoring the earlier arrangement. Keep a usable record of what changed so that an unexpected result can be investigated.

For AI systems specifically, NIST's AI RMF includes ongoing review and safe decommissioning as governance outcomes [N1]. Applying a review discipline to other recurring business processes is an analogy and a recommendation here. It is not evidence that NIST endorses removing a particular report, approval, or control. The people accountable for the actual business consequence must judge the proposal.

Examine what happens after work is removed

The apparent reduction in effort is only part of the result. Check whether another team had to reconstruct the missing information, whether decisions became harder, or whether customers experienced a delay. A task can disappear from one department's workload while becoming an unplanned obligation somewhere else.

Also examine whether the released capacity served the intended priority. If the improvement was meant to make room for customer follow-up, look for that outcome. Do not automatically translate reduced effort into a financial saving. The evidence may support a simpler process or better service before it supports a cash claim, and those distinctions should remain clear in the review.

Give processes an accountable future

For work retained after the review, record its purpose, owner, and next review point. That small amount of context can save the next team from repeating the same historical investigation. Where the process changes, communicate the new expectation and retire the superseded instructions so employees are not left choosing between conflicting versions.

Leadership creates room for new priorities partly by examining the work it continues to require. I would start with one recurring task that lacks a clear current explanation, involve the people who depend on it, and test a defensible alternative. The organization should be able to explain why the work remains, not merely that it has always been done.

Sources and References

[N1] NIST AI Risk Management Framework 1.0, Core https://airc.nist.gov/airmf-resources/airmf/5-sec-core/

2023 framework; accessed November 12, 2026. Scope: GOVERN 2.1 clear responsibilities; GOVERN 1.5 periodic review; GOVERN 1.7 safe decommissioning. Voluntary AI-specific guidance. Broader business applications in these drafts are author recommendations, not NIST requirements.

David Harris

David Harris is CEO of HAWK Network Defense, where he focuses on cybersecurity leadership, enterprise risk reduction, operational resilience, and measurable business outcomes. Through The CEO View, he examines the decisions, governance practices, and security investments that help organizations strengthen resilience and reduce business exposure.

https://www.hawk.io/about
Next
Next

The Question After Automation Isn't “How Much Did We Automate?”