Lean Onboarding Series – Problems are not a Problem

Problems Are Not a Problem

Here’s the deal. Every practice covered throughout this onboarding series exists for one single underlying purpose, helping you genuinely see problems you could not otherwise see. 3S and 5S reveal the eight wastes hiding in a cluttered, disorganized space. Seeing those wastes clearly lets you recognize waste, overburden, and unevenness as they actually show up. And recognizing those patterns is exactly what lets you find and remove real roadblocks well before they ever reach the work. That is the entire sequence, each step building directly on the one before it.

None of that sequence matters, though, if someone is psychologically unwilling to actually find a problem in the first place. That resistance is worth understanding directly, because it is the one obstacle none of these practical tools can fix on their own.

Why Some People Cannot Bring Themselves to Find a Problem

People will not genuinely hunt for problems if finding one threatens how they see themselves. Think about anyone who has built a strong personal identity around a very specific, recognizable image, a particular way of carrying themselves, a reputation they have worked hard to maintain. Once someone attaches their sense of self to always getting it right, to never making a mistake, to being the person who simply does not have problems, actively searching for a problem becomes something their own identity resists.

If someone in construction genuinely identifies as a person who never makes mistakes, who is always perfect, they will not go looking for problems to eliminate ahead of time. Which means those problems will eventually find them instead, usually at a far worse moment than if they had simply been caught early.

This is a genuinely subtle trap because it often looks like confidence from the outside. A superintendent who projects total certainty and never admits a gap in their own knowledge can seem impressive in the moment, right up until a problem they never went looking for finally surfaces on its own, usually at the worst possible time to discover it.

Watch for these signs someone has quietly attached their own identity to appearing problem-free, rather than to genuinely finding and fixing real problems.

• Defensiveness or visible discomfort whenever a genuine mistake or issue gets raised directly, rather than curiosity about how to fix it.
• A pattern of minimizing or quietly covering small issues rather than surfacing them openly for the team to address.
• Reluctance to admit uncertainty or ask for help, treating either one as a threat to a carefully maintained reputation.

Why We Have to Get Comfortable With This Idea

We have to genuinely internalize something that sounds almost contradictory at first. Problems are not a problem. The only real problem is believing, or pretending, that no problems actually exist on your project, and therefore never going out to find and remove them ahead of time.

The actual measure of success on a real construction project is not the absence of problems. If a project manager, superintendent, foreman, and crew are all genuinely doing their jobs well, they will find dozens of real problems every single day, and they will actively work to fix every one of them. A project without problems simply does not exist. It never has.

That reframe matters because it changes what a genuinely well run jobsite should actually look like day to day. It is not a site where nothing ever goes wrong. It is a site where problems get surfaced constantly, openly, and in small enough form that fixing them barely registers as a disruption at all.

What It Actually Means When a Project Looks Problem-Free

Here is the part worth sitting with directly. The only time a project appears to have no problems is when those problems are being hidden rather than genuinely resolved. That hidden problem does not disappear. It manifests eventually, as someone getting hurt, as a real quality defect discovered later, as an issue quietly passed along to the owner instead of being fixed, or as something else genuinely catastrophic further down the line.

Watch for these signs a project that looks remarkably smooth on the surface may actually be hiding real problems rather than genuinely preventing them.

• Status updates and reports that consistently sound positive with no real issues ever mentioned, regardless of how complex the work genuinely is.
• A team reluctant to bring up a concern directly, preferring to handle it quietly rather than surface it to the broader group.
• Problems that eventually surface as a safety incident, a quality defect, or an owner complaint, rather than being caught and resolved earlier in a much smaller form.

Why the Best People Are the Ones Who Find the Most Problems

The best workers, the best foremen, the best superintendents, and the best project managers are not the ones who appear flawlessly perfect. That standard simply does not exist in reality. The best people in this industry are specifically the ones who consistently find, identify, and remove real problems ahead of time, treating that discovery as genuine success rather than something to hide or feel embarrassed about.

That distinction is worth repeating to anyone early in their career who assumes the most respected people around them simply never struggle with anything. The opposite is usually true. The people worth genuinely learning from are the ones who have gotten remarkably comfortable admitting what is not yet working, precisely because that comfort is what lets them actually fix it before it becomes something much larger.

Building This Mindset Into Your Own Team

None of this requires pretending problems are enjoyable or that finding one feels good in the moment. It requires genuinely decoupling your own sense of identity and self-worth from the illusion of being problem-free, and reattaching it instead to how consistently and how early you actually find and fix real problems.

That shift takes real, deliberate practice, especially for anyone who has spent years building a reputation around never being wrong. Starting small, admitting one genuine uncertainty out loud, raising one real concern before it becomes urgent, tends to build that muscle far more reliably than trying to overhaul an entire identity all at once.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build a genuine culture where surfacing a real problem is treated as a win worth celebrating, rather than something anyone needs to hide to protect their own reputation.

So here is the challenge. Notice the next time you, or someone on your team, hesitates to admit a real problem exists. Ask honestly whether that hesitation comes from genuine uncertainty about the facts, or from a quiet fear that admitting the problem might damage how others see them. That honest answer is exactly where this entire mindset shift actually has to begin.

Jason Schroeder said it plainly: “Problems are not a problem.” Learn to see finding one as a genuine win, and the rest of this entire onboarding series finally has somewhere real to land.

On we go.

FAQ

Why does the article argue that a project with no visible problems is actually a warning sign rather than a good sign?

Because every real construction project involves genuine complexity, and complexity reliably produces real problems along the way. A project that appears to have none is far more likely hiding issues rather than genuinely preventing them, and those hidden issues tend to resurface later in a more serious and costly form, like a safety incident or a quality defect.

Why does personal identity matter so much to whether someone is willing to find and report a real problem?

Because someone who has built their self-image around being flawless or always correct experiences admitting a problem as a genuine threat to that identity, not simply as a neutral observation about the work. Decoupling self-worth from the appearance of perfection, and reattaching it to the habit of finding and fixing real problems early, removes that psychological barrier entirely.

How does this concept connect to the earlier practices covered in this onboarding series, like 5S and finding roadblocks?

Each of those practices exists specifically to help someone see a real problem clearly, whether that is clutter hiding waste, overburden disrupting a crew’s pace, or a roadblock sitting further down the schedule. None of those practices produce genuine value if the person using them is unwilling to actually act on what they find, which is exactly why this mindset shift has to come before or alongside the practical tools themselves.

Why does the article treat finding dozens of problems daily as a sign of a well run project rather than a poorly run one?

Because genuinely identifying and fixing problems early is precisely what prevents them from accumulating into something far more serious later. A team actively surfacing and resolving small issues every day is functioning exactly as it should, while a team that appears to encounter no problems at all is more likely suppressing or overlooking issues that will eventually surface in a much more damaging way.