Technical Dissent Protocol: Build It in 30 Days

Technical dissent is one of the cheapest safety controls a supervisor can protect, because it catches weak assumptions before a permit, isolation, lift plan, traffic route, or restart decision becomes irreversible. The problem is that most sites say dissent is welcome while reacting to it as delay.

A technical dissent protocol is a simple operating routine that protects a worker, supervisor, engineer, or EHS specialist who challenges a safety-critical decision with evidence. It defines when dissent must pause work, who reviews it, how fast the answer returns, and what proof closes the loop.

In Amy Edmondson's 1999 study on psychological safety and learning behavior in work teams, psychological safety was associated with learning behavior in 51 work teams. In occupational safety, the lesson is practical rather than academic: people speak earlier when the first reaction from authority is curiosity instead of embarrassment, sarcasm, or pressure to continue.

ISO 45001:2018 specifies requirements for an OH&S management system that prevents work-related injury and ill health, and ILO Convention 155 states that workers should report situations they reasonably believe present imminent and serious danger. A dissent protocol turns those principles into a supervisor routine that can be used in the first 10 minutes of disagreement.

Step 1: What counts as technical dissent?

Technical dissent is a safety-relevant challenge to a decision, plan, condition, or assumption, and it should be treated as valid when it names a hazard, barrier, exposure, uncertainty, or standard requirement. In 30 days, the site should move from informal disagreement to a defined trigger list that supervisors can recognize during live work.

Start by separating dissent from complaint. A complaint may say, "This job is badly planned." Technical dissent says, "The scaffold handover does not match the access point, and the crew will cross under suspended material." The second statement gives the supervisor something to test.

Use 6 trigger families: uncertain isolation, missing critical control, conflicting procedure, changed site condition, competence doubt, and abnormal pressure to continue. This keeps the protocol close to work rather than turning every interpersonal conflict into a formal review.

Across 25+ years leading EHS at multinationals, Andreza Araujo has identified that weak cultures often silence technical dissent before the record begins. The worker rarely says, "I was punished." More often, the worker learns that raising doubt creates irritation, and that social cost is enough to keep the next warning quiet.

Step 2: Define the 10-minute pause rule

The 10-minute pause rule gives the supervisor a short, legitimate window to examine dissent without making the person who spoke up look obstructive. The clock matters because a vague pause becomes production conflict, while a defined pause becomes part of the work method.

Write the rule in operational language: when technical dissent touches a high-risk task, the immediate supervisor pauses the affected activity for up to 10 minutes, protects the person from interruption, and tests the named control with the crew member who raised the concern. If the doubt involves imminent and serious danger, the pause remains active until a competent reviewer resolves it.

This rule should be linked to existing stop-work authority, but it should not depend on a dramatic stop-work moment. Many people will raise a doubt earlier if the first step is a technical pause rather than a confrontation. The related guide on 48-hour safety concern triage is useful for concerns that do not require immediate field review.

10 minutes is enough to inspect the permit, control point, changed condition, or supervisor assumption in many routine jobs, and it is short enough to make the pause acceptable in production settings. The discipline is not the number alone. It is the promise that dissent receives a time-boxed technical answer.

Step 3: Assign the reviewer before the first conflict

A dissent protocol fails when the reviewer is chosen during the argument, because hierarchy and production pressure usually select the person most invested in continuing. Before launch, each high-risk work family needs a named reviewer and a backup who can judge the technical point without defending the original plan.

For energized work, the reviewer may be the electrical authority. For lifting, it may be the appointed person or rigging engineer. For confined space, it may be the rescue coordinator or permit issuer. For vehicle-pedestrian interaction, it may be the logistics supervisor with EHS support.

As Andreza Araujo argues in Safety Culture: From Theory to Practice, culture appears in repeated management behavior, not declared intention. The reviewer choice is one of those behaviors. If the organization always sends dissent back to the person who approved the plan, the field learns that the review is symbolic.

Document reviewer names in the permit-to-work standard, risk assessment procedure, and supervisor playbook. A simple table is enough when it names the task family, first reviewer, backup reviewer, escalation level, and expected response time.

Step 4: Build a dissent card supervisors can use on shift

A dissent card is a one-page field script that helps supervisors receive bad news without improvising under pressure. It should fit one screen or one laminated card, because a 12-page procedure will not help a foreperson standing beside a delayed job.

The card should include 5 prompts: what changed, which control is uncertain, what could happen if work continues, what evidence supports the concern, and what decision would make the job safe enough to proceed. Those prompts keep the conversation technical.

The card should also include 3 forbidden reactions: sarcasm, interrogation about attitude, and immediate reassurance without checking the field. These reactions are common because supervisors often feel judged by dissent. The card reminds them that the issue is the control, not their authority.

NIOSH explains that Total Worker Health prioritizes a hazard-free work environment, and that principle applies here even when the subject is voice. Dissent is not only a cultural signal. It is a way to find hazardous work design before exposure becomes accepted.

Step 5: Train the first response in 30 minutes

Supervisors do not need a full-day seminar to start protecting dissent, but they do need deliberate practice with the first 3 sentences they say after bad news arrives. A 30-minute microdrill can prevent the defensive reaction that kills the next report.

Train supervisors to answer dissent with this sequence: "Show me the condition," "Which control are you worried about?" and "What would you need to see before we continue?" Those sentences are short, but they shift the conversation from personality to evidence.

The drill should include at least 4 scenarios: a junior mechanic challenging an isolation, a contractor questioning a lift path, an operator warning about a changed line-of-fire exposure, and a new employee disagreeing with a restart decision. The last scenario matters because new workers often see abnormal conditions that experienced teams have normalized.

The article on near-miss debriefs for supervisors expands the same discipline after an event has already occurred. Technical dissent works earlier, while the task is still adjustable.

Step 6: How should EHS record dissent without creating fear?

EHS should record technical dissent as control intelligence, not as a person-centered complaint, because the record will shape whether workers trust the protocol. The minimum record should capture the task, concern, control tested, decision made, reviewer, response time, and answer returned to the person who raised the issue.

Avoid forms that ask whether the worker was correct. That wording turns dissent into a trial. The better question is whether the concern revealed uncertainty that needed verification. Sometimes the original plan will stand, although the review still has value because it proves the control was tested.

Use 4 status options: accepted and work changed, accepted and control verified, escalated for technical decision, or not applicable with reason. Do not use "rejected" as the default label, because it teaches people that speaking up creates a win-loss record.

In more than 250 cultural transformation projects, Andreza Araujo observes that answer speed is often more important than form complexity. If the person who raised the concern receives no answer, the protocol becomes another reporting box whose silence confirms the old culture.

Step 7: Connect dissent to the daily safety meeting

The daily safety meeting should review technical dissent patterns without exposing names or turning the discussion into a blame ritual. Within 30 days, supervisors should be able to say which control families generated dissent, which decisions changed, and which repeated doubts need a risk owner.

Use the meeting to ask 3 pattern questions. Which dissent signals repeated this week? Which one changed a control, sequence, or permit? Which one returned because the root condition remained? These questions keep the meeting away from storytelling and close to risk reduction.

When dissent comes from a new employee, contractor, or quiet operator, protect the source unless that person asks to be named. A public compliment can still create unwanted exposure in a crew where conformity pressure is strong. The post on post-incident meeting pitfalls shows how quickly group dynamics can silence evidence.

Every week without a visible dissent route teaches the field that doubt must be solved privately, and private workarounds are exactly where weak controls become normal.

Step 8: How do leaders know the protocol is working?

Leaders know the protocol is working when dissent changes decisions before events, not when the number of reports simply rises. In the first 30 days, the dashboard should show response time, percentage of signals reviewed within the shift, repeated control themes, and decisions changed because of dissent.

Use at least 5 indicators: average minutes to first response, share of dissent signals tied to high-risk work, percentage closed with a returned answer, number of repeated themes escalated to a risk owner, and number of controls changed. These indicators are stronger than counting how many people attended training.

5 indicators can show whether dissent is becoming a control routine instead of a campaign. A spike in signals during the first month may be healthy if response quality improves, because the organization is hearing warnings that previously stayed underground.

During Andreza Araujo's PepsiCo South America tenure, where the accident ratio fell 50% in 6 months, leadership cadence mattered because it forced follow-up. The same logic applies here: a dissent protocol without weekly review will fade as soon as production pressure returns.

Step 9: Close the 30-day pilot and decide what changes

The 30-day pilot should end with a decision review, not a celebration of participation. Leaders should decide which procedures, reviewer routes, supervisor routines, and risk thresholds must change because the pilot exposed weak assumptions in real work.

Review 10 dissent records, even if the pilot generated more. Choose records across different shifts, roles, and work families. For each one, ask whether the concern was specific, whether the supervisor used the pause rule, whether the reviewer was independent enough, and whether an answer returned to the worker.

Then change the system. If dissent repeatedly appears in contractor maintenance, revise the contractor interface. If it appears in restart decisions, strengthen restart readiness. If it appears in behavioral observation, align observers using the method described in behavioral observation calibration. If it appears in safety reporting, compare it with the traps described in safety reporting myths.

Andreza Araujo's book Make The Difference: Be a Leader in Health & Safety frames leadership as daily action, and technical dissent tests that action before the incident. A mature supervisor does not need to agree with every challenge. The supervisor does need to prove that a safety-critical challenge receives a fair technical route.

Organizations that want technical dissent to survive need a visible mechanism, named reviewers, short response times, and leaders who review changed decisions rather than slogans. Andreza Araujo and ACS Global Ventures help companies build that operating discipline through safety culture diagnosis, leadership routines, and field-control governance at andrezaaraujo.com.