BBS Leadership Case: 2,300 Projects, 5 Years

BBS leadership is the executive and frontline discipline that turns behavior-based safety from an observation quota into a managed system of trust, coaching, and risk reduction. It treats observations as evidence, but it treats leadership quality as the condition that decides whether the evidence changes work.

The Bureau of Labor Statistics reported 5,070 fatal work injuries in the United States in 2024, and a worker died from a work-related injury every 104 minutes. This case study shows why behavior-based safety does not scale through more forms, but through leadership quality that changes what supervisors do after the observation.

1. What was the initial scenario?

Behavior-based safety often begins with a reasonable promise: observe work, identify safe and unsafe actions, coach the crew, and reduce exposure before an injury occurs. OSHA's recommended practices for safety and health programs identify management leadership as the first core element because the program only has authority when leaders visibly set direction, allocate resources, and expect performance.

On a Headline Podcast episode, Dr. Thomas Krause described evidence from 2,300 behavior-based safety projects followed across 5 years. The strongest predictor was not the number of observations collected by the workforce, but the quality of leadership given to the initiative. That finding matters because many companies still treat BBS as a frontline activity owned by the safety department.

The common failure is easy to recognize. The organization launches observation cards, trains observers, celebrates a monthly count, and then wonders why the pattern of serious risk does not move. The problem is not that observation is useless; the problem is that observation without decision rights becomes clerical work.

Headline readers who have followed Dr. Thomas Krause's conversation on safety leadership will recognize the same core point: leadership is not background noise. It is the mechanism that turns field knowledge into changed work.

2. Why did leadership quality beat observation volume?

Leadership quality beat observation volume because a behavior observation only creates value after someone removes an obstacle, adjusts a condition, coaches a supervisor, or changes a production decision. A site can collect 10,000 cards in a year and still leave the same high-risk shortcuts untouched if leaders never act on the patterns.

Dr. Krause's 2,300-project evidence gives executives a more useful question than "how many observations did we complete?" The sharper question is whether leaders reviewed the data with enough seriousness to change staffing, tooling, work sequence, maintenance priority, or supervisor routines. Observation volume is a signal of activity, while leader response is a signal of control.

Co-host Andreza Araujo's book *Cultura de Segurança: Da Teoria à Prática* makes a similar point from the culture side: safety starts with the individual, but it spreads through the organization only when leaders give it practical continuity. In that reading, BBS does not fail because people dislike correction. It fails when leaders outsource culture to a form.

For an executive sponsor, the practical move is to review a sample of 30 closed observations each month and ask which 5 changed the system. If the answer is "none," the BBS process is recording behavior but not managing risk.

3. What decision changed the case?

The decision that changed the case was treating BBS as a leadership system rather than a worker-monitoring system. Once leaders accepted that the observation database was evidence for management action, the program stopped asking only "what did the worker do?" and started asking what the organization made easy, hard, normal, or invisible.

This distinction protects the method from a familiar trap. When BBS is used to catch the 3 percent of moments where a worker missed a rule, it trains people to hide. When BBS is used to understand why the other 97 percent of safe work happened and where it becomes fragile, it gives leaders a map of the conditions they need to preserve.

The Headline discussion framed this as a trust problem, not just a measurement problem. Workers know whether the safety professional is acting as a collaborative partner or as a compliance police officer. That is why safety coaching after shortcuts has to be specific, timely, and connected to work design rather than delivered as a generic warning.

The executive decision is simple to describe and hard to sustain. BBS ownership must sit with operations leadership, with EHS acting as method owner and coach. If the plant manager is absent from the review rhythm, the workforce reads the program as another safety-department campaign.

4. How did execution look on the floor?

Execution on the floor looked like leaders walking work areas with observers, asking questions before giving answers, and following up on barriers that made unsafe behavior more likely. OSHA's safety program guidance lists worker participation as a core element, but participation only stays credible when management closes the loop on what workers report.

In practical terms, that means the observation conversation should separate 3 things: the behavior seen, the condition that shaped it, and the leadership action required. A forklift driver crossing a pedestrian path may need coaching, but the deeper fix may be a traffic layout change, a supervisor's production pressure, or a missing pedestrian barrier.

Andreza Araujo's work on cultural transformation repeatedly warns against mistaking compliance evidence for culture evidence. Across 250+ cultural transformation projects, the recurring lesson is that a system is measured by what happens when no one is watching, which is exactly where weak BBS programs lose credibility.

The best execution rhythm uses a 7-day loop. Observe work, classify the risk driver, assign one accountable leader, verify the corrective action in the field, then report back to the workgroup. Without that last step, participation decays because people conclude that their information went nowhere.

5. What result should leaders measure?

Leaders should measure whether observations change the risk system, not whether the organization hits an observation quota. In 2024, BLS reported that transportation incidents remained the largest fatal event category, which is a reminder that behavior data matters only when it reaches the operational decisions that shape exposure.

A useful BBS dashboard has 4 leadership measures: percent of observations that identify system obstacles, closure time for leader-owned actions, repeat observations on the same condition, and field verification quality. The first two show whether leadership is listening. The last two show whether the fix lasted.

This is where BBS connects with executive safety sponsorship. A sponsor who asks only for participation rate will get participation theater. A sponsor who asks which controls changed, which supervisor practice changed, and which repeated obstacle disappeared forces the program to serve risk reduction.

2,300 projects over 5 years is large enough to make the lesson uncomfortable: if leadership quality is the predictor, then a weak BBS result cannot be blamed only on worker resistance or observer skill.

6. Where do BBS programs drift?

BBS programs drift when the metric becomes safer than the conversation. A site that celebrates 95 percent completion while supervisors ignore repeated exposure is not running a weak version of BBS; it is running a reporting ritual whose numbers protect leaders from seeing the work.

The first drift point is quota pressure. The second is punitive response. The third is a dashboard that cannot distinguish a low-severity housekeeping note from a high-energy exposure. Once these 3 distortions appear together, the workforce learns that the program wants activity rather than truth.

NIOSH's Total Worker Health program argues that safety, health, and well-being are shaped by work design and organizational conditions, not only individual choices. That broader lens helps BBS leaders avoid blaming a worker for behavior that a schedule, layout, tool design, or incentive system made predictable.

Each quarter that BBS runs as a quota system teaches the workforce a habit that is hard to reverse: give the company the observation number it wants, while keeping the uncomfortable risk story off the form.

7. How should executives compare weak and strong BBS?

Executives should compare BBS models by the quality of decisions they produce, not by the neatness of the observation process. A weak model creates compliance evidence; a strong model creates operational signal, visible follow-up, and fewer repeated exposure patterns.

The table below gives a board-level diagnostic that can be used in a quarterly safety review. It is deliberately practical because senior leaders do not need another slogan. They need a way to spot whether the system is changing work or merely documenting it.

The table also shows why safety culture drift can hide inside a polished program. When leaders see a high completion rate, they may assume the culture is improving even though workers are only learning how to satisfy the measurement.

8. What should a senior leader do in the next 30 days?

A senior leader should spend the next 30 days testing whether BBS has changed work in at least 5 concrete places. The review should include observation samples, supervisor interviews, repeat-risk patterns, and field verification, because a program that cannot name changed work is not yet a risk-control system.

Start with 3 meetings. In week 1, review the last 30 observations and classify each as behavior only, condition, supervision, planning, or design. In week 2, walk the field with 2 supervisors and ask what they changed because of the observations. In week 4, ask workers whether they saw their input return as action.

As Andreza Araujo argues in *Muito Além do Zero*, good indicators do not guarantee good practices. The same applies here. A BBS metric becomes valuable when it forces a better leadership decision, not when it gives the dashboard a greener month.

The leadership lesson from the 2,300-project case is direct: behavior-based safety is not won at the observation card. It is won in the moment a leader hears the pattern, accepts ownership, and changes the work before the next exposure repeats.

Conclusion

BBS scales when leaders treat observations as evidence for operational decisions, because the 2,300-project Headline case points to leadership quality as the multiplier behind the method.

If your organization wants better safety conversations at executive and frontline level, listen to Headline Podcast and use this case to challenge whether your BBS program is changing work or only counting it.