Most companies are good at solving problems. They have capable people, real budgets, and whole teams whose job is to fix what's broken. If you point them at a clearly defined problem with a deadline, they will usually solve it. So it's strange how many expensive problems survive for years inside otherwise well-run companies. It turns out that fixing a problem is rarely the hard part, seeing it in the first place is.
A problem you can name clearly is already halfway to fixed because your organization knows how to mobilize against a named problem. But the ones that drain money year after year are the ones nobody has named yet, because nobody noticed there was anything to name.
The genuinely hard part of improvement is figuring out what the actual problem is. Once you've done that, solving it is often the straightforward part. Yet almost all of a company's training, recognition, and practice goes to the solving. People get coached on how to fix things, praised for fixing things, and promoted for fixing things.
But almost no one gets trained to look at work that is running along just fine and ask whether it should be happening at all. There is no course for it, no metric that rewards it, and little practice at it. So the company ends up with a great deal of skill pointed at solving and almost none pointed at seeing, even though seeing is where the bigger opportunities are hiding.
A problem is easy to spot when something is visibly broken. The difficulty comes when a problem is wrapped inside something that appears to be working, because then there is nothing to trip an alarm.
Think about a company that runs a busy call center. Over time, the team gets genuinely good at handling angry customers. They learn the scripts, calm people down, resolve the complaint and move to the next call. By any local measure, the operation is healthy. What almost never happens is someone stepping back to ask the harder question: what’s going on? Why are all these customers angry in the first place? The skill the team built at managing the symptom is the very thing that keeps anyone from questioning the cause. The better they get at handling the calls, the more normal the flood of calls comes to feel.
That is how the most expensive problems hide. They don't really look like problems, they look like a process that is being handled well.
You might expect the best-run companies to be the best at catching these hidden problems. Often it's the opposite, and the reason is almost reassuring.
When you give capable people a task, their instinct is to do it as well as possible. They streamline it, tighten it, and get efficient at it. That's a good instinct, but it has a side effect: the harder someone works to do a task well, the more they take for granted that the task should be done at all. All their attention goes into doing it better, and none goes into asking whether it needs doing in the first place.
The people closest to the work feel this most. They run the same process every day, so anything that might look strange to an outsider feels completely normal to them. The longer something has been done a certain way, the more invisible it becomes to the people doing it.
None of this is a sign of a weak operation but a side effect of a strong one, full of capable people quietly optimizing things nobody thought to question.
The frustrating part is that you can't fix this just by deciding to pay closer attention. If a problem already feels normal to you, then by definition you've stopped noticing it, and telling yourself to look harder won't bring it back into view. You'll look right past it again, only with more effort this time.
Asking your team to study the process more closely doesn't help either, because they're the ones it feels normal to. To see something that has become invisible, you need a fresh set of eyes, someone who hasn't done it a hundred times and still finds it strange.
Here's the good news: in most companies, someone can still see it. It tends to be the people who haven't been doing it long enough to accept it, or who sit far enough from the decision that they never got the official reason for why it's done this way.
It could be the new hire who asks "why do we do it like this?" in their first week. Or the person on the line who has always thought "this doesn't make sense" but assumed someone above them must have a reason.
They can see what you can't because the process never became invisible to them. They haven't run it ten thousand times, so it still looks strange, and strange is exactly what you need someone to notice.
The catch is that this person almost never walks into a leader's office to say so. The observation feels too small to bother anyone with, or not their place to raise, or like something everyone above them surely already knows. So the one view that could expose the problem stays right where it is, unspoken, while the company keeps carefully optimizing around a question nobody has thought to ask.
This is the gap Tell Jules is built to close. Your company already knows how to solve problems, what it's been missing is a reliable way to find the ones hiding in plain sight, and the people most likely to spot those are the ones closest to the work.
Tell Jules is how you hear from them at scale.
It has a roughly ten-minute conversation with your chosen people, at every level and not just management, in virtually any language, and at their own convenience.
Because it's a real conversation and it asks follow-up questions, it draws out the observations that never surface on their own. The kind of thing someone has quietly wondered for years, like why a step in their process still exists when the reason for it disappeared long ago, but has never mentioned because it felt too small to bring up or like something everyone must already know.
Tell Jules gives you the seeing, not the solving. It surfaces the problems your people have noticed and stopped mentioning, and hands them to you in their own words. It doesn't tell you what to fix first, and it isn't meant to, because that's the part your team is already good at. It closes the gap this whole article has been about.
You were never short on the ability to fix things, you just need a clear view of what needs fixing, and that is exactly what Tell Jules gives you.
Your people can already see what you can't. The only thing missing is a way to ask them.
Run a free trial with a team of ~50 employees, surface the hidden operational problems, and let your company do what it already does best: fix them.
Finding a problem is harder because most organizations are trained and rewarded for solving, not for noticing. Companies have people, budgets, and long practice aimed at fixing clearly defined problems, so once a problem is named it usually gets handled. Almost no one is trained to spot a problem in the first place, especially when the work looks like it's running fine, so unnamed problems can quietly survive for years even though the company could have fixed them easily.
Companies miss obvious inefficiencies because of normalization: once people do something the same way long enough, they stop seeing it as a choice and it starts to feel like just how things are done. A process that looks strange to an outsider feels completely normal to the people running it every day. That's why an inefficiency can sit in plain sight for years without anyone questioning it.
The most reliable way for leaders to find hidden problems is to ask the people closest to the work what they've stopped questioning. Those employees are the most likely to have noticed something was off before they got used to it. Because the "why do we even do it this way" thoughts rarely feel big enough to escalate, leaders need to create a direct, low-pressure way for people to share them, rather than waiting for the observations to come up on their own.
Yes. A team can become expert at handling the symptoms of a problem without anyone addressing the cause. A call center that gets very good at calming angry customers, for example, may never ask why customers are angry in the first place. Skill at managing a problem can actually hide it, because the process looks healthy from the outside while the underlying issue keeps costing money.
Not easily, because failing to notice is exactly what normalization means. Telling yourself to look harder usually points you at the same blind spot, and asking the people who already accepted the process as normal tends to return that same blind spot. Seeing what has become invisible generally takes a fresh perspective, someone who hasn't been doing it long enough to treat it as normal, which is why new people and the employees closest to the work are so valuable for spotting it.