Transparency by Default: How Government Systems Should Evolve

Daniel Falzon (6/1/2026)

Malta has spent a decade growing quickly, and the conversation is finally maturing from whether we grow to how we grow well. There is a phrase gaining ground for this, the innovation economy, and at its best it means something simple: an economy that works better, not just harder. I want to add a practitioner's view to that conversation, because I have spent the last decade building software systems, and the discipline that takes is, I think, exactly what our public sector has been missing.

When you build systems for a living, you learn that good intentions count for very little on their own. What matters is whether the thing actually works for the person using it, whether it holds up under pressure, and whether it can be examined honestly when it does not. Over the years I have come to hold four principles about how systems should be built. They are not technical. They are about seriousness. And they apply just as well to a public service as to a piece of software.

The first is that the end user comes first. Every system exists for the people who use it, and the moment you lose sight of them you start building for the convenience of the institution instead. Too many public services feel designed around the department rather than the citizen, asking people to navigate the organisation's internal logic rather than meeting them where they are. A good system starts from the person and works backwards.

The second is that transparency belongs at the core, not bolted on afterwards. A system you cannot see into is a system you cannot trust, and one that cannot easily be corrected when it drifts. When how a decision was made is visible by default, it can be checked by anyone, and the mere fact that it can be checked tends to keep it honest. Transparency is not a feature you add at the end. It is part of the foundation, or it is not really there at all.

The third is that these systems must be built by the best people we can find, chosen for what they can do rather than who they know. Competence is not a luxury in public works; it is the difference between something that serves the country for a generation and something that has to be dug up and redone within years. Insisting on merit is not elitism. It is respect for the public money and public trust being spent.

The fourth is that building these systems should create room for Maltese businesses and talent to grow. When the public sector invests in capability, it can either send that value abroad by default or use it to strengthen the firms, the engineers and the skills we have at home. A small country gets stronger by building its own competence, not by perpetually importing it. The work itself can be a way of growing the people who will do the next piece of work.

None of this is abstract to me. I see the gap between these principles and the reality every time a road is dug up twice, a public service frustrates the people it is meant to serve, or information that should be open requires a formal request and a long wait. I intend to write about those specifics in the pieces that follow, and to make the case that they are fixable.

Malta is small enough to run well. That is the part we forget. The difference is not money and it is not talent. It is whether we are willing to treat how we build things as something that deserves discipline, transparency, and care.


Ikkuntattjani

Tixtieq tikkollabora fuq proġett jew tiddiskuti xi blog post tiegħi? Tiddejjaqx tikkuntattjani!