Anyone who has spent years working behind the systems that others use without seeing them soon learns to distrust silence. The most dangerous failures rarely announce themselves. They appear as a slowdown of a few milliseconds, an alarm that goes off at the same time every night and that everyone has learnt to ignore, or a restart that "you just do" without anyone remembering why any more.
Those close to these systems develop a precise feeling that is difficult to explain: something is wrong, even though all the indicators are green. There are no words for it yet, and without words you cannot raise a ticket, request action or convince anyone. All that remains is unease.
Organisations live with the same condition. Problems that everyone somehow knows about and no one can articulate. They do not appear in reports, have no budget line and never reach the agenda. Yet they are felt, in the body before they enter speech: a pervasive tension, an inexplicable weariness, an irritation that seems disproportionate to its apparent cause.
These pages look at that moment before the name, and at what it feels like to pass through it.
Knowing without being able to say
Anyone who has spent years alongside a system knows this: knowledge exceeds what we can say. It is a knowledge that lives in the hands, in habit, in an attentiveness trained over thousands of nights. It will not fit into a manual, and for that very reason it struggles to carry weight in a meeting.
Those working on the front line recognise a customer in difficulty from the tone of their first sentence, a team member about to give up from the way they end a call, a fragile release from how quickly it is approved. None of these clues ends up in a report. Yet they are often the first things to change.
This is how a problem without a name first presents itself. Not as a piece of data, but as lived experience: an unease in those close enough to feel it. Emotion, in this sense, is a form of knowledge that precedes language. It arrives before the concept, and is often the only trace available.
When the anomaly becomes normal
Let us return to that nightly alarm. The first time, everyone looks at it. The second, someone writes a note. By the tenth, it is background noise, and no one remembers why it sounds. Each time, nothing happens, and each time ignoring it seems the reasonable choice. There is relief in that habit, too. To stop worrying is a way of regulating an anxiety that has nowhere to go.
This is how deviation becomes normality, one step at a time. The history of technical accidents is full of anomalies seen, recorded and then reclassified as acceptable risk, until the day they were no longer acceptable. The information was there. What was missing was a box in which that information could become a problem.
The same thing happens in organisations, with less commotion. The team where "it has always been like this". The meeting where no one really speaks. The capable person who leaves, and is said to have "found a better offer". These are known facts. They are not named facts. And what is not named does not disappear: it settles as individual frustration, often experienced as a personal limitation rather than the effect of a system.
There is one place where this happens more often: the gap between stated values and everyday work. The walls say collaboration, trust, people first; deadlines, incentives and meetings often harbour something else.
That gap rarely has a name. It is felt as weariness, as irony, as a sentence spoken under one's breath at the coffee machine.
The map comes afterwards
Every organisation looks at itself through its maps: indicators, processes, organisational charts, frameworks. They are useful. But anyone who has kept real systems running knows that the perfect diagram does not survive the first incident in production.
The problem begins when the map becomes the criterion for what exists. Whatever does not fit inside it is filed away as noise, as "perception", as anecdote. And the more sophisticated the map, the more invisible whatever does not appear on it becomes. Sophistication produces confidence, and confidence removes the need to look beyond.
There is another distinction, too: tickets arrive with a title; reality does not. It arrives in confusion, and the first task, the hardest, is to decide what one is looking at. A problem without a name is a problem that no one has yet framed.
Sometimes no one can, because the words themselves are missing. Someone living through an experience feels that something is wrong, but the shared concepts were written by those who do not live through that experience. It is a silent injustice for which the vocabulary is missing. And that absence has a specific emotional cost. Those who cannot say what they are living through end up doubting what they feel, and self-doubt takes the place of doubt about the system.
At the boundaries between teams
Many problems without a name lie between one team and another. Those who sell see the deadlines, those who deliver see the capacity, those who support the customer see the consequences. Everyone has a piece of the truth; no one has the whole picture.
The space between silos belongs to everyone, and therefore to no one. Information arrives there late, incomplete, filtered through the priorities of those passing it on. The unease arising in that void is attributed, each time, to the other department, and so it never becomes a shared problem.
Bridges are needed. Not one or two heroes who take everything upon themselves until they burn out, but people at different levels and in different functions, with a clear mandate to carry what they see from one side to the other. The more diverse the perspectives, the more likely it is that someone will notice what others have learnt not to see.
The signal as information
There is an intermediate stage, the moment when something can already be perceived but cannot yet be said. In organisations it manifests itself through specific signals, if one knows where to look.
A signal of this kind has certain recognisable features. It recurs, even in different forms: the same complaint returns in new words, the same friction moves from one team to another. It is perceived by those on the ground before those looking at the numbers, and often by those at the margins: newcomers, those who belong to a minority, those who do not speak the organisation's dominant language.
These are precisely the people whose perceptions are most easily dismissed as oversensitivity. The signal eludes the available categories, and so tends to be reduced to something already familiar: a problem of character, communication or motivation. And it produces unease rather than data: it expresses itself in sighs, jokes, metaphors, sentences that begin with "I can't explain it, but".
Not every complaint is a signal of this kind. Discontent usually has a clear object: a workload, a decision or a person. It can be stated, even if people do not like hearing it. The nameless signal, by contrast, has no object yet: those who perceive it struggle to point to exactly what is wrong, and the proposed solutions do not touch it. This is perhaps the most reliable sign: when the stated problem is solved and the unease remains, the real problem probably does not yet have a name.
Reorganisations offer a frequent example. The plan is clear, the slides are ready, and after a few weeks come confusion, stress, declining trust. These are often immediately labelled resistance to change; sometimes, instead, they are the signal of something the plan had not anticipated: the emotional dimension of those living through the change.
In technical systems, an anomaly is observed, because that is often where the cause of a larger failure is found. Organisations tend to do the opposite. They treat it as interference to be eliminated, perhaps by applying the model of the moment. Organisations that cannot afford to get things wrong have learnt the opposite: they distrust simplifications and, at critical moments, let those who know the issue make the decisions, not those highest up. They take weak signals seriously.
To recognise is to listen
How, then, do we recognise a problem that does not yet have a name? There is no checklist. There is, rather, an attitude: that of someone who stays close long enough to feel, and open enough not to know in advance what they will feel.
There is a kind of listening that catches only what confirms what one already thinks, and another that allows something to emerge that neither participant knew before. A problem without a name reveals itself only in the second.
But listening is not enough if speaking is unsafe. Where a doubt can lead to punishment or humiliation, problems without a name remain mute. Not because no one feels them, but because saying them costs too much. And it costs more for those with less power.
That is why recognising a problem without a name is a form of attention, what someone called the rarest form of generosity. Those who suffer most often have fewer words to say so, and their signal is easily lost in places accustomed to listening only to those who speak their language.
Who one speaks to matters too. If the only person to whom one can bring a doubt is the same person who assesses one's work, that doubt stays in one's pocket: the space for listening works better when it is separate from the space for judgement. And it matters to give signals a regular place, a recurring moment when persistent problems are spoken aloud, even without a solution. An anomaly recounted once is an anecdote. The same anomaly brought up every week begins to take shape.
Those who support people and teams know one temptation well, always the same: to give something a name too soon. To arrive with a ready-made label, "resistance to change", "leadership problem", "silos", and lay it over another person's experience. It is a reaction that reassures the person proposing it, because it reduces the anxiety of uncertainty, and closes the conversation precisely where it ought to open.
To direct what another person should notice is to influence. To create together the space in which the other person chooses what to notice is to accompany. It asks us to remain for a long time in not knowing, present, without rushing towards the answer: to tolerate ambiguity, recognise our own unease without offloading it onto the other person. An imposed name risks becoming yet another mistaken belief that seems true. A name that emerges from those living with the problem restores their dignity.
Questions that remain open
There is no conclusion, and perhaps there should not be. Instead, a few questions remain. Who has the right to name a problem in an organisation? Those who live with it, those who study it, those with the power to intervene? And what happens when these are not the same people, as is almost always the case? And then: who is left outside a name, even when that name finally arrives?
What do we lose when a problem finally receives a name? To name means to make something open to discussion, but also to simplify. Some words born to describe a real unease have, in just a few years, become fashionable formulas, good for a headline and of little use for understanding. And finally: how many signals are being ignored at this moment because the indicators are green and no one yet knows what to call what they feel? No system holds together thanks to a single expert. It holds together thanks to people talking to one another. Perhaps recognising a problem without a name means this: to stop looking for it in maps, and begin asking People about it.
One last question remains, the one from which it all began. If a problem is felt before we know how to say it, then is thought also born before the name? The conclusion is for the reader to draw. What remains is the problem and these thoughts, dense.