Why Your Team Can’t See the Problem

I’ve worked on projects that had been stuck for months — sometimes years — where the team was completely unable to see the signals of the real problem staring them in the face. It’s like they were wearing blinders. Some kind of mental blind spot that filters out the very information they need to move forward.

It used to surprise me how pervasive this is. It doesn’t surprise me anymore.

It’s Not Stupidity

Let me be clear about something: these are smart, experienced, hardworking people. The teams I’m talking about include senior engineers, product managers with decades of experience, directors who’ve shipped products used by millions. This is not about intelligence.

The blindness isn’t personal. It’s structural. When you’ve been inside a problem long enough, you lose the ability to see it from the outside. You’ve internalized so many assumptions that you can’t distinguish between “things that are true” and “things we’ve always assumed.” The context that was supposed to help you understand the problem has become the thing preventing you from seeing it.

The Communication Gap

The first reason teams stay blind is communication. Not the touchy-feely “we need to communicate better” kind. The structural kind.

Most corporate leaders are focused on revenue growth, cost reduction, or whatever signals will advance their careers. That’s not a criticism — it’s their job. The system they operate within rewards those metrics and punishes everything else.

If you walk into a leadership meeting and say “our users are struggling with the building modeling workflow,” you’ll get a polite nod and a redirect to the current priorities. If you walk in and say “we’re losing three deals a quarter because onboarding takes too long and competitors are offering a faster path,” you’ll get a meeting on the calendar before you leave the room.

Same problem. Different language. The first version describes user pain. The second describes business impact. Most UX practitioners are trained to speak the first language. Leadership only hears the second. Bridging that gap is painful — it feels like bending yourself backwards — but it’s necessary.

The Profile Gap

The second reason is deeper and more structural. It’s a combination of psychological profile differences and the systems people operate within.

People who thrive in large corporate environments tend to be risk-averse and conscientious. They follow the plan. They stay focused. They color inside the lines. Large corporations are magnets for this type of conservative thinking, and for good reason: that’s what keeps complex organizations running. You can’t operate a global supply chain or a regulated financial system with people who change direction every time they have a new idea.

But this strength creates a blind spot. The same discipline that keeps the trains running on time also filters out signals that don’t fit the plan. When someone raises a problem that wasn’t anticipated, the system’s first instinct is to suppress it. Not maliciously — structurally. The budget is set. The roadmap is committed. The team is allocated. There is literally no room in the system for “we’re solving the wrong problem.”

Two Kinds of Minds

Startups are magnets for the opposite mindset: exploratory, lateral, willing to blow things up and start over. Society needs both. I’ve heard the expression “liberals start companies, conservatives run them,” and I think there’s a lot of truth in that.

When I went to my first hackathon, I realized that everybody there was like me. After years of friction in corporate environments — being told to stay in my lane, to follow the plan, to stop asking why — I’d finally found my tribe. A room full of people who saw the same patterns I did, who got excited about the same kinds of problems, who didn’t need to be convinced that looking at things differently was valuable.

The thing is, neither mindset is complete on its own. The exploratory mind finds the right problem but struggles to ship. The disciplined mind ships reliably but sometimes ships the wrong thing. The best outcomes happen when both mindsets work together — but that requires mutual respect, and it’s surprisingly rare.

Ask Forgiveness, Not Permission

In most corporate environments, you’re expected to stay in your lane. For people like me, that’s almost physically impossible. It’s like a splinter in your mind that won’t leave you alone. I can pretend to stay in my lane for a while, but at some point I have to act, especially when it’s become painfully obvious that we’re stuck spinning our wheels.

So I don’t wait long. I start looking for opportunities to run contextual inquiry sessions with end users on my own. I don’t ask for permission. I don’t submit a research proposal. I just start talking to people.

The hard part comes after. Once you’ve discovered the right problem to solve, you face the arduous task of convincing the leadership of the company you’re working for. I’ve spent anywhere from three months to two years on this part alone. It doesn’t always work. Sometimes you get laid off in the next round of restructuring before anyone listens.

What Keeps Me Up at Night

I’ve spent most of my career pointing out other people’s blind spots. I’ve walked into organizations and seen the problem in the first week that the team couldn’t see in two years. It’s not a special power — it’s just being an outsider. Fresh eyes.

But here’s what keeps me up at night: what are my own blind spots? If I’m so good at seeing what other teams can’t see, what am I missing in my own work? What assumptions have I internalized so deeply that I can’t distinguish them from truth?

I don’t have a good answer for that. But I think the question itself is important. The moment you stop asking it is the moment your blind spots start running the show.

What You Can Do About It

If you suspect your team is stuck in a blind spot, here’s what I’d suggest:

• Bring in an outsider. Not because they’re smarter, but because they don’t share your blind spots. A consultant, an advisor, a new hire — anyone who hasn’t been inside the problem long enough to stop seeing it.
• Run contextual inquiry with real users. Go where they work. Watch what they do. Ask why. You will be surprised — probably within the first session.
• Question every assumption that’s older than six months. If the answer to “why do we do it this way?” is “we’ve always done it this way,” that’s a blind spot.
• When someone shows you evidence that contradicts your plan — listen. Your first instinct will be to explain why they’re wrong. Fight that instinct.

The blind spots don’t go away. They can’t. They’re a feature of how humans work in organizations, not a bug. The best you can do is build systems and habits that make them harder to ignore.