CYA vs. Finding & Fixing Problems

The Problem We Need to Bring to the Surface

Here’s the deal. Every construction project has problems. Every project has roadblocks. Every project has constraints. Every project has things that are not ready, not clear, not coordinated, not installed correctly, not procured, not approved, not staffed, or not communicated.

That is not the problem. The problem is when people hide them. The problem is when the culture teaches people to protect themselves instead of protecting the project. The problem is when project managers, superintendents, project engineers, directors, executives, or anyone on the team spends more energy covering their own backside than finding and fixing what is blocking flow.

That is where projects get hurt. Not because someone found a problem. Not because a roadblock showed up. Not because reality happened. Projects get hurt when the team does not bring reality to the surface fast enough to do something about it. If we want flow, we need transparency. If we want trust, we need problems visible. If we want to protect the field, we need leaders who are obsessed with finding and fixing problems, not hiding them.

The Real Construction Pain

The pain is that too many teams are afraid of problems. They treat a problem like a personal failure. They treat a roadblock like a threat to their reputation. They treat a missed detail like something that must be buried, explained away, or covered with documentation so nobody can blame them later. And when that happens, the project loses.

The field keeps moving without the truth. The team keeps planning without the truth. Leaders make decisions without the truth. Trade partners get impacted by things that should have been surfaced earlier. Foremen inherit roadblocks they did not create. Workers lose flow because someone upstream was more focused on self-protection than system protection. That is not respect for people.

Respect for people means we tell the truth early. Respect for people means we make the work visible. Respect for people means we surface the ugly, the unclear, the late, the broken, the missing, and the risky before it damages the field. Respect for people means we do not let fear create silence. When a problem stays hidden, it grows. When a roadblock stays buried, it spreads. When a team avoids transparency, they trade short-term comfort for long-term chaos.

The Failure Pattern

The failure pattern is easy to spot. Someone says, “We have it under control,” but they cannot show the log. Someone says, “It is not a big deal,” but the field is about to be impacted. Someone says, “I am not sure I am allowed to share that,” when the team needs the information to make a decision. Someone keeps a private list, a private tracker, a private issue, a private risk, or a private problem because they do not want to look bad. That is CYA culture.

CYA culture says, “Protect yourself first.” Lean culture says, “Find the problem and fix the system.” Those two mindsets cannot live together for very long. One will eventually win. If CYA wins, the project becomes defensive. People stop telling the truth. Meetings become performances. Reports become polished versions of reality. The team wastes energy looking good instead of getting better. Problems show up late, usually when they are expensive, emotional, and harder to solve. If problem finding wins, the project becomes honest. People tell the truth early. Roadblocks are visible. Leaders can help. The team can adjust. The system can improve. Flow has a chance.

The System Failed Them, Not the People

The system failed them; they didn’t fail the system. That matters because this topic can get sharp quickly. It is easy to point at someone and say, “They are hiding things.” But Jason Schroeder’s lens is system-first. We do not start by attacking people. We start by asking what environment created the behavior.

Did the company punish people for surfacing bad news? Did leaders react emotionally when problems were brought forward? Did the project culture reward looking good more than telling the truth? Did people learn that transparency gets them in trouble? Did the team confuse accountability with punishment instead of clarity, training, and follow-through?

If people believe problems are a reflection of their worth, they will hide problems. If people believe roadblocks make them look weak, they will hide roadblocks. If people believe leadership wants polished reports instead of reality, they will polish the report. That is a system problem.

A healthy Lean system teaches the opposite. Problems are not shameful. Problems are gold. Problems are signals. Problems tell us where flow is breaking. Problems show us where training is missing, where planning was weak, where make-ready failed, where procurement is late, where logistics are unclear, or where a standard is missing. The only real problem is pretending there are no problems.

A Field Story About CYA

Jason was walking a construction site when someone said something that hit the mark. They wished project managers would worry more about finding and fixing problems than hiding problems and protecting themselves. That comment opened up the whole topic.

Because when you think about it, so much of construction energy gets wasted in CYA. People hide information. They hold back. They delay transparency. They do not want to share finances. They do not want to show the log. They do not want to admit the issue. They do not want help. They do not want the team to see what is really happening. And the sad part is that all of that energy could have gone toward solving the problem.

Imagine if the same effort used to hide a roadblock was used to remove it. Imagine if the same energy used to protect an image was used to protect flow. Imagine if the same time spent building backup excuses was spent building a better plan. That is the leadership shift we need.

We need builders who want the problems. We need leaders who say, “Give me the roadblock. Give me the ugly. Give me the issue. Give me the risk. Give me the thing that is blocking flow so we can solve it together.” That is not negative. That is Lean.

Why It Matters to Flow

Roadblocks are not just annoyances. They are flow blockers. They stop the train. They interrupt handoffs. They force crews into waiting, searching, stacking, rework, and workarounds. They take a beautiful plan and turn it into daily improvisation. In the Takt Production System, flow depends on stable movement through zones. Trades need the right information, materials, tools, equipment, layout, approvals, access, and decisions. If those are missing, the wagon cannot move cleanly. If the wagon cannot move cleanly, the train gets disrupted. If the train gets disrupted, the schedule starts absorbing chaos.

That is why roadblocks must come to the surface early. A roadblock is not something to hide. A roadblock is something to remove. A constraint is something to plan around. Mixing those up creates confusion, but hiding either one creates damage. LeanTakt, Last Planner System, Scrum boards, make-ready planning, daily huddles, and visual controls all exist to make reality visible. They are not paperwork systems. They are transparency systems. They allow the team to see as a group, know as a group, and act as a group. CYA destroys that.

The Real Cost of Hiding Problems

When a team hides problems, the cost is not only schedule. The cost is trust. The cost is safety. The cost is quality. The cost is morale. The cost is the emotional weight people carry home to their families. A hidden roadblock does not stay small. It grows downstream. Missing information becomes delayed work. Delayed work becomes stacking. Stacking becomes unsafe conditions. Unsafe conditions become stress. Stress becomes mistakes. Mistakes become rework. Rework becomes overtime. Overtime becomes burnout. And then people wonder why the project feels heavy. The project feels heavy because the truth is not flowing. Here are some signs that CYA culture is blocking flow:

• People delay sharing bad news until it is unavoidable
• Logs exist privately instead of visually with the team
• Meetings sound positive, but the field feels chaotic
• People spend more time explaining issues than solving them
• Leaders react to problems with blame instead of curiosity

Those are not small signals. They are warnings. They show that the culture is not safe enough, clear enough, or disciplined enough to bring problems to the surface early.

The Lean Pattern: Find and Fix Problems

Lean, in Jason’s lens, is a people-first production system that makes work predictable by designing the environment, not by pushing people harder. It is built on respect for people, visual control, stable workflows, and continuous improvement. That means Lean is not hiding problems. Lean is finding them. One of the most practical ways to think about this is the simple rhythm of improvement. Learn to see waste. Organize your area. Make the work visible. Find what bugs you. Fix what bugs you. Then repeat. That sounds basic, but it is powerful.

When you organize a project visually, problems become easier to see. When you clean and stabilize the environment, abnormalities stand out. When the team can see roadblocks, they can remove them. When the team can see commitments, they can support them. When the team can see the plan, they can improve it. The goal is not to pretend the project is clean. The goal is to make the project honest. That is why transparency is not a soft value. Radical transparency is a production strategy. It allows teams to focus energy where it actually belongs.

Growth Mindset vs. Fixed Mindset

CYA culture is usually tied to a fixed mindset. A fixed mindset says, “If there is a problem, it means I failed.” A fixed mindset says, “If people see the issue, they will think less of me.” A fixed mindset says, “I need to protect my image.” That mindset will suffocate improvement.

A growth mindset says, “Every project has problems.” A growth mindset says, “Problems are the pathway to improvement.” A growth mindset says, “Bring it up early so we can solve it.” A growth mindset says, “This is not about looking perfect. This is about creating flow.” That is the mindset construction needs.

Great builders are not problem-free. Great builders are problem finders. Great builders are problem solvers. Great builders do not hide roadblocks. They hunt them. They pull them out into the open. They put them on a board. They assign ownership. They remove them. Then they improve the system so the same roadblock does not keep returning. That is professional construction leadership.

How Leaders Should Respond to Problems

If leaders want transparency, they must respond correctly when problems are surfaced. This is where culture is created. Not in the mission statement. Not in the poster. Not in the kickoff meeting. Culture is created in the moment someone brings bad news. If the leader reacts with blame, the team learns to hide. If the leader reacts with panic, the team learns to delay. If the leader reacts with sarcasm, the team learns to protect themselves. If the leader reacts with curiosity, clarity, and support, the team learns to surface problems early. That is leadership.

When someone brings a roadblock, the first response should be something like, “Thank you for bringing it up. What do we know? What do we need? Who can help? What is the next action?” That response teaches the team that problems are welcome because solutions are expected. We are not saying there are no standards. We are not saying people can be careless. We are saying stability must exist before accountability. Clarify expectations. Train people. Create the visual system. Follow through. Then hold the standard respectfully. That is how you build trust.

Practical Guidance for Teams

If you want to remove CYA from your project, start by making problems visible in a safe, structured way. Do not rely on side conversations, private notes, hidden logs, or memory. Put roadblocks where the team can see them. Talk about them daily. Assign owners. Track due dates. Follow up. Remove them before they hit the field.

This is where a Scrum board, roadblock log, make-ready process, and daily huddle become powerful. The goal is not to create more admin. The goal is to create visibility that protects flow. Here are practical moves that help shift the culture:

• Ask for roadblocks before asking for progress
• Thank people publicly when they surface problems early
• Put roadblocks on a visible board with owners and dates
• Separate problem finding from blame
• Review repeat problems and fix the system behind them

That is how you teach the team what matters. You are saying, “We do not hide problems here. We find them. We fix them. We learn from them. We move forward.” That is the environment where people can win.

Stop Spending Energy Looking Good

Think about how much energy it takes to hide a problem. You have to manage the story. You have to control who knows. You have to delay the conversation. You have to protect the appearance. You have to create backup explanations. You have to remember what you said. You have to hope nobody finds out before you solve it. That is exhausting. Now imagine spending that energy on solving the problem instead. Bring it up. Name it. Put it on the board. Ask for help. Remove it. Learn from it. Move on. That is lighter. That is faster. That is healthier.

No one should have to be a hero to win. No one should have to hide reality to survive. No one should have to spend their day managing appearances instead of managing flow. If the culture requires people to look perfect, the culture is broken. A real production culture wants the truth.

Connect Back to the Mission

Elevate Construction exists to build remarkable people and systems that build the world. That cannot happen in a CYA culture. Remarkable systems require transparency. Remarkable people require trust. Flow requires honesty. Stability requires visible problems. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

That sentence matters here because stabilization starts with truth. You cannot stabilize what you cannot see. You cannot schedule around what is hidden. You cannot create flow if roadblocks are buried under fear, ego, or self-protection. Construction becomes better when leaders create environments where people can tell the truth early and fix problems together. That protects the trades. That protects the customer. That protects the team. That protects families.

Conclusion: Bring the Problems Up

So here is the challenge. Stop rewarding CYA. Stop tolerating hidden roadblocks. Stop letting people spend their energy protecting appearances instead of protecting flow. Create a culture where problems are brought to the surface quickly, respectfully, and visually. Ask your team this week: “What are we hiding? What are we afraid to say? What problem do we already know about that needs to be on the board?”

Then respond well when they answer. Jason says it clearly: “Bring all problems to the surface.” That is the standard. Not because we love drama. Not because we want negativity. Because problems brought to the surface can be solved. Problems hidden in the dark will keep blocking flow. Find the problems. Fix the problems. Improve the system. Protect the people.

On we go.

Frequently Asked Questions

What does CYA culture mean in construction?

CYA culture means people spend their energy protecting themselves instead of surfacing and solving problems. It often shows up through hidden logs, delayed bad news, vague updates, and reluctance to share real risks with the team.

Why is hiding problems so damaging to flow?

Hidden problems become late problems. Late problems disrupt handoffs, create waiting, cause stacking, increase rework, and force crews into panic. Flow depends on visibility, so anything hidden becomes a threat to the production system.

How should leaders respond when someone brings up a problem?

Leaders should respond with calm curiosity and action. Thank the person for bringing it up, clarify what is known, identify what is needed, assign ownership, and remove the roadblock. The response should teach the team that truth is safe and solutions are expected.

Is surfacing problems the same as complaining?

No. Complaining circles around frustration without ownership. Surfacing problems names the roadblock, makes it visible, and moves toward action. The difference is whether the team is using the information to improve the system.

How can a project start reducing CYA behavior?

Start by making roadblocks visible in daily huddles and planning meetings. Use a shared board or log, assign owners, track due dates, and separate problem finding from blame. Over time, consistent respectful follow-through will build trust and transparency.