The Language That Keeps People Quiet About Pain

Why this matters

Most of the injuries that end trade careers start as something small: a shoulder that aches after overhead work, a wrist that is stiff in the morning, a back that is sore every Thursday. At that stage the fix is usually a change to the task, and it costs almost nothing. The reason it so often goes unmentioned until it is a torn rotator cuff or a herniated disc is not that techs do not notice. It is that the crew has taught them, a phrase at a time, that mentioning it is a mistake. "Walk it off." "Rub some dirt on it." "You're getting old." None of these are meant to do harm, and all of them do. This card is about how that language works and what a lead can say instead.

Every response is heard by the whole crew

The mechanism is simple and it is easy to miss. When a tech mentions pain and a lead answers with a joke, two people are in the conversation and the whole crew is learning from it. Everyone within earshot just found out what happens to the next person who says their back hurts. Nobody needs to be told the rule. They watched it.

So the important moment is not the formal injury report. It is the offhand mention in the van or at the supply house counter: "my elbow's been killing me." What the lead says in the next five seconds decides whether that tech, and everyone listening, ever mentions the next one.

That is also why this is about the lead, not the policy. A shop can have an excellent written early-reporting process (see related: Building a Shop Where People Report Pain Early) and still get no reports, because the crew believes the lead over the binder.

The phrases and what they teach

Some of these are cruel and most are not. "Everybody hurts, it's the job" is often said with sympathy, by someone who is hurting too. It still teaches that the pain is not worth raising, and the person saying it is frequently the next one hurt.

What the fear underneath actually is

Replacing the phrases works better once you know what a tech is actually afraid of when they keep quiet. It is rarely the pain. It is usually one of these:

• Losing hours or pay, by being sent home, put on light duty at a lower rate, or taken off overtime.
• Being seen as weak, especially for a younger tech trying to prove himself or an older one worried about being seen as past it.
• Being taken off the work they like or are proud of, and given the jobs nobody wants.
• A workers' compensation claim, which many techs believe, sometimes correctly in their experience, marks them as a problem.
• Being the reason the crew is short, which in a small shop is a real cost they can see.

Every useful replacement phrase answers one of these fears directly. A lead who says "nobody loses hours over this" has done more than any poster.

Hear the minimizer as the report

The crew's language works in the other direction too. Techs who have learned that pain is not worth raising still mention it, but they wrap it in words that make it easy to ignore: "probably nothing," "just a little tweak," "a bit stiff," "I slept on it wrong." Those are not descriptions of how bad it is. They are the tech protecting himself in advance, giving the lead an easy way to let it pass and keeping his own status intact if the lead does.

So a lead should treat a minimizer as the report itself, not as a sign that there is nothing to report. "Probably nothing" from someone who never mentions pain is worth more attention than a full complaint from someone who mentions everything. The tell to listen for is duration: "couple of weeks," "since the start of the month," "every morning now." Anything that has lasted more than a few days, or comes back with the same task, is exactly the early discomfort the shop wants to hear about.

Replacements a lead can use

The pattern for a good response is: take it seriously, ask about the task, remove the fear, close the loop.

• Instead of "walk it off": "When does it hurt? What were you doing?" This moves straight to the task, which is where the fix is.
• Instead of "you're getting old": "Good that you said something. That's how we catch it early." This rewards the mention.
• Instead of "is this a comp claim?": "Let's figure out what's causing it first." The paperwork question, where it comes up, can wait a day and comes from the office.
• Instead of "who's going to cover you?": "We'll sort the schedule. You don't lose hours over this." Name the fear and take it off the table.
• Instead of a one-time "go see someone": "I'll check in Friday and see how it's doing." Then do it. The follow-up is the part that tells the tech it was not a brush-off.

Here is what that sounds like in a real moment, at the van at the end of a day:

TECH: Shoulder's been bugging me. Probably nothing.
LEAD: How long's it been going on?
TECH: Couple weeks. Worse after the attic jobs.
LEAD: Reaching up into the air handlers?
TECH: Yeah. Holding stuff overhead.
LEAD: Glad you said. Let's get a stand-up platform
      on your van for those, cut the reach. And I'll
      ask you Friday how it feels.
TECH: Don't want to make it a thing.
LEAD: It's not a thing. It's a step stool. Nobody
      loses hours over this.

Notice what the lead did not say: nothing about pain being part of the job, no joke, no question about a claim, no instruction to see a doctor that sends the tech off alone. He asked about the task, found a fix, removed the fear and set a follow-up. Whether the tech needs medical attention is a judgment that sharpens with the follow-up, and if it is not getting better by Friday, that is when the conversation moves to a doctor and the shop's injury process.

The moment, replayed two ways

A residential HVAC tech, eight years in, mentions in the van that his right shoulder has been aching for a couple of weeks, worse after attic air-handler jobs.

First version. The lead laughs: "Welcome to your thirties. Ice it." The tech says nothing more. Over the next three months he does about two attic jobs a week, roughly 26 more in all, each with overhead work. He starts favoring the arm, compensating with his back. In month four he cannot lift his arm above his shoulder at all, sees a doctor, and is told he has a significant rotator cuff injury. He is off work for about ten weeks and on restricted duty for longer. Nobody in the van that day remembers the conversation, because to them it was not one.

Second version. The lead has the exchange in the box above. A stand-up platform goes on the tech's van that week, so the overhead reach shrinks, and for the next month the lead pairs him with a second tech on the two heaviest overhead installs. On Friday the shoulder is about the same; two weeks later it is better. No time lost, no claim, no surgery.

The two versions differ in one sentence. Everything after it follows. The mechanism by which a few weeks of strain becomes a torn tendon is covered in full elsewhere (see related: How Cumulative Strain Injuries Actually Develop); what this example shows is that the deciding moment was conversational, not medical.

What would change it. If the tech had described sudden pain from a specific event, such as feeling something give while lifting a condenser, that is an injury, not early discomfort, and it goes into the shop's injury reporting process the same day, with medical attention, rather than a wait-and-see Friday check-in. The reporting obligations and deadlines that apply then depend on your state's workers' compensation law and are covered in the injury-reporting SOPs.

The office and the owner speak this language too

Leads are not the only source. The office manager who answers an injury mention with "how did it happen?" in a tone that suggests blame teaches the same lesson. So does an owner whose first public reaction to an injury is about the insurance premium. And so do safety incentive programs that reward crews for days without an injury, which in practice reward crews for not reporting. OSHA has stated that programs which discourage reporting can violate the anti-retaliation provision of its recordkeeping rule, 29 CFR 1904.35(b)(1)(iv), and Section 11(c) of the OSH Act separately protects an employee who reports an injury from retaliation, so this is not only a culture problem.

The safe pattern for everyone: the first question is about the person and the task, and the paperwork questions come later, from whoever handles the paperwork.

Changing a lead's own habit

Most leads who say "walk it off" learned it from their own first lead and have never thought about it. Telling them to stop rarely works. What does:

• Explain the mechanism once, plainly. The crew is watching, and the next person to keep quiet might be on your crew when it turns into ten weeks off.
• Give them two or three replacement lines, not a list of banned phrases. People adopt a sentence they can say; they do not adopt a prohibition.
• Do not police banter. Crews joke, and jokes about each other's aches are part of how people get along. The problem is a joke in place of a response, not a joke at all. A lead can laugh and then ask "seriously though, how long's it been?"
• Make the follow-up a habit. The single most persuasive thing a lead can do is come back on Friday and ask. That is what the crew sees, and it does more to change what they believe than any phrase.

References

• See related: How Cumulative Strain Injuries Actually Develop
• See related: Building a Shop Where People Report Pain Early
• See related: The Early Discomfort Report SOP
• 29 CFR 1904.35(b)(1)(iv), employee involvement and the prohibition on retaliation for reporting work-related injuries and illnesses