Good Enough Mentality

What is Good Enough Mentality?

A maintenance crew was re-torquing flange bolts on a high-pressure steam line during a turnaround with aggressive deadlines. The procedure called for calibrated torque wrenches and a specific tightening sequence. The lead mechanic, under pressure to release the line for start-up, decided the bolts were "close enough" by feel and signed off the job without the final torque verification. Two weeks later, a gasket blew on that flange during normal operations, releasing 600-degree steam into a walkway. A pipe fitter suffered severe burns to his legs. The bolts were found to be 15% under specification -- close enough to hold during a cold test, but not under operating conditions.

The "good enough" mentality is the acceptance of work quality that meets the minimum apparent threshold rather than the actual required standard. It is the voice that says "that'll do" when the job is 90% right, overlooking the fact that in safety-critical work, the last 10% is often where the margin between safe and catastrophic lives.

Key Components

1. Recognizing the "Good Enough" Trap

• Notice the rationalizations: "It's held this long," "Nobody's going to check," "We're running out of time," and "It's basically the same thing" -- these are the phrases that precede most quality-related failures.
• Understand that "good enough" is subjective and expands over time -- what feels like a minor compromise today becomes the new baseline tomorrow, and the standard keeps sliding.
• Recognize that the gap between "good enough" and "right" is often invisible until a failure reveals it -- systems can appear to function normally while operating outside their design margin.
• Be aware that fatigue, schedule pressure, and social pressure from peers or supervisors are the conditions where "good enough" thinking thrives.

2. Holding the Standard When Pressure Mounts

• Know the actual specification, tolerance, or procedure requirement before you start -- you cannot judge whether something meets the standard if you do not know precisely what the standard is.
• When someone says "that's good enough," ask the clarifying question: "Good enough compared to what?" -- if the answer is not a written specification or engineered tolerance, it is an opinion, not a standard.
• Build decision points into your workflow where you stop and verify against the actual requirement, not against your memory or feeling of how it should look.
• Document and communicate when you reject "good enough" and insist on doing it right -- this creates a visible record that protects you and sets expectations for the team.

3. Addressing the Root Causes

• Push back on schedules that make doing the job correctly impossible -- if the timeline only works when people cut corners, the timeline is the problem, not the workers.
• Ensure workers have the right tools, materials, and training to meet the actual standard -- "good enough" often happens because the resources to do it right are not available.
• Create a culture where stopping to do rework is seen as professionalism, not inefficiency -- the cost of rework is always less than the cost of a failure.
• Hold leaders accountable for the conditions they create -- a supervisor who praises "getting it done fast" but punishes rework is building a "good enough" culture whether they mean to or not.

Building Your Safety Mindset

1. Define "Right" Before You Start

   • Review the written procedure, specification, or engineering standard for the task before picking up a tool -- do not rely on what you remember from last time.
   • If the standard is unclear or the procedure does not exist, stop and get clarification before proceeding -- ambiguity is where "good enough" fills the vacuum.
   • Visualize the consequence of the "good enough" version failing -- not to create fear, but to give yourself a concrete reason to hold the line when pressure arrives.

2. Resist the Drift in Real Time

   • When you feel the pull to accept "close enough," treat it as a decision point, not a thought to brush aside -- pause, assess, and make a conscious choice.
   • Say it out loud to a coworker: "I'm tempted to skip this step because we're behind schedule -- help me make the right call" -- externalizing the pressure reduces its influence.
   • Remember that "good enough" never applies to safety-critical dimensions -- a bolt is either torqued to spec or it is not, a guard is either in place or it is not, a test is either passed or it is not.

3. Build Team Norms That Reject Mediocrity

   • Celebrate crews that refuse to release equipment or sign off work that does not meet the standard, even when it delays the schedule -- what you celebrate becomes what your team values.
   • Include "Was there any pressure to accept less than the standard?" as a routine question in post-task debriefs.
   • When rework is needed, frame it as "catching it before it hurts someone" rather than "someone messed up" -- the narrative determines whether people hide or fix quality issues.

Discussion Points

1. What is the most recent example of "good enough" thinking in our work area, and what was the real risk that was being accepted without explicit acknowledgment?
2. When schedule pressure and quality standards conflict, who in our organization has the actual authority to hold the line -- and does the person doing the work feel empowered to exercise that authority?
3. How do we distinguish between smart engineering judgment ("this tolerance is acceptable for this application") and the "good enough" mentality ("this is close enough, let's move on") -- and where have we gotten that distinction wrong?

Action Steps

• Pick one task you will perform this week and look up the exact specification or procedure requirement before starting -- compare it to what you normally do from memory.
• The next time you feel pressure to accept "close enough," pause and ask yourself or a coworker: "Would I sign my name to this if an investigator reviewed it tomorrow?"
• Have a conversation with your supervisor about one situation where schedule pressure has made it difficult to meet the actual quality standard, and propose a specific solution.
• Review one completed job from the past month and honestly assess whether every element met the written standard or whether any "good enough" compromises were made.