You’re Not Declaring Breakdowns (And It’s Destroying Your Results)

Here’s the uncomfortable truth about why your projects struggle. You’re not declaring breakdowns. You’re not telling the hard truth when you see waste, defects, or confusion. And that silence is costing you quality, schedule, and team performance. Because teams that fix problems faster win. And you can’t fix problems you won’t acknowledge out loud.

Think about the difference between Pixar and Disney movies during a specific period. Disney was producing garbage. Home on the Range was a B-movie with poor animation, weak story, and mediocre humor. It flopped at the box office. Disney lost money on multiple films during that era because something in their process was broken. Then they brought in Pixar to help figure out what was wrong.

What Pixar revealed changed everything. The first review sessions at Pixar were brutal. Teams would present their characters, plot, animation, and message, and the review team would tear everything apart. Script writers and artists left those meetings dejected, knowing they’d have to go back to the drawing board. But that first critical review was key to getting it right. Because Pixar movies are fantastic. Visually stunning. Emotionally moving. Great plot twists. They draw you in and leave you feeling changed. And that excellence requires declaring breakdowns relentlessly, even when it’s hard.

The Pain of Silence That Destroys Quality

You’ve experienced this pattern. Someone on your team sees a problem. They notice waste, confusion, a defect being passed along. And they say nothing. Maybe they’re afraid of looking difficult. Maybe they think someone else will mention it. Maybe they’ve been trained their whole lives to shut up unless called on. So the problem continues. The defect gets passed to the customer. The waste compounds. And weeks later when it becomes a crisis, everyone wonders why nobody spoke up earlier when it would have been easier to fix.

That’s what was happening at Disney before Pixar’s intervention. Script writers and artists would fall in love with their characters. They’d brainstorm internally and head down a direction. If someone made a comment, they’d either be too attached to change it or nobody would speak up at all. And that silence created mediocre movies because problems weren’t surfaced and addressed when they were small and fixable.

The same dynamic destroys construction projects. We see disconnects with the team. We notice violations of culture or core values. We observe waste that needs fixing. We watch defects being passed along. We feel disrespected or confused. And we say nothing. Because speaking up feels risky or uncomfortable or like making a big deal out of something small. So we let it go. And the problem grows until it becomes a crisis that damages schedule, budget, relationships, or safety.

The System Trains Us Into Silence

Here’s what I want you to understand. Our entire culture trains us not to speak up. In school, you had to raise your hand and be quiet. If you disagreed with a teacher, they’d gripe back at you. You learned that keeping your head down and not making waves was safer than pointing out problems. And that programming follows you into the workplace where speaking up about breakdowns feels dangerous.

The construction industry amplifies this. We value getting along over healthy conflict. We promote people who don’t rock the boat. We punish or sideline those who constantly point out problems. And we create cultures where people hide issues instead of declaring them because they’ve learned that surfacing problems makes them look like complainers or troublemakers.

But here’s the truth that Pixar proved and that Lean construction and Integrated Project Delivery demonstrate repeatedly: teams that declare breakdowns relentlessly produce better results than teams that stay silent to avoid discomfort. Because problems are not a problem. Not recognizing that we have problems is the problem. And teams that see and fix problems faster win consistently.

I was consulting with an organization recently that started using a problem bowl in meetings. They put it in the middle of the room and invited everyone to write breakdowns on sticky notes and throw them in the bowl. Then during the agenda, someone would pull them out and the team would discuss them. The first week, not much happened. The person who wrote the problem maybe spoke up. The second week, people put in more pertinent problems and waited for others to speak up. Conversation started flowing. And they were culturally conditioning everyone to declare breakdowns without fear.

That’s the shift required. From silence to declaration. From hiding problems to surfacing them. From individual ownership to team responsibility. Because the breakthrough insight is this: problems belong to the group, not the person. When you declare a breakdown, you’re not attacking someone. You’re identifying something the team needs to address together.

The Bowl Technique That Removes Emotion

Let me teach you a technique that transforms difficult conversations. A trusted mentor taught me this. When you’re having a conversation about a problem, imagine that the problem is sitting in a bowl on the desk between you. You’re both looking at the problem in the bowl together. You’re not talking at each other with the problem attached to one person. You’re talking at the problem together with the emotion detached.

I’ve literally done this with people during emotional discussions. I’ve said, “Let’s imagine right here in my left hand there’s a bowl and the problem is in here. We’re talking at the problem together. We’re not talking at each other and emotionally connecting these things to each other.” And it works. We get through it without anger, without defensiveness, without making it personal.

This same principle applies to declaring breakdowns in team settings. The breakdown isn’t owned by the person who caused it or the person who noticed it. It’s owned by the team. When someone declares a breakdown, they’re not blaming anyone. They’re pointing the team’s attention to something that needs addressing. That shift from personal to collective makes speaking up safer and problem-solving more effective.

Consider calling problems “opportunities” if that helps your culture embrace them. The language matters less than the behavior. What matters is creating an environment where people feel authorized to speak up, where declaring breakdowns is praised instead of punished, and where the team stops and pays attention when someone identifies an issue.

When and How to Declare Breakdowns

Here’s when you should declare a breakdown, whether big or small. When you see a disconnect with the team. When you notice a violation of culture or core values. When you observe waste that needs fixing. When something passes a defect along to the customer. When something disrespects people. When there’s unhealthy variation and someone is confused. When results aren’t what you want them to be for the project.

Don’t get into the habit of thinking breakdowns have to be grandiose to deserve attention. Small problems become big problems when ignored. Declare them when they’re small and easy to fix. And when somebody declares a breakdown, the team must stop and pay attention. This is critical. How many times does someone say something’s wrong and we blow right past it? We can’t do that anymore.

Here’s an example from a recent organization. We were asking people to wear masks while presenting. Some people agreed immediately. Others argued about logic and science and whether it was necessary. I stopped them and said this isn’t about arguing logic on safety. If somebody doesn’t feel safe, we’re considerate enough to stop and listen and pay attention. If someone asks me to wear a mask while speaking and they can hear me fine through it, why wouldn’t I respect their concern? It’s not about winning a debate. It’s about caring enough to respond when someone declares a breakdown around safety or respect.

Here’s how you create that culture practically:

• Praise people when they bring up problems instead of making them feel like complainers • Give everyone explicit authority to stand up and speak up when they see breakdowns • De-incentivize hiding problems with consequences for people who know about issues and stay silent • Shorten the timing between when someone notices a breakdown and when they declare it • Stop and pay attention every time someone declares a breakdown, especially around safety or respect

These aren’t suggestions. These are the disciplines that separate teams who improve continuously from teams who stumble through the same problems repeatedly because nobody feels safe speaking up.

Building a Problem-Solving Culture

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. We work with builders who understand that declaring breakdowns isn’t negative or difficult. It’s the foundation of continuous improvement and the only way teams produce exceptional results consistently.

The current condition is we don’t speak up. We make crap work. Sometimes we push defects onto customers. People don’t feel authorized to speak up. And we reinforce the disconnected culture where problems hide until they become crises. That pattern destroys quality, damages relationships, and wastes resources that could be used to create value.

The challenge is to make speaking up a cultural norm. Make Lean improvements continuously. Become a problem-solving, opportunity-obtaining, continuously improving culture. And if you accumulate enough declared breakdowns that you can’t address them all immediately, put them on a scrum board as a product owner and let the team autonomously fix those opportunities as long as they’re not urgent line items requiring immediate attention.

This is the Lean and IPD mindset that transforms teams. Declaring breakdowns becomes normal instead of threatening. Problems belong to the group instead of individuals. Speaking up gets praised instead of punished. And teams fix issues faster because they surface them immediately instead of hiding them until they explode.

Think about the Pixar example again. Those brutal first reviews where everything gets torn apart create better movies than Disney’s approach where people fell in love with their work and couldn’t receive critical feedback. The discomfort of declaring breakdowns early produces excellence. The comfort of staying silent produces mediocrity.

The Challenge: Declare One Breakdown This Week

So here’s my challenge to you. This week, declare a breakdown. When you see waste, confusion, a defect, disrespect, or results that aren’t what you want, speak up. Say out loud, “I’m declaring a breakdown here.” Explain what you see. Invite the team to address it together. And watch what happens when problems get surfaced and solved instead of hidden and ignored.

Introduce the language of declaring breakdowns to your team. Explain that problems belong to the group, not individuals. Create systems like the problem bowl that make speaking up easier and less personal. Praise people when they surface issues. And commit as a team to stop and pay attention every time someone declares a breakdown.

We really have to have eyes to see. We need to make sure we all have license to speak up. We need to culturally reinforce fixing problems and get that shift started. The teams that fix problems faster win. And you can’t fix what you won’t declare out loud.

As W. Edwards Deming said, “It is not necessary to change. Survival is not mandatory.” Declaring breakdowns is how you change instead of just surviving. It’s how you build Pixar-quality results instead of Disney’s B-movies. Start speaking up.

On we go.

Frequently Asked Questions

Won’t declaring breakdowns constantly make me look like a complainer or troublemaker?

Only in unhealthy cultures that value comfort over improvement. In healthy cultures, people who surface problems early are valued as contributors who help the team win. Frame breakdowns as opportunities and focus on solutions, not just complaints. The key is speaking up constructively, not just criticizing without offering help.

How do I know if a problem is big enough to declare a breakdown or if I should just let it go?

Don’t filter based on size. Small problems become big problems when ignored. If you notice waste, confusion, defects, or disrespect, declare it regardless of scale. The team can decide together if it needs immediate attention or can be added to a list for later. But surfacing it prevents it from hiding and growing.

What if my team culture punishes people for speaking up about problems?

Then you need leadership support to change the culture or you need to find a healthier team. You can model the behavior by declaring breakdowns respectfully and inviting solutions. But if leadership consistently punishes problem-surfacing, the culture won’t change without intervention from above or personnel changes.

How do I declare a breakdown without making it personal or attacking someone?

Use the bowl technique. Frame the problem as something the team is looking at together, not something attached to an individual. Say “I’m noticing a breakdown with [specific issue]” rather than “you caused a problem.” Focus on the system or process, not the person. Invite collaborative problem-solving.

What if people start declaring every tiny thing and we waste time in meetings addressing non-issues?

That’s a facilitation problem, not a problem with declaring breakdowns. Use a scrum board or problem list for non-urgent items. Address urgent breakdowns immediately. Batch-process smaller issues. Teach people to distinguish between breakdowns needing immediate attention and those that can be scheduled for later resolution.