A Faster Company Isn't One Where Everyone Works Faster

When an organization wants to move faster, it is tempting to begin with individual productivity. Reduce meeting time. Answer messages sooner. Automate another task. Those changes can be useful, but they may leave the business result untouched if the work still waits for a decision that nobody is clearly authorized to make.

I would examine decision flow before setting another speed target. The useful question is what happens between a request becoming ready for a decision and the organization accepting the result. That interval can contain necessary scrutiny, avoidable ambiguity, or both. Leadership needs to tell the difference before asking people to accelerate.

Define the decision being measured

Choose a recurring decision with a recognizable outcome, such as approving a standard customer exception or deciding whether an operational change can proceed. Define when the request is usable, which information belongs with it, and what constitutes an accepted decision. Otherwise, different teams may measure different portions of the same process.

Track the return path as well. A fast approval that is repeatedly reopened may create more work and uncertainty than a careful decision made once. I would review elapsed time alongside corrections, exceptions, and the consequences of mistakes. The aim is a decision path the organization can rely on, rather than a better-looking timestamp.

Locate the waiting before redesigning the work

In a hypothetical customer exception, a sales manager may collect the information quickly and then wait for three separate reviews. One checks a commercial limit, another checks capacity, and a third decides whether the request is unusual enough to require an executive. Those reviews may protect different interests. Their existence alone does not establish inefficiency.

Map what each review contributes. Does it add information, exercise a distinct authority, or repeat an earlier check? Could some reviews happen in parallel? Does the final reviewer receive the reasoning behind earlier decisions? This examination gives leadership a specific problem to solve. It avoids assuming that every delay is waste or that every control should disappear.

Put authority where the decision recurs

A recurring decision needs an accountable owner, an understandable boundary, and a route for cases outside that boundary. Delegating a task without delegating an appropriate decision right can leave the employee responsible for progress while still dependent on an informal executive answer.

Security decisions illustrate why those boundaries matter. A team may identify a condition requiring action but still need authorization before changing a production system or interrupting a business service. The answer is not to eliminate approval indiscriminately. Leadership needs to establish which decisions can be made within predefined authority, which require escalation, and how the organization verifies that the resulting action was appropriate.

I would define what the owner may decide, what they must document, and which conditions require escalation. Include coverage for absence and a way to challenge or reverse an incorrect decision. For AI-related risk, clear responsibilities and communication are also explicit outcomes in NIST's AI RMF [N1]. Applying that principle to the wider operating model is a leadership recommendation here, not a claim that the framework mandates this particular design.

Preserve time for consequential judgment

Some choices should take longer. A decision that changes a major customer commitment, interrupts a critical service, or exposes the business to material uncertainty deserves examination suited to its consequences. A uniform target can make that judgment harder by treating all elapsed time as failure.

Separate routine cases from consequential exceptions. Identify which facts could change the decision and who can obtain them. If waiting will not improve the evidence, decide whether the business should act within a bounded scope, escalate, or stop. This is a decision about risk and responsibility. It should not be left to whoever is willing to keep chasing an answer.

Review the whole business result

A department can improve its completion rate while moving unresolved work downstream. The receiving team may need to interpret the answer, repair an omission, or seek a second approval before anything changes for the customer. That is why I would measure the accepted outcome as well as local task completion.

For the pilot, review the number of handoffs, reasons for rejection, reopened decisions, and the period spent waiting for authority. Keep context with the figures. A more complex case mix or a legitimate change in control requirements can affect the results. Do not credit a revised workflow with every improvement or blame it for every delay without examining the surrounding conditions.

Give the design an owner and a review date

Improving one decision path is more manageable than announcing that the entire company must become faster. Give an executive sponsor responsibility for resolving disagreements between functions. Let the operational owner run a limited test and return with examples of cases that moved appropriately and cases that still stalled.

The review should ask whether the delegated boundary was usable, whether escalation reached someone able to act, and whether the business accepted the outcomes. Preserve a record of exceptions. An exception that appears repeatedly may reveal that the standard path needs revision, while an unusual event may justify keeping a specialist review. Frequency alone does not decide the issue; consequence matters too.

Do not turn the measure into another burden

Use information the process can produce with a reasonable effort. If the pilot requires employees to reconstruct every minute in a separate reporting system, the measurement arrangement may obscure the improvement it was meant to support. Start with a small set of meaningful events and examine a representative sample in detail.

A faster company needs reliable authority and a decision path that matches the work. Individual effort remains important, but leadership owns the design that allows that effort to produce an accepted result. I would ask where the next recurring decision waits, why it waits, and what the organization can change without weakening the judgment the decision requires.

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
Previous
Previous

Top 10 Active Vulnerability Developments IN THE WILD | November 8–14, 2026

Next
Next

HAWK AI Threat Brief | Top 10 AI Developments Security Teams Should Be Watching