Calumet “K” Series Chapter 8

Why Good Decisions Fail Without Explanation: The Leadership Gap Between Making the Right Call and Getting People to Follow It

You just made the right call. The decision was sound. The logic was clear. The reasoning was solid. You balanced competing priorities, evaluated risks carefully, and chose the best path forward given impossible constraints. You know it was the right decision because you thought it through completely before making it.

And your crew thinks you’re inconsistent at best, reckless at worst, or playing favorites somewhere in between. They don’t understand your reasoning because you never explained it. They see you being strict about minor safety violations while accepting major risks to meet deadlines. They watch you enforce rules rigidly in some areas while breaking them aggressively in others. They observe you making calls that look contradictory because they can’t see the principle connecting them.

Here’s what most superintendents do. They make good decisions and expect people to trust their judgment. They assume their authority means they don’t need to explain. They believe their track record speaks for itself. They think explanations undermine leadership by appearing defensive. They tell themselves that competent workers should understand without being told why decisions make sense.

And their crews resist. Not because the decisions are wrong, but because people don’t follow what they don’t understand. Workers comply when forced but resent decisions that seem arbitrary. Foremen implement orders halfheartedly when they can’t see the logic. Teams second-guess calls that appear inconsistent. Good decisions fail not because they’re wrong but because nobody explained why they’re right.

Leadership without explanation creates resistance even when your decisions are sound. Your judgment might be excellent. Your calls might be correct. Your strategy might be brilliant. But if people don’t understand your reasoning, they’ll see inconsistency instead of principle, favoritism instead of priorities, recklessness instead of calculated risk.

The Problem Every Leader Creates

Walk any project where the superintendent makes good calls but doesn’t explain them and watch what happens. Workers see strict enforcement of minor rules alongside acceptance of major risks. They observe punishment for carelessness and tolerance for aggressive approaches that push limits. They notice decisions that look contradictory because they can’t see the framework that connects them into coherent strategy.

The superintendent knows his reasoning. He’s balancing safety against schedule. He’s distinguishing between careless negligence and calculated risk. He’s enforcing rules that protect people while accepting risks that enable deadline compliance. Every decision makes sense within his framework. But he never articulated that framework to anyone else, so they can’t see how the pieces fit together.

Most leaders defend this approach. They claim explaining decisions wastes time. They argue that authority means not having to justify choices. They insist competent workers should trust their judgment without needing detailed reasoning. They believe explaining appears defensive or weak. They think leadership means making calls and expecting compliance without question.

But unexplained decisions create resistance that explained decisions prevent. When people understand your reasoning, they implement decisions with commitment rather than reluctant compliance. When they see the principle behind choices, they stop viewing apparently contradictory calls as inconsistent and start recognizing them as applications of the same framework to different situations. When they know why you made a call, they support it even when they initially disagreed.

The pattern shows up everywhere. You fire someone for dropping a hammer into a bin where workers are below. The same week, you order equipment overloaded to meet schedule demands despite foreman objections about risk. To you, these decisions are perfectly consistent: you won’t tolerate careless disregard for safety, but you will accept calculated risks when deadlines require it. To your crew, you’re being inconsistent: strict about minor violations while accepting major hazards.

Nobody sees the principle because you never explained it. You’re distinguishing between negligence that serves no purpose and risk that enables essential speed. Between carelessness that demonstrates contempt for coworkers and aggressive approaches that protect project viability. Between avoidable dangers created by laziness and necessary dangers created by impossible deadlines. The distinction is clear to you. It’s invisible to everyone else.

The Story That Reveals the Cost

There’s a construction story about a superintendent named Bannon who made excellent decisions but rarely explained his reasoning. He understood the difference between careless safety violations and calculated risk-taking. He knew when to be rigid about rules and when to push limits. His judgment was sound. His strategy was coherent. But he kept his reasoning to himself.

When a worker named Riley deliberately dropped a hammer into a bin where laborers were working below, Bannon fired him immediately. Riley claimed it was an accident, said his hammer slipped. Bannon didn’t argue about intent or investigate whether it was deliberate. He fired Riley on the spot and told him never to return. The message to the crew was clear: dropping tools where people are working gets you fired immediately, no questions asked, no second chances.

That same week, Bannon ordered his crews to lift four or five heavy timbers simultaneously with hoists designed for one or two. His foreman Peterson objected, warning this approach would overstress equipment and create dangerous conditions. Bannon acknowledged the risk and ordered it anyway because the slower safe approach wouldn’t keep pace with carpenters waiting for materials. Days later the hoist broke, scaffolding collapsed, and someone was injured. Bannon fixed the equipment in two hours and gave the same order: carry the same load, maintain the same pace.

To Bannon, these decisions were perfectly consistent. He fired Riley for careless disregard of safety that served no purpose except laziness. He accepted hoist overloading because meeting the deadline required accepting elevated risk. One was negligence. The other was calculated necessity. One demonstrated contempt for coworkers. The other balanced competing constraints. The distinction was clear.

But Bannon never explained this reasoning to anyone. He made decisions and expected compliance without justification. The result? His office worker Hilda and her brother Max thought he was inconsistent. They couldn’t see the difference between dropping a hammer and overloading a hoist. They viewed him as rigid about minor issues while reckless about major risks. They admired his energy but questioned his judgment.

His foreman Peterson grew increasingly critical, telling Max in private conversations that Bannon’s methods were dangerous and his decisions contradictory. Peterson couldn’t understand why Bannon was strict about some safety rules while breaking others. The criticism spread. Workers complied with orders but resented decisions they viewed as arbitrary. The misunderstanding grew because Bannon was “not in the habit of giving his reasons.”

The chapter documenting this story states it directly: “Bannon’s distinction between running risks in order to push the work and using caution in minor matters was not recognized in their talks. And, as Bannon was not in the habit of giving his reasons, the misunderstanding grew.”

Good decisions. Sound reasoning. Excellent judgment. Complete failure to communicate the logic. The result was resistance, resentment, and misunderstanding even though Bannon’s calls were correct. His leadership failed not because his decisions were wrong but because nobody understood why they were right.

Why This Matters More Than Being Right

When you make good decisions without explaining them, you’re not protecting your authority—you’re undermining it. You’re creating resistance that wastes more time than explanation would cost. You’re forcing compliance instead of building commitment. You’re teaching people to distrust your judgment rather than understand your framework.

Think about what happens when leaders refuse to explain their reasoning. The crew sees you enforce a rule strictly in one situation and ignore it completely in another. Without explanation, they conclude you’re inconsistent, playing favorites, or making arbitrary calls based on mood rather than principle. They don’t see that you’re applying a framework consistently to different situations. They see contradiction where you see coherent strategy.

Your foremen watch you accept major risks to meet deadlines while punishing minor safety violations. Without understanding your distinction between calculated risks that enable success and careless negligence that serves no purpose, they think you care more about schedule than safety. They don’t realize you’re protecting both by distinguishing between necessary risks and avoidable dangers. They see hypocrisy where you see necessary balance.

Workers observe you making calls that initially seem wrong but later prove correct. Without hearing your reasoning, they assume you got lucky rather than learning that your judgment was sound from the start. They don’t develop trust in your decision-making because they never understood why your calls worked. They view success as accident rather than recognizing it as the result of good thinking.

The cost of unexplained decisions compounds over time. Early in a project, people give you benefit of the doubt. They assume your calls make sense even if they don’t understand them. But as apparently contradictory decisions accumulate without explanation, doubt grows. People start questioning everything. They resist all decisions, not just the ones they disagree with. They implement orders reluctantly, looking for reasons to prove you wrong rather than working to make decisions succeed.

Watch for These Signals That Unexplained Decisions Are Creating Resistance

Your project is suffering from leadership without explanation when you see these patterns appearing:

• Workers describe your decisions as “inconsistent” or say you have favorites, even though you’re applying the same framework consistently across different situations that look different on the surface
• Foremen comply with orders reluctantly or try to modify your decisions without permission, implementing their interpretation rather than your actual instruction because they don’t understand your reasoning
• Crews gossip about your judgment in private conversations, questioning decisions that were actually sound but appeared arbitrary because the logic wasn’t explained
• Good workers who initially supported you become critical over time as unexplained decisions that seem contradictory accumulate without the framework that would make them coherent

The Framework: Explaining Without Appearing Defensive

The goal isn’t justifying every decision to every person. It’s articulating the principles that guide your choices so people can see coherence where they currently see contradiction. When decisions appear to conflict, explanation reveals the framework that makes them consistent applications of the same values to different situations.

Start by identifying the principle behind decisions that appear contradictory. Bannon’s principle was clear but unstated: careless negligence that serves no purpose gets punished immediately, calculated risks that enable deadline compliance get accepted consciously. That principle explains both firing Riley and accepting hoist overloading. Without articulating it, people saw inconsistency. With explanation, they’d see coherent strategy.

Explain your reasoning when making calls that will appear contradictory without context. When you fire someone for a minor violation the same week you accept major risks, people need to understand the distinction. “I won’t tolerate careless disregard for safety that serves no purpose. Dropping hammers where people are working demonstrates contempt for coworkers and gets you fired. But I will accept calculated risks when meeting deadlines requires it. Overloading hoists is risky but necessary. The difference is purpose: one serves nothing, the other enables success.”

Distinguish between types of risk when accepting some dangers while punishing others. Help people see that you’re not being inconsistent about safety, you’re distinguishing between avoidable negligence and necessary risk-taking. “Careless violations that could be prevented with basic attention get punished immediately. Elevated risks required to meet deadlines get accepted consciously. We prevent dangers we can avoid. We manage dangers we can’t eliminate while still finishing on time.” If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Use examples to illustrate principles when decisions seem to contradict each other. “Last week I fired Riley for dropping a hammer into a bin. This week I’m accepting hoist overloading despite risks. These decisions follow the same principle: I won’t tolerate careless negligence, but I will accept calculated risks when deadlines require it. Riley’s action served no purpose except laziness. Hoist overloading serves deadline compliance. Purpose determines acceptable risk.”

Articulate your framework before situations arise that will test it. Don’t wait until people question your consistency to explain your reasoning. State your principles early and reference them when making calls. “We distinguish between careless violations and calculated risks. Negligence that serves no purpose gets punished immediately. Risks required to meet deadlines get managed consciously. When you see me enforce strictly in one area while accepting risk in another, you’re seeing that distinction in action.”

The Practical Path Forward

Here’s how this works in practice. You need to make decisions that will appear contradictory without explanation. You’re going to be strict about some safety rules while breaking others. You’re going to punish some violations immediately while accepting some risks consciously. People will see inconsistency unless you articulate the framework connecting these choices.

Before making calls that will seem contradictory, explain the principle that makes them consistent. Don’t wait until people question your judgment. State your reasoning proactively. “We’re going to be strict about careless safety violations that serve no purpose. Dropping tools where people are working gets you fired immediately. But we’re also going to accept elevated risks when meeting deadlines requires it. We’ll push equipment harder than comfortable limits. These aren’t contradictory—one is negligence, the other is calculated necessity.”

When crew members question your consistency, use the opportunity to clarify your framework rather than defending individual decisions. Don’t argue about whether a specific call was right. Explain the principle behind it. “You’re asking why I fired Riley but accept hoist overloading. The difference is purpose. Riley’s carelessness served nothing. Hoist overloading enables deadline compliance. I punish negligence that could be avoided. I accept risks that can’t be eliminated while still finishing on time.”

Distinguish publicly between different types of violations so everyone understands which rules are rigid and which are flexible. “Safety rules that prevent careless negligence are non-negotiable. Dropping tools, tracking mud into work areas, ignoring basic precautions—these get enforced strictly. But when deadlines require accepting elevated risks, we’ll make those decisions consciously. You’ll see me strict about some things and accepting of others. That’s not inconsistency. That’s distinguishing between avoidable dangers and necessary risks.”

Help foremen understand your decision framework so they can implement it consistently without constant supervision. Don’t just give orders. Explain the logic so they can make aligned decisions when you’re not present. “When you’re deciding whether to enforce a rule or accept a violation, ask: does this serve any purpose? Carelessness that serves nothing gets punished immediately. Aggressive approaches that enable schedule compliance get managed consciously. Apply that distinction and your calls will align with mine.”

Create opportunities for questions about decisions that seem contradictory. Don’t treat questions as challenges to authority. Treat them as requests for clarity about reasoning. “You’re wondering why I accepted this risk after punishing that violation. Good question. Let me explain the difference.” Questions reveal where your framework isn’t clear. Answer them and the resistance dissolves.

Why This Protects Projects and People

We’re not just building projects. We’re building teams that understand why decisions make sense, not just following orders because authority demands it. And explained decisions create commitment that unexplained decisions can never generate.

When Bannon refused to explain his reasoning, he created resistance even though his decisions were sound. Workers complied reluctantly. Foremen implemented orders halfheartedly. Good people like Max and Hilda questioned judgment that was actually excellent. The misunderstanding grew until Peterson moved out of their shared room and the crew split into factions supporting different approaches.

The project still succeeded because Bannon’s decisions were correct despite poor communication. But imagine how much easier success would have been with commitment instead of reluctant compliance. How much less resistance he would have faced if people understood his framework. How much more effectively his team would have implemented decisions they recognized as applications of coherent principles rather than viewing as arbitrary contradictions.

Explanation doesn’t undermine authority. It builds trust in your judgment by helping people see that your decisions follow consistent principles rather than arbitrary preferences. It creates commitment by showing that calls make sense within a framework rather than requiring blind faith in your infallibility. It enables aligned decision-making by teaching people the logic so they can apply it themselves when you’re not present.

This protects families by reducing the friction that comes from resistance. Projects where crews fight leadership waste time arguing about decisions instead of implementing them effectively. Projects where teams understand reasoning execute efficiently because everyone’s aligned around shared principles. Less friction means less overtime making up for lost productivity. Less resistance means more predictable schedules protecting family time.

The Challenge in Front of You

You can keep making good decisions without explaining them. You can expect people to trust your judgment without understanding your reasoning. You can treat questions as challenges to authority rather than requests for clarity. You can assume competent workers should understand without being told. You can let misunderstandings accumulate until resistance undermines even your best calls.

Or you can articulate your framework. You can explain the principles behind decisions that appear contradictory. You can distinguish between types of violations so people understand which rules are rigid and which are flexible. You can use questions as opportunities to clarify reasoning rather than viewing them as threats to authority. You can build commitment through understanding rather than forcing compliance through power.

The projects that succeed with least resistance aren’t led by people who make perfect decisions. They’re led by people who explain their reasoning so teams understand why calls make sense. Who articulate frameworks so apparently contradictory decisions appear as coherent applications of consistent principles. Who build commitment through clarity rather than demanding compliance through authority.

Your impossible deadline requires decisions that will seem contradictory without explanation. You’ll be strict about some rules while accepting violations of others. You’ll punish some risks immediately while accepting other risks consciously. You’ll make calls that appear inconsistent because people can’t see the framework connecting them. Explain your reasoning or watch good decisions fail because nobody understood why they were right.

On we go.

Frequently Asked Questions

Doesn’t explaining decisions make you look defensive or weak?

Explaining proactively before questions arise shows confidence in your reasoning. Defending after being challenged can appear weak. The timing matters. State your framework early: “We distinguish between careless negligence and calculated risk.” Then when you make apparently contradictory calls, people understand the principle rather than questioning your consistency. Explanation builds authority by demonstrating you have coherent logic, not undermining it.

How much explanation is enough without over-justifying every decision?

Articulate principles, not detailed justification for individual choices. Don’t explain why you fired Riley and accepted hoist overloading with lengthy defense of each call. State the framework once: “Careless violations get punished, calculated risks get managed.” Then reference it when making calls: “This is careless negligence, not calculated risk.” The principle does the explaining. You’re teaching a framework, not defending individual decisions.

What if explaining your reasoning reveals you don’t have good logic?

Then you’re making decisions without sound reasoning and the problem isn’t communication, it’s judgment. But if your calls are actually based on coherent principles, articulating them strengthens authority rather than exposing weakness. Bannon’s framework was solid: distinguish careless negligence from calculated risk. He just never stated it. If you can’t explain your logic, maybe you don’t have logic worth following.

How do you explain calculated risks without scaring workers about safety?

Be honest about what you’re accepting and why. “We’re pushing equipment harder than comfortable limits because the deadline requires it. This increases risk. We’re accepting that consciously because the alternative is project failure that costs everyone’s jobs. Be extra careful. Watch for signs of stress. We’re managing this risk, not ignoring it.” Workers respect honesty about tradeoffs more than pretending everything’s perfectly safe when they can see it isn’t.

What if your foremen still disagree with decisions after you explain them?

Understanding doesn’t require agreement. Peterson might still object to hoist overloading even after hearing Bannon’s reasoning about deadlines requiring elevated risk. That’s fine. The goal is alignment around a framework, not universal agreement with every call. Foremen who understand your principles can implement decisions with commitment even when they’d make different choices. Understanding creates functional alignment. Agreement is nice but not necessary.