Where the work begins

Not every problem is a structural gap. We start by finding out which one you have.

Every ESFI engagement begins with the same question: what structural gap does this close, and why has no existing institution closed it?

The second half of that question matters as much as the first. Europe does not lack institutions, programmes or funding. When a problem persists despite all three, the reason is rarely that nobody has noticed it. More often, the mechanism that would address it does not exist, or exists in pieces that no one is responsible for connecting.

That is the kind of gap we work on.

Symptoms and structural gaps

Most conversations start with a symptom. A programme that delivered its outputs but not its purpose. A system that works until something needs to change. A capability that exists on paper but not in practice. A risk everyone can describe and nobody owns.

Symptoms are real, and they are where the work starts. They are not where it ends. The first task is to understand what produces the symptom.

Sometimes the answer is simple: not enough people, not enough budget, not enough time. Those are real problems, but they are not structural gaps, and they are usually better solved by the institution itself, with more of what it already has.

A structural gap looks different. It tends to appear in the space between things: between the organisation that holds responsibility and the one that holds the capability; between the strategy that was adopted and the operating model that would carry it out; between a function that crosses a border and the authorities on either side of it. It persists because closing it would require an existing institution to step outside what it was built to do.

We start with the function

We do not start with the organisation chart. We start with the function that is supposed to happen, and trace where responsibility, capability and execution separate.

In a first conversation, the questions we typically ask are:

What is supposed to happen, and what actually happens?
Who is responsible for it, and who is actually able to do it?
Where does the function depend on something no one here controls?
What has already been tried, and why did it not hold?
What would be different if the gap were closed, and how would anyone know?

The last question is the most important. If nobody can say what closing the gap would change, the work cannot be measured and should not start yet.

When we say no

Not every problem needs us, and we would rather say so early.

If an existing institution can close the gap with its own mandate and resources, we say that, and where we can, we help it do so. If the problem is one of capacity rather than structure, we say that too. If the gap is real but the conditions to close it do not yet exist, such as the right partner, the legal basis or the institutional will, we say what those conditions are, rather than starting work that cannot hold.

This is not modesty. It is how we protect the work that does start. An engagement built on a misdiagnosis will fail however well it is executed.

We do not replace what exists

ESFI does not compete with existing institutions or try to take over their responsibilities. We build what they cannot build without ceasing to be what they are.

That usually means working alongside them: connecting pieces that belong to different organisations, designing an operating model that fits real legal and institutional boundaries, or building a capability that one institution needs and no single institution can create alone.

Our mandate comes from that absence. When the gap is closed, the mandate for that piece of work is fulfilled, and the capability belongs to the institutions that carry it forward.

What happens next

When a gap is confirmed and the conditions are in place, the work moves into The sequence: understanding the gap well enough to design for it, designing something that works under real constraints, and building it until it runs without us.