The Invisible Movement
A while ago, I wrote that there is a continent of calls for proposals that no one looks at. It wasn't a particularly original metaphor, and perhaps that's why it worked: because it described with a certain precision a real, vast, stratified territory, crossed every day by concrete decisions and economic flows that have much more tangible consequences than many theoretical discussions. A continent made of documents, codes, attachments, procedures, numbers, and above all of languages that do not invite, do not welcome, do not allow easy passage. A public continent that, in the most effective way possible, manages to remain invisible.
Invisibility is almost never a matter of secrecy. It is a matter of friction. If something requires too much time, too much energy, too many skills to be even read, then it ceases to exist for most people. And public calls, as they are distributed and presented, live exactly in this zone: theoretically accessible, practically unmanageable in daily reality. Not because data is lacking, but because a form is missing that makes them observable as a whole.
VistaGare was born from this friction, and at first, it did something very simple, almost elementary: it removed friction. It did not add knowledge, did not produce interpretations, did not promise intelligence. It took data that already existed, that were already public, and arranged them in space, as one does with stars when trying to understand if a figure exists. A map, nothing more. A cartographer's gesture, in the oldest sense of the term: to mark, to orient, to say "there is something here".
But maps, when they really start to work, cease to be just representations. They become tools of perception. They change the way you look. And at that point, something happens that no longer depends only on the tool, but also on who uses it: the points begin to talk to each other.
At first, it is almost imperceptible. The data are still there, seemingly motionless, but if you look at them long enough, you begin to see densities, repetitions, trajectories that were not obvious. It is not yet analysis, it is not yet interpretation. It is something more elementary and at the same time more powerful: it is the transition from the single event to the system.
It is at that moment that it becomes clear that showing is not enough.
Showing is necessary, but it is an incomplete act. It is like opening a window onto a busy street and leaving it to the passerby to decide whether to stop or not. In most cases, they do not stop. Not because they are not interested, but because they are already in a flow, have other things to do, are already elsewhere. And so the problem is no longer visibility, but time.
To inform means to enter into the time of others. It means shifting the relationship between the observer and what happens. You are no longer the one looking for data when you have a free moment; it is the data that, when something relevant happens, make themselves known.
From here, the radar is born.
Not as an additional function, but as a change of logic. You draw an area that makes sense to you — not the administrative one, not the standardized one, but the real, operational, concrete one — and let the system observe on your behalf. There is no rush, no noise, no anxiety of continuous updates that often accompanies digital tools. There is a silent presence, that records, that waits, and that intervenes only when necessary.
The moment a notification arrives is almost trivial. A message, a signal, something that appears while you are doing something else. But that is where the decisive shift occurs: you are no longer the one chasing, you have been reached. And this seemingly minimal inversion has very concrete consequences. Because the problem, in this field, is not access to information. The data is there, and it has been there for a long time. The problem is the timeliness of attention.
Noticing early means being able to choose. Noticing late means, in most cases, having to chase.
The radar does not add data. It returns margin. And the margin, in many jobs, is worth more than the quantity of available information.
Of course, this is still not enough. Because there is a next level, which is the most difficult to build and also the easiest to trivialize: investigation.
Not the spectacular, immediate one, built to produce an effect. But the slow one, that requires staying with the data long enough to see forms emerge. It is not about immediately seeking an explanation, but about letting the occurrences speak. When a behavior repeats, when a dynamic consolidates, when a trajectory stabilizes, then the system ceases to be a sum of events and becomes an observable structure.
It is here that data, alone, are no longer enough, but they continue to be the necessary starting point. Without that foundation, any interpretation risks being just a narrative.
VistaGare today finds itself exactly in this transition. It has ceased to be a simple map and has begun to occupy time with a discreet but constant presence. It does not claim to explain everything, does not draw hasty conclusions, does not turn every signal into a story. Rather, it is learning to remain. To observe without intervening too soon. To let things take shape before being named.
It is not a finished system, and it probably should never be entirely so. Structures that are too closed, too perfect, too definitive, end up ceasing to see precisely at the moment they declare they have understood. Here, however, there is still space, and this space is part of the value.
Space to make mistakes, to correct, to change direction. But above all, space to look better.
Because the point, in the end, is not to build another tool. It is to change the way something that has always been in plain sight is observed.
The continent of calls for proposals is not new. It did not just come into being. It has always been there, moving pieces of concrete reality while elsewhere other things were being discussed.
The difference, perhaps, is that now it has started to return signals.
And when you stop searching, and something starts to find you, it becomes harder to pretend not to see.
Is your project stuck at a technical hurdle?
Book 15 minutes