Calumet “K” Series Chapter 15

The Talking Problem: Why Loud Proclamations About What You’ll Do Cost More Than Quiet Execution of What You’re Doing

Your competitors are making noise. They’re telling everyone they’ve already won. They’re claiming advantages they think are decisive. They’re talking to anyone who’ll listen about their superior position. They’re giving interviews, making proclamations, broadcasting confidence that sounds impressive to people who don’t know what actually matters.

And you’re watching them talk while you’re executing. Building the systems they claim don’t exist. Mobilizing the resources they claim aren’t available. Solving the problems they claim are unsolvable. Doing the work while they’re explaining why they’ve already won before doing it.

Here’s what most superintendents do. They join the talking. They make counter-proclamations. They defend their position publicly. They explain their advantages. They broadcast their confidence. They match noise with noise, thinking that silence means weakness and talking means strength. They believe that if competitors are talking about their advantages, you need to talk about yours or people will think the competitors are right.

And while both sides are talking, neither side is executing at maximum effectiveness because talking about what you’ll do costs attention and energy that should go into actually doing it. The fight should be won through systematic execution, not through who makes the most convincing proclamations before the work is done.

The projects that succeed despite confident competitors aren’t the ones that make the loudest claims. They’re the ones that stay quiet while building systematic capability that makes claims unnecessary. That let execution speak instead of proclamations. That understand talking for publication undermines the focus required for actually delivering what talk promises.

The Problem Every Superintendent Creates

Walk any competitive situation and watch what happens when one side starts making public proclamations. They announce their advantages. They broadcast their confidence. They claim victory before work is complete. They talk to anyone who’ll listen about why they’ll win. And the other side feels pressure to respond with their own proclamations, their own claims, their own public confidence.

Both sides start spending energy on messaging instead of execution. Both start caring what the public thinks instead of just doing the work. Both shift focus from actual capability to perceived capability, from substance to style, from systematic execution to promotional noise. And the project that should be won through better work gets complicated by who tells better stories about the work before it’s done.

Most superintendents don’t recognize that talking about advantages is different from having them. That claiming you’ll win is different from doing the work that produces victory. That public proclamations consume attention that should go to systematic execution. They think staying quiet while competitors talk makes them look weak, so they join the noise instead of just doing the work.

The pattern shows up everywhere beyond direct competition. Subcontractors making bold claims about their capabilities before proving them. Suppliers broadcasting confidence about delivery schedules they haven’t tested. Project teams announcing they’ll finish early before building the systems that would make early finish possible. Everyone talking about what they’ll do instead of quietly doing it.

Think about what talking for publication creates. When you make public proclamations about your advantages or your confidence or your inevitable victory, you’re committing to a narrative. Now you need to defend that narrative. You need to explain when reality doesn’t match proclamations. You need to spend energy managing perceptions instead of just executing. You’ve created a second job—maintaining your public image—that competes with your actual job of delivering results.

Your competitors are talking about how they’ve already won. You could join the conversation and explain why they’re wrong. Or you could ignore them completely and focus entirely on systematic execution that makes their talk irrelevant. One approach splits your attention between talking and doing. The other focuses completely on doing and lets results speak.

The Failure Pattern Nobody Recognizes

This isn’t about refusing to communicate or hiding what you’re doing. This is about understanding that talking for publication—making proclamations to impress audiences instead of communicating to execute—consumes resources that should go to actual delivery. That systematic capability defeats promotional noise because substance beats style when the deadline arrives and work needs to be done.

Construction culture sometimes confuses confidence with competence. The superintendent who talks boldly about impossible deadlines. The team that broadcasts certainty about finishing early. The company that makes public proclamations about superior capabilities. These can be signs of genuine confidence backed by systematic execution. Or they can be promotional noise covering lack of actual capability.

So superintendents make proclamations thinking it demonstrates confidence. They broadcast advantages thinking it establishes credibility. They talk for publication thinking silence means weakness. They never recognize that every minute spent on promotional messaging is a minute not spent on systematic execution. They don’t see that competitors making loud claims are revealing they care more about looking capable than being capable.

The story always goes the same way. Confident competitors make bold public claims. They announce they’ve already won. They broadcast advantages. They talk to reporters. They give interviews explaining their inevitable victory. And quiet competitors just keep building systematic capability—training agents, establishing alliances, creating infrastructure, mobilizing resources—without saying a word publicly. When the deadline arrives, systematic capability delivers while promotional noise produces nothing.

Nobody teaches superintendents that the most dangerous competitors are the quiet ones. That people making loud proclamations are usually compensating for lack of actual capability. That systematic execution speaks louder than promotional noise once the work needs to be done. That staying quiet while building capability is strength, not weakness.

A Story From the Field About Execution Versus Talk

In a major wheat market fight, a group of young speculators called “the clique” were battling an established operator named Page. The clique represented apparently unlimited capital. They were buying wheat aggressively. They believed they knew every bushel available in the country. And they were making bold public proclamations about their inevitable victory.

The story describes their approach explicitly: “They were young, eager, overstrung, flushed with the prospect of success. They were talking for publication. They believed they knew of every bushel in the country that was to be had, and they allowed themselves to say that they had already bought more than this.”

Talking for publication. Making claims designed to impress audiences. Broadcasting confidence before delivering results. Proclaiming victory before winning. The clique was focused on perception—how they looked to the public, what newspapers said about them, whether people believed they’d already won. They were fighting through promotional noise.

Page was fighting differently. He wasn’t talking. He wasn’t making proclamations. He wasn’t explaining his advantages to reporters. He was quietly building systematic capability that would deliver what talk promised but couldn’t produce.

The story contrasts their approaches directly: “The young men of the clique had forgotten that Page had trained agents in every part of the world, that he had alliances with great railroads and steamer lines, that he had a weather bureau and a system of crop reports that outdid those of the United States government, that he could command more money than two such cliques, and most important of all, that he did not talk for publication.”

Page had systematic capability. Trained agents everywhere. Alliances with railroads and steamer lines. Superior weather and crop intelligence. Command of more capital than competitors could imagine. And he kept all of it quiet. No public proclamations. No talking for publication. No broadcasting advantages. Just systematic execution of capability the clique didn’t know existed because they were too busy talking to build actual systems.

The contrast is devastating: “The young speculators were matching their wits against a great machine.” Wits versus machine. Talk versus systematic execution. Promotional noise versus actual capability. Individual cleverness versus organizational infrastructure. And the machine wins because systematic capability delivers what individual cleverness just talks about.

At Page’s construction site, reporters and newspaper illustrators showed up. They wanted to interview Bannon about the impossible deadline. They took photographs. They wrote elaborate stories about his skill. They created public narratives about whether he’d finish on time. Bannon drove them off the job. He didn’t talk to them. He didn’t explain his approach. He didn’t make proclamations about finishing. He just kept executing.

The story notes the effect of public attention on workers explicitly: “For now, they were in the public eye, and they felt a soldier’s feel, when after long months of drill and discipline, they are led to the charge.” Public scrutiny made them perform BETTER, not worse. They felt like soldiers who’d trained hard being finally called to prove what they’d built. They weren’t talking about their advantages—they were demonstrating them through systematic execution.

When ice blocked Duluth harbor and threatened to prevent wheat delivery, Page’s agents blasted channels through ice with dynamite. They mobilized resources the clique didn’t know existed. They executed solutions the clique couldn’t imagine because they’d built systematic capability while the clique was busy talking about advantages they didn’t actually have.

The lesson is clear throughout. The clique talked for publication and lost. Page built systematic capability quietly and won. Promotional noise looked impressive temporarily. Systematic execution delivered results permanently. Talking about what you’ll do consumes resources that should go into actually doing it.

Why This Matters More Than Public Perception

When you talk for publication instead of executing systematically, you’re fighting perception battles instead of capability battles. You’re trying to convince people you’ll win instead of building systems that produce victory. You’re spending attention on how things look instead of how things work. And perception without substance collapses when deadlines arrive and work needs to be done.

Think about what happens when you make bold public proclamations before delivering. You claim you’ll finish early. Now you’re committed to defending that claim. When obstacles appear, you need to explain them. When schedule slips, you need to spin it. When reality doesn’t match proclamations, you need to manage perceptions. You’ve created a second job, maintaining your public narrative—that competes with your actual job of delivering results.

Your competitors make loud claims about their advantages. You could respond with counter-claims about yours. Now both of you are fighting narrative battles instead of executing. Both spending energy on messaging instead of building capability. Both caring more about what audiences think than what work requires. Both distracted from systematic execution by the noise you’re both creating.

Or you could ignore their noise completely. Let them talk. Let them make proclamations. Let them broadcast confidence. While they’re talking, you’re building. Training people. Establishing systems. Creating infrastructure. Mobilizing resources. Doing the actual work that produces capability instead of just talking about capability you claim to have.

When the deadline arrives, systematic capability delivers. Talking for publication produces nothing except perceptions that collapse when work needs to be done. The clique talked for publication and lost when Page delivered wheat they claimed didn’t exist. Page built systematic capability quietly and won when the clique’s proclamations proved to be noise without substance.

The principle extends everywhere beyond market competition. Subcontractors who make bold claims about capabilities versus subcontractors who quietly build competence. Suppliers who broadcast confidence about unrealistic deliveries versus suppliers who systematically build reliable logistics. Teams who announce they’ll finish early versus teams who build systems that actually produce early finish. Talk versus execution. Noise versus substance. Proclamations versus systematic capability.

Watch for These Signals You’re Talking Instead of Executing

Your project is vulnerable to talking-for-publication instead of systematic execution when you see these patterns:

• Leadership spends more time explaining advantages to audiences than building actual capability, revealing they care more about perception than substance
• Bold public proclamations about what you’ll accomplish come before building the systems required to accomplish them, putting narrative ahead of execution
• Energy goes into defending claims when reality doesn’t match proclamations instead of just executing without making claims requiring defense
• Competitive focus is on what others are saying rather than what you’re building, showing you’re fighting narrative battles instead of capability battles

The Framework: Building Systematic Capability Quietly

The goal isn’t refusing all communication or hiding what you’re doing. It’s understanding that talking for publication, making proclamations to impress audiences instead of communicating to execute, consumes resources that should go to systematic execution. That substance beats style when deadlines arrive and work needs to be done.

Distinguish between communicating to execute and talking for publication. Communicating to execute means sharing information needed for coordination: “We need these resources by this date.” Talking for publication means making proclamations to impress audiences: “We’re confident we’ll finish ahead of schedule.” One enables execution. The other consumes attention that should go to execution. Communicate constantly to coordinate. Talk for publication never.

Recognize that competitors making loud proclamations are revealing vulnerability, not strength. When competitors broadcast confidence before delivering, they’re showing they care more about perception than execution. When they claim advantages publicly, they’re trying to convince audiences (and maybe themselves) rather than just having the advantages. Quiet competitors building systematic capability are more dangerous than loud competitors making proclamations.

Focus attention entirely on systematic execution instead of splitting it between execution and perception management. Page didn’t waste energy defending his approach or explaining his advantages or broadcasting confidence. He spent 100% of attention on training agents, establishing alliances, building infrastructure, mobilizing resources. The clique split attention between talking for publication and actual execution. That split cost them when systematic capability mattered. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Let results speak instead of making proclamations that require defending. Don’t claim you’ll finish early—just build the systems that produce early finish and let the actual early finish speak. Don’t broadcast advantages—just have the advantages and let delivery demonstrate them. Don’t make confident proclamations—just execute systematically and let results prove confidence was justified. Results speak louder than proclamations and don’t require defending when reality doesn’t match claims.

Build systematic capability while competitors talk about theirs. When competitors are making noise, that’s your opportunity to build substance while they’re distracted. Train your people while they’re giving interviews. Establish your systems while they’re making proclamations. Create your infrastructure while they’re broadcasting confidence. Do the actual work of building capability while they’re talking about capability they claim to have.

The Practical Path Forward

Here’s how this works in practice. Your competitors are making bold public proclamations. They’re claiming they’ve already won. They’re talking to reporters. They’re broadcasting confidence. You need to decide whether to respond with your own proclamations or ignore them and focus entirely on systematic execution.

First question: are they talking because they have substance or because they lack it? Strong competitors with actual capability don’t need to broadcast it, results demonstrate it. Weak competitors without real capability need to talk loudly to compensate for lack of substance. When competitors make bold proclamations before delivering, assume they’re compensating for weakness, not demonstrating strength. Their noise is your opportunity to build substance while they’re distracted.

Second question: does responding to their claims help you execute better or just distract you from execution? If making counter-proclamations would improve your capability somehow, consider it. But usually responding to competitive noise just creates your own distraction from systematic execution. Let them talk. Let them make claims. Let them broadcast confidence. You build capability while they’re busy talking about theirs.

Third question: what would systematic capability look like versus what would impressive talk look like? Systematic capability means trained people, established processes, proven systems, mobilized resources, tested infrastructure. Impressive talk means confident claims, bold proclamations, public narratives about advantages. Build the former. Ignore the latter. When deadline arrives, capability delivers and talk produces nothing.

Stop talking and start building when competitors are making noise. Their proclamations are your opportunity. While they’re distracted by perception management, you’re building systematic capability. While they’re explaining advantages, you’re creating them. While they’re broadcasting confidence, you’re building competence that makes confidence unnecessary. Use their noise as cover for your systematic execution.

Communicate what’s needed for execution without proclaiming what’s designed for perception. Tell your team what they need to know: “Here are the resources we’re mobilizing.” Don’t tell audiences what they don’t: “We’re confident we’ve already won.” Information that enables coordination helps execution. Proclamations that impress audiences consume attention without adding capability. Share the former. Skip the latter completely.

Why This Protects Projects and People

We’re not just building projects. We’re protecting jobs, families, and futures from competitors who talk loudly while we execute systematically. And whether you fight through proclamations or through capability determines whether perception or substance wins when deadlines arrive.

When you talk for publication, you’re creating commitments to narratives that reality might not support. You claimed you’d finish early. Reality produced delays. Now you’re explaining instead of just executing. You’re managing perceptions instead of building capability. You’re defending claims instead of doing work. The talk created a second job that competes with your actual job and consumes resources that should go to delivery.

When you build systematic capability quietly, you’re avoiding narrative commitments that create distraction. You didn’t claim you’d finish early—you just built systems that might produce it. Reality produces delays? You adapt without explaining because you never made claims requiring defense. You keep 100% focus on execution because you’re not managing perceptions about proclamations you never made.

This protects families by protecting projects from the distraction that talking for publication creates. Projects that split attention between execution and perception management fail more often than projects that focus entirely on execution. Projects that fail cost jobs. Jobs lost hurt families. Systematic execution protects families by protecting the focus required to deliver results that talking about results can’t produce.

Respect for people means building actual capability that produces results instead of making proclamations that look impressive but don’t deliver. It means focusing attention on work that matters instead of perception management that consumes resources. It means letting systematic execution demonstrate competence instead of requiring people to defend claims about competence they haven’t yet proven.

The Challenge in Front of You

You can talk for publication. You can make bold proclamations about your advantages. You can broadcast confidence before delivering results. You can explain why you’ll win before doing the work. You can split attention between execution and perception management. You can fight narrative battles instead of capability battles.

Or you can build systematic capability quietly. You can train people while competitors give interviews. You can establish systems while they make proclamations. You can create infrastructure while they broadcast confidence. You can focus 100% on execution while they split attention between talking and doing. You can let results speak instead of making claims requiring defense.

The projects that succeed despite confident competitors aren’t the ones that make the loudest claims. They’re led by people who understand that talking for publication consumes resources that should go to systematic execution. Who recognize that competitors making bold proclamations are revealing weakness, not strength. Who know that substance beats style when deadlines arrive and work needs to be done. Who build capability quietly while competitors talk about theirs.

Your competitors are making noise. They’re claiming they’ve already won. They’re talking to reporters about their inevitable victory. They’re broadcasting advantages they think are decisive. Let them talk. While they’re explaining why they’ll win, you’re building the systems that will produce actual victory. While they’re making proclamations, you’re creating capability. While they’re talking for publication, you’re executing systematically.

The clique talked for publication and lost. Page built systematic capability quietly and won. Promotional noise looked impressive until the deadline arrived. Systematic execution delivered results when talk produced nothing. The young speculators matched their wits against a great machine. The machine won because substance beats style every time.

Stop talking. Start building. Let results speak.

On we go.

Frequently Asked Questions

Isn’t staying quiet while competitors make bold claims allowing them to control the narrative?

Controlling narratives doesn’t deliver projects. Systematic execution does. The clique controlled the narrative—newspapers covered their confident proclamations extensively. Page controlled the wheat—he delivered millions of bushels they claimed didn’t exist. When the deadline arrived, narrative control meant nothing and systematic capability meant everything. Let competitors control narratives while you control capability. Results speak louder than proclamations.

How do you build confidence in your team without making public proclamations about capabilities?

Build confidence through demonstrated competence, not proclaimed confidence. Show your team the systems you’re building. Let them see the capability developing. Demonstrate progress through actual work, not through claims about work. “Here’s what we’ve built” creates more real confidence than “here’s what we’ll accomplish.” Confidence based on systematic capability is sustainable. Confidence based on proclamations collapses when reality doesn’t match claims.

What if stakeholders expect public updates about progress and confidence levels?

Communicate progress factually without making proclamations about outcomes. “We’ve completed these milestones. Here’s what’s next.” Not “We’re confident we’ll finish early.” Report what’s been done, not what you claim will be done. Stakeholders respect factual progress updates more than confident proclamations that might not materialize. If they demand proclamations, give the minimum required and focus maximum attention on actual execution.

Don’t bold claims sometimes motivate teams to higher performance?

Internal commitments to teams are different from public proclamations to audiences. Telling your team “We’re going to finish this ahead of schedule” creates internal accountability. Telling reporters “We’re confident we’ll finish early” creates external narrative requiring defense. The former can motivate. The latter distracts. Make internal commitments to your team. Avoid public proclamations to audiences. The difference is who needs the information and why.

How do you know when you’re building real capability versus just avoiding legitimate communication?

Ask: does this communication enable better execution or just create better perception? “We need these resources by this date” enables execution. “We’re the best team in the industry” creates perception. “Here’s our progress to date” informs stakeholders. “We’re confident we’ve already won” manages narratives. If communication improves coordination or provides needed information, it’s legitimate. If it’s designed to impress audiences, it’s talking for publication that consumes resources better spent on execution.