Fast-changing business conditions can expose weaknesses that remain invisible during ordinary operations. Andrew Ticknor offers a relevant lens for examining decision latency, the often-overlooked time between recognizing a problem and having the authority, information, and processes needed to act.
A delayed decision is not always a bad decision. Some choices deserve careful consideration. The problem begins when unnecessary delays prevent an organization from responding to problems, serving customers, or taking advantage of important opportunities.
What Is Decision Latency?
Decision latency is the time between recognizing that a decision is needed and taking meaningful action.
It can occur at several stages.
A problem might be identified quickly, but the information needed to evaluate it may take too long to reach the right person. Alternatively, the information may be available, but several approval layers can prevent action.
The result can look like:
Problem identified → information gathered → approval requested → approval delayed → action taken
Every additional step can add time.
In stable environments, that delay may have little consequence. In rapidly changing situations, it can become an operational risk.
Why Slow Decisions Can Become Expensive
The cost of delayed decision-making is not always visible.
A delayed response might result in:
- A customer waiting longer for resolution
- A small operational issue becoming larger
- An opportunity being lost
- Employees spending time waiting for approval
- A competitor moving first
- Resources being committed to an outdated plan
The impact depends on the decision and the environment.
A company operating in a predictable market may tolerate longer approval processes. A business facing rapidly changing customer demand may need much faster responses.
This means there is no universally correct decision speed.
The appropriate speed depends on the consequences of delay.
Not Every Decision Should Be Fast
Speed is often treated as an unquestionable business advantage.
That can create problems of its own.
Some decisions involve substantial financial, legal, operational, or reputational consequences. Making those decisions quickly without sufficient analysis can create larger problems than the original delay.
A better objective is appropriate decision speed. Routine and reversible decisions can often be made quickly. High-impact or difficult-to-reverse decisions may require more analysis.
This distinction allows organizations to move quickly where speed creates value without sacrificing judgment where caution matters.
Approval Bottlenecks
One common source of decision latency is excessive dependence on a small number of decision-makers.
If every important issue requires approval from one executive, that person can become a bottleneck.
As an organization grows, the problem can become more pronounced.
Employees may have the information necessary to make a decision but lack the authority to act on it.
This creates a mismatch:
- Information exists at one level of the organization.
- Decision authority exists at another.
The greater the distance between those two points, the greater the potential for delay.
Put Decisions Closer to the Information
Organizations can sometimes reduce decision latency by giving appropriate authority to the people closest to the relevant information.
A customer-service employee may be better positioned to resolve a routine customer issue than an executive several management layers away.
A technical employee may be able to identify an operational problem before senior management becomes aware of it.
Delegation does not mean removing oversight.
It means establishing clear boundaries around which decisions can be made independently and which require escalation.
Effective delegation can improve both speed and accountability.
Decision Rights Need to Be Clear
Delegation becomes difficult when employees do not understand the limits of their authority.
Unclear decision rights can produce two opposite behaviors.
Some employees may escalate almost everything because they fear making an unauthorized decision.
Others may make decisions that exceed their responsibilities because they misunderstand what they are permitted to do.
Organizations can reduce this ambiguity by defining:
- Which decisions can be made independently
- Which decisions require consultation
- Which decisions require formal approval
- Which situations must be escalated immediately
Clarity creates confidence.
Information Overload Can Also Slow Decisions
More information does not automatically produce better decisions.
Decision-makers can become overwhelmed when they receive excessive reports, metrics, notifications, and competing recommendations.
The challenge is distinguishing information that changes the decision from information that merely adds volume.
Useful decision systems emphasize:
- Relevant information
- Reliable data
- Clear priorities
- Defined decision criteria
- Appropriate timeframes
This does not mean ignoring detail. It means organizing information so that important signals are easier to recognize.
The Difference Between Information and Insight
A business may possess extensive data while still struggling to make timely decisions.
Data describes what is happening.
Insight helps explain what matters and what should happen next.
For example, a company might know that customer complaints increased by 15%. That information becomes more useful when the organization can determine why complaints increased, whether the change is temporary, and what action could address the underlying problem.
Decision-making improves when information is connected to context.
Build Decision Rules for Recurring Situations
Not every decision needs to be reconsidered from the beginning.
Organizations can create predefined rules for recurring situations.
For example:
- When a specific threshold is reached, an escalation begins.
- When inventory falls below a defined level, a reorder is triggered.
- When a customer issue meets predetermined criteria, frontline employees can resolve it without additional approval.
- When a financial indicator crosses a specified threshold, management reviews the situation.
Decision rules can reduce unnecessary deliberation.
They also create consistency by making expectations clear before a stressful situation occurs.
Reversible Decisions Can Move Faster
One useful way to improve decision speed is to consider how difficult a decision will be to reverse.
- A small operational experiment can often be changed if it produces poor results.
- A major acquisition cannot be reversed nearly as easily.
- This suggests a practical principle:
- The more reversible the decision, the less justification there may be for excessive delay.
Businesses can sometimes use small experiments to avoid making large commitments before enough information is available.
Instead of asking whether a major change will work perfectly, they can ask whether a smaller test can provide useful evidence.
Decision Latency and Customer Experience
Internal decision-making eventually affects external stakeholders.
Customers do not see organizational charts or approval workflows. They experience the results.
A customer may experience decision latency as:
- A delayed response
- An unresolved problem
- Repeated requests for information
- Conflicting answers
- An unnecessarily complicated process
Improving internal decision architecture can therefore have a direct effect on customer experience.
Faster decisions are not always better customer service, but unnecessary delays rarely improve it.
Decision Latency During Disruption
The consequences of slow decisions become more significant during disruptions.
When conditions are changing rapidly, information can become outdated quickly.
A decision based on yesterday’s conditions may no longer be appropriate today.
Organizations facing disruption may therefore benefit from:
- Shorter communication paths
- Clearly assigned decision-makers
- Predefined escalation procedures
- Frequent situation reviews
- Temporary delegation of authority
- Rapid feedback mechanisms
The objective is not to eliminate careful analysis.
It is to ensure that analysis does not prevent necessary action.
Avoiding the Opposite Problem
Reducing decision latency should not create reckless decision-making.
Organizations can become so focused on speed that employees feel pressured to make decisions without adequate evidence.
That creates a different risk.
A useful decision system therefore balances:
- Speed
- with
- Quality
- and
- Accountability
The right balance depends on the decision.
Routine, low-risk decisions may prioritize speed. High-impact decisions may prioritize analysis and oversight.
The important thing is to make that distinction deliberately.
Measure Where Decisions Get Stuck
Organizations cannot improve decision latency if they do not know where delays occur.
A simple process review can identify bottlenecks.
Teams can examine:
- How is the need for a decision identified?
- Who receives the relevant information?
- Who has authority to decide?
- How many approvals are required?
- What happens when the responsible person is unavailable?
- How long does each stage typically take?
- Which delays actually add value?
This analysis can reveal whether the problem lies in information flow, authority, process design, or organizational structure.
Resilience Requires Timely Action
Operational resilience is not only about having backup systems and contingency plans.
It also depends on the organization’s ability to recognize changing conditions and respond appropriately.
A company can possess excellent resources and still struggle if decisions consistently become trapped in unnecessary approval processes.
Conversely, an organization with clear decision rights and efficient information flows may be able to respond to challenges before they become major disruptions.
Decision architecture is therefore part of operational resilience.
Designing an Organization That Can Move
Every organization needs controls. Every organization also needs movement.
Too little control can produce inconsistency and unnecessary risk. Too much control can create bottlenecks that prevent capable people from responding to changing conditions.
The goal is not to remove decision-making structure.
It is to design that structure intentionally.
Organizations can start by identifying which decisions are routinely delayed, determining why the delays occur, and evaluating whether the existing approval process is proportionate to the risk.
Some decisions may need more oversight. Others may simply need clearer authority. The distinction can make a significant difference.
Turning Decision Speed Into a Strategic Capability
Decision-making is often treated as a leadership issue, but it is also an operational system.
Information must reach the right people. Authority must exist where decisions are made. Processes must distinguish routine choices from high-impact commitments. Employees need clear boundaries. Leaders need enough visibility to intervene when necessary.
When these elements work together, organizations can respond without sacrificing judgment.
The objective is not to make every decision faster.
It is to make the right decisions at the right speed.
In uncertain operating environments, that capability can become an important source of resilience. Organizations that understand where decisions slow down, why they slow down, and which delays actually add value are better positioned to respond when circumstances change.
Operational strength is not simply about having the right resources. It is also about being able to turn information into action before an opportunity disappears or a manageable problem becomes a serious one.