Decision Age: 5 Frictions That Undercut Risk Decisions

Decision age is the time between the first useful signal and the moment someone with authority actually changes the work. In safety, that delay matters more than how clean the chart looks, because a fresh number can still arrive after the field has already moved on.

Across 25+ years leading EHS in multinationals and more than 250 cultural transformation projects across 30+ countries, Andreza Araujo has seen the same pattern repeat. The report reaches the meeting on time, the score looks tidy, and the decision still comes after the exposure has already spread. As Andreza Araujo argues in Safety Culture: From Theory to Practice, repeated decisions reveal culture. Muito Alem do Zero warns that a flattering metric can hide the real operating picture, while A Ilusao da Conformidade shows why a clean process can still be structurally weak.

That is why decision age is not a data problem alone. It is a governance problem, a field problem, and a control problem. If the board receives the signal too late, or if the signal reaches the wrong owner first, the organization may still feel informed while it is already governing yesterday's risk.

1. Why decision age matters more than metric freshness

Metric freshness tells you whether the data is recent. Decision age tells you whether the data is still useful. Those are not the same thing, because a report can be current and still miss the moment when authority should have moved.

James Reason's work on latent failures helps here. A delay rarely starts at the top of the meeting agenda. It is usually built into the system long before the issue surfaces, which is why a green dashboard can coexist with a slow organization.

For board members, safety leaders, and EHS analysts, the question is simple: when the signal arrived, was there still time to change the work? If the answer is no, then the organization did not have a risk decision. It had a record of one.

2. Friction 1: the signal reaches the wrong owner

The first friction is ownership. Many signals are visible, but they land in a mailbox, a dashboard, or a status meeting instead of the person who can actually change the task. That adds an extra handoff, and every handoff adds time, friction, and social hesitation.

In more than 250 projects, Andreza Araujo has seen that the fastest organizations do not wait for perfect clarity before naming the next owner. They define the owner early, define the escalation route, and define the field check that will confirm whether the issue is contained. The result is not more noise. It is less drift.

If your team still uses phrases like "someone is looking at it" or "we have escalated it", check whether the next decision owner was named in the first minute. When ownership is vague, decision age grows quietly while everyone feels busy.

3. Friction 2: the board gets the number after the field moved

Boards often ask for a clean monthly pack, but monthly packs can be structurally late for a dynamic exposure. By the time the number is locked, reviewed, and presented, the field may already have changed twice. The chart is not false. It is just old enough to miss the decision window.

As Muito Alem do Zero makes clear, a number can improve while the underlying risk stays intact. That is why a board should ask not only what the number says, but also when the field condition last changed and what action was still possible at that moment.

This is where many executive reviews become ceremonial. The room discusses the metric as if the metric were the risk. In reality, the metric is only one step behind the risk, and sometimes it is two or three steps behind the authority that could still intervene.

4. Friction 3: the dashboard tracks activity instead of control proof

Activity counts feel productive because they are easy to report. Trainings delivered, inspections completed, and meetings held all create movement on the page. The problem is that activity is not proof of control, and a lot of dashboards confuse the two.

Safety Culture Diagnosis: Learn how to do your own is useful here because it forces the leader to separate perception from evidence. A control proof asks whether the barrier actually held in the field. A checklist asks whether someone said it did. Those are different questions.

If your board review still treats completion rates as evidence of risk reduction, the dashboard is measuring administrative motion. That is not a trivial error. It lengthens decision age because leaders think they already have an answer when they only have a count.

5. Friction 4: the response window is invisible

A signal becomes useful only when the organization can see the time available to act. If the response window is hidden, the issue can sit in process long enough to become normal. That is how delay turns into habit.

James Reason's model of latent conditions applies here as well. The visible problem is not the delay itself. The visible problem is the system that made delay acceptable, predictable, and socially safe. Once that happens, the clock stops feeling real.

The fix is to name the response window in plain language. Say who must decide, by when, and what field check will confirm that the decision reached the work. When the window is explicit, decision age becomes a number the organization can manage instead of a feeling it can ignore.

6. Friction 5: escalation travels slower than exposure

Escalation is supposed to move risk to the person with the authority to change it. In practice, it often becomes a polite forwarding exercise that adds delay without adding authority. The issue moves upward, but the ability to act does not move with it.

That is why Andreza Araujo keeps returning to visible decision rights in her work. In Safety Culture: From Theory to Practice, culture shows up when a leader makes the next move obvious. In A Ilusao da Conformidade, the warning is sharper: a process can look complete while the actual control route remains weak.

For readers of Headline Podcast, the lesson is practical. If escalation takes longer than exposure, then the system has already lost the prevention race. The right response is not more urgency theater. It is a shorter route from signal to authority.

7. Data age, decision age, and response age are not the same number

That distinction matters because a fast report can still produce a slow consequence. If the number is recent but the owner is unclear, response age grows. If the owner is clear but the field check is missing, decision age grows. If both are slow, the organization may still be congratulating itself for being data driven while governing too late.

Executive teams do not need one more dashboard that looks precise. They need a clock that tells them whether the current data can still change the work. That is the threshold between information and governance.

8. What leaders should change this week

Start by naming one signal that matters, one owner who can act, and one field check that proves the change reached the work. Then write the response window on the same page as the metric, because if the clock sits elsewhere it will be forgotten.

• Stop asking whether the chart is green before asking whether the signal is still live.
• Replace vague phrases like "we escalated it" with a named owner and a visible deadline.
• Separate activity counts from control proof so the dashboard does not reward motion alone.
• Ask the field what changed, not just what was reported, because the field often knows before the pack does.
• Review one recent issue end to end and measure the delay between signal, decision, and visible response.

If you want the deeper framework, Safety Culture: From Theory to Practice and Muito Alem do Zero show why repeated decisions reveal the real operating model. For a practical next step, visit the Andreza Araujo store or keep following Headline Podcast for more field-facing diagnosis.

FAQ

What is decision age in safety?

Decision age is the time between a useful signal and the moment authority changes the work. It is the clock that tells you whether the organization still had time to act.

How is decision age different from metric freshness?

Metric freshness only tells you whether the data is recent. Decision age tells you whether the data was recent enough to matter, which is a much stricter test.

Why can a green dashboard still hide risk?

Because activity counts, delayed packs, and missing control proof can all look orderly while the field has already moved on. A clean page is not the same thing as a controlled operation.

Which Andreza Araujo book fits this topic best?

Safety Culture: From Theory to Practice fits because it ties culture to repeated decisions. Muito Alem do Zero and A Ilusao da Conformidade fit because they separate flattering numbers from real control.

What should a board ask instead of only asking for the latest number?

The board should ask when the field condition last changed, who owned the next decision, and whether the response window was still open. Those three questions expose decision age fast.

What is the fastest way to reduce decision age?

Name the owner earlier, shorten the escalation route, and require one field verification before closure. That turns the metric from a report into a decision tool.