Calumet “K” Series Chapter 17

The Public Praise Problem: Why Leaders Who Deflect Credit Build Stronger Teams Than Leaders Who Accept It

You did it. The impossible deadline got met. The project everyone said couldn’t be finished is complete. Your crew worked through blizzards, equipment failures, corruption attempts, and every obstacle the schedule could throw at them. They delivered. Now it’s time to celebrate, and someone wants to stand up and tell everyone how great you are as a leader.

Your delegate is giving a speech. He’s talking about the hard work. The team effort. How everyone came together. Good so far. Then he pivots: “We thought we understood our boss pretty well. But I’ve just found out we didn’t know as much as we thought we did. He’s been a pretty square friend to all of us, and I’m going to tell you something that’ll give you a chance to show you’re square friends of his, too.”

He’s about to praise you publicly. Tell a story that makes you look good. Shift focus from team achievement to individual leadership. And you’ve got a choice: let him continue and accept the recognition, or stop him and redirect credit back to the team.

Here’s what most superintendents do. They let the praise happen. They sit there looking humble while someone tells stories about their leadership. They accept recognition gracefully. They think refusing praise would seem false or ungrateful. They believe their crew wants to honor them, so refusing that honor would insult the team. They let individual glorification replace team celebration because stopping it feels awkward.

And while everyone’s praising the superintendent, the message being sent is that success came from individual heroics instead of systematic team execution. That leadership mattered more than the crew’s work. That one person deserves recognition while hundreds deserve applause. The celebration that should build team culture becomes a speech about why the boss is special.

The projects that build the strongest teams after impossible achievements aren’t led by superintendents who accept public praise. They’re led by people who physically stop praise speeches before they start. Who refuse individual glorification even when it makes the moment awkward. Who understand that “no soft soap” protects team culture better than humble acceptance of recognition you didn’t earn alone.

The Problem Every Superintendent Creates

Walk into any project celebration after a major achievement and watch what happens when someone starts praising the superintendent publicly. The team is gathered. The victory is fresh. Someone stands up to give a speech. They talk about the work, the challenges, the achievement. Then they shift to leadership: “And we couldn’t have done it without our superintendent’s vision and dedication.”

The superintendent sits there. Maybe looking down at the table. Maybe smiling modestly. Maybe nodding in acknowledgment. The crew applauds. The speaker continues with stories about the superintendent’s decisions, leadership moments, personal sacrifices. And throughout all of it, the superintendent accepts it. Lets it happen. Thanks them afterward for the kind words.

Most superintendents don’t recognize what this creates. When you accept public praise for team achievement, you’re endorsing the narrative that success came from individual leadership instead of systematic team execution. You’re letting one story—about your decisions—replace the real story about hundreds of people executing under pressure. You’re allowing individual glorification when you should be redirecting every word back to the crew who did the actual work.

The pattern shows up everywhere beyond formal celebrations. The client meeting where someone credits your leadership for the early finish, and you accept it instead of redirecting to your foremen and crews. The company newsletter featuring your photo with the completed project, positioning you as the hero. The award ceremony recognizing your individual achievement when the achievement required systematic team execution. Every time you accept individual credit for team achievement, you’re teaching people that leadership matters more than execution.

Think about what accepting praise communicates. When your delegate tells the crew “our boss is special,” and you sit there accepting it, you’re agreeing with him. When someone makes a speech about your leadership, and you thank them for the recognition, you’re endorsing the narrative that puts you at the center. When the story becomes about individual heroics instead of team systems, and you let it stand, you’re teaching your crew that success comes from special leaders instead of ordinary people executing well.

Your crew worked through a blizzard. They adapted when the first plan failed. They maintained momentum after crisis. They executed calculated risks. They anticipated attacks. They showed up when exhausted. They did the work. And now someone’s making a speech about how great YOU are for leading them. If you let that stand, you’ve just told them their execution mattered less than your leadership.

The Failure Pattern Nobody Recognizes

This isn’t about false humility or refusing all recognition. This is about understanding that accepting public praise for team achievement undermines the culture you’re trying to build. That individual glorification teaches people to look for hero leaders instead of building systematic capability. That “soft soap” about leadership destroys the focus on execution that produced the actual results.

Construction culture sometimes celebrates individual heroics. The superintendent who saved the project. The foreman who worked impossible hours. The leader whose vision made it possible. These stories sound inspiring. They make good speeches. They position leadership as the critical factor in success. And they’re dangerous because they teach people that extraordinary leaders produce extraordinary results, when actually systematic teams do.

So superintendents accept praise thinking it acknowledges their contribution. They let speeches happen thinking their crew wants to honor them. They receive recognition gracefully thinking refusal would seem ungrateful. They never recognize that every minute spent talking about leadership is a minute not spent celebrating the crew who executed. They don’t see that accepting individual credit undermines team culture more than refusing it protects.

The story always goes the same way. Project succeeds through systematic team execution. Celebration happens. Someone makes a speech praising the superintendent’s leadership. Superintendent accepts it gracefully, looking humble, thanking them for the kind words. Crew applauds politely. And the message sent is that leadership mattered most—that the superintendent deserves special recognition while the crew who did the actual work gets generic “great team” acknowledgment. The celebration becomes about individual heroics instead of systematic achievement.

Nobody teaches superintendents that deflecting credit builds stronger culture than accepting it. That physically stopping praise speeches protects team focus better than humble acceptance of recognition. That “we aren’t handing out any soft soap” creates more authentic celebration than eloquent speeches about leadership. That the strongest teams are built by leaders who refuse to be positioned as special.

A Story From the Field About Refusing Praise

A construction superintendent named Bannon had just completed an impossible deadline. The project was done. Wheat was flowing. The deadline was met with hours to spare. Everyone who’d worked on the job, hundreds of men, gathered for a victory dinner to celebrate the achievement.

The speeches began. Different crew members stood and talked. Eventually the delegate James got up to speak. He started well: “Boys, we’ve worked hard together on this job. And one way and another, we’ve come to understand what sort of man our boss is.” The crew roared approval. Hilda, sitting next to Bannon, blushed at the attention.

Then James pivoted to individual praise: “We thought we understood him pretty well. But I’ve just found out that we didn’t know so much as we thought we did. He’s been a pretty square friend to all of us. And I’m going to tell you something that’ll give you a chance to show you’re square friends of his, too.”

James was about to reveal something personal about Bannon—probably about his engagement to Hilda. He was building to a big reveal that would shift focus from team achievement to Bannon’s personal story. Making the celebration about individual glory instead of systematic team execution. And Bannon stopped him physically.

The story describes it directly: “He paused and then was about to go on, leaning forward with both hands on the table and looking straight down on the long rows of bearded faces when he heard a slight noise behind him. A sudden laugh broke out and before he could turn his head, a strong hand fell on each shoulder and he went back into his chair with a bump.”

Bannon didn’t ask James to stop. Didn’t politely interrupt. Didn’t wait for the speech to finish and then deflect credit afterward. He physically grabbed James by both shoulders and shoved him back into his chair before the words could leave his mouth. The intervention was immediate, physical, and unmistakable.

Then Bannon explained the rule explicitly. When the room quieted, he said: “Look here, boys, we aren’t handing out any soft soap at this dinner. I won’t let this man up till he promises to quit talking about me.”

“No soft soap.” Direct statement that praise speeches weren’t happening. Clear boundary that individual glorification was prohibited. Explicit rule that the celebration was about team achievement, not leadership recognition. And physical enforcement, Bannon literally held James in the chair until he agreed to stop.

The crew laughed. James protested. Bannon looked down at him “quietly and with a twinkle in his eyes, but very firmly” and said: “If you try that again, I’ll throw you out of the window.”

The threat was delivered with humor but meant seriously. James could get up and continue speaking, but only if he stopped talking about Bannon. Any attempt to shift focus back to individual leadership would result in physical removal. The boundary was clear, firm, and enforced with enough force that James understood it was real.

James finally agreed and was allowed to stand. Bannon slipped back into his seat next to Hilda and said quietly: “It’s all right. They won’t know it now until we get out of here.” He’d protected his personal story from becoming public spectacle. More importantly, he’d protected the team celebration from becoming individual glorification.

But James couldn’t resist completely. He tried one more approach, praising Bannon without revealing personal details. He shouted quickly “in order to get the words out before Bannon could reach him again”: “How about this, boys? Shall we stand it?” The crew shouted “No!” in chorus. “All right, then. Three cheers for Mr. Bannon. Now, hip-hip!”

The crew gave the cheers. Bannon couldn’t stop that, it happened too fast. But he’d accomplished what mattered: preventing the detailed leadership-glorification speech that would have made the celebration about individual heroics instead of team achievement. The crew could acknowledge Bannon’s role briefly. They couldn’t make a speech positioning him as the hero who deserved special recognition.

The lesson is clear throughout. Bannon physically stopped individual glorification. Explicitly prohibited “soft soap” about leadership. Threatened physical removal if James tried again. Protected team celebration from becoming leadership worship. And the result was a victory dinner that celebrated achievement without making it about one person being special.

Why This Matters More Than Graceful Acceptance

When you accept public praise for team achievement, you’re endorsing a false narrative about what produced success. You’re letting people believe leadership mattered most when actually systematic execution by hundreds of ordinary people did. You’re positioning yourself as special when you should be redirecting focus to the crew who did the actual work.

Think about what James was building toward. A speech about Bannon’s personal qualities. Stories that would position Bannon as uniquely capable. Details that would make the crew see their superintendent as exceptional rather than as someone who built systems that let them execute exceptionally. The speech would have been eloquent. The crew would have applauded. And the message would have been that this project succeeded because Bannon was special, not because the team was systematic.

When you let that happen—when you sit there accepting recognition for team achievement—you’re teaching your crew that success comes from extraordinary leaders instead of ordinary people executing well. You’re reinforcing the belief that they need special superintendents to succeed instead of building confidence that systematic teams can deliver without heroes. You’re creating dependency on leadership instead of building independent capability.

Your crew beat a blizzard. They adapted when plans failed. They maintained momentum after crisis. They anticipated attacks. They executed through exhaustion. They did the work that produced the results. And if you let someone make a speech about YOUR leadership being the reason they succeeded, you’ve just told them their execution mattered less than your direction. You’ve stolen their achievement and claimed it as yours.

The principle extends everywhere beyond formal celebrations. The client presentation where someone credits your leadership, and you redirect to your foremen by name. The company meeting where they want to feature your photo, and you insist on a crew photo instead. The award ceremony recognizing individual achievement, and you physically bring your key people on stage with you. Every time you deflect credit back to the team who executed, you’re teaching people that systematic execution matters more than individual leadership. If your project needs superintendent coaching, project support, or leadership development to build leaders who deflect credit instead of accepting it, Elevate Construction can help your field teams stabilize, schedule, and flow.

Watch for These Signals You’re Accepting Credit You Shouldn’t

Your project culture is vulnerable to individual glorification when you see these patterns:

• Celebration speeches focus more on leadership decisions than crew execution, revealing the narrative positions superintendent as hero instead of team as achievers
• Leaders accept recognition gracefully without redirecting credit, showing they’re comfortable being positioned as special rather than as system-builders
• Stories about project success center on superintendent moments rather than crew capabilities, indicating celebration is about individual heroics instead of team achievement
• Crew members describe success as “we had a great leader” rather than “we executed well,” revealing they’ve been taught to credit leadership over their own systematic work

The Framework: Celebrating Achievement Without Soft Soap

The goal isn’t refusing all recognition or pretending leadership doesn’t matter. It’s understanding that accepting public praise for team achievement undermines the culture you’re building. That individual glorification teaches wrong lessons about what produces results. That “no soft soap” protects team focus better than eloquent speeches about leadership.

Stop praise speeches before they start, not after they finish. Bannon didn’t wait for James to complete his speech and then deflect credit gracefully afterward. He physically stopped James before the words left his mouth. Once the speech happens, the damage is done, the crew has heard the narrative positioning leadership as special. Stop it immediately. Interrupt. Make it awkward if necessary. Prevent the speech from occurring, don’t just respond to it politely after it’s delivered.

Make “no soft soap” an explicit rule, not an implied preference. Don’t hint that you’d prefer less recognition. State clearly: “We aren’t handing out any soft soap at this dinner.” Make it a boundary. Explain it’s not about your comfort—it’s about protecting team culture from narratives that credit leadership over execution. When the rule is explicit, people know you mean it and enforcement doesn’t require repeated explanation.

Redirect focus to crew execution specifically, not just generically. Don’t say “the team did great work.” Name people. Describe specific execution moments. Tell stories about how the foreman adapted when the first solution failed. How the crew maintained pace after the crisis. How individuals anticipated problems and solved them. Make celebration about specific systematic execution, not generic “great team” acknowledgment that still positions leadership as the important factor.

Physically enforce boundaries when people try to circumvent them. James agreed to stop talking about Bannon, then tried to sneak in praise another way. Bannon threatened to throw him out the window. The threat was humorous but real. When people try to work around “no soft soap” rules, enforcement needs to be immediate and firm. Not mean, not angry, but clear that the boundary is real and violation has consequences.

Accept brief acknowledgment but stop detailed glorification. Bannon couldn’t prevent the three cheers, they happened too fast. He didn’t try to stop brief recognition. He stopped the detailed speech that would have made celebration about individual leadership instead of team achievement. The difference matters. Brief acknowledgment: acceptable. Extended speeches positioning you as hero: prohibited. Know where the line is and enforce it clearly.

The Practical Path Forward

Here’s how this works in practice. Your project just succeeded. Celebration is happening. Someone wants to make a speech praising your leadership. You need to decide whether to let it happen gracefully or stop it before it starts.

First question: is this brief acknowledgment or detailed glorification? “Thanks to our superintendent’s leadership” said quickly in passing—that’s acknowledgment you can let go. “I want to tell you a story about our superintendent that shows what kind of leader he is”, that’s detailed glorification building to extended speech. Stop the latter immediately. The former is acceptable. The latter undermines team culture by making celebration about individual heroics.

Second question: what narrative is being created? Listen to the first few words. If they’re building toward “the superintendent is special and that’s why we succeeded,” interrupt immediately. If they’re describing “we executed systematically and here’s how,” let them continue. The narrative matters more than the duration. Short speech with wrong narrative does more damage than long speech with right narrative. Listen for what story is being told, not just how long it takes.

Third question: can you redirect without accepting? Sometimes you can’t stop recognition completely, it’s happening too fast or interrupting would create bigger problems than allowing it. But you can redirect during your response. Someone praises your leadership? Stand up immediately and name three foremen who executed brilliantly. Client credits your vision? Redirect to your crew’s adaptation when plans failed. You can’t control what others say, but you control what you say in response, use it to shift focus back to team execution.

Stop it physically if words don’t work. Bannon didn’t politely ask James to stop. He grabbed his shoulders and shoved him into the chair. Physical intervention seems extreme until you recognize what’s at stake—team culture being undermined by individual glorification. If someone won’t stop when asked, physical intervention (grabbing their shoulder, standing between them and the microphone, literally removing them from the platform) protects culture better than allowing the speech to continue.

Make your rule clear early in celebration. Don’t wait until someone starts praising you to announce “no soft soap.” Say it at the beginning: “This celebration is about team execution. No speeches about individual leadership. We’re here to acknowledge systematic work, not glorify heroes.” When the rule is stated upfront, enforcement is easier because everyone knows stopping praise speeches isn’t personal, it’s protecting culture you explained matters from the start.

Why This Protects Projects and People

We’re not just celebrating achievements. We’re teaching lessons about what produces results. And whether we celebrate through individual glorification or team execution determines whether crews learn to depend on hero leaders or build systematic capability themselves.

When you accept public praise for team achievement, you’re teaching your crew that leadership produced the results. That they succeeded because you’re special, not because they executed systematically. That future success requires finding another hero superintendent instead of building their own capability. You’re creating dependency on individual leadership instead of confidence in systematic team execution.

When you deflect credit to crew execution, you’re teaching different lessons. That systematic work produces results, not individual heroics. That ordinary people executing well matter more than extraordinary leaders directing them. That they can succeed again by building systems and executing them, not by waiting for a special leader to show them how. You’re building independent capability instead of leadership dependency.

This protects families by building crews who can execute systematically without requiring hero leadership. Projects that depend on extraordinary superintendents fail when those superintendents leave. Projects built on systematic team execution continue succeeding because capability lives in the crew, not in one person. Sustainable success protects jobs. Jobs protect families. Deflecting credit builds sustainability by teaching teams they don’t need heroes, they need systems and execution.

Respect for people means letting them own their achievements instead of stealing credit for their work. It means positioning them as the achievers instead of accepting recognition for their execution. It means building their confidence in systematic capability instead of their dependency on your leadership. It means “no soft soap” about how special you are, and detailed acknowledgment of how systematically they executed.

The Challenge in Front of You

You can let the praise happen. You can sit there looking humble while someone tells stories about your leadership. You can accept recognition gracefully. You can thank them for the kind words. You can let individual glorification replace team celebration. You can teach your crew that leadership mattered most.

Or you can stop it before it starts. You can physically interrupt the speech. You can establish “no soft soap” as explicit rule. You can redirect every word of credit back to crew execution. You can make celebration about systematic team achievement instead of individual leadership. You can teach your crew they succeeded because they executed well, not because you’re special.

The projects that build the strongest teams after impossible achievements aren’t led by superintendents who accept public praise. They’re led by people who understand that deflecting credit builds stronger culture than graceful acceptance. Who recognize that “no soft soap” protects team focus better than eloquent leadership speeches. Who know that the strongest teams are built by leaders who refuse to be positioned as heroes.

Your delegate is making a speech. He’s building toward stories about your leadership. The crew is waiting to hear how great you are. You can let it happen and teach them that success came from you being special. Or you can grab his shoulders, shove him into the chair, and tell everyone: “We aren’t handing out any soft soap at this dinner.”

Bannon stopped the speech physically. James tried again. Bannon threatened to throw him out the window. The crew gave three cheers anyway, but the detailed glorification speech never happened. The celebration stayed focused on team achievement instead of individual heroics. And the culture remained: systematic execution matters more than leadership glory. Stop the soft soap. Deflect the credit. Celebrate the team.

On we go.

Frequently Asked Questions

Isn’t refusing recognition when your crew wants to honor you insulting to them?

Your crew doesn’t need to honor you, they need to own their achievement. When you stop praise speeches, you’re not rejecting their appreciation. You’re redirecting it from individual leadership to team execution. Bannon didn’t say “don’t celebrate.” He said “don’t make soft soap speeches about me.” The celebration continued. The focus shifted from leadership glory to team achievement. That’s not insulting—that’s protecting the real story about who did the work.

What if the client or owner is the one praising your leadership publicly?

Redirect immediately during your response. Client says “This project succeeded because of your leadership”? Stand and reply: “This project succeeded because my foremen adapted when plans failed, my crews maintained momentum through crisis, and my team executed systematically under pressure. Let me name some people who made it happen.” You can’t control the client’s narrative, but you control yours. Use your response to shift focus back to team execution every time.

How do you distinguish between appropriate acknowledgment and damaging glorification?

Duration and narrative. Brief acknowledgment: “Thanks to our superintendent” in passing while describing team achievement. That’s acceptable. Detailed glorification: Extended speech about superintendent’s qualities, decisions, personal sacrifices that positions leadership as the critical success factor. That undermines culture. The test: is the speech teaching “we succeeded because leadership was special” or “we succeeded because execution was systematic”? Stop the former. Allow the latter.

Don’t teams sometimes genuinely succeed because of exceptional leadership?

Even when leadership decisions matter significantly, accepting public praise for them teaches wrong lessons. Your crew learns to credit leadership over their execution. Future teams learn to wait for hero leaders instead of building systematic capability. Better outcome: redirect to the crew who executed your decisions well. “I made calls, but they did the hard work of making those calls succeed through systematic execution.” Build culture that values execution over direction, even when direction mattered.

What if stopping the praise speech creates an awkward moment that ruins the celebration?

The awkward moment protecting team culture is better than the smooth speech undermining it. Bannon created awkwardness, grabbed James’s shoulders, shoved him into chair, threatened to throw him out the window. The room laughed, but the message was clear: no individual glorification. Momentary awkwardness protecting culture beats eloquent speeches teaching wrong lessons about what produces results. Your celebration survives brief awkwardness. Your culture doesn’t survive repeated leadership glorification.